From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Arjan van de Ven <arjan@infradead.org>,
Jeff Garzik <jeff@garzik.org>, Andi Kleen <ak@suse.de>,
discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] Re: Please pull x86-64 bug fixes
Date: Sat, 7 Oct 2006 00:01:01 +0200 [thread overview]
Message-ID: <200610070001.01752.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.64.0610060906140.3952@g5.osdl.org>
On Friday, 6 October 2006 18:07, Linus Torvalds wrote:
>
> On Fri, 6 Oct 2006, Arjan van de Ven wrote:
> >
> > we can do a tiny bit better than the current code; some chipsets have
> > the address of the MMIO region stored in their config space; so we can
> > get to that using the old method and validate the acpi code with that.
>
> Yes. I think trusting ACPI is _always_ a mistake. It's insane. We should
> never ask the firmware for any data that we can just figure out ourselves.
>
> And we should tell all hardware companies that firmware tables are stupid,
> and that we just want to know what the hell the registers MEAN!
>
> I've certainly tried to tell Intel that. I think they may even have heard
> me occasionally.
>
> I can't understand why some people _still_ think ACPI is a good idea..
I violently agree.
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
next prev parent reply other threads:[~2006-10-06 22:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 17:10 Please pull x86-64 bug fixes Andi Kleen
2006-10-05 17:17 ` Jeff Garzik
2006-10-05 17:31 ` [discuss] " Andi Kleen
2006-10-05 17:43 ` Jeff Garzik
2006-10-05 17:53 ` Andi Kleen
2006-10-05 19:29 ` Jeff Garzik
2006-10-05 19:42 ` Andi Kleen
2006-10-05 20:02 ` Jeff Garzik
2006-10-05 20:10 ` Andi Kleen
2006-10-05 22:45 ` Linus Torvalds
2006-10-05 22:52 ` Andi Kleen
2006-10-05 23:07 ` Linus Torvalds
2006-10-05 23:21 ` Andi Kleen
2006-10-05 23:36 ` Jeff Garzik
2006-10-06 0:57 ` Jeff Garzik
2006-10-06 1:29 ` Linus Torvalds
2006-10-06 11:03 ` Arjan van de Ven
2006-10-06 16:07 ` Linus Torvalds
2006-10-06 16:19 ` Arjan van de Ven
2006-10-06 22:01 ` Rafael J. Wysocki [this message]
2006-10-06 22:31 ` Duran, Leo
2006-10-06 23:06 ` Jeff Garzik
2006-10-07 5:23 ` Arjan van de Ven
2006-10-07 2:20 ` Linus Torvalds
2006-10-08 20:59 ` Duran, Leo
2006-10-08 22:42 ` Linus Torvalds
2006-10-05 22:00 ` Alan Cox
2006-10-05 21:44 ` Andi Kleen
2006-10-06 11:14 ` Alan Cox
2006-10-16 12:21 ` Andi Kleen
2006-10-05 17:21 ` Linus Torvalds
2006-10-05 17:27 ` [discuss] " Andi Kleen
2006-10-05 22:59 ` Linus Torvalds
2006-10-05 23:05 ` Andi Kleen
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=200610070001.01752.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=ak@suse.de \
--cc=arjan@infradead.org \
--cc=discuss@x86-64.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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