From: David Schleef <ds@schleef.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Vipin Malik <vipin.malik@daniel.com>,
joakim.tjernlund@lumentis.se,
'Chris Read ' <chris.read@activesilicon.co.uk>,
mtd@infradead.org
Subject: Re: Power blackouts and brownouts
Date: Fri, 27 Apr 2001 13:37:17 -0700 [thread overview]
Message-ID: <20010427133716.A20218@stm.lbl.gov> (raw)
In-Reply-To: <22885.988382072@redhat.com>; from dwmw2@infradead.org on Fri, Apr 27, 2001 at 03:34:32PM +0100
On Fri, Apr 27, 2001 at 03:34:32PM +0100, David Woodhouse wrote:
>
> Note that 'well designed embedded systems' does _not_ include the Intel
> Assabet platform. I believe nothing ever asserts the flash reset line, so if
> you reset while the flash is in a mode other than read mode, the CPU's reset
> vector is pointing at status words :)
This is also a problem for soft-reset. (Been there, dont that.)
That's why the Sharp chip driver always puts the chips into read
mode after checking the status. I believe at least one of the
other chip drivers don't do this.
dave...
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2001-04-27 20:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-26 15:55 Power blackouts and brownouts Vipin Malik
2001-04-27 7:39 ` Joakim Tjernlund
2001-04-27 14:30 ` Vipin Malik
2001-04-27 14:34 ` David Woodhouse
2001-04-27 15:31 ` Vipin Malik
2001-04-27 20:37 ` David Schleef [this message]
2001-04-28 10:34 ` David Woodhouse
2001-04-28 16:00 ` sharp driver dissimilarities David Schleef
2001-04-28 16:11 ` David Woodhouse
2001-04-28 17:15 ` David Schleef
2001-04-28 17:26 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-04-26 13:54 Power blackouts and brownouts Hicks, Jamey
2001-04-26 13:06 Chris Read
2001-04-26 15:35 ` Bari Ari
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=20010427133716.A20218@stm.lbl.gov \
--to=ds@schleef.org \
--cc=chris.read@activesilicon.co.uk \
--cc=dwmw2@infradead.org \
--cc=joakim.tjernlund@lumentis.se \
--cc=mtd@infradead.org \
--cc=vipin.malik@daniel.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