From: Pavel Machek <pavel@suse.cz>
To: Alexander Viro <viro@math.psu.edu>
Cc: Jonathan Corbet <corbet@lwn.net>,
"Grover, Andrew" <andrew.grover@intel.com>,
linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: Re: ACPI mentioned on lwn.net/kernel
Date: Mon, 28 Jan 2002 12:15:05 +0000 [thread overview]
Message-ID: <20020128121504.B35@toy.ucw.cz> (raw)
In-Reply-To: <20020125165045.5104.qmail@eklektix.com> <Pine.GSO.4.21.0201251344000.25424-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0201251344000.25424-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Fri, Jan 25, 2002 at 01:49:02PM -0500
Hi!
> > Increasingly, it seems that it will not be possible to use modern hardware
> > without ACPI. So, in a sense, the point will be moot. Certainly it is
> > only a good thing that Linux has a high-quality ACPI implementation in the
> > works, so that users will have the option to use it. I expect that most
> > will happily run it and look no further.
> >
> > But that doesn't change the fact that a lot of people do not like the ACPI
> > standard. There is some selling yet to be done if that dislike is to be
> > overcome.
>
> Well, let's hope that when x86-64 comes out, it will go with saner chipsets.
> Pity that it hadn't happened years ago - world without Itanic would certainly
> be a nicer place...
Can you describe pitfalls to avoid, and mail that to discuss@x86-64.org?
AMD *is* listening.
Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
next prev parent reply other threads:[~2002-01-29 11:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 1:29 Grover, Andrew
2002-01-25 16:50 ` Jonathan Corbet
2002-01-25 18:49 ` Alexander Viro
2002-01-28 12:15 ` Pavel Machek [this message]
2002-01-25 17:55 ` Alan Cox
2002-01-25 18:31 ` [ACPI] " Patrick Mochel
2002-01-25 18:51 ` Alan Cox
2002-01-26 3:37 ` Jamie Lokier
2002-01-26 8:10 ` David Weinehall
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=20020128121504.B35@toy.ucw.cz \
--to=pavel@suse.cz \
--cc=acpi-devel@lists.sourceforge.net \
--cc=andrew.grover@intel.com \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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
Powered by JetHome