From: Dave Kleikamp <shaggy@kernel.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH V2 1/6] powerpc: Move udbg_early_init() after early_init_devtree()
Date: Wed, 02 Mar 2011 07:03:00 -0600 [thread overview]
Message-ID: <1299070980.8367.8.camel@shaggy-w500> (raw)
In-Reply-To: <1299037037.8833.821.camel@pasglop>
On Wed, 2011-03-02 at 14:37 +1100, Benjamin Herrenschmidt wrote:
> On Mon, 2011-02-07 at 19:29 +1100, David Gibson wrote:
> > On Wed, Feb 02, 2011 at 06:00:25PM -0600, Dave Kleikamp wrote:
> > > On Thu, 2011-02-03 at 10:06 +1100, David Gibson wrote:
> > > > On Tue, Feb 01, 2011 at 12:48:41PM -0600, Dave Kleikamp wrote:
> > > > > so that it can use information from the device tree.
> > > >
> > > > Hrm. On the other hand this means that the early_init_devtree() code
> > > > can't benefit from hardcoded early debugging. Since you don't
> > > > actually appear to use devtree information in udbg_early_init() in the
> > > > latest series, I'd suggest dropping this patch.
> > >
> > > Patch 2 depends on early_init_devtree() being run. Until then, I don't
> > > know of a way to get at the bootargs.
> >
> > Ah, yes. Drat.
>
> Doesn't matter. _Early_ debug has (or should have) the address in
> the .config file anyways, so it really shouldn't have to care about the
> arguments.
>
> So I'll drop this patch.
>
> There are plenty of reasons why we want to be able to use the early
> debug stuff to debug what's happening inside early_init_devtree() :-)
Fair enough. I wasn't sure this was the right thing to do. It's either
turn off early debug for AMP, or build separate kernels with a different
address in .config.
Shaggy
next prev parent reply other threads:[~2011-03-02 13:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 18:48 [PATCH V2 0/6] powerpc: AMP support for 47x Dave Kleikamp
2011-02-01 18:48 ` [PATCH V2 1/6] powerpc: Move udbg_early_init() after early_init_devtree() Dave Kleikamp
2011-02-02 23:06 ` David Gibson
2011-02-03 0:00 ` Dave Kleikamp
2011-02-07 8:29 ` David Gibson
2011-03-02 3:37 ` Benjamin Herrenschmidt
2011-03-02 13:03 ` Dave Kleikamp [this message]
2011-02-01 18:48 ` [PATCH V2 2/6] powerpc/44x: allow override to hard-coded uart address Dave Kleikamp
2011-02-01 18:48 ` [PATCH V2 3/6] powerpc/47x: allow kernel to be loaded in higher physical memory Dave Kleikamp
2011-02-02 7:45 ` Kumar Gala
2011-02-09 22:59 ` Dave Kleikamp
2011-02-01 18:48 ` [PATCH V2 4/6] powerpc/44x: don't use tlbivax on AMP systems Dave Kleikamp
2011-02-02 7:48 ` Kumar Gala
2011-02-02 13:19 ` Dave Kleikamp
2011-02-02 23:08 ` David Gibson
2011-02-02 23:53 ` Dave Kleikamp
2011-02-03 5:03 ` David Gibson
2011-02-03 23:15 ` Dave Kleikamp
2011-02-04 2:22 ` Timur Tabi
2011-02-07 8:30 ` David Gibson
2011-02-04 13:56 ` Josh Boyer
2011-02-04 14:44 ` Dave Kleikamp
2011-02-01 18:48 ` [PATCH V2 5/6] powerpc/44x: boot wrapper: allow kernel to load into non-zero address Dave Kleikamp
2011-02-01 19:13 ` Scott Wood
2011-02-01 19:41 ` Dave Kleikamp
2011-02-04 14:07 ` Josh Boyer
2011-02-04 14:44 ` Dave Kleikamp
2011-02-01 18:48 ` [PATCH V2 6/6] powerpc/476: Create a dts files for two 476 AMP instances under ISS Dave Kleikamp
2011-02-02 2:43 ` David Gibson
2011-02-09 23:03 ` Dave Kleikamp
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=1299070980.8367.8.camel@shaggy-w500 \
--to=shaggy@kernel.org \
--cc=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@lists.ozlabs.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).