From: Aras Vaichas <arasv@magellan-technology.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: cmdlineparts and chip initialization order
Date: Fri, 12 Nov 2004 10:18:03 +1100 [thread overview]
Message-ID: <4193F32B.3080308@magellan-technology.com> (raw)
In-Reply-To: <20041111220146.GA1898@buici.com>
Marc Singer wrote:
> With a command line like this:
>
> console=ttyAM0 root=/dev/hda1 mtdparts=norflash:2m(boot),-(root);nandflash:32k(apex)ro,-(root)
>
> I am able to initialization partitions for the NOR flash, but not the
> NAND flash. It look like the problem is that the NOR flash driver is
> initializing before the mtdparts command line parsed, but the NAND
> flash isn't.
> <SNIP>
> BTW, it looks like none of the other NAND drivers expect a command
> line partition setup. Has anyone else tried?
I recently had to do this and had the same problem. I took a look at the low
level driver code for my particular processor and noted that not all MTD
drivers had partition parsing code.
e.g in at91_dataflash.c there is parser related code:
int parse_cmdline_partitions(struct mtd_info *master,
struct mtd_partition **pparts, const char *mtd_id);
and ...
#ifdef CONFIG_MTD_CMDLINE_PARTS
char mtdID[14];
#endif
and ...
#ifdef CONFIG_MTD_CMDLINE_PARTS
sprintf(mtdID, "dataflash%i", nr_devices-1);
mtd_parts_nr = parse_cmdline_partitions(device, &mtd_parts, mtdID);
#endif
This parsing code is missing from at91_nand.c, and that's why I wasn't able to
setup my NAND partitions from the command line (previous posting).
regards,
Aras
prev parent reply other threads:[~2004-11-11 23:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 22:01 cmdlineparts and chip initialization order Marc Singer
2004-11-11 22:51 ` Thomas Gleixner
2004-11-12 10:18 ` Marc Singer
2004-11-12 10:27 ` Marc Singer
2004-11-11 23:18 ` 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=4193F32B.3080308@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 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.