| 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: <1154680873.31031.182.camel@shinybook.infradead.org> Date: Fri, 04 Aug 2006 16:41:12 +0800 From: David Woodhouse <dwmw2@...radead.org> To: Haavard Skinnemoen <hskinnemoen@...el.com> Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH] MTD: Add lock/unlock operations for Atmel AT49BV6416 On Fri, 2006-08-04 at 10:28 +0200, Haavard Skinnemoen wrote: > What's the best way to do this? Unlock the flash in the board-specific > mapping driver perhaps? That's what we used to do. If more people are emulating the Intel brain damage and having chips which render the lock operation entirely pointless by locking the chips at every power cycle, then I suppose we ought to consider making auto-unlock a function of the chip type. -- dwmw2 - 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