Make it clear we are targeting PCI UltraSPARC [for now].

This commit is contained in:
David E. O'Brien 2001-06-06 18:21:20 +00:00
parent 22e64162fa
commit 6560a47f9d
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=9553

View file

@ -1,13 +1,13 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [ <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
<!ENTITY base CDATA ".."> <!ENTITY base CDATA "..">
<!ENTITY date "$FreeBSD: www/en/platforms/sparc.sgml,v 1.1 2000/11/30 18:56:25 jim Exp $"> <!ENTITY date "$FreeBSD: www/en/platforms/sparc.sgml,v 1.2 2001/06/06 18:17:10 obrien Exp $">
<!ENTITY title "FreeBSD/SPARC Project"> <!ENTITY title "FreeBSD/Sparc64 Project">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;]> <!ENTITY % includes SYSTEM "../includes.sgml"> %includes;]>
<html> <html>
&header; &header;
<p>This page contains information about porting FreeBSD to SPARC <p>This page contains information about porting FreeBSD to UltraSPARC
systems.</p> systems.</p>
<h3>General Information</h3> <h3>General Information</h3>
@ -65,7 +65,7 @@
<h3><a name="history">Port History</a></h3> <h3><a name="history">Port History</a></h3>
<p>The FreeBSD/SPARC port was initiated by Jason Evans in 1997. <p>The FreeBSD/Sparc64 platform port was initiated by Jason Evans in 1997.
Originally, the port was backed by Sun Microelectronics, but they Originally, the port was backed by Sun Microelectronics, but they
have since backed out. This is quite interesting, given <a have since backed out. This is quite interesting, given <a
href="http://www.sun.com/smi/Press/sunflash/1999-12/sunflash.991214.1.html">this href="http://www.sun.com/smi/Press/sunflash/1999-12/sunflash.991214.1.html">this
@ -78,7 +78,7 @@
href="http://docs.freebsd.org/cgi/getmsg.cgi?fetch=0+0+archive/1998/freebsd-sparc/19980405.freebsd-sparc">Jason's href="http://docs.freebsd.org/cgi/getmsg.cgi?fetch=0+0+archive/1998/freebsd-sparc/19980405.freebsd-sparc">Jason's
post</a> suggesting that somebody needed to take the reins.</p> post</a> suggesting that somebody needed to take the reins.</p>
<p>FreeBSD/SPARC didn't die, however disheartening the news of Sun's <p>FreeBSD/Sparc64 didn't die, however disheartening the news of Sun's
retreat was. The mailing list did go on hiatus for a while while retreat was. The mailing list did go on hiatus for a while while
several people working on coding. Late in October 1998, a source several people working on coding. Late in October 1998, a source
code tarball was made available.</p> code tarball was made available.</p>
@ -117,8 +117,8 @@
Evans.</i></p> Evans.</i></p>
</blockquote> </blockquote>
<p>The SPARC port is in it's infancy. We've done a good bit of <p>The Sparc64 platform port is in it's infancy. We've done a good bit of
research into what needs to be done in order to make FreeBSD/SPARC a research into what needs to be done in order to make FreeBSD/Sparc64 a
reality, but the vast majority of the work has yet to be done.</p> reality, but the vast majority of the work has yet to be done.</p>
<p>Here's a short history of what led up to this porting effort. Sun <p>Here's a short history of what led up to this porting effort. Sun
@ -142,7 +142,7 @@
servers. FreeBSD is fast and lean for small servers. It is also servers. FreeBSD is fast and lean for small servers. It is also
useful for certain types of embedded applications, which is actually useful for certain types of embedded applications, which is actually
the main reason SME is interested in seeing a port of FreeBSD to the main reason SME is interested in seeing a port of FreeBSD to
SPARC.</p> UltraSPARC.</p>
<p>A while back, SME approached the FreeBSD core team and offered <p>A while back, SME approached the FreeBSD core team and offered
monetary compensation of some nature (I don't know the details) in monetary compensation of some nature (I don't know the details) in
@ -203,9 +203,9 @@
<ol> <ol>
<li><a href="#1">What happened to the old FAQ?</a></li> <li><a href="#1">What happened to the old FAQ?</a></li>
<li><a href="#2">What is the status of the port?</a></li> <li><a href="#2">What is the status of the port?</a></li>
<li><a href="#3">What machines will FreeBSD/SPARC run on?</a></li> <li><a href="#3">What machines will FreeBSD/Sparc64 run on?</a></li>
<li><a href="#4">Does FreeBSD/SPARC support device X?</a></li> <li><a href="#4">Does FreeBSD/Sparc64 support device X?</a></li>
<li><a href="#5">Will FreeBSD/SPARC run Solaris/SunOS binaries?</a></li> <li><a href="#5">Will FreeBSD/Sparc64 run Solaris/SunOS binaries?</a></li>
</ol> </ol>
<h4><a name="1">What happened to the old FAQ?</a></h4> <h4><a name="1">What happened to the old FAQ?</a></h4>
@ -226,21 +226,20 @@
in the porting effort, you can view the <a href="#status">status</a> in the porting effort, you can view the <a href="#status">status</a>
online.</p> online.</p>
<h4><a name="3">What machines will FreeBSD/SPARC run on?</a></h4> <h4><a name="3">What machines will FreeBSD/Sparc64 run on?</a></h4>
<p>Currently? None. The port is a long way away from running on <p>Currently? None. The port is a long way away from running on
anything. We have plans to support every machine we can. It is anything. We have plans to support every machine we can. It is
safe to assume that FreeBSD/SPARC will run on at least all the safe to assume that FreeBSD/Sparc64 will run on at least all PCI / IDE
machines that OpenBSD and NetBSD run on. This includes sun4, sun4c, based workstations. </p>
sun4m, and sun4u.</p>
<h4><a name="4">Does FreeBSD/SPARC support device X?</a></h4> <h4><a name="4">Does FreeBSD/Sparc64 support device X?</a></h4>
<p>See <a href="#3">question #3</a>.</p> <p>See <a href="#3">question #3</a>.</p>
<h4><a name="5">Will FreeBSD/SPARC run Solaris/SunOS binaries?</a></h4> <h4><a name="5">Will FreeBSD/Sparc64 run Solaris/SunOS binaries?</a></h4>
<p>It is reasonable to say that FreeBSD/SPARC will provide some <p>It is reasonable to say that FreeBSD/Sparc64 will provide some
Solaris/SunOS emulation. It is too early in the life of the port to Solaris/SunOS emulation. It is too early in the life of the port to
answer this any more specifically.</p> answer this any more specifically.</p>