Linux ACPI
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Stefan Bader <stefan.bader@canonical.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: Less strict requirements for video device detection
Date: Fri, 21 Aug 2009 09:17:38 +0800	[thread overview]
Message-ID: <1250817458.17853.141.camel@rzhang-dt> (raw)
In-Reply-To: <4A8D140F.1090909@canonical.com>

On Thu, 2009-08-20 at 17:14 +0800, Stefan Bader wrote:
> Hardware: Acer 6920G (from a bug report)
> 
> Another case of a broken BIOS. In this case there are several definitions for 
> video bus devices but only one has _DOS and _DOD defined. All other definitions 
> only have _DOD.

I have seen such kind of BIOS too.

> In the past (2.6.27) _ADR was not evaluated to make sure of using a present 
> video device, but with that bug brightness could be changed.
> 
> Now the video bus having _DOS and _DOD is detected as not being present. The 
> other definitions are not considered because they are lacking the _DOS method.
> Using the attached patch, would cause the detection code to consider the other 
> definitions and has been tested to enable backlight control.
> 

> Would this be an acceptable approach?

I think so. I generated a similar patch before, but didn't sent it out
for some reason.
My suggestion is that we should also print out a warning message if _DOS
is missed, what do you think?

thanks,
rui

>  From the ACPI spec it rather sounds like 
> _DOD and _DOS must be present for a device for display switching and _DOS would 
> indicate possible backlight control as well. So the question might not be so 
> much is it the right thing than is it safe enough to allow more compatibility 
> with broken implementations without causing other problems...
> 
> -Stefan
> 


  reply	other threads:[~2009-08-21  1:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-20  9:14 Less strict requirements for video device detection Stefan Bader
2009-08-21  1:17 ` Zhang Rui [this message]
2009-08-21 10:00   ` Less strict requirements for video device detection (v2) Stefan Bader
2009-08-24  1:19     ` Zhang Rui
2009-08-24 14:44       ` Less strict requirements for video device detection (v3) Stefan Bader
2009-08-25  1:08         ` Zhang Rui
2009-09-30 20:23           ` Stefan Bader
2009-10-09  1:30             ` Zhang Rui
2009-10-13  6:52               ` Len Brown

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=1250817458.17853.141.camel@rzhang-dt \
    --to=rui.zhang@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=stefan.bader@canonical.com \
    /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