From: Randy Dunlap <rdunlap@xenotime.net>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: jsimmons@infradead.org, adaplas@gmail.com
Subject: Re: mode_option or mode parameter (was: i810fb module parameter 'mode_option' inconsistent with other framebuffer modules)
Date: Tue, 5 Feb 2008 14:03:17 -0800 [thread overview]
Message-ID: <20080205140317.c6746e47.rdunlap@xenotime.net> (raw)
In-Reply-To: <20080205070810.9BF9D1B00D8@f41.poczta.interia.pl>
On 05 Feb 2008 08:08:10 +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.
Hi,
Hopefully one of the fbdev driver developers will know for sure.
I would (do) say that "mode_option" is being redundant. Yes, it's
an option, but we don't usually name options (in other parts of the
kernel) with an _option suffix. Sure, the variable could be called
<mode_option>, but the userspace name should just be "mode". IMHO.
Please keep Documentation/fb/modedb.txt updated if you make any
relevant changes.
Thanks.
---
~Randy
-------------------------------------------------------------------------
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 22:03 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
2008-02-05 12:25 ` Alain Kalker
2008-02-05 22:03 ` Randy Dunlap [this message]
-- 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=20080205140317.c6746e47.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=adaplas@gmail.com \
--cc=jsimmons@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).