Recent changes to feature-requests

GP2Lynx TSB12LV32 driver

Stefan Richter — Wed, 02 Mar 2005 16:03:51 -0000

driver is available as a patch against linux1394.org's
config-rom-2.4 branch:
http://marc.theaimsgroup.com/?m=110977516121805

GUID Override

Anonymous — Mon, 22 Mar 2004 20:57:59 -0000

Some manufacturers of motherboard and PCI-based
firewire hosts are using the same GUID number. This
causes problems when using shared firewire disk drives
for clusters.

It would be nice to be able to set the GUID when loading
the module with an option.

Data backup

Unstable Geek — Thu, 09 Oct 2003 05:03:35 -0000

Is there any work to implement data backup over 1394?

The Mac has DV Backup (http://www.coolatoola.com/)
which looks very promising, and about the only thing I can
find for linux is Backfire (http://www.ajwm.net/backfire/)
which looks to be dead, although it did make it into
sourceforge (http://sourceforge.net/projects/backfire/)

There is a window$ ver$ion (http://www.dvstreamer.com/)

Just wonderin'

Documentation

Anonymous — Fri, 31 Jan 2003 19:33:48 -0000

Please extend documentation on installation, dependencies,
driver structure and most of all trouble shooting.
It is nearly
impossible to find the cause of an error by inspecting logs or the
project home page.
I know you work voluntarily and I am
thankful. But it is frustrating to stumble from one error to another
without being able to help myself.

Thank you
again,

Tobias

linux as an sbp2 device

Adam Csiki — Fri, 20 Dec 2002 10:07:28 -0000

Hi,

Is it possible that a linux may behave as an sbp2 device
(offering one of it's block devices e.g. an md device)?

Is anyone there dealing with this problem?

Thx
Adam

ignore inactive link

Dan Dennedy — Sat, 14 Dec 2002 18:40:58 -0000

On 27 Oct, Stefan Richter wrote:
> Should the added MODULE_PARM go into nodemgr.c?
I shifted it from ieee1394_core.c to nodemgr.c after
spotting
another MODULE_PARM in csr.c.
--
Stefan Richter
-=====-=--=- =-=- ==-==
http://arcgraph.de/sr/

Index: ./nodemgr.c

--- ./nodemgr.c
+++ ./.svn/tmp/nodemgr.c.62348.00001.tmp Sun Oct 27
02:51:20 2002
@@ -20,6 +20,7 @@
#ifdef CONFIG_PROC_FS
#include <linux/proc_fs.h>
#endif
+#include <linux/module.h>
#include <asm/atomic.h>
#include <asm/byteorder.h>

@@ -32,6 +33,14 @@
#include "csr.h"
#include "nodemgr.h"

+/*
+ * Probe nodes by nodemgr even if their link layers
are not active.
+ * Some SBP-2 devices seem to erroneously report an
inactive link layer.
+ */
+MODULE_PARM(ignore_inactive_link, "i");
+MODULE_PARM_DESC(ignore_inactive_link, "Probe nodes
with inactive link layers (default =
0).");
+static int ignore_inactive_link = 0;
+
#ifdef CONFIG_IEEE1394_OUI_DB
struct oui_list_struct {
int oui;
@@ -1192,8 +1201,14 @@
continue;

if (!sid->link_active) {
- nodeid++;
- continue;
+#ifdef CONFIG_IEEE1394_VERBOSEDEBUG
+ HPSB_DEBUG("link inactive at node " NODE_BUS_FMT ,
+ NODE_BUS_ARGS(nodeid));
+#endif
+ if (!ignore_inactive_link) {
+ nodeid++;
+ continue;
+ }
}

nodemgr_node_probe_one(host, nodeid++, generation);

sbp2 hotplug patch

Dan Dennedy — Thu, 12 Dec 2002 21:58:13 -0000

As has been reported a few times on the linux1394-devel
mailing
list, hotplugging firewire drives only sortof works. A
recent
posting to the list rehashing the problems

http://sourceforge.net/mailarchive/forum.php?thread_id=1151203&forum_id=5389

reminded me of my old partial fix for this problem that was
sitting unfinished. So last night I polished it up,
fixed the
bugs, and it is now working perfectly for me.

Without this patch, hotplugging firewire drives will
register the
drives with the 1394 layers, but will not register them
with the
SCSI subsystem. Unplugging firewire drives leaves the (now
absent) drives still registered with the SCSI
subsystem. As you
can imagine, the current situation sucks, and makes
hotplugging
firewire drives mostly useless. To make things behave
correctly,
one needs to manually add/remove SBP-2 devices using a
shell script
(http://www.garloff.de/kurt/linux/rescan-scsi-bus.sh) that
pokes at /proc/scsi/scsi by scanning though all your
SCSI hosts
and then does things like
echo "scsi remove-single-device 0 0 0 0" >
/proc/scsi/scsi
for each and every SCSI device on your system. I don't
consider
such things safe or desirable at all.

It seemed to me that since the kernel had all the
information to
do the Right Thing(tm), it made sense to connect the
remove-single-device and add-single-device functionality of
/proc/scsi/scsi together with the sbp2 driver so the Right
Thing(tm) could happen automagically.

With my patch applied, one can now plug in firewire
drives and
they will all be automagically registered with the SCSI
subsystem. When one unplugs SBP-2 devices, they will be
automagically unregistered from the SCSI subsystem.

When I posted my earlier effort to the linux1394-devel
list:

http://sourceforge.net/mailarchive/forum.php?thread_id=949390&forum_id=5389
it was decided that the change to the SCSI subsystem
needed to
expose scsi_add_single_device() and
scsi_remove_single_device()
was not desirable. I'll leave the decision on that to
others.

For the moment, this patch is works nicely for me and
makes using
firewire drives a much nicer experience.

Have fun,

-Erik

--
Erik B. Andersen
http://codepoet-consulting.com/
--This message was written using 73% post-consumer
electrons--

Support for formac studio dv/tv

Anonymous — Sat, 28 Sep 2002 08:49:29 -0000

Support for this device would be truly awesome,
allowing any linux 1394 machine to have the equivalent
of a full capture suite.

http://www.formac.com/p_bin/?cid=solutions_converters_studiodvtv

redhat boot1394.img

Anonymous — Tue, 15 May 2001 16:59:22 -0000

Sorry I could not login this evening...

How could we go about asking RedHat to provide on their
ftp server a boot image disk with ieee1394, ohci1394
and spb2 modules instead of adaptec scsi ones?

I have studied the possibility of making one myself but
the init process to get into the second stage of the
installer is stopping me.

I think that by providing such a disk and showing that
ieee1394 support exists for Linux would also be a very
smart marketing move by RedHat.

Last of all with us as testers the time involved would
be trivial.

Any sugestions on how to contact the right people?

Cheers

Tony Grant

Sony Proprietary Datasheet wanted

Anonymous — Fri, 13 Apr 2001 12:17:21 -0000

If anyone has a software API datasheet for the Sony-
proprietary Firewire chipset, please let me know.
mailto:linux-dsl@home.com