From: Onur Kucuk <onur@delipenguen.net>
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: pp@ee.oulu.fi, galibert@pobox.com, linux-kernel@vger.kernel.org
Subject: Re: Buggy DSDTs policy ?
Date: Fri, 22 Oct 2004 19:44:06 +0300 [thread overview]
Message-ID: <20041022194406.330004e1.onur@delipenguen.net> (raw)
In-Reply-To: <1098459316.31003.93.camel@gonzales>
Xavier Bestel wrote:
> Le ven 22/10/2004 à 17:19, Pekka Pietikainen a écrit :
> > On Fri, Oct 22, 2004 at 04:55:35PM +0200, Xavier Bestel wrote:
> > > > CONFIG_ACPI_CUSTOM_DSDT is included in 2.6.9
> > >
> > > But fixed DSDTs are a pain to find, and fixing a buggy DSDT is
> > > impossible for a non-hacker.
> > >
> > http://acpi.sourceforge.net/dsdt/index.php has quite a few.
>
> .. which aren't all proper fixes (I tried the DSDT for Armada 1700,
> it's a partial fix only).
This can be an issue to work on. I am sure acpi people won't reject
proper fixes.
> > 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.
The initrd approach seems nicer and more customisable.
> Yes, sure. But real non-technical people won't replace their DSDT
> either.
Real non-technical people follow their distros. They don't need to
recompile a kernel of their own. It is a distro's job for them.
--
Onur Kucuk Knowledge speaks,
<onur.--.-.delipenguen.net> but wisdom listens
next prev parent reply other threads:[~2004-10-22 16:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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=20041022194406.330004e1.onur@delipenguen.net \
--to=onur@delipenguen.net \
--cc=galibert@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pp@ee.oulu.fi \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®