On 29/07/07 10:50, maximilian attems wrote: > so your bugreport needs to reach upstream, > so that your chipset regains support on the new stack.
http://wiki.linux1394.org/ToDo states: "Come up with a quirk fix for NForce2. The person to do so will most certainly require direct access to this hardware. Note, the NForce2 workaround in ohci1394 is unacceptable by today's standards as it involves busy-waiting in the interrupt handler. Either we find something better for firewire-ohci, or NForce2 remains unsupported in firewire-ohci." This means that we can't expect any nforce2 support for the foreseeable future. In light of this, I'd hope the Debian Kernel Team would take the remark by Alexander E. Patrakov into consideration: On 09/09/07 10:50, Alexander E. Patrakov wrote: > http://wiki.linux1394.org/JujuMigration clearly says: > >> Regarding Linux 2.6.22 and 2.6.23, the best advice to Linux distributors >> (kernel packagers) as well as to regular users is: Build only the old IEEE >> 1394 drivers. > > The same page contains blacklisting instructions for those who want to > give the users the opportunity to choose between the two stacks. Please > implement the instructions. It would be nice if we could activate (by blacklist) the old stack for only those devices that used to work but not anymore, and the new stack for the rest. Thanks, Mourad DC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
