From: Thomas Renninger <trenn@suse.de>
To: Len Brown <lenb@kernel.org>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
linux-acpi <linux-acpi@vger.kernel.org>,
Zhao Yakui <yakui.zhao@intel.com>,
me@markdoughty.co.uk,
linux-thinkpad <linux-thinkpad@linux-thinkpad.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
"devel@acpica.org" <devel@acpica.org>
Subject: [RESEND] [PATCH 0/3] Blacklist broken ThinkPads to use 32 bit FADT addresses
Date: Sun, 19 Oct 2008 23:49:31 +0200 [thread overview]
Message-ID: <200810192349.32949.trenn@suse.de> (raw)
Hi,
can this be taken into .28 if it works out with acpica integration.
Patches are in OpenSUSE for quite a while now (also 11.0) and the
issue has been evaluate to the ground now.
Lenovo confirmed that some rare models which got Vista support added
late through BIOS upgrades could have wrong 64 bit addresses.
Vista also takes the broken 64 bit addresses like Linux does (spec conform).
XP does take the correct 32 bit addresses.
A generic approach (e.g. check through _OSI) does not work, because:
- the affected models support Vista (there the wrong addresses are also
taken, but
the symptoms seem not to happen or are also workarounded)
- Those IO addresses are touched before the DSDT is parsed -> no OSI
OS feature support check possible.
Be aware that one patch makes changes in ACPICA code.
Thanks,
Thomas
next reply other threads:[~2008-10-19 21:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 21:49 Thomas Renninger [this message]
2008-10-20 3:32 ` [RESEND] [PATCH 0/3] Blacklist broken ThinkPads to use 32 bit FADT addresses Zhao Yakui
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=200810192349.32949.trenn@suse.de \
--to=trenn@suse.de \
--cc=devel@acpica.org \
--cc=hmh@hmh.eng.br \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-thinkpad@linux-thinkpad.org \
--cc=me@markdoughty.co.uk \
--cc=mjg59@srcf.ucam.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