public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Zhao Yakui <yakui.zhao@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	linux-acpi@vger.kernel.org, lenb@kernel.org
Subject: Re: [RESEND] [PATCH 2/4]  ACPI: Get the device power state in the course of scanning device
Date: Mon, 11 Aug 2008 08:52:45 +0200	[thread overview]
Message-ID: <20080811065245.GK9038@one.firstfloor.org> (raw)
In-Reply-To: <1218438140.6671.96.camel@yakui_zhao.sh.intel.com>

On Mon, Aug 11, 2008 at 03:02:20PM +0800, Zhao Yakui wrote:
> On Mon, 2008-08-11 at 08:45 +0200, Andi Kleen wrote:
> > On Mon, Aug 11, 2008 at 02:55:05PM +0800, Zhao Yakui wrote:
> > > Subject:ACPI: Get the device power state in the course of scanning device
> > > From: Zhao Yakui <yakui.zhao@intel.com>
> > > 
> > > Get the device power state in the course of scanning device if the device 
> > > power flag is power_managable. i.e. The device has the _PSx/_PRx object.
> > > 
> > > At the same time before the drivers/acpi/power module is loaded, there is no
> > > relation between acpi_power_resource and acpi device. So the first parameter 
> > > of acpi_power_get_state is changed to acpi_handle.
> > > 
> > > http://bugzilla.kernel.org/show_bug.cgi?id=8049
> > > http://bugzilla.kernel.org/show_bug.cgi?id=11000
> > 
> > Seems to be an pretty old bug. I assume it's not critical
> > enough to require pushing into .27? 
> Yes. It is not critical. 
> But in fact windows can work well on such broken BIOS. In order to make

Any guess how do they do that? Do they have a blacklist for this case?

> Linux be compatible with this broken BIOS, it will be OK to merge them.

The option is fine since it is off by default, but I'm a little scaried 
about the init sequence ordering for .27. That might break something.

-Andi

  reply	other threads:[~2008-08-11  6:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-11  6:55 [RESEND] [PATCH 2/4] ACPI: Get the device power state in the course of scanning device Zhao Yakui
2008-08-11  6:45 ` Andi Kleen
2008-08-11  7:02   ` Zhao Yakui
2008-08-11  6:52     ` Andi Kleen [this message]
2008-08-11  7:51       ` Zhao Yakui
2008-08-11  7:56         ` Andi Kleen
2008-08-11 10:21           ` Zhao Yakui
2008-08-11 10:48             ` Andi Kleen
2008-08-11 11:54               ` Rafael J. Wysocki

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=20080811065245.GK9038@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=yakui.zhao@intel.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