From: Pekka Pietikainen <pp@ee.oulu.fi>
To: "Yu, Luming" <luming.yu@intel.com>
Cc: Xavier Bestel <xavier.bestel@free.fr>,
Onur Kucuk <onur@delipenguen.net>,
Olivier Galibert <galibert@pobox.com>,
linux-kernel@vger.kernel.org
Subject: Re: Buggy DSDTs policy ?
Date: Mon, 25 Oct 2004 12:01:31 +0300 [thread overview]
Message-ID: <20041025090131.GA3404@ee.oulu.fi> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F84041ABFE0@pdsmsx403>
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.
But that's all userspace, the kernel should still make it possible (via
initrd or something else ;) )
next prev parent reply other threads:[~2004-10-25 9:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 6:21 Buggy DSDTs policy ? Yu, Luming
2004-10-25 9:01 ` Pekka Pietikainen [this message]
2004-10-25 9:13 ` Xavier Bestel
-- strict thread matches above, loose matches on Subject: below --
2004-10-25 5:56 Yu, Luming
2004-10-22 12:23 Olivier Galibert
2004-10-22 14:41 ` Onur Kucuk
2004-10-22 14:55 ` Xavier Bestel
2004-10-22 15:19 ` Pekka Pietikainen
2004-10-22 15:35 ` Xavier Bestel
2004-10-22 16:30 ` Pekka Pietikainen
2004-10-22 16:44 ` Onur Kucuk
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=20041025090131.GA3404@ee.oulu.fi \
--to=pp@ee.oulu.fi \
--cc=galibert@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@intel.com \
--cc=onur@delipenguen.net \
--cc=xavier.bestel@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.