public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Aras Vaichas <arasv@magellan-technology.com>
To: linux-mtd@lists.infradead.org
Subject: Re: Setting up MTD via command line?
Date: Mon, 13 Sep 2004 09:38:02 +1000	[thread overview]
Message-ID: <4144DDDA.1060109@magellan-technology.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0409092347290.6169-100000@gemini.home.net>

Jamie Guinan wrote:
 >>>Can anyone explain, or is there docs on how to setup MTD via command

from <your kernel here>/Documentation/Configure.help

CONFIG_MTD_CMDLINE_PARTS
   Allow generic configuration of the MTD paritition tables via the kernel
   command line. Multiple flash resources are supported for hardware where
   different kinds of flash memory are available.

   You will still need the parsing functions to be called by the driver
   for your particular device. It won't happen automatically. The
   SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
   example.

   The format for the command line is as follows:

   mtdparts=<mtddef>[;<mtddef]
   <mtddef>  := <mtd-id>:<partdef>[,<partdef>]
   <partdef> := <size>[@offset][<name>][ro]
   <mtd-id>  := unique id used in mapping driver/device
   <size>    := standard linux memsize OR "-" to denote all
   remaining space
   <name>    := (NAME)

   Due to the way Linux handles the command line, no spaces are
   allowed in the partition definition, including mtd id's and partition
   names.

   Examples:

   1 flash resource (mtd-id "sa1100"), with 1 single writable partition:
   mtdparts=sa1100:-

   Same flash, but 2 named partitions, the first one being read-only:
   mtdparts=sa1100:256k(ARMboot)ro,-(root)

   If unsure, say 'N'.

      reply	other threads:[~2004-09-12 23:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26  5:24 Setting up MTD via command line? Bo Henriksen
2004-08-31 16:18 ` Jamie Guinan
2004-09-11 14:26   ` Jamie Guinan
2004-09-12 23:38     ` Aras Vaichas [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=4144DDDA.1060109@magellan-technology.com \
    --to=arasv@magellan-technology.com \
    --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