linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 14:39:51 +0100	[thread overview]
Message-ID: <1202218791.10131.11.camel@localhost> (raw)
In-Reply-To: <20080205124029.620C01B00DA@f41.poczta.interia.pl>


On Tue, 2008-02-05 at 13:40 +0100, krzysztof.h1@poczta.fm wrote:
> Alain Kalker napisał:
> 
> > >From Documentation/fb/modedb.txt:
> > ---
> > When a frame buffer device receives a video= option it doesn't know, it
> > should consider that to be a video mode option. If no frame buffer
> > device is specified in a video= option, fbmem considers that to be a
> > global video mode option.
> > 
> > Valid mode specifiers (mode_option argument):
> > ...
> > 
> > >From this I believe that "mode_option" is the standard way, It also
> > indicates that the parameter name itself is optional, but I am not sure
> > if there is an overall Linux standard for indicating optional parameter
> > names.
> > 
> 
> If the mode_option is the correct one please email Andrew Morton to remove the patch I made for i810fb.
> I will fix drivers which use the "mode" option.

Done.

> 
> > 
> > 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'll update it with every driver I reworked.

Thanks!

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/
_______________________________________________
Linux-fbdev-devel mailing list
Linux-fbdev-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel

  reply	other threads:[~2008-02-05 13:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 12:40 mode_option or mode parameter (was: i810fb module parameter 'mode_option' inconsistent with other framebuffer modules) krzysztof.h1
2008-02-05 13:39 ` Alain Kalker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-07  7:21 krzysztof.h1
2008-02-06  7:15 krzysztof.h1
2008-02-06 16:47 ` Alain Kalker
2008-02-06 16:53   ` 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=1202218791.10131.11.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 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).