On Tue, May 02, 2006 at 08:28:17PM +0200, Rainer Orth wrote:
> Jonathan Adams writes:
> 
> > > * When UltraSPARC I support is resurrected, it seems to be correct to
> > >   rename /usr/include/sys/fm/cpu/UltraSPARC-II.h to UltraSPARC.h (or
> > >   UltraSPARC-I.h) since this file already refers to both CPU types.
> > 
> > You should discuss this change with [EMAIL PROTECTED]
> 
> ok, will do.
> 
> > > * uts/common/krtld/kobj.c forcibly handles all US-I and US-II CPUs as 
> > > US-II.
> > >   This change is inappropriate when US-I CPUs are supported again.  I
> > >   haven't found how this was done in the Solaris 9 sources (if at all) and
> > >   what the real problems is, do I don't know how to handle this.
> > 
> > The reason is spelled out in a comment right above the definition of 
> > ultra_2:
> > 
> > --- cut here ---
> > /*
> >  * Some PROMs return SUNW,UltraSPARC when they actually have
> >  * SUNW,UltraSPARC-II cpus. SInce we're now filtering out all
> >  * SUNW,UltraSPARC systems during the boot phase, we can safely
> >  * point the auxv CPU value at SUNW,UltraSPARC-II. This is what
> >  * we point it at.
> >  */
> > const char          *ultra_2 = "SUNW,UltraSPARC-II";
> > --- cut here ---
> 
> I know that, but I couldn't find any code dealing with the underlying issue
> in S9 sources so I have no idea how this was dealt with before (if at all).

In Solaris 9, the SUNW,UltraSPARC module was delivered.  The bugid:
> > 4944965 SUNW,UltraSPARC should not be delivered

stopped building and delivering the SUNW,UltraSPARC kernel module.

The CPU module is a critical module that is loaded (along with the
'platform' module) by krtld before unix and genunix gain any control.
It provides key routines like copyin(), gethrtime(), bcopy(), and many
others.

You'll either need to verify that the UltraSPARC-II module is compatible
with the UltraSPARC-I chip, or re-coerce the build to generate an UltraSPARC
module, and remove this code.

Cheers,
- jonathan

-- 
Jonathan Adams, Solaris Kernel Development
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code

Reply via email to