[Meego-architecture] Autoloading modules in startup process

[Arjan van de Ven]

On 12/9/2010 2:12 AM, Carsten Munk wrote:
> Hi,
>
> We are struggling with some various bugs that require modprobing of
> modules in startup process such as
> http://bugs.meego.com/show_bug.cgi?id=9824 or
> http://bugs.meego.com/show_bug.cgi?id=9057
>
> Due to size constraints, we can't build-in most modules into a kernel
> and require some kind of autodetection or the likes that loads the
> modules.
>
> What's the intended way of dealing with situations like this? Could we
> do something smart related to /etc/machinename idea?
>
> I guess the 'best way' would be having udev do it? And is there some
> good documentation on how this is handled on kernel source basis or
> configuration?

surely the platform has SOME kind of enumeration (be it device tree, 
SFI, or hardware based enumeration)
if that enumeration is hooked up properly, and the driver has the right 
module alias... udev ought to be
autoloading modules correctly.

I would strongly suggest figuring out why the enumeration->udev path is 
not working... everything else is going to be some
hacky, hard to maintain workaround.