mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "Ronald G. Minnich" <rminnich@lanl.gov>
Cc: Andi Kleen <ak@suse.de>, Li-Ta Lo <ollie@lanl.gov>,
	yhlu <yinghailu@gmail.com>, Stefan Reinauer <stepan@openbios.org>,
	discuss@x86-64.org, LinuxBIOS <linuxbios@openbios.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [discuss] Re: [LinuxBIOS] NUMA support for dual core Opteron
Date: Thu, 14 Jul 2005 21:54:23 +0200	[thread overview]
Message-ID: <20050714195422.GJ23737@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0507141303210.22630@enigma.lanl.gov>

On Thu, Jul 14, 2005 at 01:04:26PM -0600, Ronald G. Minnich wrote:
> 
> 
> On Thu, 14 Jul 2005, Andi Kleen wrote:
> 
> > However you'll likely need ACPI for other reasons anyways, e.g. for
> > better power saving.
> 
> bummer. What the BIOS vendors are doing (to lock in proprietary BIOS, some
> say)  is making ACPI tables copyright the BIOS vendor, not the motherboard 
> vendor. So LinuxBIOS will have to reverse engineer their own, somehow. 

You don't need full support, many of it is optional and will
fall back to the old methods if not available. e.g. you can
probably leave out most of the PCI support if you don't want to support
PCI hotplug. Longer term it might be needed again for power management
though.

Doing PST objects for power saving shouldn't be that difficult, but you
need knowledge of the CPUs from their data sheet (and some testing 
if the power regulators on the mobo can take all the transitions) 
But it shouldn't be very motherboard specific.

However that said there is a lot of useful information
in the FADT and some other tables and I definitely plan to use more of it 
in the future.

-Andi


  reply	other threads:[~2005-07-14 19:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-14 17:58 yhlu
2005-07-14 18:29 ` [LinuxBIOS] " Li-Ta Lo
2005-07-14 18:48   ` [discuss] " Andi Kleen
2005-07-14 18:58     ` yhlu
2005-07-14 19:04     ` Ronald G. Minnich
2005-07-14 19:54       ` Andi Kleen [this message]
2005-07-14 18:48   ` yhlu
2005-07-14 18:52   ` [discuss] " Andi Kleen
2005-07-14 19:00 ` Ronald G. Minnich
2005-07-14 19:09   ` [discuss] " Andi Kleen
2005-07-15  2:46     ` yhlu
2005-07-15  3:05       ` Andi Kleen
2005-07-15  3:52         ` yhlu
2005-07-15  4:05           ` Andi Kleen
2005-07-15  4:14             ` yhlu
2005-07-15 14:37         ` Ronald G. Minnich
2005-07-15 18:15     ` Tom Vier
2005-07-15 18:20       ` 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=20050714195422.GJ23737@wotan.suse.de \
    --to=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxbios@openbios.org \
    --cc=ollie@lanl.gov \
    --cc=rminnich@lanl.gov \
    --cc=stepan@openbios.org \
    --cc=yinghailu@gmail.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

all inboxes | Powered by JetHome®