Re: Linux 1394 somewhat unfriendly during boot?

[Manfred W. <e95...@st...>]

Sebastien Rougeaux wrote:
> I have not tested the ohci driver directly linked into the kernel, and so
> I would not recommend using this option yet.

1) I do not use ohci, but pcilynx.

2) I meanwhile compiled the stuff as modules, and the problem remains.
But I have now the possiblity to avoid the hang-ups of my machine by
unloading the 1394-modules before generating a bus reset und insmoding
them afterwards -> so it is definitely a bug in the driver.
Concerning the other thing I mentioned, the several bus resets on
bootup, I have not checked this yet. So I cannot tell you if it depends
on whether the driver is in the kernel or in a module. Maybe I check
this on Tuesday or Thursday (if I have time).

3) If it is not recommended to put the driver into the kernel, but
rather to put it into a module, this should be mentioned in the
documentation (/usr/src/linux/Documentation/Configure.help). If one does
not intend to update the driver more frequently than the driver, it
makes much sense to put it into the kernel, because then you do not have
to bother around with the insmod's. So if it is depreciated to compile
it into the kernel, there should be an explicit warning. BTW: Is there
any difference between kernel and module besides the moment, when the
code is loaded and activated?

> Yes, it is very likely to be sofware related. The linux1394 subsystem is
> still very much alpha quality, that is why it is tagged as experimental
> in the kernel configuration process.

ack.

Manfred Weihs