From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Thomas Renninger <trenn@suse.de>,
ak@linux.intel.com, linux-acpi@vger.kernel.org,
linux-next@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Julia Jomantaite <julia.jomantaite@gmail.com>,
marcus@better.se, dannybaumann@web.de, corsac@debian.org
Subject: Re: [PATCH 1/2] ACPI Video: Ignore devices that aren't present in hardware
Date: Fri, 4 Jul 2008 10:13:07 +0100 [thread overview]
Message-ID: <20080704091307.GB8905@srcf.ucam.org> (raw)
In-Reply-To: <20080704030948.GB31908@khazad-dum.debian.net>
On Fri, Jul 04, 2008 at 12:09:49AM -0300, Henrique de Moraes Holschuh wrote:
> On Thu, 03 Jul 2008, Matthew Garrett wrote:
> > Not until the opregion code is merged, no. If you'd like that to happen
> > faster, then figuring out why it triggers a 750ms delay on brightness
> > changes on the T61 would be a great help, because I haven't a clue why
> > it's broken...
>
> I have never really tried finding out WTF in the firmware causes this, but:
>
> 1. The backlight-change firmware runs in SMM.
> 2. The calls happen in ACPI DSDT
> 3. The SMM code DOES take care of the CMOS NVRAM
As far as I can tell, it's sleeping in the DSDT. But all the ready flags
are set appropriately according to the opregion spec, so I'm confused as
to why. Hardware failure has meant I've got to use the T61 this week, so
I'll try to fix it while I'm stuck in an airport tomorrow...
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-07-04 9:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 16:05 [PATCH 1/2] ACPI Video: Ignore devices that aren't present in hardware Thomas Renninger
2008-07-03 16:08 ` Matthew Garrett
2008-07-03 16:15 ` Thomas Renninger
2008-07-03 16:16 ` Matthew Garrett
2008-07-03 16:21 ` Yves-Alexis Perez
2008-07-03 19:24 ` Matthew Garrett
2008-07-04 10:08 ` Thomas Renninger
2008-07-04 10:18 ` Matthew Garrett
2008-07-04 3:09 ` Henrique de Moraes Holschuh
2008-07-04 9:13 ` Matthew Garrett [this message]
2008-07-04 11:55 ` Henrique de Moraes Holschuh
2008-07-04 17:39 ` Matthew Garrett
2008-07-04 19:49 ` Henrique de Moraes Holschuh
2008-07-05 15:46 ` Henrique de Moraes Holschuh
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=20080704091307.GB8905@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=corsac@debian.org \
--cc=dannybaumann@web.de \
--cc=hmh@hmh.eng.br \
--cc=julia.jomantaite@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marcus@better.se \
--cc=trenn@suse.de \
/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