From: David Vrabel <dvrabel@arcom.com>
To: linux-mtd list <linux-mtd@lists.infradead.org>
Subject: Re: Why CFI_DEVICETYPE_X8 in cfi_send_gen_cmd()?
Date: Fri, 27 Feb 2004 10:03:43 +0000 [thread overview]
Message-ID: <403F15FF.5010307@arcom.com> (raw)
In-Reply-To: <3236F92B82933347807DFF6A8BA632802133B9@wcosmb04.cos.agilent.com>
> Could you please explain why the cfi->addr_unlock1 is 0x1555 in the
> case of CFI_DEVICETYPE_X32?
Nope. I can't. No 32 bit chips here. It looks wrong to me though.
David Vrabel
--
David Vrabel, Design Engineer
Arcom, Clifton Road Tel: +44 (0)1223 411200 ext. 3233
Cambridge CB1 7EA, UK Web: http://www.arcom.com/
next parent reply other threads:[~2004-02-27 10:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3236F92B82933347807DFF6A8BA632802133B9@wcosmb04.cos.agilent.com>
2004-02-27 10:03 ` David Vrabel [this message]
2004-02-25 1:24 Why CFI_DEVICETYPE_X8 in cfi_send_gen_cmd()? Shawn Jin
2004-02-25 11:08 ` David Vrabel
2004-02-25 12:31 ` 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=403F15FF.5010307@arcom.com \
--to=dvrabel@arcom.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