public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Mike Hill" <mhill@bustech.com>
Cc: mtd@infradead.org
Subject: Re: MTD on intel 28F320B3 flash memory
Date: Fri, 17 Nov 2000 14:18:02 +0000	[thread overview]
Message-ID: <9558.974470682@redhat.com> (raw)
In-Reply-To: <004601c0509e$b10d5630$e3e8b2c6@hawk>


mhill@bustech.com said:
>  The 28F320B3 is a BOOT BLOCK flash part.  It contains Eight 8K
> regions and 63 64K regions.  The CFI code assumes that all regions are
> of the same size. I am currently using this part in a design.  To get
> around this problem, I changed the CFI code to treat the 8K regions as
> a single 64K region. 

I think that's the correct way do do things. I don't think the MTD layer 
needs to handle variable erase sizes within a single MTD partition. Either 
your CFI driver registers a single device with 64K erasesize, or it 
registers two devices, one with 8K erasesize and the remainder with 64K 
erasesize.

I can't think of any situation in which you'd want to _use_ the multiple 
erasesize without actually using the boot blocks for a separate purpose to 
the remainder of the flash, in which case they should be in different MTD 
devices anyway, as far as the MTD layer is concerned.

--
dwmw2




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

  reply	other threads:[~2000-11-17 14:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-16 23:59 MTD on intel 28F320B3 flash memory Peter De Schrijver
2000-11-17  1:23 ` David Woodhouse
2000-11-17  8:44 ` Nick Ivanter
2000-11-17 13:59   ` Mike Hill
2000-11-17 14:18     ` David Woodhouse [this message]
2000-11-17 16:23       ` Nicolas Pitre
2000-11-17 16:13         ` David Woodhouse
2000-11-17 16:29         ` 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=9558.974470682@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=mhill@bustech.com \
    --cc=mtd@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