public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Starikovskiy <astarikovskiy@suse.de>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: 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: Tue, 02 Dec 2008 20:13:00 +0300	[thread overview]
Message-ID: <49356C9C.4050907@suse.de> (raw)
In-Reply-To: <20081202155228.GI1668@khazad-dum.debian.net>

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...
> 
> Otherwise, the situation never seems to get better :(
> 


  reply	other threads:[~2008-12-02 17:13 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 [this message]
2008-12-03  0:09         ` 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=49356C9C.4050907@suse.de \
    --to=astarikovskiy@suse.de \
    --cc=Linux-acpi@vger.kernel.org \
    --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