From: Clive Davies <cdavies@altera.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] add access to AMD secure silicon area
Date: Tue, 15 Oct 2002 11:25:09 +0100 [thread overview]
Message-ID: <200210151025.g9FAP9221781@localhost.localdomain> (raw)
In-Reply-To: <19345.1034676569@passion.cambridge.redhat.com>
>
> + cfi_send_gen_cmd(0xAA, cfi->addr_unlock1, chip->start, map, cfi,
> CFI_DEVICETYPE_X8, NULL); + cfi_send_gen_cmd(0x55, cfi->addr_unlock2,
> chip->start, map, cfi, CFI_DEVICETYPE_X8, NULL); + cfi_send_gen_cmd(0x90,
> cfi->addr_unlock1, chip->start, map, cfi, CFI_DEVICETYPE_X8, NULL);
> + cfi_send_gen_cmd(0x00, cfi->addr_unlock1, chip->start, map, cfi,
> CFI_DEVICETYPE_X8, NULL);
>
> Is this always correct?
It should be, it matches the command sequence in the data sheet for the
AM29DL322D/323D/324D devices.
>
> + /* does this chip even have a secsi area? */
> + if(cfi->mfr!=1)
> + return -EINVAL;
> + switch(cfi->id){
> + case 0x50:
> + case 0x53:
> + case 0x55:
> + case 0x56:
> + case 0x5C:
> + case 0x5F:
> + break;
> + default:
> + return -EINVAL;
>
> Er, is this information not available from the CFI info? I really want to
> avoid having stuff like this in the chip drivers.
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.
Clive
next prev parent reply other threads:[~2002-10-15 10:26 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 [this message]
2002-10-15 10:36 ` David Woodhouse
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=200210151025.g9FAP9221781@localhost.localdomain \
--to=cdavies@altera.com \
--cc=dwmw2@infradead.org \
--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