public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: David Schleef <ds@schleef.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: Sat, 28 Apr 2001 11:34:45 +0100	[thread overview]
Message-ID: <9152.988454085@redhat.com> (raw)
In-Reply-To: <20010427133716.A20218@stm.lbl.gov>


ds@schleef.org said:
>  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. 

This bit me too, on suspend/resume. We now have MTD suspend/resume 
functions which deal with that case.

Incidentally, is there any particular reason why the functionality of the 
sharp driver shouldn't be provided by a more generic version of the Intel/
Sharp CFI commandset driver? Once we fix up the probe, of course.

--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2001-04-28 10:35 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
2001-04-28 10:34         ` David Woodhouse [this message]
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=9152.988454085@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=chris.read@activesilicon.co.uk \
    --cc=ds@schleef.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