From: Len Brown <lenb@kernel.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH] acpi: Export EDID blocks to the kernel
Date: Wed, 31 Mar 2010 20:53:59 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1003312053220.5062@localhost.localdomain> (raw)
In-Reply-To: <20100330164947.GA27983@srcf.ucam.org>
On Tue, 30 Mar 2010, Matthew Garrett wrote:
> On Tue, Jan 12, 2010 at 02:17:03PM -0500, Matthew Garrett wrote:
> > The ACPI spec includes a provision for hardware to provide EDID via the
> > ACPI video extension. In the KMS world it's necessary for a way to obtain
> > this from within the kernel. Add a function that either returns the EDID
> > for the provided ACPI display ID or the first display of the provided type.
> > Also add support for ensuring that devices with legacy IDs are supported.
> >
> > Signed-off-by: Matthew Garrett <mjg@redhat.com>
>
> Did this get picked up?
No, it did not.
Rui,
Matthew is proposing adding an API to your driver.
-Len
next prev parent reply other threads:[~2010-04-01 0:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 19:17 [PATCH] acpi: Export EDID blocks to the kernel Matthew Garrett
2010-03-30 16:49 ` Matthew Garrett
2010-04-01 0:53 ` Len Brown [this message]
2010-04-02 3:19 ` Zhang Rui
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=alpine.LFD.2.00.1003312053220.5062@localhost.localdomain \
--to=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.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