linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Barry G <mr.scada@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Combining multiple NAND MTDs
Date: Wed, 6 Apr 2011 13:47:50 -0500	[thread overview]
Message-ID: <20110406134750.489e2ba6@schlenkerla.am.freescale.net> (raw)
In-Reply-To: <BANLkTim=oxHcW-HV5Z062r2p2D1nTL8mcQ@mail.gmail.com>

On Tue, 5 Apr 2011 16:35:10 -0700
Barry G <mr.scada@gmail.com> wrote:

> I want to run UBIFS on the combined 2 gigs of flash.  Whats the best
> way to do this?
> 
> I tried using the mtdconcat stuff and wrote a small driver
> but I am not sure how to populate the mtd_info structure since do_probe_map
> doesn't work with NAND AFAIK.
> 
> I see that fsl_elbc_select_chip says "hardware does not seem to support this".
> Not sure if this is related.

It's not related -- it's talking about a single physical chip with
multiple chip selects, not a logical concatenation of multiple separate
devices.

> I see some comments in mtd-physmap.txt about using multiple reg ranges?
> Does this work with NAND?

No.

I don't know of an out-of-the-box configuration step you can take to do
mtdconcat of eLBC NAND, but you could try creating a custom map driver that
glues things together as you wish.  Or if you want to be more ambitious,
perhaps a kernel command line (or other dynamic config) option that lets you
glue arbitrary MTD devices together.

-Scott

      reply	other threads:[~2011-04-06 18:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05 23:35 Combining multiple NAND MTDs Barry G
2011-04-06 18:47 ` Scott Wood [this message]

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=20110406134750.489e2ba6@schlenkerla.am.freescale.net \
    --to=scottwood@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mr.scada@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).