public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Abraham vd Merwe <abraham@2d3d.co.za>
To: Frederic Giasson <fgiasson@mediatrix.com>
Cc: MTD for Linux <linux-mtd@lists.infradead.org>
Subject: Re: mtd_info->write
Date: Wed, 6 Jun 2001 15:35:13 +0200	[thread overview]
Message-ID: <20010606153513.A9850@crystal.2d3d.co.za> (raw)
In-Reply-To: <F1BED55F35F4D3118C0F00E0295CFF4D99548A@mail.mediatrix.com>; from fgiasson@mediatrix.com on Wed, Jun 06, 2001 at 09:25:33 -0400

[-- Attachment #1: Type: text/plain, Size: 1442 bytes --]

Hi Frederic!

> I am almost sure that you have to validate the erase state of the sector you
> want to write to.  For example, I use cfi_amdstd_write function, and
> absolutely no validation is made in that fonction for this.

You mean the user process/module has to, not the chip driver? I'm writing a
chip driver and I want to know whether the chip driver is responsible for
the checking.

I noticed the other chip drivers (like you say here) doesn't so I'm assuming
I don't have to but I just want to make sure.

> > If the data is all ones ("1"), it has been erased.   If not, it has not.
> 
> Yes, I know, but I want to know whether I have to check if that's the case
> or not.
> 
> > Can you safely assume in the MTD write function that the blocks on which
> the
> > data is have been erased or do you actually have to do some error checking
> > and return with -EINVAL if you discover that it's not been erased?

-- 

Regards
 Abraham

Chemistry professors never die, they just fail to react.

__________________________________________________________
 Abraham vd Merwe - 2d3D, Inc.

 Device Driver Development, Outsourcing, Embedded Systems

  Cell: +27 82 565 4451         Snailmail:
   Tel: +27 21 761 7549            Block C, Antree Park
   Fax: +27 21 761 7648            Doncaster Road
 Email: abraham@2d3d.co.za         Kenilworth, 7700
  Http: http://www.2d3d.com        South Africa


[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-06-06 13:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-06 13:25 mtd_info->write Frederic Giasson
2001-06-06 13:35 ` Abraham vd Merwe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-06 13:38 mtd_info->write Frederic Giasson
2001-06-06 13:44 ` mtd_info->write David Woodhouse
2001-06-06 13:34 mtd_info->write Frederic Giasson
2001-06-06 13:41 ` mtd_info->write David Woodhouse
2001-06-06 13:42   ` mtd_info->write kira brown
2001-06-06 13:49     ` mtd_info->write David Woodhouse
2001-06-06 13:32 mtd_info->write Frederic Giasson
     [not found] <F1BED55F35F4D3118C0F00E0295CFF4D995488@mail.mediatrix.com>
2001-06-06 13:28 ` mtd_info->write Abraham vd Merwe
2001-06-06 13:35   ` mtd_info->write David Woodhouse
2001-06-06 17:50   ` mtd_info->write Nicolas Pitre
2001-06-06  9:12 mtd_info->write Abraham vd Merwe

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=20010606153513.A9850@crystal.2d3d.co.za \
    --to=abraham@2d3d.co.za \
    --cc=fgiasson@mediatrix.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