From mboxrd@z Thu Jan  1 00:00:00 1970
From: nico@fluxnic.net (Nicolas Pitre)
Date: Wed, 04 May 2011 09:51:27 -0400 (EDT)
Subject: [PATCH] kirkwood: add dir-665 support
In-Reply-To: <20110504080924.GX19806@kw.sim.vm.gnt>
References: <1303922086-10531-1-git-send-email-camhirundo@gmail.com>
	<20110503205056.GA13075@gentoodev.compulab.local>
	<BANLkTimQM_J2ZbDjAewUsp+XSEP+x+eniA@mail.gmail.com>
	<BANLkTinybLSF418PsocXR6dwuaksv_+UCQ@mail.gmail.com>
	<20110504080924.GX19806@kw.sim.vm.gnt>
Message-ID: <alpine.LFD.2.00.1105040940410.24613@xanadu.home>
To: linux-arm-kernel@lists.infradead.org
List-Id: linux-arm-kernel.lists.infradead.org

On Wed, 4 May 2011, Simon Guinot wrote:

> Hi Hirundo,
> 
> On Wed, May 04, 2011 at 10:54:52AM +0800, Hirundo Cam wrote:
> > Hi Mike and Simon,
> > 
> > I've send a machine submit to arm-linux, it generated the mach-types as
> > 
> > [stripped]
> > mx51_moray		MACH_MX51_MORAY		MX51_MORAY		3484
> > thales_cbc		MACH_THALES_CBC		THALES_CBC		3485
> > bluepoint		MACH_BLUEPOINT		BLUEPOINT		3486
> > dir665			MACH_DIR665		DIR665			3487
> > 
> > Is this correct for the DIR665 board using mv88f6281 chips?
> 
> It looks correct.

It may look correct, but I'll ask that you hang to it for a while as 
there is a desire to stop the addition of such board specific files to 
the kernel and move towards a solution such as device tree instead to 
represent those board details.

I think that Kirkwood is actually a good case for device tree as the 
differences between boards is really simple as it usually boils down to 
different GPIO usage and MPP assignments.  If someone would like to 
contribute to the DT effort on ARM then this would be a nice and easy 
target to convert over.


Nicolas