Re: [Linux-fbdev-devel] Frame buffer drivers compiled as mo

[Petr V. <VAN...@vc...>]

On 21 May 01 at 22:21, Otto Wyss wrote:

> What's the reason for this? It might be that the lilo kernel parameters
> won't get routed to the modularized drivers but why weren't options read
> from modules.conf?

Drivers do not read options from modules.conf, modprobe does. When built
into kernel, fbdev drivers support unified 'video=<fbdevname>:options' 
kernel cmdline argument, but when they are built as modules, it differs
from driver to driver (f.e. matroxfb supports all these options,
instead of video=matrox:a:b you write 'insmod matroxfb_base a=b')

> It seems the the frame buffer drivers gets started rather late in the
> startup process. What defines this order, could frame buffer drivers be
> moved more to the beginning?

I do not understand. Of course that if you compiled these drivers as modules
then they are started after / is mounted r/w. What else do you expect
from modules? And if you are talking about fbdev drivers in kernel, then
I think that they are started too early. Currently my kernel initializes
all device drivers after all other subsystems were initialized, just before
mounting root read-only, and I'm very happy from this. Only problem is that
I had to do some hotplugging fixes in some code.
                                    Best regards,
                                            Petr Vandrovec
                                            van...@vc...