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: <AANLkTim3kMCE=LhCRcUDif8ENSA-E-_Xga5cDSYs0x25@mail.gmail.com>
Date:	Thu, 24 Mar 2011 13:39:56 -0400
From:	Mike Frysinger <vapier@...too.org>
To:	Jamie Iles <jamie@...ieiles.com>
Cc:	linux-kernel@...r.kernel.org, gregkh@...e.de
Subject: Re: [RFC PATCHv2 0/4] Support for OTP memory

On Thu, Mar 24, 2011 at 11:21, Jamie Iles wrote:
> Following some feedback from Greg, I've updated this series to be more
> of a generic OTP layer.  Everything is now registered under the "otp"
> bus and I've also converted the blackfin OTP driver to use this
> framework (which is the only current OTP driver I could find).

really, i'm the only one who wrote a driver ?  that's boring.

i guess this isnt trying to handle OTP stuff that exists in the MTD
layer already ?

> Mike, I wasn't 100% sure how big the blackfin OTP is but I found a
> datasheet talking about 64KB so I've assumed that for now.

the datasheets say 64K *bits* :).  i think all our datasheets tend to
use bits rather than bytes because they're stupid and bigger numbers
always means better parts !

but yes, on-chip OTP on all relevant Blackfin parts today are 8KiB in
size.  0x200 128bit pages is how things are organized.
-mike
--
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/