From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Frysinger Date: Tue, 3 Apr 2012 17:37:37 -0400 Subject: [U-Boot] [RFC v0 0/11]: Add In-Reply-To: <1332443357-14062-1-git-send-email-trini@ti.com> References: <1332443357-14062-1-git-send-email-trini@ti.com> Message-ID: <201204031737.38404.vapier@gentoo.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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: