linux-kernel - Aw: [PATCH v2 0/2] tpm: add driver for cr50 on SPI

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: <trinity-26286f32-3045-4711-8972-ee0964b74003-1469466561717@3capp-gmx-bs15>
Date:	Mon, 25 Jul 2016 19:09:21 +0200
From:	"Peter Huewe" <PeterHuewe@....de>
To:	"Andrey Pronin" <apronin@...omium.org>
Cc:	"Jarkko Sakkinen" <jarkko.sakkinen@...ux.intel.com>,
	"Marcel Selhorst" <tpmdd@...horst.net>,
	"Jason Gunthorpe" <jgunthorpe@...idianresearch.com>,
	tpmdd-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
	"Christophe Ricard" <christophe.ricard@...il.com>,
	"Andrey Pronin" <apronin@...omium.org>
Subject: Aw: [PATCH v2 0/2] tpm: add driver for cr50 on SPI

Hi Andrey,

thanks for the update.

> This patchset adds support for H1 Secure Microcontroller running
> Cr50 firmware. It implements several functions, including TPM-like
> functionality, and communicates over SPI using the FIFO protocol
> described in the PTP Spec, section 6.
> H1 is a proprietary chip that the Chrome OS team is investigating
> for inclusion in future Chromebooks.

so is this "broken" device already in the field? (i.e. can I buy it? how many of them)
from the description it seems not. ("future chromebooks")
--> how likely is it that the firmware of that device will be fixed that it can work with the regular driver?

Although I really like to see driver upstreamed, I also want to avoid maintenance hell for obscure hardware :/

Thanks,
Peter