From: Nick Ivanter <nick@auriga.ru>
To: David Woodhouse <dwmw2@infradead.org>
Cc: mark.langsdorf@amd.com, mtd@infradead.org
Subject: Re: CFI ident problems with AMD chips.
Date: Mon, 25 Dec 2000 14:44:02 +0300 [thread overview]
Message-ID: <3A473302.74DD6A6B@auriga.ru> (raw)
In-Reply-To: 4883.977501550@redhat.com
They surely have differnet Device ID's which can be found in a datasheet
and compared with the reported ones.
Nick
David Woodhouse wrote:
> Hi,
>
> I've now started using AMD chips. I have a chip which I believe to be a
> 4MiB part with TOP boot blocks. Should be 63*64KiB erase regions followed by
> 8*8KiB erase regions.
>
> However, the CFI "Erase Block Region" information reports them in the wrong
> order - the 8*8KiB blocks _before_ the 63*64KiB.
>
> Is there some way to tell the top-boot parts apart from the bottom-boot
> parts?
>
> --
> 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:[~2000-12-25 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-22 16:12 CFI ident problems with AMD chips David Woodhouse
2000-12-25 11:44 ` Nick Ivanter [this message]
2000-12-25 11:59 ` David Woodhouse
2001-01-02 18:53 ` Alice Hennessy
2001-01-02 22:30 ` David Woodhouse
2001-01-02 23:27 ` Alice Hennessy
2001-01-02 23:29 ` 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=3A473302.74DD6A6B@auriga.ru \
--to=nick@auriga.ru \
--cc=dwmw2@infradead.org \
--cc=mark.langsdorf@amd.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 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.