public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Kári Davíðsson" <kd@flaga.is>
Cc: mtd@infradead.org, nico@cam.org
Subject: Re: partitions and erase regions
Date: Tue, 24 Apr 2001 18:41:10 +0100	[thread overview]
Message-ID: <28157.988134070@redhat.com> (raw)
In-Reply-To: <EADB10BAC266A14A85ECBF8686A73E310A9148@kolkrabbi.flaga.is>


kd@flaga.is said:
> It sounds reasonable to me. Although I have a problem with the "major"
> erazesize in general. The erase regions are in the flash for a reason,
> i.e. the chip is not of one "major" erase size but of many erase
> sizes, although most of it (untill now, who knows what AMD, Intel and
> others might do in the future 8-)) is of one erase size.

I have a strong suspicion that we'll never see chips without a 'major' 
erasesize. Making all clients (such as JFFS2) deal with variable erase 
sizes is possible, but IMHO suboptimal. If we can avoid that complexity, it 
would be nice. 

Perhaps, however, we should provide a way for clients which _do_ know about 
variable erase regions to write to partitions which don't have a 'major' 
erasesize.

--
dwmw2




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

  reply	other threads:[~2001-04-24 17:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-24 10:29 partitions and erase regions Kári Davíðsson
2001-04-24 17:41 ` David Woodhouse [this message]
     [not found] <EADB10BAC266A14A85ECBF8686A73E3145911F@kolkrabbi.flaga.is>
2001-04-27 11:20 ` David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2001-04-25  9:36 Kári Davíðsson
2001-04-27 10:58 ` David Woodhouse
2001-03-30 22:56 Kári Davíðsson
2001-04-23 14:10 ` David Woodhouse
2001-03-30 22:47 Kári Davíðsson
2001-03-30 16:06 Kári Davíðsson
2001-03-30 17:52 ` Nicolas Pitre
2001-03-29 17:03 Kári Davíðsson

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=28157.988134070@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=kd@flaga.is \
    --cc=mtd@infradead.org \
    --cc=nico@cam.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