--Signature_Mon__20_Jun_2005_20_40_32_-0400_4HZCAqzoY=MiqDIP
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hello,

>    On the other hand - a lot of code seems to be already in place, and it=
's
>    supposed to work pretty much the same as on sparc32, isn't it?
>=20
>=20
> not really -- sparcv8 & sparcv9 kernel-level things are really quite
> different.  amazingly so.  compare to amd64 - you can run x86 oses
> on this directly without any problem.  sparc64 _needs_ a sparc64
> kernel whether it is compiled 32 or 64 bit.

I merely meant the way multiple CPUs are handled ( and no, I didn't read ne=
arly enough yet )

> chuq could probably explain better than i can ;-)

He'd be among the first people I'd pester about this ;)

have fun
Michael

--Signature_Mon__20_Jun_2005_20_40_32_-0400_4HZCAqzoY=MiqDIP
Content-Type: application/pgp-signature

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

iQEVAwUBQrdiAMpnzkX8Yg2nAQJ9cAf/VqNn0eOCZHz2ACR/4+0x1ocQAp/VIdr2
ppdBnMe98DZVs1LiW9hjg/AjMR2cSZaWaqi+J5dwSVX6PhiaxOOGQv6SxPjRcHIo
mJLH2aO/aaH4m4ZDcRrHFrSM+s1/Rj4m1krRZMij3zXcoVUaqnX0R/J2KWKid28k
M1wYWfkIHygheG5PKGH4y82xt/vjAjn3e1SHXlL75szBCPLS+gghQhmyrYzqy34G
ksIzztEl/btbPbBLB7KqL7/TKmYsWcJnq1IhzERdc6utTqNJC2HqnLcHFB6ZjubB
J3aRd543pR8gnxDMyzUs+2LMhVHqpeH3Kdn+UG9QvX7FMeReGTOX/Q==
=xn8Y
-----END PGP SIGNATURE-----

--Signature_Mon__20_Jun_2005_20_40_32_-0400_4HZCAqzoY=MiqDIP--