From: Ollie Lho <ollie@sis.com.tw>
To: Pete Skelly <pete.skelly@astanetworks.com>
Cc: "'mtd@infradead.org'" <mtd@infradead.org>
Subject: Re: DOC2000 - 96MB on a 650Mhz PIII - cannot doc_read_ecc
Date: Fri, 02 Mar 2001 19:06:34 +0800 [thread overview]
Message-ID: <3A9F7EBA.4A6C0ED1@sis.com.tw> (raw)
In-Reply-To: 15E6537E180CC545848148F30F6688D81945BF@navajo.astanetworks.com
Pete Skelly wrote:
>
> Looks like timing is in fact the problem. I multiplied the delay
> in the routine DoC_Delay by 3, making this call last as long
> as if my machine were a 200Mhz machine (which is probably closer to
> what the Doc2000 drivers we're developed on), and was able to
> successfully use nflt on the drive.
>
> Although it looks like M-Systems doesn't publish the actual delays required,
> they did indicate that there were in fact delays that had to be taken into
> account.
>
> Any idea on the real numbers for the delays. If one knew that, one could
> write
> proc-speed independent delay code (err, not sure whether I'm volunteering or
> not)
>
> Also, could this be related to some of the problems people are seeing with
> larger
> modules? Do the larger modules have greater delays for sending commands to
> the chip,
> or are they simply found in faster systems?
>
M-System does "publish" the timming requirement in their documents. But they
does not made it very clearly, and it seems that the timming varies with
the age of the flash and/or different lot.
Ollie
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-03-02 11:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-02 8:38 DOC2000 - 96MB on a 650Mhz PIII - cannot doc_read_ecc Pete Skelly
2001-03-02 8:57 ` David Woodhouse
2001-03-02 11:06 ` Ollie Lho [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-05 22:48 Pete Skelly
2001-03-06 8:53 ` David Woodhouse
2001-03-02 0:58 Pete Skelly
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=3A9F7EBA.4A6C0ED1@sis.com.tw \
--to=ollie@sis.com.tw \
--cc=mtd@infradead.org \
--cc=pete.skelly@astanetworks.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