All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] powerpc: Cleanup BOOTFLAG_* usage
Date: Mon, 13 Sep 2010 21:40:52 -0500	[thread overview]
Message-ID: <1284432052.15941.4.camel@ptyser-laptop> (raw)
In-Reply-To: <20100913171353.6fb40978@schlenkerla.am.freescale.net>

On Mon, 2010-09-13 at 17:13 -0500, Scott Wood wrote:
> On Tue, 14 Sep 2010 00:02:49 +0200
> Wolfgang Denk <wd@denx.de> wrote:
> 
> > Dear Peter Tyser,
> > 
> > In message <1284389585.26713.2967.camel@petert> you wrote:
> > >
> > > Sounds good, I'll resubmit.  Getting rid of the BOOTFLAG_* defines will
> > > make bd->bi_bootflags unused.  What's the policy on modifying the
> > > bd_info structure?  Leave an unused bi_bootflags field to prevent
> > > breakage of OSes?
> > 
> > AFAICT only 2.4 PowerPC Linux kernels make use of bd_info. I think we
> > can just drop that entry.
> 
> 2.6 arch/ppc used it, and cuImage still does.  Ideally people would
> use a device tree if they have a new kernel and a new U-Boot (are
> there still individual boards that don't yet have device tree support in
> U-Boot?), but currently the old scheme still works.  IMHO it should
> either work, or be obvious about not working -- that is, either keep
> bd_info compatible or remove support for passing it to an OS altogether.

I agree with Scott; breaking the bd_info defeats it purpose.  I won't
modify bd_info in my change and leave removing bd_info for a future
discussion.

Thanks,
Peter

  reply	other threads:[~2010-09-14  2:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-13  5:21 [U-Boot] [PATCH] powerpc: Cleanup BOOTFLAG_* usage Peter Tyser
2010-09-13  5:34 ` Wolfgang Denk
2010-09-13  6:27   ` Stefan Roese
2010-09-13 14:53     ` Peter Tyser
2010-09-13 22:02       ` Wolfgang Denk
2010-09-13 22:13         ` Scott Wood
2010-09-14  2:40           ` Peter Tyser [this message]
2010-10-12 20:49 ` Wolfgang Denk

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=1284432052.15941.4.camel@ptyser-laptop \
    --to=ptyser@xes-inc.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.