Linux ACPI
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Len Brown <lenb@kernel.org>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] acpi: Export EDID blocks to the kernel
Date: Fri, 02 Apr 2010 11:19:49 +0800	[thread overview]
Message-ID: <1270178389.24064.4534.camel@rzhang1-desktop> (raw)
In-Reply-To: <alpine.LFD.2.00.1003312053220.5062@localhost.localdomain>

On Thu, 2010-04-01 at 08:53 +0800, Len Brown wrote:
> 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.
> 

Acked-by: Zhang Rui <rui.zhang@intel.com>

> -Len
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



      reply	other threads:[~2010-04-02  3:18 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
2010-04-02  3:19     ` Zhang Rui [this message]

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=1270178389.24064.4534.camel@rzhang1-desktop \
    --to=rui.zhang@intel.com \
    --cc=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