[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#398948: i810fb not available at boot-time if compiled as a module



On Sat, 2007-01-20 at 12:59 -0800, Matt Zimmerman wrote:
> The options are passed to it by modprobe, based on command-line parameters
> and its configuration files, either in early userspace (initramfs) or from
> an init script.
> 

It seems that it doesn't parse the kernel command line as a module.
According to the last parapgraph of "Processing kernel command line" at
the end of "Building the Linux Kernel Image" of "Kernel 2.4
Internals" (not sure if things have changed mcuh for 2.6, but can't find
any references)

http://www.faqs.org/docs/kernel_2_4/lki-1.html#ss1.9

"Note that __setup() does nothing for modules, so the code that wishes
to process boot commandline and can be either a module or statically
linked must invoke its parsing function manually in the module
initialisation routine. This also means that it is possible to write
code that processes parameters when compiled as a module but not when it
is static or vice versa."

Looking at the i810fb.c code I don't see where it is doing kernel
command-line parsing in its module form.

I've just built a custom kernel with i810fb, intel_agp, drm, etc.
statically linked and that worked as expected, switching into graphic
mode, displaying the Ubuntu usplash screen, and giving me a full-screen
1024x768 tty.

TJ.




Reply to: