From: Dave Jones <davej@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: Adrian Bunk <bunk@stusta.de>, Zachary Amsden <zach@vmware.com>,
Arjan van de Ven <arjan@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Christoph Hellwig <hch@infradead.org>,
Rusty Russell <rusty@rustcorp.com.au>, Jack Lo <jlo@vmware.com>,
v4l-dvb-maintainer@linuxtv.org, linux-acpi@vger.kernel.org
Subject: Re: Options depending on STANDALONE
Date: Thu, 3 Aug 2006 16:41:35 -0400 [thread overview]
Message-ID: <20060803204135.GH16927@redhat.com> (raw)
In-Reply-To: <20060803202807.GA7712@kroah.com>
On Thu, Aug 03, 2006 at 01:28:07PM -0700, Greg Kroah-Hartman wrote:
> On Thu, Aug 03, 2006 at 10:25:43PM +0200, Adrian Bunk wrote:
> > ACPI_CUSTOM_DSDT seems to be the most interesting case.
> > It's anyway not usable for distribution kernels, and AFAIR the ACPI
> > people prefer to get the kernel working with all original DSDTs
> > (which usually work with at least one other OS) than letting the people
> > workaround the problem by using a custom DSDT.
>
> Not true at all. For SuSE kernels, we have a patch that lets people
> load a new DSDT from initramfs due to broken machines requiring a
> replacement in order to work properly.
Whilst this is a quick fix for users who either know how to hack DSDTs
themselves, or know where to get a fixed one, it doesn't solve the bigger
problem, that the interpretor doesn't get fixed.
And by 'fixed', I mean we aren't bug for bug compatible with that
other OS. We need to be adding workarounds to the ACPI interpretor
so this stuff 'just works', not hiding from the problem and creating
"but it works in $otherdistro when I do this" scenarios.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-08-03 20:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44D1CC7D.4010600@vmware.com>
[not found] ` <1154603822.2965.18.camel@laptopd505.fenrus.org>
[not found] ` <44D23B84.6090605@vmware.com>
[not found] ` <20060803190327.GA14237@kroah.com>
[not found] ` <44D24B31.2080802@vmware.com>
[not found] ` <20060803193600.GA14858@kroah.com>
[not found] ` <20060803195617.GD16927@redhat.com>
2006-08-03 20:25 ` Options depending on STANDALONE Adrian Bunk
2006-08-03 20:28 ` Greg KH
2006-08-03 20:41 ` Dave Jones [this message]
2006-08-03 23:40 ` [v4l-dvb-maintainer] " Trent Piepho
2006-08-05 10:51 ` Adrian Bunk
2006-08-06 11:18 ` Oliver Endriss
2006-08-13 16:36 ` Adrian Bunk
2006-08-14 21:15 ` Trent Piepho
2006-08-27 21:45 ` Adrian Bunk
2006-08-03 20:49 Brown, Len
2006-08-03 20:51 ` Greg KH
2006-08-03 21:01 ` Dave Jones
2006-08-03 21:41 ` Greg KH
2006-08-07 17:33 ` Thomas Renninger
2006-08-07 17:56 ` Greg KH
2006-08-07 18:46 ` Eric Piel
2006-08-08 11:00 ` Thomas Renninger
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=20060803204135.GH16927@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=bunk@stusta.de \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=jlo@vmware.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@osdl.org \
--cc=v4l-dvb-maintainer@linuxtv.org \
--cc=zach@vmware.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;
as well as URLs for NNTP newsgroup(s).