From: David Woodhouse <dwmw2@infradead.org>
To: simon.munton@talk21.com
Cc: mtd@infradead.org
Subject: Re: (No Subject)
Date: Tue, 24 Apr 2001 15:46:26 +0100 [thread overview]
Message-ID: <3311.988123586@redhat.com> (raw)
In-Reply-To: <20010424113037.FQCK11909.t21mta02-app.talk21.com@t21mtaV-lrs>
simon.munton@talk21.com said:
> Back in January, I posted a similar question about the unlock bypass
> mode.
> Unfortunately, I've been busy on other things since then, so I've not
> been able to follow up on it.
Yes, it's currently broken. It should probably be disabled unless someone
cares sufficiently to fix it, and can show that it's actually an advantage to
disable interrupts in return for the (probably minimal) speedup.
simon.munton@talk21.com said:
> I've also noticed that CFI_DEVICETYPE_X8 is used in several places,
> where it seems that cfi->device_type should be used instead (one
> instance is in issuing the enter bypass mode commands).
The unlock addresses are set with that fact taken into consideration. The
reason is that some devices with DEVICETYPE_16 need unlock addresses which
are odd, for which the 'multiply by two' doesn't help us much :)
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-04-24 14:46 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 11:29 (No Subject) simon.munton
2001-04-24 14:46 ` David Woodhouse [this message]
2001-04-25 9:51 ` Masami Komiya
2001-04-25 10:26 ` David Woodhouse
2001-04-25 12:19 ` Masami Komiya
2001-04-25 12:26 ` David Woodhouse
2001-04-25 12:55 ` Masami Komiya
2001-04-25 13:30 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-05-02 15:17 (no subject) Zydla Tsui
2001-05-02 15:24 zud sdf
2001-05-02 15:32 ` David Woodhouse
2001-05-02 15:29 zud sdf
2001-05-02 15:59 zud sdf
2001-09-14 16:25 Siders, Keith
2001-09-14 16:32 ` David Woodhouse
2001-09-14 20:11 Siders, Keith
2001-12-19 19:01 ilatypov
2001-12-28 23:48 Sheela Kashyap
2001-12-28 23:52 ` David Woodhouse
2002-01-02 23:57 ` Sheela Kashyap
2002-01-03 0:06 ` David Woodhouse
2002-01-03 0:27 ` Sheela Kashyap
2002-01-03 9:26 ` David Woodhouse
2002-01-03 18:57 ` Sheela Kashyap
2002-01-03 15:46 Allen Curtis
2002-03-15 4:15 Jim Zeus
2002-03-15 9:27 ` David Woodhouse
2002-03-15 9:55 Jim Zeus
2002-03-15 10:15 ` David Woodhouse
2002-03-17 10:21 Jim Zeus
2002-03-17 10:32 ` David Woodhouse
2002-03-18 7:42 Jim Zeus
2002-03-18 8:38 ` David Woodhouse
2002-03-19 7:59 Jim Zeus
2002-03-27 8:01 Jim Zeus
2002-03-27 8:06 ` David Woodhouse
2002-04-11 6:13 Jim Zeus
2002-04-19 3:23 swimming_fisher
2002-04-29 14:19 Jim Zeus
2002-05-03 11:46 victor.martin
2002-06-19 2:24 Áº²¨
2002-07-02 17:00 Roy Lauer
2002-07-15 10:25 Valls Pellicer,Joan
2002-11-15 20:58 Wauviel
2002-11-19 21:13 BBRAM Jörn Engel
2002-11-20 2:01 ` (no subject) Taeil Um
2002-11-20 7:20 ` David Woodhouse
2002-11-21 8:40 ` Taeil Um
2004-11-16 11:42 Artem B. Bityuckiy
2004-11-16 13:48 Artem B. Bityuckiy
2004-11-16 13:55 ` David Woodhouse
2005-06-21 14:48 David L
2005-07-03 2:47 Amit Sharma
2005-07-03 12:04 ` Artem B. Bityuckiy
2005-07-18 12:06 murasfdg sjhfsd
2005-07-23 4:50 Mr.Derrick Tanner.
2005-09-15 13:22 Konstantin Kletschke
2005-10-20 16:05 Korolev, Alexey
2006-03-10 13:57 Selmeci, Tamas
2009-05-18 12:20 Mnl
2009-05-18 15:18 Mnl
2009-06-01 11:20 Mnl
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=3311.988123586@redhat.com \
--to=dwmw2@infradead.org \
--cc=mtd@infradead.org \
--cc=simon.munton@talk21.com \
/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