Date: Fri, 22 Aug 2008 21:33:17 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Kip Macy <kmacy@freebsd.org> Cc: sun4v@freebsd.org, freebsd-hackers@freebsd.org, FreeBSD Current <freebsd-current@freebsd.org>, freebsd-stable@freebsd.org Subject: Re: the future of sun4v Message-ID: <20080822113317.GD32539@server.vk2pj.dyndns.org> In-Reply-To: <3c1674c90808211442t707966fq29997b53a70ed2f7@mail.gmail.com> References: <3c1674c90808211442t707966fq29997b53a70ed2f7@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--2YJj5f1P6Th4nBRw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [Replies re-directed to freebsd-sun4v] On 2008-Aug-21 14:42:55 -0700, Kip Macy <kmacy@freebsd.org> wrote: >I believe that there is a general expectation by freebsd users and >developers that unsupported code should not be in CVS. Although sun4v >is a very interesting platform for developers doing SMP work, I simply >do not have the time or energy to maintain it. If someone else would >like to step up and try his hand I would be supportive of his efforts. >In the likely event that no one steps forward by the time that 7.1 is >released I will ask that it be moved to the Attic. Since there are no other current SPARC CPUs that FreeBSD can run on (the US-II has been obsolete for about 6 years and FreeBSD won't run on any more recent sun4u chips), that will also remove the justification for maintaining a SPARC64 port. I don't have the knowledge or available time to maintain the sun4v port by myself but would be happy to be part of a team doing so. One impediment I have is that I don't have a T-1 or T-2 system that I can dedicate to FreeBSD. I could work on FreeBSD in a guest domain - but since FreeBSD doesn't support either the virtual disk or virtual network, actually getting FreeBSD running there presents somewhat of a challenge. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --2YJj5f1P6Th4nBRw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkiuo/0ACgkQ/opHv/APuIdIQwCaAgOo6jkMtJjWZq6IblsdfjZJ v7cAnRilBTMhsEbCcqlHiGWbGMY9DFQX =6heT -----END PGP SIGNATURE----- --2YJj5f1P6Th4nBRw--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080822113317.GD32539>