From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jason <u-boot@lakedaemon.net>
Date: Mon, 12 Sep 2011 10:11:53 -0400
Subject: [U-Boot] [PATCH V2] ARM: Update mach-types
In-Reply-To: <4E6E1177.3010607@keymile.com>
References: <1315799692-16076-1-git-send-email-marek.vasut@gmail.com>
	<4E6DD6AB.2080809@compulab.co.il>
	<201109121536.47545.marek.vasut@gmail.com>
	<4E6E0EF9.1090307@denx.de> <4E6E1177.3010607@keymile.com>
Message-ID: <20110912141153.GG7688@titan.lakedaemon.net>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Mon, Sep 12, 2011 at 04:04:39PM +0200, 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?

Dreamplug has the same issue.  See here [1].  Basically, move the
relevant bits from mach-types.h to your board config file.

hth,

Jason.

[1] http://www.mail-archive.com/u-boot at lists.denx.de/msg60921.html