| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <1191912184.6355.66.camel@pasglop> Date: Tue, 09 Oct 2007 16:43:04 +1000 From: Benjamin Herrenschmidt <benh@...nel.crashing.org> To: David Brownell <david-b@...bell.net> Cc: greg@...ah.com, davem@...emloft.net, linux-usb-users@...ts.sourceforge.net, linux-kernel@...r.kernel.org Subject: Re: OHCI root_port_reset() deadly loop... On Mon, 2007-10-08 at 22:00 -0700, David Brownell wrote: > > > > The old /etc/hotplug/usb.rc script made sure to load those modules > > > > in the correct order: EHCI first. > > > > > > I expected to find something cute attempting to handle this under > > > /etc/udev, I have failed so far :-) > > > > No, nothing cute in udev itself, but it seems that all distros that I > > know of have a "load these modules now" type setting in their init > > scripts that can be used here. > > > > I can't think of a way to enforce this load order on the modules > > themselves due to the fact that OHCI might not even be needed for EHCI > > devices on UHCI (Intel) based chipsets :( > > Assuming PCI is present, /sys/bus/pci/devices/*/class can tell > if EHCI is present (0x0c0320) ... if so, load that driver. > Then repeat for OHCI (0x0c0310) and UHCI (0x0c0300). That will not work for all of the non-PCI implementations though. Ben. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists