From: David Woodhouse <dwmw2@infradead.org>
To: Clive Davies <cdavies@altera.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] add access to AMD secure silicon area
Date: Tue, 15 Oct 2002 11:36:44 +0100 [thread overview]
Message-ID: <26135.1034678204@passion.cambridge.redhat.com> (raw)
In-Reply-To: <200210151025.g9FAP9221781@localhost.localdomain>
cdavies@altera.com said:
> It should be, it matches the command sequence in the data sheet for
> the AM29DL322D/323D/324D devices.
And CFI_DEVICETYPE_X8 is always correct? No X16 devices?
> Unfortunately not. There's no mention of it at all in the AMD primary
> vendor specific extended query table v1.1 which is used on these
> devices. I don't like this method either but in the absence of CFI
> info I don't have any better ideas.
Argh. FFS. So AMD can't manage to get the fscking erasesize table correct
in the CFI data, and they can't manage to add the appropriate fields to
their own vendor-specific table to remove the need to keep the device ID
tables which CFI was supposed to eliminate?
Would someone from AMD care to either contradict me or promise me
faithfully that they've taken a baseball bat to whoever is responsible?
I suspect we need a new 'amd_is_bloody_stupid_probe' alongside jedec_probe
and cfi_probe :)
--
dwmw2
next prev parent reply other threads:[~2002-10-15 10:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 8:16 [PATCH] add access to AMD secure silicon area Clive Davies
2002-10-15 10:09 ` David Woodhouse
2002-10-15 10:25 ` Clive Davies
2002-10-15 10:36 ` David Woodhouse [this message]
2002-10-15 13:21 ` Clive Davies
2002-10-15 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=26135.1034678204@passion.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=cdavies@altera.com \
--cc=linux-mtd@lists.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