On Apr 30, 2006, at 9:51 PM, Daniel O'Connor wrote: > On Monday 01 May 2006 13:50, Marcel Moolenaar wrote: >>> As for building acpi into kernel, i386/conf/NOTES says: >>> >>> # Note that building ACPI into the kernel is deprecated; the >>> module is >>> # normally loaded automatically by the loader. >>> >>> I thought that was deprecated? >> >> No, it isn't really. The use of modules is not a requirement. > > However you wouldn't expect that using it as a module would result > in reduced > functionality. True. This is exactly where our kernel modules have a weakness. Or differently put, where our kernel configuration has its weakness. A module is pretty much all-inclusive. A kernel configuration is minimalistic by nature (hence, one would actually expect reduced functonality). Mixing them gives unwanted results in a pre-dominantly modular configuration. One way to attack it is to make a kernel configuration the same as a bundled set or a preloaded set of modules. This means for example that if you configure ppc(4) into the kernel, you get the acpi attachment even if you don't have device acpi configured into the kernel. This of course may result in unresolved symbols, so it's not a trivial solution. If it's a solution at all... -- Marcel Moolenaar USPA: A-39004 marcel_at_xcllnt.netReceived on Mon May 01 2006 - 14:55:42 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:55 UTC