[U-Boot] [RFC] CONFIG naming convetion

[Robin Getz]

On Sat 18 Jul 2009 18:25, Wolfgang Denk pondered:
> >
>  > I guess we could back up a step and look at the users, and defined things
>  > as things that should be changed by:
>  >  - arch maintainers (Core/CPU specific)
>  >  - SoC maintainer (SoC specific)
>  >  - Board maintainer (PCB specific)
>  >  - End user of the above (changes options, but nothing from the above list?)
>  
>  Frankly, this makes no sense to me. I have yet to see any such clear
>  split of roles and functions. When you bring up a new board, you
>  usually have to check everything.
>  
>  The only split that made, and still makes, kind of sense to me is the
>  split into normal users (CONFIG_) versus "root" (CONFIG_SYS_) groups.

I guess I still don't understand how you are making the distinction between
"normal users" and "root" - I think there are more categories of users
between those two...

People responsible for the archicture/CPU core may set things up, and
not want anyone to change things - on any SoC or Board. 

People responsible for SoC developments should be able to take what
the arch provider delivers, write a few device drivers, make some
specific choices that anyone who implements that SoC is going to have
to live with.

People responsible for Board porting, should be able to take what
the SoC provider delivers, customise things for their platform,
and move on.

Then there are end users - which must live with the choices that all three
have made, until they get their own hardware back, or in the case where
the hardware is a module - just change some non-hardware related options.

So maybe it is core, chip, PCB, and user.

In some cases - all 4 categories are the same person - in many cases they
are not.