From: Alain Kalker <miki@dds.nl>
To: krzysztof.h1@poczta.fm
Cc: linux-fbdev-devel@lists.sourceforge.net, jsimmons@infradead.org,
463129@bugs.debian.org, adaplas@gmail.com
Subject: Re: mode_option or mode parameter (was: i810fb module parameter 'mode_option' inconsistent with other framebuffer modules)
Date: Tue, 05 Feb 2008 13:09:46 +0100 [thread overview]
Message-ID: <1202213386.5357.40.camel@localhost> (raw)
In-Reply-To: <1202211756.5357.31.camel@localhost>
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
-------------------------------------------------------------------------
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/
next prev parent reply other threads:[~2008-02-05 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 7:08 mode_option or mode parameter (was: i810fb module parameter 'mode_option' inconsistent with other framebuffer modules) krzysztof.h1
2008-02-05 11:42 ` Alain Kalker
2008-02-05 12:09 ` Alain Kalker [this message]
2008-02-05 12:25 ` Alain Kalker
2008-02-05 22:03 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2008-02-05 12:40 krzysztof.h1
2008-02-05 13:39 ` Alain Kalker
2008-02-06 7:15 krzysztof.h1
2008-02-06 16:47 ` Alain Kalker
2008-02-06 16:53 ` Alain Kalker
2008-02-07 7:21 krzysztof.h1
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1202213386.5357.40.camel@localhost \
--to=miki@dds.nl \
--cc=463129@bugs.debian.org \
--cc=adaplas@gmail.com \
--cc=jsimmons@infradead.org \
--cc=krzysztof.h1@poczta.fm \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.