On Wed, Nov 22, 2006 at 08:50:21AM -0500, Joey Hess wrote: > <Md> joeyh: I remember talking about #398962 with waldi, IIRC platform > devices in recent kernels provide $MODALIAS while they should not. so udev > will always try loading again the driver after it has been loaded > <Md> I suppose I could add a workaround in udev since I do not know about any > platform driver which provides a meaningful $MODALIAS > <fjp> Md: Has there been a discussion with kernel developers about that? > Will/has it been fixed in later kernels? > <Md> fjp: no clue. somebody should ask greg k-h but I am too much busy these > days > <joeyh> Md: afaics, there's no way udev can autoload that pcmcia bridge > driver .. would just blacklisting it in udev make sense? Is there a way to > blacklist it that doesn't blacklist it from modprobe? > <Md> joeyh: try adding in hotplug.rules, as the third line: > SUBSYSTEM=="platform", GOTO="hotplug_driver_loaded" > <Md> IIRC it uses SUBSYSTEM=="platform", double check the log if needed > <joeyh> ok, that works, tested in d-i > <Md> I will add the workaround to the next upload > <joeyh> I imagine a more targeted rule that also matches the driver would > also work > <joeyh> at least for this one module.. dunno about other platform modules.. > <Md> all platform drivers have this problem, the bug is in the drivers core
Notice that the pegasos marvell gigabit ethernet port is such a platform device. We currently have a hacked patch in our kernel with makes it masquarade as a pci device, listening on the northbridge pci id, but when i tried to push this patch upstream, i was told it was not needed because of the platform device modalias support. There are probably other devices which gained hotplug and thus automatically loaded modules, in this way. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
