public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ronald G Minnich <rminnich@lanl.gov>
To: yhlu <yinghailu@gmail.com>
Cc: Andi Kleen <ak@suse.de>,
	discuss@x86-64.org, linuxbios@openbios.org,
	yhlu <yhlu.kernel@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [LinuxBIOS] x86_64: apic id lift patch
Date: Wed, 23 Nov 2005 13:23:41 -0700	[thread overview]
Message-ID: <4384CFCD.9010304@lanl.gov> (raw)
In-Reply-To: <2ea3fae10511230919l4d9829d8j3ce5d820b74074d1@mail.gmail.com>

yhlu wrote:
> sth about SRAT in LinuxBIOS,  I have put SRAT dynamically support in 
> LinuxBIOS, but the whole acpi support still need dsdt, current we only 
> have dsdt for AMD chipset in LB. And we can not have the access the dsdt 
> asl from Nvidia chipset yet...

yeah, this is the great thing about ACPI, it has put us into a whole new 
  era of copyrighted stuff. ACPI tables describe hardware, and are 
copyright bios vendors. The question of which ACPI bits we can use in 
linuxbios is unresolved. AMD has committed to open-source ACPI tables, 
but ... what about companies like nvidia? unknown. And, to add to the 
fun, the mainboard vendors don't own their own ACPI tables -- the BIOS 
vendors do. So the mainboard vendor has their hardware design encoded 
into ACPI tables, which are copyright the bios vendor, not the mainboard 
vendor.

ACPI is a looming problem for all the open-source bios efforts out there.

I don't much like ACPI. It's just another mechanism for hiding 
information and limiting its distribution.

ron

  parent reply	other threads:[~2005-11-23 20:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 21:49 x86_64: apic id lift patch yhlu
2005-11-21 22:06 ` Andi Kleen
2005-11-21 22:17   ` yhlu
2005-11-21 22:24     ` Andi Kleen
2005-11-21 22:31       ` yhlu
2005-11-22  9:44         ` Andi Kleen
2005-11-23 16:58   ` [LinuxBIOS] " Ronald G Minnich
2005-11-23 17:35     ` Andi Kleen
     [not found]       ` <2ea3fae10511230943y5f697eb8sdbf891497fa8b88f@mail.gmail.com>
2005-11-23 17:50         ` Andi Kleen
2005-11-23 18:01           ` yhlu
2005-11-23 20:29             ` [discuss] " Andi Kleen
2005-11-23 20:29               ` Ronald G Minnich
2005-11-23 18:28       ` Stefan Reinauer
2005-11-23 20:26       ` Ronald G Minnich
     [not found]     ` <2ea3fae10511230919l4d9829d8j3ce5d820b74074d1@mail.gmail.com>
2005-11-23 17:36       ` Andi Kleen
2005-11-23 17:40         ` yhlu
2005-11-23 18:18           ` Stefan Reinauer
2005-11-23 18:22             ` yhlu
2005-11-23 18:35               ` yhlu
2005-11-23 20:28                 ` [discuss] " Andi Kleen
2005-11-23 18:17         ` Stefan Reinauer
2005-11-23 20:23       ` Ronald G Minnich [this message]
2005-11-23 20:34         ` [discuss] " 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=4384CFCD.9010304@lanl.gov \
    --to=rminnich@lanl.gov \
    --cc=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxbios@openbios.org \
    --cc=yhlu.kernel@gmail.com \
    --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