From mboxrd@z Thu Jan 1 00:00:00 1970 From: Troy Kisky Date: Wed, 29 Feb 2012 13:33:24 -0700 Subject: [U-Boot] ARM: Update mach-types In-Reply-To: <4F4D6AED.1050006@denx.de> References: <4F4BFBFC.7080200@boundarydevices.com> <201202272356.32578.marek.vasut@gmail.com> <4F4C2A64.3030100@boundarydevices.com> <1330401093.1507.2.camel@konomi> <4F4D6AED.1050006@denx.de> Message-ID: <4F4E8B94.4030405@boundarydevices.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 2/28/2012 5:01 PM, stefano babic wrote: > Am 28/02/2012 04:51, schrieb Marek Vasut: >>> On 2/27/2012 3:56 PM, Marek Vasut wrote: >>>>> |ARM: Update mach-types >>>>> | >>>>> |This commit updates the mach-types based on the latest in Linus's >>>>> head | >>>>> |Signed-off-by: Marek Vasut >>>>> >>>>> Hi Marek, >>>>> >>>>> >>>>> Can I get you to do this again? I'd the symbol for >>>>> MACH_MX6Q_SABRELITE. >>>> No, can you please submit the mach-types update yourself? Thank you! >>>> >>> I don't think I'm trusted to do that. I think that some machines may >>> have been removed >>> from Linux that u-boot may want to keep. >> So these machines have to define their mach id in their config (and you need to fix them after replacing mach-types). >> >> Since I only want to use the >>> value in 1 place, >>> is it acceptable to just use the hex value instead? >> No, either update the mach types (preffered) or ... Update the mach types ;) > It was discussed and accepted that the boards can set CONFIG_MACH_TYPE > directly into the configuration file. In this way, we continue to > support in U-Boot boards independently if they are pushed to Linux > mainline or not. > > On the other side, everybody can send the current mach-types from the > Linux kernel to Albert (ARM Maintainer) - if a board is already in > kernel mainline is the preferred way. > > Best regards, > Stefano Babic > Thanks for the information. I'll send to Albert soon. Troy