On Wed, 10 Dec 2003 20:33:24 +0100the biggest advantage from modules is the ability to enable/disable devices with different initialization configurations without rebooting, including the use of devices that aren't present during boot or may be added to a system that cant be put down to reboot. Embedded systems usually do not change, that's just part of being embedded, modules dont really make sense there unless things like filesystems and non-device modules never get used at the same time and memory is limited such that 100KB actually matters.
mru@xxxxxx (Måns Rullgård) wrote:
Witukind <witukind@xxxxxxxxxxxxxxxxxx> writes:
On Tue, 09 Dec 2003 10:39:32 +0100 mru@xxxxxx (Måns Rullgård) wrote:
Is there a specific case for which people want this feature?
Offhand it seems like a slightly odd thing to ask for...
I believe the original motivation for module autoloading was to
save> memory by unloading modules when their devices were unused. Loading> them automatically on demand made for less trouble for
users, who> didn't have to run modprobe manually to use the sound
card, or> whatever. This could still be a good thing in embedded
systems.>
I don't see why it wouldn't be a good thing for regular systems
also. Saving memory is usually a good idea.
The biggest modules are about 100k. Saving 100k of 1 GB doesn't
really seem worth any effort.
I don't have 1 Gb of memory. On my laptop with 16 mb RAM saving 100k is worth
the effort.