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: Wed, 05 Jul 2000 16:16:57 +0900	[thread overview]
Message-ID: <3962E0E9.14051B82@crossnet.co.jp> (raw)
In-Reply-To: 7330.962615057@cygnus.co.uk


It is CFI-compliant. May be, the command set is the different from
Intel's.

I changed the definition of the flash memory address in nora.c
according to our board. Kernel can detects flash momeries correctly.
But the module cfi_cmdset_0002 is required.   

The messages from kernel are:

Main: Initialising MTD Drivers
nora flash device: 200000 at bf000000
NORA: Found a coupled pair of CFI devices at location 0 in 16 bit mode
Primary Vendor Command Set: 0002 (AMD/Fujitsu Standard)
Primary Algorithm Table at 0040
Alternative Vendor Command Set: 0000 (None)
No Alternate Algorithm Table
Vcc Minimum: 2.7 V
Vcc Maximum: 3.6 V
No Vpp line
Typical byte/word write timeout: 16 sssss
Maximum byte/word write timeout: 512 sssss
Full buffer write not supported
Typical block erase timeout: 1024 sssss
Maximum block erase timeout: 16384 sssss
Chip erase not supported
Device size: 0x200000 bytes (2 Mb)
Flash Device Interface description: 0x0002
  - supports x8 and x16 via BYTE# with asynchronous interface
Max. bytes in buffer write: 0x1
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

request_module[cfi_cmdset_0002]: Root fs not mounted
Invalid Extended Query Table at 0040: 40 C0 80
No supported Vendor Command Set found
ftl_cs: FTL header not found.


Should I make cfi_cmdset_0002? Is there the another resources ?

Best regards.

Masami Komiiya


David Woodhouse wrote:
> 
> mkomiya@crossnet.co.jp said:
> > We try to port Linux kernel to our embedded system that has Fujitsu's
> > NOR type Flash memory MBM29LV160.
> 
> Is it CFI-compliant?
> 
> If so, it'll be at least detected by the current code.
> 
> If it is capable of using the Intel command set, then it is supported.
> Otherwise, you will have a little bit of work to do to add support for it.
> 
> It should be quite simple to add support for it if it doesn't support the
> Intel command set.
> 
> First you need to provide a 'map' driver which allows access to the flash
> chips. Look at something simple like nora.c for an example - if your flash
> chips are mapped into virtual memory then all you need to do is change a
> couple of defines in nora.c to drive your own board.
> 
> Then load the cfi_probe module and the nora module (or your own map driver).
> 
> Show me all the output you get from it.
> 
> --
> dwmw2


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

  reply	other threads:[~2000-07-05  8:14 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 [this message]
2000-07-05  8:43     ` David Woodhouse
2000-07-06 10:34       ` Masami Komiya
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=3962E0E9.14051B82@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