public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Masami Komiya <mkomiya@crossnet.co.jp>
To: David Woodhouse <dwmw2@infradead.org>
Cc: mtd@infradead.org
Subject: Re: Fujitsu MBM29LV160
Date: Thu, 06 Jul 2000 19:34:19 +0900	[thread overview]
Message-ID: <396460AB.9BEC2657@crossnet.co.jp> (raw)
In-Reply-To: Pine.LNX.4.21.0007050937500.1226-100000@imladris.demon.co.uk

I will try to make cfi_cmdset_0002. After making it,
I want to use FTL and JFFS for our system.
These filesystems can be used on AMD's flash chips?

Our system has two interleaved flash in 32 bit mode.
So I want to implement only 32bit read & write
routines instead of 16 bit if it is allowed.
FTL or JFFS require 16bit read & write routines ?

Best Regards.

Masami Komiya


David Woodhouse wrote:
> 
> On Wed, 5 Jul 2000, Masami Komiya wrote:
> 
> >
> > It is CFI-compliant. May be, the command set is the different from
> > Intel's.
> >
> > The messages from kernel are:
> >
> > NORA: Found a coupled pair of CFI devices at location 0 in 16 bit mode
> > Primary Vendor Command Set: 0002 (AMD/Fujitsu Standard)
> 
> Excellent.
> 
> > Number of Erase Block Regions: 4
> >   Erase Region #0: BlockSize 0x4000 bytes, 1 blocks
> >   Erase Region #1: BlockSize 0x2000 bytes, 2 blocks
> >   Erase Region #2: BlockSize 0x8000 bytes, 1 blocks
> >   Erase Region #3: BlockSize 0x10000 bytes, 31 blocks
> 
> > Should I make cfi_cmdset_0002? Is there the another resources ?
> 
> Yes, you need to make cfi_cmdset_0002 for that particular
> configuration (2x16bit). It should be quite simple t copy cfi_cmdset_0001
> and modify it accordingly - not only changing the command set used
> but also changing it to drive two interleaved chips at once. You'll need
> the AMD data sheets for those chips.
> 
> For now, I'd suggest that you combine all the smaller erase blocks at the
> beginning of the device, and pretend that the erase size is always 0x10000
> (actually 0x20000 because you have two chips interleaved).  Then when you
> receive an erase request at location zero, erase all the smaller blocks at
> once.
> 
> We'll work out how to handle that properly, but not quite yet. Probably
> the cfi_probe routine needs to be able to return more than one MTD device.
> 
> --
> dwmw2


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

  reply	other threads:[~2000-07-06 11:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-01 10:16 Fujitsu MBM29LV160 Masami Komiya
2000-07-03  9:04 ` David Woodhouse
2000-07-05  7:16   ` Masami Komiya
2000-07-05  8:43     ` David Woodhouse
2000-07-06 10:34       ` Masami Komiya [this message]
2000-07-06 12:55         ` 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=396460AB.9BEC2657@crossnet.co.jp \
    --to=mkomiya@crossnet.co.jp \
    --cc=dwmw2@infradead.org \
    --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