From: Bill Burgess <burgess@greeneridge.com>
To: <linux-mtd@lists.infradead.org>
Subject: 576-MB DOC reports as Millennium?
Date: Wed, 31 Jul 2002 20:23:37 -0700 [thread overview]
Message-ID: <20020801032337.18882@smtp.impulse.net> (raw)
Doc2000.c can't seem to handle the new 576-MB DoC's.
The docprobe.c driver (version 1.30) reports them as
Millenniums, but then doc2000.c (version 1.46) fails
to access the mfr or id using Millennium-oriented calls;
these come back 0xff or 0. If I force the ChipID to be
a 2000, docprobe doesn't even get past the initial toggle
test. Also like a blank Millennium, there is no 0x55aa
signature at the base address, only 0xffff.
The 576's have NOT been formatted with DFORMAT
or anything else, they came raw. However what I am
attempting is so low-level, the formatting should be
irrelevant -- shouldn't it??
I am not actually using Linux, but have incorporated
the drivers into a low-level custom system based on
a 68K. The drivers have worked beautifully for months.
Even now I can swap an 8-MB or a 288-MB DOC2000
into the socket and they work fine. So I don't think
it's my platform that's suddenly gone off.
If the solution is not obvious or quick I will have
to buy some 288's very soon, which will hurt as I have
already bought the 576's :-< Help!
Cheers & thanks!
--Bill
_________________________________________________________
William C. Burgess, Ph.D., Senior Research Engineer
Greeneridge Sciences Inc., 1411 Firestone Rd., Goleta, CA 93117
Tel: (805) 899-3558 Fax: (805) 967-7720
http://www.greeneridge.com
next reply other threads:[~2002-08-01 3:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 3:23 Bill Burgess [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-01 3:46 576-MB DOC reports as Millennium? Vadim Khmelnitsky
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=20020801032337.18882@smtp.impulse.net \
--to=burgess@greeneridge.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