linux-kernel - Re: [tpmdd-devel] [PATCH 02/13] tpm atmel: Call request

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]

Date:	Wed, 2 Oct 2013 22:36:47 -0600
From:	Jason Gunthorpe <jgunthorpe@...idianresearch.com>
To:	Ashley D Lai <adlai@...ux.vnet.ibm.com>
Cc:	Peter H?we <PeterHuewe@....de>,
	Leonidas Da Silva Barbosa <leosilva@...ux.vnet.ibm.com>,
	linux-kernel@...r.kernel.org, Rajiv Andrade <mail@...jiv.net>,
	tpmdd-devel@...ts.sourceforge.net, Sirrix AG <tpmdd@...rix.com>,
	Teddy Reed <teddy@...sauce.org>
Subject: Re: [tpmdd-devel] [PATCH 02/13] tpm atmel: Call request_region
 with the correct base

On Wed, Oct 02, 2013 at 07:11:14PM -0500, Ashley D Lai wrote:

> > I somewhat have the feeling that we should maybe begin to deprecate
> > the vendor specific 1.1 tpms...

> I agree. If we have a machine to test and it fails then we know we don't
> have a user for this.

Is this driver is only used on IBM systems? If so, will IBM provide
support for those systems on RHEL7? If not the driver can probably
safely be dropped.

The trouble with these old drivers is that they don't follow modern
conventions (there are several little bugs at least) and nobody can
test them to safely fix them.

If you do find hardware, we can at least take a solid run at sprucing
up the testable drivers which should give them more life..

Jason
--
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/