From: Alain Kalker <miki@dds.nl>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Randy Dunlap <rdunlap@xenotime.net>,
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: Wed, 06 Feb 2008 17:53:50 +0100 [thread overview]
Message-ID: <1202316830.5109.29.camel@localhost> (raw)
In-Reply-To: <1202316423.5109.26.camel@localhost>
On Wed, 2008-02-06 at 17:47 +0100, Alain Kalker wrote:
> I would like to propose instead to make the 'mode' / 'mode_option'
> parameter name optional for all drivers where possible. This will
> greatly simplify framebuffer driver loading by the boot scripts, which
> currently cannot easily identify drivers needing either parameter name.
so one would be able to use
# modprobe <xxxfb> 1024x768 <other options>
instead of
# modprobe <xxxfb> mode_option=1024x768 <other options>
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-06 16:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 7:15 mode_option or mode parameter (was: i810fb module parameter 'mode_option' inconsistent with other framebuffer modules) krzysztof.h1
2008-02-06 16:47 ` Alain Kalker
2008-02-06 16:53 ` Alain Kalker [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-07 7:21 krzysztof.h1
2008-02-05 12:40 krzysztof.h1
2008-02-05 13:39 ` Alain Kalker
2008-02-05 7:08 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
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=1202316830.5109.29.camel@localhost \
--to=miki@dds.nl \
--cc=adaplas@gmail.com \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=rdunlap@xenotime.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).