On Sat, May 22, 2010 at 01:09:12AM +0300, Felipe Contreras wrote: > On Sat, May 22, 2010 at 12:57 AM, Russell King - ARM Linux > <linux@xxxxxxxxxxxxxxxx> wrote: > > The only reason 3 would be loaded due to that dependency is if 2 were > > being modprobed, which means it's going to be inserted after 3 anyway. > > > > I don't see anything else in 3 which would trigger it to be loaded. > > > > The "platform:omap2-mailbox" module alias of 2 should result in 2 > > being modprobed, > > I see, at initialization? That's the theory - and it should be that same mechanism which allows things like already plugged in PCMCIA and the like cards to be properly dealt with at boot time. > > causing 3 to be loaded to satisfy the dependency. > > As already pointed out, this should happen as a result of udev or > > (older) hotplug initialization. > > Well, in the minimal system I have in my beagleboard it doesn't > happen. I load bridgedriver, which loads mailbox, but fails > immediately because mailbox_mach is not there. I assume that having the MMC host driver built in, but the MMC block driver as a module also doesn't work on your setup? I don't see this as something that should be worked around in the kernel by making things non-modular - I view the missing userspace functionality causing the problem. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
