All of lore.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Sur3 <sur3@gmx.de>
Cc: linux-acpi@vger.kernel.org
Subject: Re: dmidecode to linux-acpi@vger.kernel.org - SANTA ROSA CRB
Date: Sun, 20 Jan 2008 19:37:25 -0500	[thread overview]
Message-ID: <200801201937.25476.lenb@kernel.org> (raw)
In-Reply-To: <47923589.9090506@gmx.de>

On Saturday 19 January 2008 12:38, Sur3 wrote:
> Len Brown schrieb:
> > is this a production system?
> > If yes, can you upgrade to a production BIOS?
> > 
> > then...
> > 
> > Do you notice any functional difference when booting with
> > 
> > "acpi_osi=Linux"        (default for 2.6.22 and earlier)
> > vs.
> > "acpi_osi=!Linux"       (default for 2.6.23 and later)
> > 
> > Also, please send me the output from acpidump.
> > 
> > thanks,
> > -Len
> > 
> > ps
> > If you don't have acpidump, you can get it from pmtools here:
> > http://www.lesswatts.org/projects/acpi/utilities.php
> 
> 
> hi Len,
> the acpidump is in the attachment.
> what do you mean by "production system"?

This system seems to be running the BIOS from an Intel example design,
which is an example implementation for our customers, not intended
really for retail systems.

> it's kind of a normal laptop.

I'm curious what brand and what model it is.

> i'll check for differences with the different boot-params the next days...

You don't have to, OSI(Linux) is a NOP in this BIOS.
Like many others, it sets LINX, but never uses it.

It does remind me to ping the BIOS group and verify
that they've delted this from their latest BIOS.

maybe I should update the dmesg to say:

BIOS BUG: Please tell your BIOS vendor not to query _OSI(Linux)

thanks,
-Len

      parent reply	other threads:[~2008-01-21  0:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-23 13:06 dmidecode to linux-acpi@vger.kernel.org Sur3
     [not found] ` <200801182352.18426.lenb@kernel.org>
     [not found]   ` <47923589.9090506@gmx.de>
2008-01-21  0:37     ` Len Brown [this message]

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=200801201937.25476.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=sur3@gmx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.