Bug#463129: mode_option or mode parameter (was: i810fb module parameter 'mode_option' inconsistent with other framebuffer modules)
On Tue, 2008-02-05 at 12:42 +0100, Alain Kalker wrote:
> 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 have to rephrase that, the situation is much more complicated (sigh).
The only pattern I see is that drivers which support ModeDB (e.g.
i810fb) use the parameter name 'video_mode' which can then be optional,
while others (e.g. cirrusfb) use hardcoded video modes and _require_ the
parameter name to be present, which must then be called 'mode'.
Kind regards,
Alain
Reply to: