Adrian Bunk wrote: > > Do modular framebuffers really make sense? Yes. e.g., on embedded systems you may not use the display hardware (and would therefore like to save a bit of memory) but it's convenient to have only one build of the kernel/modules.
> OK, distributions like to make everything modular, but all the > framebuffer drivers I've looked at parse driver specific options in > their *_setup function only in the non-modular case. Not the (new) Geode framebuffer driver -- it uses regular module parameters for this very reason. > And most framebuffer drivers contain a module_exit function. > Is there really any case where this is both reasonable and working? It's useful for testing if nothing else. True, the Geode framebuffer driver won't restore the mode on unload but since the software VGA emulation on a Geode is less than perfect[*] I would expect people to not use vgacon and thus there's nothing really to restore. David Vrabel [*] I never did work out what happened to the cursor... -- David Vrabel, Design Engineer Arcom, Clifton Road Tel: +44 (0)1223 411200 ext. 3233 Cambridge CB1 7EA, UK Web: http://www.arcom.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/