From: Marius Groeger <mgroeger@sysgo.com>
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 16:15:38 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.56.0406291606500.5355@mag.sysgo.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0406290859430.24373@localhost.localdomain>
On Tue, 29 Jun 2004, Robert P. J. Day wrote:
> excellent, this just gets better and better. however, will partition
> definitions on the command line override those in rpxlite.c? i notice
> that the generic rpxlite.c that comes from the bk tree has a default
> partition definition of fe000000/800000. should that be removed
> first? or will it be ignored? it's not clear from the comments in
> the source.
I don't think your version of rpxlite.c supports command line
partitioning at all. The official one doesn't. You should see the
existing mapping drivers such as physmap.c to learn how to add this,
it is not difficult.
The implementation should always give precedence to the command line
defininition.
Regards,
Marius
--
Marius Groeger <mgroeger@sysgo.com> Project Manager
SYSGO AG Embedded and Real-Time Software
Voice: +49 6136 9948 0 FAX: +49 6136 9948 10
www.sysgo.com | www.elinos.com | www.osek.de | www.imerva.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-06-29 14:15 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
2004-06-29 13:02 ` Robert P. J. Day
2004-06-29 14:15 ` Marius Groeger [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=Pine.LNX.4.56.0406291606500.5355@mag.sysgo.com \
--to=mgroeger@sysgo.com \
--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).