70093cfde8
Until now, ieee1394 put an IP-over-1394 capability entry into each new host's config ROM. As soon as the controller was initialized --- i.e. right after modprobe ohci1394 --- this entry triggered a hotplug event which typically caused auto-loading of eth1394. This irritated or annoyed many users and distributors. Of course they could blacklist eth1394, but then ieee1394 wrongly advertized IP-over- 1394 capability to the FireWire bus. Therefore - remove the offending kernel config option IEEE1394_CONFIG_ROM_IP1394, - let eth1394 add the ROM entry by itself, i.e. only after eth1394 was loaded. This fixes http://bugzilla.kernel.org/show_bug.cgi?id=7793 . To emulate the behaviour of older kernels, simply add the following to to /etc/modprobe.conf: install ohci1394 /sbin/modprobe eth1394; \ /sbin/modprobe --ignore-install ohci1394 Note, autoloading of eth1394 when an _external_ IP-over-1394 capable device is discovered is _not_ affected by this patch. Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de> |
||
---|---|---|
.. | ||
config_roms.c | ||
config_roms.h | ||
csr1212.c | ||
csr1212.h | ||
csr.c | ||
csr.h | ||
dma.c | ||
dma.h | ||
dv1394-private.h | ||
dv1394.c | ||
dv1394.h | ||
eth1394.c | ||
eth1394.h | ||
highlevel.c | ||
highlevel.h | ||
hosts.c | ||
hosts.h | ||
ieee1394_core.c | ||
ieee1394_core.h | ||
ieee1394_hotplug.h | ||
ieee1394_transactions.c | ||
ieee1394_transactions.h | ||
ieee1394_types.h | ||
ieee1394-ioctl.h | ||
ieee1394.h | ||
iso.c | ||
iso.h | ||
Kconfig | ||
Makefile | ||
nodemgr.c | ||
nodemgr.h | ||
ohci1394.c | ||
ohci1394.h | ||
pcilynx.c | ||
pcilynx.h | ||
raw1394-private.h | ||
raw1394.c | ||
raw1394.h | ||
sbp2.c | ||
sbp2.h | ||
video1394.c | ||
video1394.h |