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

[Alain Kalker <miki@dds.nl>]

On Tue, 2008-02-05 at 08:08 +0100, krzysztof.h1@poczta.fm wrote:
> Hi,
> 
> Few days ago, a bug was reported that the i810fb uses "mode_option" parameters while other framebuffers uses the "mode" parameter to set initial mode. It was spotted later that some drivers uses "mode_option", some uses "mode" and some does use none.
> 
> I want to ask what is a correct way. I can rework at least some of the drivers to a standard way, but I don't know what the standard is.

With your permission, I have cc:'ed your question to my original Debian
bug report,

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.

Kind regards,

Alain

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.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/