This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig459ACBA8C166A754FDF243C0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Volker A. Brandt wrote:
> [I've kept just port-sparc64 and dropped tech-kern.]

I'm not on that list; please CC me replies.

>>>Getting this to work would be a big step forward for the Sparc64 port
>>>and SMP on NetBSD in general.
>>Hmm, I'm not sure how much the T1 resembles III and IV, but it would be
>>a good thing if those were supported as well. As well as SMP on sparc64,
>>ofcourse. But given the fact that support for those is currently
>>lacking, I'm not sure how soon it'll surface?
> I have no idea how soon.  The chip is binary-compatible to sparcv9,
> but there are some differences under the hood.  The platform is
> called "sun4v" (as opposed to "sun4u), and there is a hypervisor
> layer "below" the OpenSparc cores.

'Sources' say it's sooner than I was thinking initially ;).

> The difference is that for USIII and USIV, not all documentation
> is available.  For the T1, there is...

OpenSolaris can function as hardware reference.

Cheers,
-- 
         Thomas E. Spanjaard
         tgen@netphreax.net

--------------enig459ACBA8C166A754FDF243C0
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (NetBSD)

iD8DBQFEg1XR6xCMwBJ+1+sRA/lUAJ96r7Ejm3mcDpxfbh6etkPLctO36ACfW4yT
7TcIfqlCkQloIRn6bBYSoO4=
=RLwV
-----END PGP SIGNATURE-----

--------------enig459ACBA8C166A754FDF243C0--