[lkml]   [2003]   [Apr]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: The IEEE-1394 saga continued... [ was: IEEE-1394 problem on init ]
On Sat, Apr 26, 2003 at 10:29:57AM +0200, Stelian Pop wrote:
> On Wed, Apr 23, 2003 at 10:42:58PM +0200, Stelian Pop wrote:
> > > I haven't been able to figure out how to get the scsi
> > > subsystem to remove devices in this condition:
> >
> > Well, hopefully someone here will direct you towards the
> > correct solution before 2.4.21 gets final... Firewire devices
> > tend to be plugged / unplugged quite often.
> This was three days ago. Today, without *any* notice (like posting
> a patch on lkml for example, as I already suggested it), I saw a
> new IEEE1394 patch was checked in into Marcelo's tree.
> As usual, the patch was quite big, in Ben's own words "virtualy
> bloated [...] by format changes". Why he continues to submit patches
> like that one in -rc stage is beyond my understanding.
> And guess what ? The new patch broke (again) my setup. When I plug
> in my iPod, the scsi layer does not see it anymore.

Good lord would you calm down.

Run the script floating around. Out own website
describes having to use this for 2.4 kernels. It was either leave sbp2
oopsing, or rewrite the load logic so that there was no way for left
over scsi cruft. The side affect is that the only hot-plug situation
ieee1394 had in 2.4 is gone.

Before, loading sbp2 before loading ohci1394 gave the same affect. Now,
loading sbp2 before ohci1394 also requires running
Blame the scsi layer, not me.

Debian -
Linux 1394 -
Subversion -
Deqo -
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:35    [W:0.066 / U:5.768 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site