Torsten Kaiser wrote:
> On 11/2/07, Stefan Richter <[email protected]> wrote:
>> To which extent do you need IEEE 1394 drivers?
>
> Using eth1394 as primary network connection on this computer.
> So switching to the new stack is currently not an option,
That's right.
> Looking that calltrace upwards, it seems replacing the
> memset(dma->sglist,...) with sg_init_table(...) would fix the BUG_ON()
> as that inits the SG_MAGIC.
Yes, this should be the first thing to be fixed.
> But I do not trust myself to fixing all
> the iterators correctly to convert this completely to the new API.
Since ieee1394 doesn't create chained s/g lists, we might even get away
with ieee1394's existing iterators.
(The other place where the 1394 stack deals with s/g lists is sbp2 where
we have to deal with what comes from the SCSI stack or the block layer.
But sbp2's s/g list handling is entirely unrelated to ieee1394's own
code for isochronous I/O and async streams, which eth1394 needs and
caused the bug.)
--
Stefan Richter
-=====-=-=== =-== ---=-
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
