Hi Robin,
Thanks for reviewing the patch.
I like your idea of having a single kernel which can boot on any board
and also agree with you that code duplication is not a good thing.
However, based on our customer's feedback so far, we prefer to keep it separate
for each board, so that code doesn't get to messy or people don't have to
look at unwanted code.
Also since IDT's processors are SoC's and do undergo various rev's for the chips,
in which certain feature (hardware) are fixed/removed/added. In this case having
a separate directory (at the cost of code duplication) is easier to maintain.
Regards
Rakesh
-----Original Message-----
From: linux-mips-bounce@xxxxxxxxxxxxxx [mailto:linux-mips-bounce@xxxxxxxxxxxxxx] On Behalf Of Robin H. Johnson
Sent: Thursday, March 09, 2006 9:15 PM
To: linux-mips@xxxxxxxxxxxxxx
Subject: Re: [PATCH] IDT Interprise Processor Support for Linux 2.6.x
On Thu, Mar 09, 2006 at 05:08:49PM -0800, Tiwari, Rakesh wrote:
> The attached patch adds support for the IDT Interprise series of
> processor
> based on the MIPS 4KC and Cronus (RC32300) core.
I'm not Ralf, but I gave your patch a quick once-over anyway for the hell of it.
I see a lot of duplicated code, esp in arch/mips/idt-boards and the network drivers.
Is it possible to have a kernel capable of booting on all IDT boards? Could such a kernel detect what board it's actually running on - or enough elements of the board configuration to provide more generic drivers?
--
Robin Hugh Johnson
E-Mail : robbat2@xxxxxxxxxxxxxxxxxx
Home Page : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ# : 30269588 or 41961639
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
