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

2 messages, 2 authors, 2008-02-05 · open the first message on its own page

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

From: <hidden>
Date: 2008-02-05 12:40:36

Alain Kalker napisa³:
quoted
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):
...
quoted
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.
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.

Regards,
Krzysztof


Pogoda na najblizsze dni.
Sprawdz >>> http://link.interia.pl/f1ce1


-------------------------------------------------------------------------
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/

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

From: Alain Kalker <hidden>
Date: 2008-02-05 13:40:18

On Tue, 2008-02-05 at 13:40 +0100, krzysztof.h1@poczta.fm wrote:
Alain Kalker napisał:
quoted
quoted
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):
...
quoted
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.
quoted
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

-------------------------------------------------------------------------
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/
_______________________________________________
Linux-fbdev-devel mailing list
Linux-fbdev-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help