From: Wolfgang Denk <wd@denx.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: kernel option "Command line partition table parsing"
Date: Tue, 29 Jun 2004 14:57:05 +0200 [thread overview]
Message-ID: <20040629125710.B6B28C109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 29 Jun 2004 08:24:51 EDT." <Pine.LNX.4.60.0406290821150.19485@localhost.localdomain>
In message <Pine.LNX.4.60.0406290821150.19485@localhost.localdomain> you wrote:
>
> i'm intrigued by the above kernel option. currently, i define my
> MTD partitions in drivers/mtd/maps/rpxlite.c, using structs map_info,
> mtd_info, etc., and calling the appropriate routines, which works just
> fine.
>
> will this kernel option actually let me define the basic MTD
> partitions completely from the kernel command line without messing
> with rpxlite.c? or am i misreading the purpose of this option?
Yes, it will.
See http://www.denx.de/twiki/bin/view/DULG/BootTimeConfigurationOfMTDPartitions
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Even if you aren't in doubt, consider the mental welfare of the per-
son who has to maintain the code after you, and who will probably put
parens in the wrong place. - Larry Wall in the perl man page
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-29 12:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 12:24 kernel option "Command line partition table parsing" Robert P. J. Day
2004-06-29 12:46 ` Sylvain Munaut
2004-06-29 14:37 ` Wolfgang Denk
2004-06-29 14:45 ` Robert P. J. Day
2004-06-29 16:32 ` David Woodhouse
2004-06-29 12:57 ` Wolfgang Denk [this message]
2004-06-29 13:02 ` Robert P. J. Day
2004-06-29 14:15 ` Marius Groeger
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=20040629125710.B6B28C109F@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rpjday@mindspring.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).