From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert P. J. Day Date: Fri, 20 Nov 2009 09:59:40 -0500 (EST) Subject: [U-Boot] [PATCH v2] BeagleBoard: Add a comment explaining the use of "OMAP34XX" macros. In-Reply-To: <4B069C13.6060807@windriver.com> References: <4B069C13.6060807@windriver.com> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Fri, 20 Nov 2009, Tom wrote: > Robert P. J. Day wrote: > > Make it clear to the reader that, since OMAP 34XX and 35XX are the > > same silicon, the BeagleBoard can use the OMAP34XX macros. > > > > Signed-off-by: Robert P. J. Day > > > > --- > > > > diff --git a/include/configs/omap3_beagle.h b/include/configs/omap3_beagle.h > > index 19a5ec9..59b7edc 100644 > > --- a/include/configs/omap3_beagle.h > > +++ b/include/configs/omap3_beagle.h > > @@ -30,6 +30,9 @@ > > > > /* > > * High Level Configuration Options > > + * > > + * Note that since OMAP 34XX and 35XX are the same silicon, the > > + * OMAP 3530-based BeagleBoard can use the OMAP34XX macros. > > I think this comment would be appropriate in the omap3 readme. > > > Perhaps the omap3 specific defines could be explained in > greater detail there. > certainly, there's nothing amiss about a longer explanation in the README file. but the rationale for the above was just a couple lines to prevent any confusion on the part of anyone who wanted to peruse the beagle config file, nothing more. it wasn't meant to be a big deal. rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Kernel Pedantry. Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday ========================================================================