public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Abraham vd Merwe <abraham@2d3d.co.za>
To: MTD for Linux <linux-mtd@lists.infradead.org>
Subject: erase questions
Date: Thu, 7 Jun 2001 13:03:09 +0200	[thread overview]
Message-ID: <20010607130309.A28720@crystal.2d3d.co.za> (raw)

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

Hi!

I have a couple of questions about mtd_info->erase which isn't covered in
the MTD API:

From the MTD API docs, it seems the erase function can only be called
erase_info->len == mtd->erasesize. This is obviously not true anymore since
there can be multiple erase regions with multiple erase sizes and the user
might request an erase on one of the smaller blocks.

So can I assume that I only have to deal (read: allow) with erases where
erase_info->addr == START_OF_SOME_BLOCK and erase_info->len ==
LENGTH_OF_THAT_BLOCK?

So basically it boils down to 2 questions. Is ->addr always equal to the
start of a block and is ->len always equal to the size of that block or may
->len span multiple blocks.

If ->len may span multiple blocks, must it be equal to the size of all the
blocks (e.g. if you we're to erase a 2x 4k + 3x 8k consecutive blocks, must
len be equal to 32k)?

-- 

Regards
 Abraham

Reading is to the mind what exercise is to the body.

__________________________________________________________
 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-07 10:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-07 11:03 Abraham vd Merwe [this message]
2001-06-07 11:12 ` erase questions 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=20010607130309.A28720@crystal.2d3d.co.za \
    --to=abraham@2d3d.co.za \
    --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