Date: Mon, 27 Apr 2015 16:36:51 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Trevis Elser <trevis+freebsd-sun4v@clickscape.com> Cc: freebsd-sparc64 <freebsd-sparc64@freebsd.org> Subject: Re: Volunteer To Revive Sun4v Message-ID: <CAJ-Vmom_a-vCb1qV2_oc87tzC4e_n%2BB_y5q2Fa-40jbmLs=sEw@mail.gmail.com> In-Reply-To: <CAJirhcdLoZWv1zOQV8kwiAktm6PBGoV5joh5LxCy0sSKdb8WmQ@mail.gmail.com> References: <CAJirhcdLoZWv1zOQV8kwiAktm6PBGoV5joh5LxCy0sSKdb8WmQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! Yes, please do resurrect the port if you'd like. ;) Having updated sun4v support would be great. Those boxes have a lot of threads and useful virtualisation tuff to work on. Thanks! -adrian On 27 April 2015 at 08:50, Trevis Elser <trevis+freebsd-sun4v@clickscape.com> wrote: > Hi everyone. I posted a similar message on the sun4v mailing list, but > activity there seems pretty much dead and these are related. I'd like to > volunteer to restart the sun4v arch port. > > Obvious places to start seem to be: > 1) Posting on the sparc64 mailing list a similar message about volunteering > to take this on. > > 2) Digging up the old sun4v code. > > 3) Taking a look at OpenBSD's support for sun4v, which is merged in with > sparc64 there. So perhaps something similar, or at least a minimization of > code duplication from sparc64 could be achieved in FreeBSD. > > Any thoughts, directions, tips, encouragement, discouragement (though that > would be a curiosity), or hardware to work with :) etc. etc. would be > greatly appreciated! > > Thank you for the time it took to read, > > Trevis > _______________________________________________ > freebsd-sparc64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64 > To unsubscribe, send any mail to "freebsd-sparc64-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmom_a-vCb1qV2_oc87tzC4e_n%2BB_y5q2Fa-40jbmLs=sEw>