From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC v0 0/11]: Add <configs/omap3_common.h>
Date: Tue, 3 Apr 2012 17:37:37 -0400 [thread overview]
Message-ID: <201204031737.38404.vapier@gentoo.org> (raw)
In-Reply-To: <1332443357-14062-1-git-send-email-trini@ti.com>
On Thursday 22 March 2012 15:09:06 Tom Rini wrote:
> Here's something I've talked about a bit before. This series adds
> include/configs/omap3_common.h and makes all CONFIG_OMAP34XX boards use
> it. This particular round of posting doesn't directly apply as I'm
> working off of a series of cleanups that I'll post once I'm sure I don't
> find any others from doing this (unused CONFIG options) general series.
> What I'm really looking for is feedback on the implementation, namely
> what I lay out in the first patch of a section to set before using
> omap3_common.h, including, and a section for after omap3_common.h. The
> series isn't nearly complete but introduces at least one example of a
> "our board isn't like all the others" in each of the sections.
seems like for the most part this is soc-specific default configs, and one or
two might be a vendor (TI) specific defaults (which aren't really harmful).
the patches as-is generally look OK, but i wonder if we shouldn't expand the
arm asm/config.h to tail into an asm/arch/config.h so these soc-specific defaults
can live there rather than include/configs/.
-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/20120403/649e136b/attachment.pgp>
next prev parent reply other threads:[~2012-04-03 21:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 19:09 [U-Boot] [RFC v0 0/11]: Add <configs/omap3_common.h> Tom Rini
2012-03-22 19:09 ` [U-Boot] [RFC v0 01/11] omap3+: Introduce <configs/omap3_common.h> Tom Rini
2012-03-23 1:48 ` Jason Kridner
2012-03-23 15:26 ` Tom Rini
2012-03-22 19:09 ` [U-Boot] [RFC v0 02/11] omap3: Move DISPLAY_CPUINFO / DISPLAY_BOARDINFO to common Tom Rini
2012-03-22 19:09 ` [U-Boot] [RFC v0 03/11] omap3: Move V_OSCK / V_SCLK to omap3_common.h Tom Rini
2012-03-22 19:09 ` [U-Boot] [RFC v0 04/11] omap3: Move '#undef CONFIG_USE_IRQ' " Tom Rini
2012-03-22 19:09 ` [U-Boot] [RFC v0 05/11] omap3: Move CONFIG_MISC_INIT_R " Tom Rini
2012-03-22 19:09 ` [U-Boot] [RFC v0 06/11] omap3: Move ATAGS and OF_LIBFDT " Tom Rini
2012-03-22 19:09 ` [U-Boot] [RFC v0 07/11] omap3: Move SYS_MALLOC_LEN and ENV_SIZE " Tom Rini
2012-03-22 19:09 ` [U-Boot] [RFC v0 08/11] omap3: Consolidate UART information in omap3_common.h Tom Rini
2012-04-03 21:35 ` Mike Frysinger
2012-04-03 23:45 ` Tom Rini
2012-04-04 2:42 ` Mike Frysinger
2012-04-04 18:19 ` Tom Rini
2012-03-22 19:09 ` [U-Boot] [RFC v0 09/11] omap3: Consolidate HSMMC support into omap3_common.h Tom Rini
2012-03-22 19:09 ` [U-Boot] [RFC v0 10/11] omap3: Consolidate NAND information in omap3_common.h Tom Rini
2012-03-22 19:09 ` [U-Boot] [RFC v0 11/11] omap3: Consolidate I2C information into omap3_common.h Tom Rini
2012-04-03 21:37 ` Mike Frysinger [this message]
2012-04-03 23:35 ` [U-Boot] [RFC v0 0/11]: Add <configs/omap3_common.h> Tom Rini
2012-04-04 2:46 ` Mike Frysinger
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=201204031737.38404.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 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.