From: Holger Brunck <holger.brunck@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/4] cfi_flash: Enable PPB protection for all AMD cmdset flash chips
Date: Fri, 07 Dec 2012 10:19:45 +0100 [thread overview]
Message-ID: <50C1B4B1.2010105@keymile.com> (raw)
In-Reply-To: <1354805052-32347-3-git-send-email-sr@denx.de>
Hi Stefan,
On 12/06/2012 03:44 PM, Stefan Roese wrote:
> Not only Spansion supports the Persistent Protection Bits (PPB) locking.
> Other devices like the Micron JS28F512M29EWx also support this type
> of locking/unlocking. Detection of support is done in the same way as
> done for the Spansion chips - via the 0x49 CFI word.
>
> This patch enables this PPB protection mechanism for all AMD type
> (AMD commandset) chips.
>
> Signed-off-by: Stefan Roese <sr@denx.de>
> Cc: Anatolij Gustschin <agust@denx.de>
> Cc: Holger Brunck <holger.brunck@keymile.com>
> ---
> drivers/mtd/cfi_flash.c | 13 +++++--------
> 1 file changed, 5 insertions(+), 8 deletions(-)
>
Tested-by: Holger Brunck <holger.brunck@keymile.com>
Regards
Holger
next prev parent reply other threads:[~2012-12-07 9:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 14:44 [U-Boot] [PATCH 1/4] cfi_flash: Add manufact_match helper function Stefan Roese
2012-12-06 14:44 ` [U-Boot] [PATCH 2/4 v2] cfi_flash: Read PPB sector protection from device for AMD/Spansion chips Stefan Roese
2012-12-07 9:19 ` Holger Brunck
2012-12-06 14:44 ` [U-Boot] [PATCH 3/4] cfi_flash: Enable PPB protection for all AMD cmdset flash chips Stefan Roese
2012-12-07 9:19 ` Holger Brunck [this message]
2012-12-06 14:44 ` [U-Boot] [PATCH 4/4] cfi_flash: Report Advanced Sector Protection (PPB) with flinfo cmd Stefan Roese
2012-12-07 9:20 ` Holger Brunck
2013-01-10 14:33 ` [U-Boot] [PATCH 1/4] cfi_flash: Add manufact_match helper function Stefan Roese
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50C1B4B1.2010105@keymile.com \
--to=holger.brunck@keymile.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.