From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alexey Starikovskiy <astarikovskiy@suse.de>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Zhao Yakui <yakui.zhao@intel.com>, LenBrown <lenb@kernel.org>,
"Linux-acpi@vger.kernel.org" <Linux-acpi@vger.kernel.org>
Subject: Re: [RFC][PATCH] ACPI: EC: Don't trust ECDT tables from ASUS
Date: Wed, 3 Dec 2008 01:09:38 +0100 [thread overview]
Message-ID: <200812030109.38768.rjw@sisk.pl> (raw)
In-Reply-To: <49356C9C.4050907@suse.de>
On Tuesday, 2 of December 2008, Alexey Starikovskiy wrote:
> Henrique de Moraes Holschuh wrote:
> > On Tue, 02 Dec 2008, Alexey Starikovskiy wrote:
> >> ASUSTek keeps feeding us with broken ECDT tables, which are very hard to workaround.
> >> So, we end up always checking that ECDT from ASUS has the same info as DSDT, and
> >> bark otherwise.
> >
> > I wish we would do more of that, AND printk "BIOS BUG" and "FIRMWARE BUG"
> > everytime we activate any quirk or bug due to something we are completely
> > sure to be a vendor firmware screw-up.
> I've talked to several Taiwanese notebook BIOS writers lately, and they all seem to
> know only one thing -- if Windows boots, BIOS is ok. So we might write huge banners in
> neon letters -- it will not work...
At least the users may notice and hopefully they will buy from another vendor
next time ...
Thanks,
Rafael
prev parent reply other threads:[~2008-12-03 0:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 20:47 [RFC][PATCH] ACPI: EC: Don't trust ECDT tables from ASUS Alexey Starikovskiy
2008-12-02 8:14 ` Zhao Yakui
2008-12-02 9:38 ` Alexey Starikovskiy
2008-12-02 15:52 ` Henrique de Moraes Holschuh
2008-12-02 17:13 ` Alexey Starikovskiy
2008-12-03 0:09 ` Rafael J. Wysocki [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=200812030109.38768.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=Linux-acpi@vger.kernel.org \
--cc=astarikovskiy@suse.de \
--cc=hmh@hmh.eng.br \
--cc=lenb@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