All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Hawkins <a.hawkins@cabletime.com>
To: D.A.Fedorov@inp.nsk.su
Cc: linux-mtd@lists.infradead.org
Subject: Re: Problem writing to NOR flash
Date: 26 Jul 2004 15:49:26 +0100	[thread overview]
Message-ID: <1090853366.2220.11.camel@adh> (raw)
In-Reply-To: <Pine.SGI.4.10.10407262126150.569820-100000@Sky.inp.nsk.su>

Hi,

On Mon, 2004-07-26 at 15:35, Dmitry A. Fedorov wrote:
> > Can I have a copy of these patches then?
> 
> Some time later (a few days).

Thanks for that.

> 
> > Have you had any problems writing to NOR?
> 
> No, after upgrade from the MTD snapshot.
> There were problems with erase (ioctl call did not wait of
> completion of erase operation) and jffs2 did not allowed to
> write. Now it works properly.

Ah, should have been more clear. This is a 'raw' write to the NOR
device. It appears that it's crashing inside do_xxlock_oneblock in
cfi_cmdset_0002.c (where it does the 'cfi_write').

There's a comment at the top of the code saying that it's very chip
specific, and hasn't been tested on an interleaved device (which I think
mine is).

Anyone help?

Thanks.

Andy

  reply	other threads:[~2004-07-26 14:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-26 13:32 Problem writing to NOR flash Andy Hawkins
2004-07-26 14:00 ` Dmitry A. Fedorov
2004-07-26 14:11   ` Andy Hawkins
2004-07-26 14:35     ` Dmitry A. Fedorov
2004-07-26 14:49       ` Andy Hawkins [this message]
2004-07-26 15:00         ` Dmitry A. Fedorov
2004-07-26 15:39           ` Andy Hawkins
2004-07-26 16:07             ` Andy Hawkins
2004-08-05 23:24               ` Eric W. Biederman
2004-08-12  6:59                 ` Eric W. Biederman
2004-07-29 19:41 ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2004-07-19 16:06 Andy Hawkins

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=1090853366.2220.11.camel@adh \
    --to=a.hawkins@cabletime.com \
    --cc=D.A.Fedorov@inp.nsk.su \
    --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 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.