On 7/28/06, Bjorn Helgaas <[email protected]> wrote:
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?
We don't know. Maybe they check the ThinkPad part number (of which
there are many hundreds but IBM/Lenovo has the full list and can
update the driver whenever a new model comes out); or maybe just
assume you won't install it on the wrong hardware.
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.
Yes. But it's the best we've been able to come up with, after
considerable community effort.
Anyway, this patch is independent of the ThinkPad case; DMI
information is there for drivers to see it, after all, so the kernel
should make it possible. Can I get a Signed-off-by?
Shem
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
