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

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

On 22 May 01 at 20:46, Otto Wyss wrote:
> > someone have to change types for curblink, noaccel and default_vram to
> > int and then add
> > 
> > MODULE_PARM(curblink, "i"); MODULE_PARM(noaccel, "i") ... and so on.

> I'm not a kernel/driver developer and have not enough time to get used
> to it.

Then build driver into kernel.
 
> I tried it and the post-install works on the first console but not on
> others. Besides fbset needs HHHHxVVVV-RR (note the "-" before the

Sorry.

> refresh rate). What's the meaning of the "-a" at the end? Neither man
> modules.conf nor man fbset shows its meaning.

Set resolution on all consoles ;-)
 
> [OFF TOPIC ON]
> With only 3 different graphics card I could easily compile all into the
> kernel. But I thought it might be a good time to try the modularized
> versions. It's just a matter of time until all drivers where able to run
> as modules and only the absolute essentials will be kept in the kernel.
> With the introduction of the hotplug feature drivers slowly will be uses
> as modules and than made hotplugable even if the never get
> plugged/unplugged. So it might be a good idea to care about it as well.
> [OFF TOPIC OFF]

It looks like that it is trivially fixable (except modedb):
remove all #if[n]def MODULE, create

static const char* opt = NULL;
MODULE_PARM(opt, "s");

and add atyfb_setup(opt) at the beginning of its init_module()
function, just before atyfb_init() - then atyfb will understand
opt="font:VGA8x16,noblink,noaccel,vram:123,pll:456,mclk:789" (do not
forget " around the string, otherwise insmod splits string at commas).
Just something to think about...
                                            Petr Vandrovec
                                            van...@vc...