linux-kernel - Re: [PATCH] tpm: Autodetect itpm devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4CC6D440.10604@linux.vnet.ibm.com>
Date:	Tue, 26 Oct 2010 11:14:40 -0200
From:	Rajiv Andrade <srajiv@...ux.vnet.ibm.com>
To:	Matthew Garrett <mjg@...hat.com>
CC:	debora@...ux.vnet.ibm.com, m.selhorst@...rix.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tpm: Autodetect itpm devices

On 21/10/10 19:42, Matthew Garrett wrote:
> Some Lenovos have TPMs that require a quirk to function correctly. This can
> be autodetected by checking whether the device has a _HID of INTC0102. This
> is an invalid PNPid, and as such is discarded by the pnp layer - however
> it's still present in the ACPI code, so we can pull it out that way. This
> means that the quirk won't be automatically applied on non-ACPI systems,
> but without ACPI we don't have any way to identify the chip anyway so I
> don't think that's a great concern.
>
> Signed-off-by: Matthew Garrett<mjg@...hat.com>
Thanks Matthew,

I'd be glad to remove the module option after this patch, but the 
non-ACPI case wouldn't
remain covered indeed.

Acked-by: Rajiv Andrade <srajiv@...ux.vnet.ibm.com>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/