Am 01.08.2011 17:23, schrieb Dave Reisner: > It's also not recommended by upstream, as per modprobe.conf(5). We > shouldn't make any guarantees about module load order. What's the > problem we're trying to solve with this juggling? Is this bandaiding and > issue that should be taken upstream to the kernel folk? Or, is this some > pre-emptive attack against hardware being claimed by the wrong module, > in which case we should be leaving it up the user to figure out which > module they want to use...
Apparently, it is recommended upstream to load ehci before uhci or ohci (which userspace cannot safely guarantee) and actual bugs are caused if we don't. I don't like this, but we couldn't think of another solution.
signature.asc
Description: OpenPGP digital signature
