From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [Announce][RFC] CFG_ macro renaming
Date: Tue, 2 Sep 2008 01:56:24 +0200 [thread overview]
Message-ID: <20080901235624.GC316@game.jcrosoft.org> (raw)
Hi,
As announce during OLS conference, it's plain to
use kconfig to manage board configuration.
For this purpose and Makefile conditional compile we're
move CFG_ macro to new CONFIG_ marco
For memory
There are two classes of configuration variables:
* Configuration _OPTIONS_:
These are selectable by the user and have names beginning with
"CONFIG_".
* Configuration _SETTINGS_:
These depend on the hardware etc. and should not be meddled with if
you don't know what you're doing; they have names beginning with
"CFG_".
to keep CFG_ meaning we will rename them in the following change
1) Basic config
For environment we will use CONFIG_ENV_ (will be done this merge windows)
For configuration settings CONFIG_SYS_
additional proposition
2) Extra config
For memory settings CONFIG_MEM_ or CONFIG_SYS_MEM_
For PCI settings CONFIG_PCI_ or CONFIG_SYS_PCI_
For USB settings CONFIG_USE or CONFIG_SYS_PCI_
For flash settings CONFIG_FLASH or CONFIG_SYS_FLASH_
For nand settins CONFIG_NAND or CONFIG_SYS_NAND_
For dtt settgins CONFIG_DTT or CONFIG_SYS_DTT
etc...
Comments are welcome.
The move to new style will be done for the beggining of the next merge window
Best Regards,
J.
next reply other threads:[~2008-09-01 23:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 23:56 Jean-Christophe PLAGNIOL-VILLARD [this message]
2008-09-02 0:34 ` [U-Boot] [Announce][RFC] CFG_ macro renaming Wolfgang Denk
2008-09-02 0:59 ` Jean-Christophe PLAGNIOL-VILLARD
2008-09-13 21:38 ` Luigi 'Comio' Mantellini
2008-09-13 21:41 ` Jean-Christophe PLAGNIOL-VILLARD
2008-09-13 22:12 ` Luigi 'Comio' Mantellini
2008-09-13 22:18 ` Jean-Christophe PLAGNIOL-VILLARD
2008-09-13 22:54 ` Wolfgang Denk
2008-09-02 6:19 ` Markus Klotzbücher
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=20080901235624.GC316@game.jcrosoft.org \
--to=plagnioj@jcrosoft.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.