From: Tolunay Orkun <listmember@orkun.us>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] cfi_flash.c bug regarding intel k3 devices
Date: Thu, 12 May 2005 11:15:14 -0500 [thread overview]
Message-ID: <42838112.6090805@orkun.us> (raw)
In-Reply-To: <20050512142803.GA4333@synertronixx3>
Konstantin Kletschke wrote:
> Hi!
>
> cfi_flash.c handles intel k3 devices not correct, they power up with all
> sectors locked. Similair to flash_unlock_seq for amd devices, there must exist
> a flash_unlock_seq_intelk3 to do this for intel devices.
Why do you need this? Can't you just use "protect off" command to unlock
the sectors you need to write? I think issuing automatic unlock commands
prior to write/erase is against the sprit of protection.
Best regards,
Tolunay
next prev parent reply other threads:[~2005-05-12 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 14:28 [U-Boot-Users] cfi_flash.c bug regarding intel k3 devices Konstantin Kletschke
2005-05-12 14:45 ` Konstantin Kletschke
2005-10-08 23:18 ` Wolfgang Denk
2005-05-12 16:15 ` Tolunay Orkun [this message]
2005-05-12 19:56 ` Konstantin Kletschke
2005-05-12 22:13 ` Tolunay Orkun
2005-05-12 22:24 ` Konstantin Kletschke
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=42838112.6090805@orkun.us \
--to=listmember@orkun.us \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox