linux-kernel - Re: [RFC PATCHv2 0/4] Support for OTP memory

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: <20110324183205.GI3130@pulham.picochip.com>
Date:	Thu, 24 Mar 2011 18:32:05 +0000
From:	Jamie Iles <jamie@...ieiles.com>
To:	Mike Frysinger <vapier@...too.org>
Cc:	Jamie Iles <jamie@...ieiles.com>, linux-kernel@...r.kernel.org,
	gregkh@...e.de
Subject: Re: [RFC PATCHv2 0/4] Support for OTP memory

On Thu, Mar 24, 2011 at 01:56:17PM -0400, Mike Frysinger wrote:
> just an overview note here ... the Blackfin OTP is actually IP we
> bought from someone (not sure if i can say more, although i dont know
> the details myself ... i'd have to go ask around), so much of the
> feedback i give about the structure of it most likely (hopefully) be
> applicable to other people who have purchased this IP.  if/when anyone
> who is also using this IP steps forward, we could even see about
> generalizing the bfin-otp driver.

Yes, we have a similar thing here - a block of OTP from an IP vendor and 
a wrapper to provide an AXI interface.  As far as I know there are only 
a few OTP vendors so there may well be plenty of common code in 
different OTP implementations.

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