| 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
| ||
|
Message-ID: <AANLkTinDWA1xU1G0kBk8XPr_ZaRgHtBQP60DX6-x3tsn@mail.gmail.com> Date: Thu, 24 Mar 2011 13:56:17 -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 13:47, Jamie Iles wrote: > On Thu, Mar 24, 2011 at 01:39:56PM -0400, Mike Frysinger wrote: >> On Thu, Mar 24, 2011 at 11:21, Jamie Iles wrote: >> > 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 ! > > That sounds very familiar! 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. -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/
Powered by blists - more mailing lists