From: Alain Kalker <miki@dds.nl>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: jsimmons@infradead.org, linux-fbdev-devel@lists.sourceforge.net,
adaplas@gmail.com
Subject: Re: [Bugme-new] [Bug 9847] New: i810fb: module parameter 'mode_option' inconsistent with other framebuffer modules
Date: Sat, 02 Feb 2008 06:27:19 +0100 [thread overview]
Message-ID: <1201930040.2704.37.camel@localhost> (raw)
In-Reply-To: <20080201203737.141b11d1.akpm@linux-foundation.org>
On Fri, 2008-02-01 at 20:37 -0800, Andrew Morton wrote:
> On Sat, 02 Feb 2008 05:18:10 +0100 Alain Kalker <miki@dds.nl> wrote:
>
> > Should this be filed as a more general bug report?
>
> It is unlikely that anyone would actually act upon such a thing, I'm afraid.
> Maybe if we could come up with a single, centralised option parser
> for all the drivers and then migrate individual drivers over to or
> or something like that..
The reason I asked is that the current situation presents a problem to
the boot scripts. Currently none of the modules support both options
simultaneously, and I'm not sure if every module supports the parameter
name being optional. The only sure ways to ensure that kernel boot
option "video=<framebuffer>:<videomode> works as intended, is either to
parse the modules' option list using modinfo (which may not be available
at boot) or to try each option name in turn using "modprobe
--first-time", which I find very kludgy.
-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-02 5:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 7:01 [Bugme-new] [Bug 9847] New: i810fb: module parameter 'mode_option' inconsistent with other framebuffer modules krzysztof.h1
2008-02-01 7:32 ` Andrew Morton
2008-02-02 4:18 ` Alain Kalker
2008-02-02 4:37 ` Andrew Morton
2008-02-02 5:27 ` Alain Kalker [this message]
[not found] <bug-9847-10286@http.bugzilla.kernel.org/>
2008-01-30 5:33 ` Andrew Morton
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=1201930040.2704.37.camel@localhost \
--to=miki@dds.nl \
--cc=adaplas@gmail.com \
--cc=akpm@linux-foundation.org \
--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).