From: Pekka Pietikainen <pp@ee.oulu.fi>
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: Onur Kucuk <onur@delipenguen.net>,
Olivier Galibert <galibert@pobox.com>,
linux-kernel@vger.kernel.org
Subject: Re: Buggy DSDTs policy ?
Date: Fri, 22 Oct 2004 19:30:17 +0300 [thread overview]
Message-ID: <20041022163017.GA18156@ee.oulu.fi> (raw)
In-Reply-To: <1098459316.31003.93.camel@gonzales>
On Fri, Oct 22, 2004 at 05:35:16PM +0200, Xavier Bestel wrote:
> > The problem is getting the fixed dsdt in use without recompiling your
> > kernel, since quite a few people, especially non-technical ones, use vendor
> > kernels. There's an approach that uses initrd, but this isn't merged
> > yet. I'd say it should be, assuming no better solution can be found.
>
> 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.
But that's userspace (with possible problems in distributing dsdt's, which
is why xdelta might be an acceptable solution), the kernel should just make
something like like that possible, if someone wants to do it.
next prev parent reply other threads:[~2004-10-22 16:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 12:23 Buggy DSDTs policy ? 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 [this message]
2004-10-22 16:44 ` Onur Kucuk
-- strict thread matches above, loose matches on Subject: below --
2004-10-25 5:56 Yu, Luming
2004-10-25 6:21 Yu, Luming
2004-10-25 9:01 ` Pekka Pietikainen
2004-10-25 9:13 ` Xavier Bestel
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=20041022163017.GA18156@ee.oulu.fi \
--to=pp@ee.oulu.fi \
--cc=galibert@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--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.