On Wed, 2007-08-08 at 18:22 -0400, Bill Nottingham wrote: > Kay Sievers ([EMAIL PROTECTED]) said: > > Ah, ok, makes sense. Yeah, that weird "platform devices loads itself by > > the name" thing got disabled in the platform subsystem. It caused > > modprobe loops for other devices. > > > > The whole idea of issuing MODALIAS with plain module names instead of > > aliases can't really work, but the platform maintainer didn't like to > > use the usual aliases and the matches in the modules, for a reason I > > didn't understand while we talked about the problem last time. > > So, the solution is for the platform device to issue a random modalias > that pcskpr exports?
I would still like to see "MODALIAS=platform:<string>" exported by the bus, and matching aliases the modules, just like every other subsystem does. Like SCSI, with the "artificial" aliases for the modules it wants to autoload: $ /sbin/modinfo sd_mod ... alias: scsi:t-0x0e* alias: scsi:t-0x07* alias: scsi:t-0x00* ... $ cat /sys/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/modalias scsi:t-0x00 That way you would get full control over the loading or blacklisting with module-init-tools config files, which doesn't work with direct module name requests, and no magic in the bus code or the drivers would be needed. Kay - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
