From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Fri, 23 Mar 2012 08:26:27 -0700 Subject: [U-Boot] [RFC v0 01/11] omap3+: Introduce In-Reply-To: References: <1332443357-14062-2-git-send-email-trini@ti.com> Message-ID: <20120323152627.GB9551@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Thu, Mar 22, 2012 at 09:48:27PM -0400, Jason Kridner wrote: > I'm reading/replying to these one-by-one for sanity/clarity with regards > to BeagleBoard... [snip] > >diff --git a/include/configs/omap3_beagle.h > >b/include/configs/omap3_beagle.h > >index 80b9a5a..21e4b01 100644 > >--- a/include/configs/omap3_beagle.h > >+++ b/include/configs/omap3_beagle.h > >@@ -29,16 +29,21 @@ > > #define __CONFIG_H > > > > /* > >- * High Level Configuration Options > >+ * Values that differ from platform defaults or are unspecified. > > */ > >-#define CONFIG_OMAP 1 /* in a TI OMAP core */ > >-#define CONFIG_OMAP34XX 1 /* which is a 34XX */ > >-#define CONFIG_OMAP3_BEAGLE 1 /* working with BEAGLE */ > >+#define CONFIG_SDRC /* The chip has SDRC controller */ > > > >-#define CONFIG_SDRC /* The chip has SDRC controller */ > > I can see it can make sense to have an OMAP/DM/AM3x target without SDRC > enabled. Er, right. That's why SDRC or EMIF is done per-board for us (omap4/5 are EMIF only and if we can honestly keep am335x at one config for all boards it'll just be opting in to later parts of these kind of series). -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: