public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] global_data: unify global flag defines
Date: Mon, 5 Dec 2011 11:44:37 -0500	[thread overview]
Message-ID: <201112051144.38066.vapier@gentoo.org> (raw)
In-Reply-To: <CALButCLGUppjCaAaD+mjcKHp+dHTmEs2qrhtCan8ea8sy6PwcQ@mail.gmail.com>

On Monday 05 December 2011 00:47:12 Graeme Russ wrote:
> Hi Mike,
> 
> On Mon, Dec 5, 2011 at 5:39 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> > On Sunday 04 December 2011 22:47:59 Graeme Russ wrote:
> >> On Mon, Dec 5, 2011 at 2:43 PM, Mike Frysinger wrote:
> >> > +/*
> >> > + * Base for arches to start adding their own:
> >> > + * #define GD_FLG_FOO  (GD_FLG_ARCH_BASE << 0)
> >> > + * #define GD_FLG_BAR  (GD_FLG_ARCH_BASE << 1)
> >> > + * #define GD_FLG_COW  (GD_FLG_ARCH_BASE << 2)
> >> > + */
> >> > +#define GD_FLG_ARCH_BASE       0x00100
> >> > +
> >> > +#endif
> >> 
> >> This doesn't leave any room for new standard flags - flags is a u32,
> >> so why not define the low 16 bits as standard and the high 16 bit as
> >> arch specific - Maybe even split the high 16 bits into low 8 bits for
> >> arch specific, high 8 bits for board specific?
> > 
> > when we add a new common flag, we simply update GD_FLG_ARCH_BASE.  i
> > don't see the need for this complexity.
> 
> So the flags can change depending on the build - What is the
> implication for stand-alone apps (we have gone over the impact of
> changing gd before without a 100% concrete conclusion)

i did go through the research effort and posted all the details:
	http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/114029
but no one responded

> And you must rember to update GD_FLG_ARCH_BASE if anyone adds a new
> flag - Not immediately obvious (no comments to that effect)

i can add a comment

> I don't see any complexity in:
> 
> #define GD_FLG_ARCH_BASE       0x00010000
> #define GD_FLG_BOARD_BASE       0x01000000
> 
> Gives us 16 common flags (we have only used 8 so far) 8 arch flags and
> 8 board flags

i'm fine with simply adding defines and leaving the rest up to people.  but 
adding any additional macro code is overkill imo.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20111205/19344ce7/attachment.pgp>

  reply	other threads:[~2011-12-05 16:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-05 17:22 [U-Boot] [PATCH/RFC] global_data: unify global flag defines Mike Frysinger
2011-12-05  3:43 ` [U-Boot] [PATCH v2] " Mike Frysinger
2011-12-05  3:47   ` Graeme Russ
2011-12-05  6:39     ` Mike Frysinger
2011-12-05  5:47       ` Graeme Russ
2011-12-05 16:44         ` Mike Frysinger [this message]
2011-12-05 20:14           ` Graeme Russ
2012-03-06  5:00 ` Mike Frysinger
2012-03-17 21:43   ` Wolfgang Denk
2012-03-19  0:31 ` [U-Boot] [PATCH v3] " Mike Frysinger
2012-07-20 14:55   ` Mike Frysinger
2012-08-09 19:46   ` 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=201112051144.38066.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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