public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Aleksander Sanochkin <asanochkin@Lnxw.COM>
Cc: linux-mtd@lists.infradead.org, jffs-dev@axis.com
Subject: Re: cfi_cmdset_001.c problem
Date: Sat, 01 Dec 2001 09:54:54 +0000	[thread overview]
Message-ID: <16089.1007200494@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111300305120.11565-200000@newbast.lynuxworks.com>

asanochkin@Lnxw.COM said:
>  I see that after write and erase operations, the current version of
> cfi_cmdset_0001.c driver can left a Flash device not in the READY
> state. If soft reboot is performed in such a situation, applications
> that use flash will behave erroneously since they expect that the
> flash is in the READY state. For instance, if the system is supposed
> to boot from flash, it will hang.

Thanks for this. One thing that concerns me is that I have a vague 
recollection that Nico once drastically improved the performance of the 
same driver by ripping out all the gratuitous state changes. I wonder if it 
would be better to do this with a reboot notifier than by changing back to 
read mode after every other operation?

Also, we need to make sure we do the right thing if the JFFS or JFFS2 GC
thread is actually in the process of writing to the flash while
machine_restart() happens on another CPU.

--
dwmw2

  reply	other threads:[~2001-12-01  9:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-30 11:13 cfi_cmdset_001.c problem Aleksander Sanochkin
2001-12-01  9:54 ` David Woodhouse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-03 15:24 Aleksander Sanochkin
2001-12-03 16:11 ` David Woodhouse

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=16089.1007200494@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=asanochkin@Lnxw.COM \
    --cc=jffs-dev@axis.com \
    --cc=linux-mtd@lists.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