From mboxrd@z Thu Jan 1 00:00:00 1970 From: Igor Grinberg Date: Tue, 13 Sep 2011 10:46:45 +0300 Subject: [U-Boot] [PATCH V2] ARM: Update mach-types In-Reply-To: <201109121610.11650.marek.vasut@gmail.com> References: <1315799692-16076-1-git-send-email-marek.vasut@gmail.com> <4E6E0EF9.1090307@denx.de> <4E6E1177.3010607@keymile.com> <201109121610.11650.marek.vasut@gmail.com> Message-ID: <4E6F0A65.2010605@compulab.co.il> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 09/12/11 17:10, Marek Vasut wrote: > On Monday, September 12, 2011 04:04:39 PM Holger Brunck wrote: >> Hi, >> >> On 09/12/2011 03:54 PM, Stefano Babic wrote: >>> On 09/12/2011 03:36 PM, Marek Vasut wrote: >>>>> Have you checked that the removed boards are not supported in U-Boot? >>>> >>>> No, but then the respective maintainers will get a warning and will be >>>> forced to fix their boards in both linux and uboot. >>> >>> Maybe the simplest way to catch these boards (if any) is to run MAKEALL >>> on arm targets with your mach-types file. If no board is broken, we have >>> not to worry about. >> >> sorry, I didn't follow the whole discussion, but this patch will remove the >> mach type for our km_kirkwood board. >> >> -#define MACH_TYPE_KM_KIRKWOOD 2255 >> >> This board is supported in u-boot but not mainlined in linux. So how should >> we handle this? > > #define MACH_TYPE... in your board config file until you get that mainline So, Marek, Albert, Is this our official solution to the mach_types cleanup by Russell? Or should we use the way discussed in thread [1], as already agreed by Albert and Wolfgang? [1] - http://lists.denx.de/pipermail/u-boot/2011-May/092218.html -- Regards, Igor.