From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Where does U-Boot's CFI driver check for top/bottom boot?
Date: Sat, 4 Nov 2006 11:03:12 +0100 (MET) [thread overview]
Message-ID: <200611041104.36057.sr@denx.de> (raw)
In-Reply-To: <454BC9B3.8030806@orkun.us>
Hi Tolunay,
On Friday 03 November 2006 23:58, Tolunay Orkun wrote:
> I just looked at the datasheet of your flash part as well as datasheet
> of a couple of intel flash parts as well as the current code. As I
> suspected for your particular part, it looks like they are using the
> same values for "Erase Bank Area 1" and "Erase Bank Area 2" irrespective
> of top boot or bottom boot flash. I think, this is fundamentally wrong
> and non-compliant with the general CFI standard.
>
> I will look at some AMD part datasheets. If this is generally available
> on all AMD and AMD like parts, we can add it as a patch for AMD only.
> Otherwise, we will either add CONFIG_GEOMETRY_REVERSED definition or
> restrict a patch to specific vendor ids (and possibly part ids) which is
> then a pain to manage.
I suggest that we also look at the linux mtd cfi driver to see, if and how
those devices are handled. I remember seeing something like "broken CFI
table" in the linux bootlog on some boards.
Best regards,
Stefan
next prev parent reply other threads:[~2006-11-04 10:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 16:15 [U-Boot-Users] Where does U-Boot's CFI driver check for top/bottom boot? Timur Tabi
[not found] ` <454BC9B3.8030806@orkun.us>
2006-11-04 10:03 ` Stefan Roese [this message]
2006-11-05 7:56 ` Tolunay Orkun
2006-11-05 9:31 ` Wolfgang Denk
2006-11-05 5:51 ` Tolunay Orkun
2006-11-05 7:44 ` Tolunay Orkun
2006-11-06 19:13 ` Timur Tabi
2006-11-06 22:00 ` Timur Tabi
-- strict thread matches above, loose matches on Subject: below --
2006-11-06 22:27 Yogi
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=200611041104.36057.sr@denx.de \
--to=sr@denx.de \
--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