All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duke <ezbonites@gmail.com>
To: "Nicolas Ferre" <nicolas.ferre@atmel.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: SPI Flash
Date: Tue, 18 Dec 2007 09:46:36 -0600	[thread overview]
Message-ID: <79ac09b60712180746o7f1fb8d1hc37c2f7eaa043fda@mail.gmail.com> (raw)
In-Reply-To: <79ac09b60712180745u475839b6q98de2a8500a6f483@mail.gmail.com>

On 12/18/07, Duke <ezbonites@gmail.com> wrote:
> On 12/18/07, Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
> > Duke :
> > > Hi all,
> > > Has anyone use ST's SPI flash and Atmels SPI DataFlash suscessfully?
> >
> > Atmel DataFlash are working on Linux with this configuration in your
> > .config :
> > CONFIG_MTD_DATAFLASH=y
> >
> > > How does the interface look from userspace? Is it still an mtdblockX
> > > device or is it a spi device node?
> >
> > It is seen as a mtd device :
> > # cat /proc/mtd
> > dev:    size   erasesize  name
> > [..]
> > mtd2: 00840000 00000420 "spi0.0-AT45DB642x"
> >
> > So you can mount is using mtdblockx interface.
>
> Thanks,
> Various DataFlash cards have different size alterable, is this
> supported my the mtd driver? Let say I want to have a section that I
> never want altered, do I need to do partition the dataflash
> accordingly so this section wouldn't be erased, or I don't need to do
> that? Taken into consideration the filesystem limit on block sizes.
>
> Do you know if this is the same for all spi flash chips that may not
> be from atmel?
>

Sorry, I ment Chips, not Cards (I don't indent to use DataFlash Cards).

  reply	other threads:[~2007-12-18 15:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-18 15:02 SPI Flash Duke
2007-12-18 15:39 ` Nicolas Ferre
2007-12-18 15:45   ` Duke
2007-12-18 15:46     ` Duke [this message]
     [not found] <mailman.54.1197992805.2861.linux-mtd@lists.infradead.org>
2007-12-19 15:17 ` Ian McDonnell

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=79ac09b60712180746o7f1fb8d1hc37c2f7eaa043fda@mail.gmail.com \
    --to=ezbonites@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nicolas.ferre@atmel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.