linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 01/18] Include autoconf.h from the bootwrapper.
Date: Thu, 25 Jan 2007 13:21:11 +1100	[thread overview]
Message-ID: <20070125022111.GD26212@localhost.localdomain> (raw)
In-Reply-To: <56B86A8F-4E40-4C58-A774-0DE3C7AA8CE2@kernel.crashing.org>

On Wed, Jan 24, 2007 at 08:08:02PM -0600, Kumar Gala wrote:
> 
> On Jan 24, 2007, at 5:51 PM, David Gibson wrote:
> 
> > On Wed, Jan 24, 2007 at 03:06:54PM -0600, Scott Wood wrote:
> >> This will be required by the u-boot compatibility code to obtain a
> >> compatible bd_t layout, to determine how to calculate the  
> >> timebase, and
> >> to know what soc fields need to be modified.
> >
> > Erm.. I believe the omission of *all* kernel header files from the
> > boot wrapper code, including the config, is a deliberate decision.
> > The idea is that the wrapping can, if necessary, be done independent
> > of the kernel build.
> 
> I think the problem is how to resolve the variations of the u-boot/ 
> ppcboot bd_t that changes from board to board and based on config.

Don't do that.  We're trying to get rid of this config dependant crap
that means the kernel must be built for a single board.  Instead make
the different bd_t options different options to the wrapper script.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  reply	other threads:[~2007-01-25  2:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-24 21:06 [PATCH 01/18] Include autoconf.h from the bootwrapper Scott Wood
2007-01-24 23:51 ` David Gibson
2007-01-25  2:08   ` Kumar Gala
2007-01-25  2:21     ` David Gibson [this message]
2007-01-25  2:40     ` Paul Mackerras
2007-01-25 17:39       ` Scott Wood
2007-01-25 22:15         ` Paul Mackerras

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=20070125022111.GD26212@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@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).