From: David Woodhouse <dwmw2@infradead.org>
To: Paul Nash <paulnash@wildseed.com>
Cc: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: Restart problems after writing to mtdblock?
Date: Thu, 28 Nov 2002 09:44:08 +0000 [thread overview]
Message-ID: <20628.1038476648@passion.cambridge.redhat.com> (raw)
In-Reply-To: <43CB1396676FD4119F03001083FD299401A1C6BA@neptune.kirkland.local>
paulnash@wildseed.com said:
> On our StrongARM board at the moment, we don't have nRESET_OUT fed
> into the flash chip. We're investingating that, but I would like to
> knoew the root cause.
This kind of thing is usually caused by inappropriate use of drugs on the
part of the hardware designer, AFAICT.
paulnash@wildseed.com said:
> Partially answering my question, it looks like I was partly correct.
> It appears that MTD is setup to lazily delay a reset to read array
> mode until an actual read request comes along. In my case, this is
> fatal.
> I'm wondering if a reasonable solution is to do something like install
> a reboot_notifier so I can guarantee the chip is back in Read Array
> mode. Where would be a good place to do such a thing, or if this is a
> bad idea, what is a better one? Thanks...
It's been discussed before. IIRC the conclusion that it wouldn't be 100%
reliable, and it was better to fix the hardware and confiscate the drugs.
--
dwmw2
next prev parent reply other threads:[~2002-11-28 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 0:57 Restart problems after writing to mtdblock? Paul Nash
2002-11-28 9:44 ` David Woodhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-28 2:33 Paul Nash
2002-11-28 7:39 ` Jörn Engel
2002-11-30 14:46 Paul Nash
2002-11-30 16:22 ` David Woodhouse
2002-12-02 9:34 Paul Nash
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=20628.1038476648@passion.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=paulnash@wildseed.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.