From: Andrew Morton <akpm@osdl.org>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH 4/5] fbdev: Make BIOS EDID reading configurable
Date: Thu, 23 Feb 2006 20:10:30 -0800 [thread overview]
Message-ID: <20060223201030.d5a70121.akpm@osdl.org> (raw)
In-Reply-To: <43FE83DA.3050505@gmail.com>
"Antonino A. Daplas" <adaplas@gmail.com> wrote:
>
> >
> > Also, is it not possible to defer this operation until we've parsed the
> > command line, control it with a kernel boot parameter?
> >
>
> I thought of that, but it seems a bit complicated to me to parse boot
> options in assembly so I left this for another time.
Well I'm wondering whether we can instead do this query later on, after
we've entered start_kernel().
> The firmware EDID is only used as fallback, or if drivers have no DDC/I2C
> support. Currently, all drivers that use the firmware EDID also have I2C
> support in place. And chances are, if DDC transfers failed, the firmware
> EDID will also be absent.
hm. Don't you think `default y' would be better? As it is, people's stuff
will mysteriously stop working.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next prev parent reply other threads:[~2006-02-24 4:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 12:00 [PATCH 4/5] fbdev: Make BIOS EDID reading configurable Antonino A. Daplas
2006-02-24 0:34 ` Andrew Morton
2006-02-24 3:56 ` Antonino A. Daplas
2006-02-24 4:10 ` Andrew Morton [this message]
2006-02-24 5:24 ` Antonino A. Daplas
2006-02-24 5:29 ` Andrew Morton
2006-02-24 5:44 ` [PATCH] fbdev: Make config firmware EDID default to yes Antonino A. Daplas
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=20060223201030.d5a70121.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=adaplas@gmail.com \
--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).