On Sun, 2016-05-22 at 21:01 +0200, Steinar H. Gunderson wrote: > On Sun, May 22, 2016 at 07:49:35PM +0100, Ben Hutchings wrote: > > > > The device tree already tells the kernel what trigger should be used, > > and the kernel can then make the decision whether that requires loading > > a module. > Does this mean the initramfs would also need to know that the module should > be included? I assume the kernel cannot re-trigger modules when switching > from initramfs to the real root. If the module is loaded based on a device's uevent, rather than a request_module() from the kernel, there is another chance to load it when udev is restarted. That's how most drivers get loaded! > > > > I disagree; it doesn't make sense to build in every trigger that might > > be needed. > Why not? They are small, and some would be useful even before loading > initramfs (although this would necessitate also having the PWM driver =y). We build in code because we have to, not because it's merely useful. And here we're talking about modules that are useful for only a small proportion of armhf systems. Ben. -- Ben Hutchings friends: People who know you well, but like you anyway.
Attachment:
signature.asc
Description: This is a digitally signed message part