Subject: Re: Buggy DSDTs policy ?
From: Xavier Bestel <xavier.bestel@free.fr>
To: Pekka Pietikainen <pp@ee.oulu.fi>
Cc: "Yu, Luming" <luming.yu@intel.com>, Onur Kucuk <onur@delipenguen.net>,
       Olivier Galibert <galibert@pobox.com>, linux-kernel@vger.kernel.org
In-Reply-To: <20041025090131.GA3404@ee.oulu.fi>
References: <3ACA40606221794F80A5670F0AF15F84041ABFE0@pdsmsx403>
	 <20041025090131.GA3404@ee.oulu.fi>
Content-Type: text/plain; charset=utf-8
Message-Id: <1098695638.11449.11.camel@gonzales>
Mime-Version: 1.0
Date: Mon, 25 Oct 2004 11:13:58 +0200
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1134
Lines: 26

Le lun 25/10/2004 à 11:01, Pekka Pietikainen a écrit :
> On Mon, Oct 25, 2004 at 02:21:09PM +0800, Yu, Luming wrote:
> > >> Yes, sure. But real non-technical people won't replace their DSDT
> > >> either.
> > >Their distro could do it for them :-) A simple approach would be to
> > >store md5sums of known-bad dsdt's and xdeltas to fixed ones, and the 
> > >fixed one gets placed in /etc where mkinitrd automagically picks it up
> > >whenever a new kernel is installed.
> > 
> > I don't think distro can do that, because they are not the owner of
> > DSDT.
> That's what I said xdelta, so the only "new" code is patches against
> the broken vendor code in /proc/acpi/dsdt. But it's messy even
> that way, I know.

Hackish at best. Having an AML interpreter able to follow MS's quirks
seems a preferred solution (2.6.9's ACPI is said to be better at that, I
haven't tested it yet).

	Xav

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/