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

Bug#463129: mode_option or mode parameter (was: i810fb module parameter 'mode_option' inconsistent with other framebuffer modules)



On Tue, 2008-02-05 at 13:40 +0100, krzysztof.h1@poczta.fm wrote:
> Alain Kalker napisał:
> 
> > >From Documentation/fb/modedb.txt:
> > ---
> > When a frame buffer device receives a video= option it doesn't know, it
> > should consider that to be a video mode option. If no frame buffer
> > device is specified in a video= option, fbmem considers that to be a
> > global video mode option.
> > 
> > Valid mode specifiers (mode_option argument):
> > ...
> > 
> > >From this I believe that "mode_option" is the standard way, It also
> > indicates that the parameter name itself is optional, but I am not sure
> > if there is an overall Linux standard for indicating optional parameter
> > names.
> > 
> 
> If the mode_option is the correct one please email Andrew Morton to remove the patch I made for i810fb.
> I will fix drivers which use the "mode" option.

Done.

> 
> > 
> > P.S.: Krzysztof, maybe it would be a good idea to update fbmode.txt
> > too, as there are now many more framebuffer drivers which support video
> > mode naming.
> > 
> > 
> 
> I'll update it with every driver I reworked.

Thanks!

Regards,

Alain



Reply to: