> >I was debating this.  It's a matter of whether we want to treat EBSA285 as a
> >seperate arch dir, or as part of cats.  cats is really an EBSA285 with a few
> >extras.  IE the 2 are near identical.  Should I just make an EBSA285 kernel
> >in the cats dir?
> 
> How hard is it to get a GENERIC kernel what will boot off either?  One thing
> we are trying to do is to have a single GENERIC config that will work for all
> supported under a given port.  There has to be a way to detect whether you
> are being run on a CAT .vs. a EBSA285.

Or not care (ie kernel will run equally well on either).

R.