mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: "Duran, Leo" <leo.duran@amd.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Linus Torvalds <torvalds@osdl.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, 07 Oct 2006 07:23:18 +0200	[thread overview]
Message-ID: <1160198598.3000.134.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <4526E175.9090608@garzik.org>

On Fri, 2006-10-06 at 19:06 -0400, Jeff Garzik wrote:
> Duran, Leo wrote:
> > OK, lets' take K8 processor performance states (p-states) as an example:
> > BIOS, which should know 'best' about a given platform, needs to
> > communicate to the OS what 'voltage' (VID code) is correct for given
> > 'frequency' (FID),
> > and it can do that via ACPI processor tables (_PSS). Otherwise, OS code
> > is left with having to manage a HUGE amount 'specifics' (processor
> > models), and endless driver revisions to account for new parts.
> > 
> > So, one can argue that there's merit on having ACPI, it's just a shame
> > when BIOS doesn't get it right! (thus the justification for lack of
> > 'trust'... the same can probably be said about other BIOS issues, not
> > just ACPI)
> 
> That's pretty much it in a nutshell...  Since most BIOS are largely 
> tested and qualified only on That Other OS, Linux often gets the short 
> end of the stick. 

fwiw we're trying to get this changed; Intel released the Linux-ready
firmware developer kit recently which is designed to make it real easy
for bios people to test their bios with linux....

see http://www.linuxfirmwarekit.org

-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com


  reply	other threads:[~2006-10-07  5:24 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 17:10 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
2006-10-06 22:31                       ` Duran, Leo
2006-10-06 23:06                         ` Jeff Garzik
2006-10-07  5:23                           ` Arjan van de Ven [this message]
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=1160198598.3000.134.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=jeff@garzik.org \
    --cc=leo.duran@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --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

all inboxes | Powered by JetHome®