From: Robert Hancock <hancockrwd@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: matt.causey@gmail.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: Is via-velocity broken in 2.6.34?
Date: Sat, 11 Sep 2010 16:53:18 -0600 [thread overview]
Message-ID: <4C8C085E.4050200@gmail.com> (raw)
In-Reply-To: <20100909.125710.226781968.davem@davemloft.net>
On 09/09/2010 01:57 PM, David Miller wrote:
> From: Matt Causey<matt.causey@gmail.com>
> Date: Thu, 9 Sep 2010 10:42:21 -0700
>
>> So it wasn't immediately intuitive that we would need power
>> management enabled in order to use other parts of the system.
>
> ACPI is not power management.
>
> It's a set of infrastructure (including an interpreter and small
> firmware programs to drive specialized hardware) that allows the
> important details of your motherboard to be described accurately to
> the kernel by firmware authors.
>
> That's why it's called "Advanced Configuration and Power Interface"
> and not just "Advanced Power Interface" :-)
>
> It also provides more accurate tables to describe things like
> the cpus in your system etc., to replace deprecated mechanisms
> for that such as MPS.
I'd think we'd save some trouble if we forced ACPI to on unless EMBEDDED
was set or something, to indicate you shouldn't turn it off unless you
really know what you're doing..
next prev parent reply other threads:[~2010-09-11 22:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinK4VywsJ86jaC8wQjbXjzvP-z44JD3XbZbMM2a@mail.gmail.com>
2010-09-07 23:33 ` Is via-velocity broken in 2.6.34? David Miller
2010-09-08 0:13 ` Matt Causey
2010-09-08 0:24 ` David Miller
2010-09-08 15:27 ` Matt Causey
2010-09-08 15:30 ` David Miller
[not found] ` <AANLkTimRPOD857-pFXUJPxBw0RYXYe8OiPFwisY28x5B@mail.gmail.com>
2010-09-09 19:57 ` David Miller
2010-09-11 22:53 ` Robert Hancock [this message]
[not found] ` <20100907232957.GA11595@electric-eye.fr.zoreil.com>
2010-09-08 0:05 ` Matt Causey
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=4C8C085E.4050200@gmail.com \
--to=hancockrwd@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.causey@gmail.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).