From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Config: Add "board options" column to boards.cfg
Date: Mon, 20 Sep 2010 19:36:25 -0400 [thread overview]
Message-ID: <201009201936.28660.vapier@gentoo.org> (raw)
In-Reply-To: <1285025204-8463-1-git-send-email-marek.vasut@gmail.com>
On Monday, September 20, 2010 19:26:44 Marek Vasut wrote:
> There are some boards where it's not currently possible to detect all board
> information at runtime, therefore I introduced a new column called
> "options" to boards.cfg .
>
> This column can contain multiple options, separated by comma [,] . This
> column is case sensitive. In case there's a simple options like
> 256M_U_BOOT, it's plain expanded to "#define CONFIG_256M_U_BOOT" in
> config.h . In case there's an assignment, like "ram=8192", it's expanded
> to "#define CONFIG_RAM 8192" in config.h . There can also be multiple such
> options, then each is expanded to separate "#define CONFIG_xyz" statement.
>
> Also, I had to add fallback logic, because each of the board variants has a
> distinct name. This led to the mkconfig #including incorrect board
> configuration file (<configs/whole-board-configuration-name.h> aka. the
> value in column one). I implemented a logic which checks if such file
> exists and if it does not, it includes<configs/board-name.h> aka. the
> value in third column.
why not use the existing -t option instead of introducing your own new
"options" argument t mkconfig ?
-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/20100920/f0bcccb9/attachment.pgp
next prev parent reply other threads:[~2010-09-20 23:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 23:26 [U-Boot] [PATCH] Config: Add "board options" column to boards.cfg Marek Vasut
2010-09-20 23:36 ` Mike Frysinger [this message]
2010-09-21 6:21 ` 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=201009201936.28660.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