From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: <linuxppc-dev@lists.linuxppc.org>, <linuxppc-commit@fsmlabs.com>
Subject: Re: bi_records and cmd_line
Date: Sun, 11 Mar 2001 21:12:00 +0100 [thread overview]
Message-ID: <20010311201200.25426@smtp.wanadoo.fr> (raw)
In-Reply-To: <20010311121049.A24589@opus.bloom.county>
>Hey all. I'm working on getting all of the in-kernel "bootloaders" to use
>the bi_records struct for cmd_line. I've got a question tho about xcoff
>(oldworld and newworld or no?). Right now arch/ppc/kernel/setup.c has a
>comment in identify_machine about if we're xcoff, grab the cmd line from
>/chosen/bootargs. Shouldn't this belong in coffboot.c instead? (Or,
chrmain.c
>as well?).
Tup. I beleive it's here for historical reasons.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-03-11 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-11 19:10 bi_records and cmd_line Tom Rini
2001-03-11 20:12 ` Benjamin Herrenschmidt [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=20010311201200.25426@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=linuxppc-commit@fsmlabs.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).