public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Hinko Kocevar <hinko.kocevar@cetrtapot.si>
To: Damian Slee <Damian@commtech.com.au>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Serial flash memory support
Date: Thu, 26 May 2005 17:08:35 +0200	[thread overview]
Message-ID: <4295E673.3050704@cetrtapot.si> (raw)
In-Reply-To: <B967C997C2BE2D48A6BBE14078F79BD601CE3A@ntserver.commtech.com.au>

Damian Slee wrote:
> Jffs2 does support atmel serial dataflash, as far as the driver for spi,
> that is more hardware dependent.   They recently changed the conditional 
> compiles to be CONFIG_JFFS2_FS_WRITEBUFFER for nand and dataflash.
> 
> BTW JFFS2 takes ages to do the startup scan of the flash with the 528 or
> 1056 block size of the dataflash.

Our serial flash uses 256 byte pages and is forming sectors with them, 
depending on the whole flash size. But I guess that is no case for accessing it 
quicker.

>  I was evalutating the latest cvs JFFS2 last week upon eCos.  I think it
> was about 7 seconds for 64kbytes, with the SPI clocked at 15MHz.

That is too slow for our application.
My conclusion would be that JFFS2 is too much for 'slow' SPI serial flash. I 
guess will just use raw access to the data stored there and achieve maximum 
speed. Can mtd raw access driver/module be used for this purpose or is that 
driver meant for a another stuff?

regards,
hinko k
-- 
..because under Linux "if something is possible in principle,
then it is already implemented or somebody is working on it".

					--LKI

       reply	other threads:[~2005-05-26 15:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B967C997C2BE2D48A6BBE14078F79BD601CE3A@ntserver.commtech.com.au>
2005-05-26 15:08 ` Hinko Kocevar [this message]
2005-05-25 19:41 Serial flash memory support Hinko Kocevar
2005-05-26  6:35 ` Andrew Victor
2005-05-26 14:52   ` Hinko Kocevar

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=4295E673.3050704@cetrtapot.si \
    --to=hinko.kocevar@cetrtapot.si \
    --cc=Damian@commtech.com.au \
    --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