From: Ondrej Zajicek <santiago@crfreenet.org>
To: Andres Salomon <dilinger@queued.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, adaplas@gmail.com
Subject: Re: [PATCH 1/4] gxfb: Replace FBSIZE config option with a kernel argument
Date: Sun, 9 Mar 2008 23:00:25 +0100 [thread overview]
Message-ID: <20080309220025.GD9971@localhost.localdomain> (raw)
In-Reply-To: <20080308201950.28f6eae8@ephemeral>
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.
--
Elen sila lumenn' omentielvo
Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org, jabber: santiago@njs.netlab.cz)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
-------------------------------------------------------------------------
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/
WARNING: multiple messages have this Message-ID (diff)
From: Ondrej Zajicek <santiago@crfreenet.org>
To: Andres Salomon <dilinger@queued.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, adaplas@gmail.com
Subject: Re: [Linux-fbdev-devel] [PATCH 1/4] gxfb: Replace FBSIZE config option with a kernel argument
Date: Sun, 9 Mar 2008 23:00:25 +0100 [thread overview]
Message-ID: <20080309220025.GD9971@localhost.localdomain> (raw)
In-Reply-To: <20080308201950.28f6eae8@ephemeral>
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.
--
Elen sila lumenn' omentielvo
Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org, jabber: santiago@njs.netlab.cz)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
next prev parent reply other threads:[~2008-03-09 22:00 UTC|newest]
Thread overview: 21+ 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:31 ` Andrew Morton
2008-02-28 0:58 ` Andres Salomon
2008-02-28 0:58 ` Andres Salomon
2008-02-28 1:12 ` Jordan Crouse
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 1:19 ` Andres Salomon
2008-03-09 1:19 ` Andres Salomon
2008-03-09 18:12 ` Randy Dunlap
2008-03-09 18:12 ` Randy Dunlap
2008-03-09 22:00 ` Ondrej Zajicek [this message]
2008-03-09 22:00 ` [Linux-fbdev-devel] " Ondrej Zajicek
2008-03-09 23:57 ` Andres Salomon
2008-03-09 23:57 ` [Linux-fbdev-devel] " Andres Salomon
2008-03-10 8:16 ` Geert Uytterhoeven
2008-03-10 8:16 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2008-03-11 20:25 ` Andres Salomon
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=20080309220025.GD9971@localhost.localdomain \
--to=santiago@crfreenet.org \
--cc=adaplas@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dilinger@queued.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.