LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Len Brown <lenb@kernel.org>
Cc: Thomas Renninger <trenn@suse.de>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-acpi <linux-acpi@vger.kernel.org>,
	Kay Sievers <kasievers@suse.de>
Subject: Re: [PATCH 3/3] ACPI autoloading - Create __mod_acpi_device_table symbol for all acpi drivers.
Date: Tue, 3 Jul 2007 12:06:27 -0300	[thread overview]
Message-ID: <20070703150627.GA32367@khazad-dum.debian.net> (raw)
In-Reply-To: <200707030311.36139.lenb@kernel.org>

On Tue, 03 Jul 2007, Len Brown wrote:
> My $0.02 on thinkpad_acpi & HID's...
> 
> 1. moving to DMI binding from PNP-id binding
> sounds like a step in the wrong direction.

IBM made real use of the DMI data, so they even issued BIOS fixes to get it
right when crap made it to the DMI tables.  I am not sure Lenovo will keep
up the good work, but so far they did not do anything braindamaged to the
DMI tables AFAIK.

And we have a damn good table of the more interesting DMI data, which the
community maintains.  It is at http://www.thinkwiki.org/wiki/List_of_DMI_IDs
so I have a lot of support to take DMI-based decisions.

Note that I can use PNP-id autoload as well as the DMI-based one, it just
won't buy much.  AFAIK the driver already auto-loads on every supported
thinkpad, including new ones.

As for using PNP-id autoloading instead of DMI-based autoloading, I have two
problems with it:

	1. I don't trust IBM0068 more than the dmi data.  If you can assure
	me IBM0068 is only used for thinkpad laptops, because that's how
	these things work or somesuch, then I might change my mind.

	2. Lots of what thinkpad-acpi does has nothing to do with IBM0068.
	Autoloading based only on IBM0068 seems wrong to me, in this case.

> Are there thinkpads that you need to support that don't export IBM0068?

There could be, especially the very old ones that thinkpad-acpi partially
supports.  AFAIK, IBM0068 is a firmware-OS message-passing device, and also
hot key handler.  But it does little else.  Most of the other stuff is done
by directly poking stuff in different ACPI subtrees, or ACPI EC registers,
or accessing the CMOS NVRAM, and those have no unique HIDs...

> There is a long tradition of DMI information being copy/pasted
> and being invalid.  While the thinkpad BIOS guys are probably
> above average here, they're probably not immune from this issue.

No, they are not imune :-)  Some thinkpads have had slightly screwed up dmi
tables, but none due to something as ridiculous as copy-and-paste, and IBM
issued BIOS updates to fix the breakages.  Lenovo didn't break anything in
DMI so far, either (AFAIK, anyway).

> At the end of the day, I'd be astonished if somebody told me that
> the Windows thinkpad platform driver binds via DMI strings instead
> of binding to IBM0068 -- which was likely invented for this sole purpose.

They bind by HID, I think.  But I don't know what *else* they check before
they decide to load sucessfully.  If anyone would like to do some clean-room
reverse engineering of the windows drivers and send us the information,
fine, I'd welcome the information and use it.  But I am not touching the
Windows drivers.

Also, there are a number of different drivers, and AFAIK only the hot keys
one bind by HID.  I have not ever touched the Windows drivers, I just used
the thinkpad for a while with Windows to learn how it was supposed to act to
different events, but that's it.

> 2. IBM_PCI_HID = ACPI_PCI_HOST_HID = PCI_ROOT_HID_STRING = "PNP0A03"
> 
> There is nothing IBM specific about a PCI root bridge.
> If you need to use this one, please call it PCI_ROOT_HID_STRING.

Sure, it is something internal to the driver, and *IT MUST NOT BE USED FOR
AUTOLOADING*.  I will rename it, or get rid of it.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  reply	other threads:[~2007-07-03 15:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-17 20:24 [PATCH 1/3] ACPI autoloading - ACPICA adjustance Thomas Renninger
2007-06-17 20:27 ` [PATCH 2/3] ACPI autoloading - Create acpi alias interface Thomas Renninger
2007-06-17 20:24   ` [PATCH 3/3] ACPI autoloading - Create __mod_acpi_device_table symbol for all acpi drivers Thomas Renninger
2007-06-17 22:49     ` Henrique de Moraes Holschuh
2007-06-19 12:53       ` Thomas Renninger
2007-06-19 16:23         ` Mattia Dongili
2007-06-19 21:27         ` Henrique de Moraes Holschuh
2007-07-03  7:11           ` Len Brown
2007-07-03 15:06             ` Henrique de Moraes Holschuh [this message]
2007-06-20 17:06     ` Mattia Dongili
2007-06-20 17:47       ` Thomas Renninger
2007-06-21  4:16         ` Mattia Dongili
2007-07-03  7:15         ` Len Brown
2007-07-04  7:33           ` Mattia Dongili
2007-07-04 10:17             ` Thomas Renninger
2007-06-20 15:52   ` [PATCH 2/3] ACPI autoloading - Create acpi alias interface Mattia Dongili
2007-06-20 17:24     ` Thomas Renninger
2007-07-03  7:58 ` [PATCH 1/3] ACPI autoloading - ACPICA adjustance Len Brown
2007-07-03 12:23   ` Thomas Renninger

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=20070703150627.GA32367@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=kasievers@suse.de \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trenn@suse.de \
    --subject='Re: [PATCH 3/3] ACPI autoloading - Create __mod_acpi_device_table symbol for all acpi drivers.' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).