All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Henrique de Moraes Holschuh <hmh@debian.org>
Cc: Shem Multinymous <multinymous@gmail.com>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Matt Domsch <Matt_Domsch@dell.com>,
	"Brown, Len" <len.brown@intel.com>
Subject: Re: [PATCH] DMI: Decode and save OEM String information
Date: Fri, 28 Jul 2006 12:37:45 -0600	[thread overview]
Message-ID: <200607281237.45576.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <20060728124940.GA26735@khazad-dum.debian.net>

On Friday 28 July 2006 06:49, Henrique de Moraes Holschuh wrote:
> On Thu, 27 Jul 2006, Bjorn Helgaas wrote:
> > > > If that's true, isn't it a BIOS defect if this embedded controller isn't
> > > > described via ACPI?
> > > 
> > > The ThinkPad ACPI tables do list the relevant IO ports (0x1600-0x161F)
> > > as reserved, but provide no way to discern what's behind them.
> > 
> > How are they listed?  Maybe an example would help.  Do you mean the
> 
> In the T43, very recent BIOS, it is inside _SB_.PCI0.LPC.SIO, where _HID is
> PNP0C02, and it holds resources to a number of different devices.  Port 1600
> is not even in a block by itself, it is in a block that reserves 0x42 bytes,
> while the EC occupies just 0x1600-0x161F.

And there are no other devices that consume 0x1600-0x161F?  Interesting.
I wonder what Windows does to bind drivers to the LPC devices?  Do they
have to do the same SMBIOS OEM string hack?

> The table (within the driver, for whitelisting) has exactly *one* substring
> for string match, that works for all models since the A31, and maybe even
> earlier ones.  The OEM string table used by IBM is quite stable.

I guess as long as they change the OEM string the same time they change
the EC/accelerometer/battery/kitchen-sink implementation, you're OK :-)
It just feels like living on borrowed time.

  reply	other threads:[~2006-07-28 18:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27 13:47 [PATCH] DMI: Decode and save OEM String information Shem Multinymous
2006-07-27 16:10 ` Bjorn Helgaas
2006-07-27 16:42   ` Shem Multinymous
2006-07-28  3:27     ` Bjorn Helgaas
2006-07-28 12:49       ` Henrique de Moraes Holschuh
2006-07-28 18:37         ` Bjorn Helgaas [this message]
2006-07-28 20:52           ` Shem Multinymous
2006-07-28 21:08             ` Bjorn Helgaas
2006-07-28 22:07               ` Shem Multinymous
2006-07-29 12:55 ` Shem Multinymous
2006-07-29 16:29   ` Carl-Daniel U. Hailfinger
2006-07-29 17:09     ` Shem Multinymous
2006-08-02 12:19     ` Pavel Machek
2006-08-02 10:39 ` Pavel Machek

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=200607281237.45576.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas@hp.com \
    --cc=Matt_Domsch@dell.com \
    --cc=hmh@debian.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=multinymous@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 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.