(moved to port-mips from source-changes)

In article <030501160748.M0121246@mirage.ceres.dti.ne.jp> on source-changes
I wrote:

> In article <20030501070206.21ABFB004@cvs.netbsd.org>
> igy@netbsd.org wrote:

> > Module Name:	src
> > Committed By:	igy
> > Date:		Thu May  1 07:02:06 UTC 2003
> > Modified Files:
> > 	src/sys/arch/hpcmips/conf: files.hpcmips majors.hpcmips
>  :
> > 	src/sys/arch/hpcmips/conf: LCARD std.lcard
>  :
> > Log Message:
> > Support for Laser5's L-Card+ Embedded CPU Board
> 
> Shouldn't this be in evbmips rather than hpcmips?
> (and IMHO all VR41xx and TX39xx cpu dependent code should be in arch/mips.)

In article <87ade7umxk.wl@portellen.arhc.org> on source-changes
Naoto Shimazaki wrote:

> > Shouldn't this be in evbmips rather than hpcmips?
> > (and IMHO all VR41xx and TX39xx cpu dependent code should be in arch/mips.)
>
> I also think CPU dependent code should be placed under arch/mips.
> And when it is happen, evbmips is much better place than hpcmips
> for L-Card+.  (and, I think, for L-Router too.)
>
> Unfortunately, current code depending on VR41xx is deeply bound with
> HPC dependent code.  Separating these code might take a bunch of work.
> So I chose to add L-Card+ support with minimum modification for the
> first step, and placed new code for L-Card+ near by VR41xx.
>
> Anyway, it is better to move CPU dependent code to arc/mips.
>
> // I'm not sure whether I'm good for such work....

Ok, then are there critical problem to move these CPU dependent code
into arch/mips? Does it require any changes of API or some structures?
Or it's just "a bunch of work"?

In article <20030501075600.5CFD453E7F@thoreau.thistledown.com.au>
simonb@wasabisystems.com wrote:

> > Shouldn't this be in evbmips rather than hpcmips?
> Probably.  Just from looking at the commit message, it doesn't appear
> to be a handheld device.

> > (and IMHO all VR41xx and TX39xx cpu dependent code should be in arch/mips.)
> Definitely this.  arch/mips/nec and arch/mips/toshiba?

Currently hpcmips port has hpcmips/vr and hpcmips/tx,
but I prefer mips/vr41 and mips/tx39 (or mips/vr41xx, mips/tx39xx)
because both vendors have many other own mips processors,
Vr4300,5000,7700 by NEC and TX49,79 by Toshiba:
http://www.necel.com/micro/english/product/vr/vr.html
http://www.toshiba.com/taec/cgi-bin/display.cgi?table=Family&FamilyID=5

(BTW, what should we do for Toshiba R5900 on PlayStation2?)
---
Izumi Tsutsui
tsutsui@ceres.dti.ne.jp