public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Alice Hennessy <ahennessy@mvista.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: mark.langsdorf@amd.com, mtd@infradead.org
Subject: Re: CFI ident problems with AMD chips.
Date: Tue, 02 Jan 2001 15:27:03 -0800	[thread overview]
Message-ID: <3A5263C6.31F5D67D@mvista.com> (raw)
In-Reply-To: Pine.LNX.4.30.0101022228090.612-100000@imladris.demon.co.uk

David Woodhouse wrote:

> On Tue, 2 Jan 2001, Alice Hennessy wrote:
>
> > > Is there some way to tell the top-boot parts apart from the bottom-boot
> > > parts?
> >
> > In the Am29DL322D/323D/324D spec, there's  a Top/Bottom Boot Sector Flag at
> > the end of the Primary Vendor-Specific Extended Query at address 4F (word mode)
> >
> > where 02 = bottom, 03 = top.   I haven't tried it  yet.
>
> Ah - hadn't found that bit, thanks. I'll poke at it in the morning.
>
> So, are the chips violating the CFI spec by recording the blocks in a
> strange order, or does the CFI spec not actually guarantee an _ordering_
> on the erase regions? It's not clear which is the case - either way,
> _someone_ seems to be on crack here.
>
> --
> dwmw2

I don't see any specific language that states that the regions have to be in order
(too obvious to mention).

BTW,  I tried it and it gives the correct value for my top boot device.

Alice



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2001-01-02 23:25 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
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 [this message]
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=3A5263C6.31F5D67D@mvista.com \
    --to=ahennessy@mvista.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox