From: "Johan Adolfsson" <johan.adolfsson@axis.com>
To: "David Woodhouse" <dwmw2@infradead.org>,
"Jonas Holmberg" <jonas.holmberg@axis.com>
Cc: <mtd@infradead.org>
Subject: Re: Problems with cfi_cmdset_0002.c
Date: Mon, 12 Feb 2001 18:14:40 +0100 [thread overview]
Message-ID: <020701c09517$48fc61e0$0a070d0a@axis.se> (raw)
In-Reply-To: 14127.981995794@redhat.com
Wouldn't it be possible to check both the bootloc and the erase regions and
do something like this? :
(Haven't looked in the code how the cfi structure is typed etc. and may be
totally
out when it comes to what the problem is, but you'll probably get the idea)
flip_cfi_table = 0;
if (bootloc == CFI_TOP_BOOT){
/* We expect the small regions at the top */
if (EraseRegionInfo[0].size <
EraseRegionInfo[cfi->cfiq->NumEraseRegions-1].size){
flip_cfi_table = 1;
} else if (bootloc == CFI_BOTTOM_BOOT){
/* We expect the small regions at the bottom */
if (EraseRegionInfo[0].size >
EraseRegionInfo[cfi->cfiq->NumEraseRegions-1].size){
flip_cfi_table = 1;
}
if (flip_cfi_table){
/* Flip the damn thing */
...
}
/Johan
----- Original Message -----
From: David Woodhouse <dwmw2@infradead.org>
To: Jonas Holmberg <jonashg@axis.com>
Cc: <mtd@infradead.org>
Sent: Monday, February 12, 2001 17:36
Subject: Re: Problems with cfi_cmdset_0002.c
>
> jonas.holmberg@axis.com said:
> > I have now tested with a bottom boot chip also and it works (it is
> > not swapped and should not be). So the problem is how to find out that
> > the top boot chip is a top boot chip. A table does not sound like a
> > very nice solution, but I don't know of any other. The datasheet for
> > the flash chip does not mention the address used to read bootloc:
>
> > bootloc = cfi_read_query(map, (adr+15)*ofs_factor);
>
> The datasheet for the AM29LV320D lists it - page 23 of AMD publication
> #23579, Rev A; issued Nov 1, 2000.
>
> Personally, my inclination would be to return the poxy things to AMD
> complaining that the CFI tables are broken. How many are you buying?
>
> Otherwise, I think the JEDEC ID may be the only option.
>
>
> jonas.holmberg@axis.com said:
> > I haven't got commit access...
>
> Gimme SSH public key.
>
> --
> dwmw2
>
>
>
>
> To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
>
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-02-12 17:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-12 16:31 Problems with cfi_cmdset_0002.c Jonas Holmberg
2001-02-12 16:36 ` David Woodhouse
2001-02-12 17:14 ` Johan Adolfsson [this message]
2001-02-12 17:24 ` David Woodhouse
2001-02-12 17:33 ` Johan Adolfsson
-- strict thread matches above, loose matches on Subject: below --
2001-02-15 15:49 Jonas Holmberg
2001-02-15 13:02 Jonas Holmberg
2001-02-15 12:44 Jonas Holmberg
2001-02-15 12:56 ` David Woodhouse
2001-02-15 11:01 Jonas Holmberg
2001-02-15 11:10 ` David Woodhouse
2001-02-14 15:41 Jonas Holmberg
2001-02-14 15:45 ` David Woodhouse
2001-02-13 12:53 Jamey Hicks
2001-02-13 13:31 ` David Woodhouse
2001-02-13 10:04 Jonas Holmberg
2001-02-13 10:15 ` David Woodhouse
2001-02-13 8:59 Jonas Holmberg
2001-02-13 8:31 Jonas Holmberg
2001-02-13 8:30 ` Johan Adolfsson
2001-02-13 9:17 ` David Woodhouse
2001-02-13 9:27 ` Johan Adolfsson
2001-02-12 12:08 Jonas Holmberg
2001-02-12 13:24 ` David Woodhouse
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='020701c09517$48fc61e0$0a070d0a@axis.se' \
--to=johan.adolfsson@axis.com \
--cc=dwmw2@infradead.org \
--cc=jonas.holmberg@axis.com \
--cc=mtd@infradead.org \
/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