From: David Woodhouse <dwmw2@infradead.org>
To: David Vrabel <dvrabel@arcom.co.uk>
Cc: mtd@infradead.org
Subject: Re: 2nd CFI chip detection fails sometimes
Date: Mon, 07 Aug 2000 15:33:30 +0100 [thread overview]
Message-ID: <6467.965658810@cygnus.co.uk> (raw)
In-Reply-To: <398EC83C.D9F4AE57@arcom.co.uk>
dvrabel@arcom.co.uk said:
> The line marked error causes problems because it can put the flash
> chip into an error state preventing correct detection. We need some
> way of knowing if it's RAM before we do the write. Suggestions
> welcome!
We should probably only put back the original value if we completely fail
to probe the device, _AND_ if it appears to be behaving like RAM (i.e. if
the contents of the address are exactly what we wrote to it.
Alternatively, we could accept the fact that we overwrite some bytes in a
RAM chip when we unload and reload its driver, and just not bother to write
back those bytes at all.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-08-07 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-07 14:31 2nd CFI chip detection fails sometimes David Vrabel
2000-08-07 14:33 ` David Woodhouse [this message]
2000-08-07 16:17 ` Stephane Laroche
2000-08-07 16:21 ` Stephane Laroche
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=6467.965658810@cygnus.co.uk \
--to=dwmw2@infradead.org \
--cc=dvrabel@arcom.co.uk \
--cc=mtd@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