From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Andrew Morton <akpm@linux-foundation.org>,
adaplas@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] gxfb: Replace FBSIZE config option with a kernel argument
Date: Mon, 10 Mar 2008 09:16:34 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0803100915300.8567@anakin> (raw)
In-Reply-To: <20080309195754.6d972be7@ephemeral>
On Sun, 9 Mar 2008, Andres Salomon wrote:
> On Sun, 9 Mar 2008 23:00:25 +0100
> Ondrej Zajicek <santiago@crfreenet.org> wrote:
>
> > On Sat, Mar 08, 2008 at 08:19:50PM -0500, Andres Salomon wrote:
> > > > assuming this is historical at this point, and manual options parsing can
> > > > be removed from all fb drivers at this point, or is there another reason
> > > > why manual parsing would be necessary?
> > > >
> > >
> > > Could I get an answer from the fbdevel folks about this? It looks like
> > > the fb_get_options stuff is there for backwards compatibility.
> >
> > I think so. I used fb_get_options() in arkfb and vt8623fb for mode option
> > only. Universal notation module.option=value is much nicer than manual
> > options parsing.
This `module.option=value' is a quite recent introduction? I first saw it
mentioned earlier this year...
> If that is indeed the case, here's a patch that might be useful. I have
> no idea what kind of timeframe would be proposed for removing
> fb_get_options (or if it's even desirable to remove it at all given that
> people are likely still using video=$foo syntax).
Probably it's way too early for that...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
-------------------------------------------------------------------------
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-03-10 8:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 6:10 [PATCH 1/4] gxfb: Replace FBSIZE config option with a kernel argument Andres Salomon
2008-02-28 0:31 ` Andrew Morton
2008-02-28 0:58 ` Andres Salomon
2008-02-28 1:12 ` Jordan Crouse
2008-03-09 1:19 ` [PATCH 1/4] " Andres Salomon
2008-03-09 1:19 ` Andres Salomon
2008-03-09 18:12 ` Randy Dunlap
2008-03-09 22:00 ` Ondrej Zajicek
2008-03-09 23:57 ` Andres Salomon
2008-03-10 8:16 ` Geert Uytterhoeven [this message]
2008-03-11 20:25 ` Andres Salomon
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=Pine.LNX.4.64.0803100915300.8567@anakin \
--to=geert@linux-m68k.org \
--cc=adaplas@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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).