From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] Global Data: Flagify have_console and env_valid
Date: Mon, 29 Aug 2011 13:47:24 -0500 [thread overview]
Message-ID: <4E5BDEBC.1010501@freescale.com> (raw)
In-Reply-To: <201108261615.35642.vapier@gentoo.org>
On 08/26/2011 03:15 PM, Mike Frysinger wrote:
> looks sane enough to me
>
> when changing the global_data structure, do we need to bump the u-boot
> standalone API number (XF_VERSION in exports.h) ? and i vaguely recall global
> data being passed to like Linux for some arches ? although looking at the
> number of #ifdef's in there, maybe that's already been a long lost battle.
The data passed to Linux in the non-device-tree case was bd_t, not gd_t.
Of course, that's full of ifdefs too, at least on powerpc. :-P
-Scott
next prev parent reply other threads:[~2011-08-29 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-26 13:23 [U-Boot] [PATCH] Global Data: Flagify have_console and env_valid Graeme Russ
2011-08-26 13:36 ` [U-Boot] [PATCH V2] " Graeme Russ
2011-08-26 20:15 ` Mike Frysinger
2011-08-26 22:36 ` Graeme Russ
2011-08-29 18:47 ` Scott Wood [this message]
2011-10-06 21:48 ` 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=4E5BDEBC.1010501@freescale.com \
--to=scottwood@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox