diff --git a/en/platforms/sparc.sgml b/en/platforms/sparc.sgml index 5c216ddbba..fe6b1e7b38 100644 --- a/en/platforms/sparc.sgml +++ b/en/platforms/sparc.sgml @@ -1,248 +1,204 @@ - + %includes;]> &header;

This page contains information about porting FreeBSD to UltraSPARC systems.

General Information

Source Code

Documentation and White Papers

Other Links of Interest


-

Port History

- -

The FreeBSD/sparc64 platform port was initiated by Jason Evans in 1997. - Originally, the port was backed by Sun Microelectronics, but they - have since backed out. This is quite interesting, given this - press release from Sun, which announces that RedHat Linux 6.1 - can now be purchased and shipped with a new UltraSPARC server or - workstation. Sun joined Linux International in May 1998, shortly - after Jason announced that he would no longer be working on the port - in an official capacity. Jordan Hubbard, the FreeBSD release - engineer, responded to Jason's - post suggesting that somebody needed to take the reins.

- -

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 - several people working on coding. Late in October 1998, a source - code tarball was made available.

- -

Paolo Di Francesco was the next "father" of the port. Paolo - attempted, for the first time in the history of the port, to - organize information, developers, and tasks into a structure that - can only be known as project management. If not for the 98-99 - holiday season and a few overspoken individuals on the mailing list, - Paolo would have continued on. During his tenure, a number of - people stepped up to work on the older Sun SPARC architectures. - This did cause a slight chasm in the project, and many of the more - qualified individuals were on the side of the UltraSPARC family of - machines. Luckily, this didn't end up a period of quiet on the - mailing list, as Telecom Italia provided us with a list keep-alive. - A glitch in their system caused one of Paolo's posts to keep coming - back and back and back and back... This repeat post continued well - into 1999, when the list did once again become mostly silent.

+

Latest News

-

This brings us up-to-date. David O'Brien had been itching for a - long time to start work on the port, but was waiting for some sort - of direction. As the months dragged on into 2000, he decided that - nobody was going to accept the challenge if he didn't. As to the - port status, nothing much has changed since the early boot code - release of October 1998. The rest of the port history is best - expressed by Jason Evans, and can be found here.

+ -
-

While reading this, keep in mind it is from 1997 or 1998. - This information is pulled from the original FAQ, written by Jason - Evans.

-
-

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/sparc64 a - reality, but the vast majority of the work has yet to be done.

+

Port History

-

Here's a short history of what led up to this porting effort. Sun +

The FreeBSD/sparc64 platform port was initiated by Jason Evans in + 1997. Originally, the port was backed by Sun Microelectronics. Sun Microelectronics (SME) is the part of Sun that makes microprocessors. Up until now, SMCC (the part of Sun that makes workstations) has been the overwhelmingly primary customer of SME. SME naturally wants to expand its sales, and to do that, they need - to sell CPUs to people outside of Sun. FreeBSD is perceived as + to sell CPUs to people outside of Sun. FreeBSD was perceived as being a way of accomplishing this.

To understand why Sun could fund a FreeBSD port, which would seem to conflict with Sun's Solaris offerings, you need to realize that Sun is broken up into separate business units that often - compete with each other. The Solaris people at Sun - may not like having a FreeBSD port to compete with, but their power - to prevent it is somewhat diminished due to the business model. Of - course, if the FreeBSD port were a major threat, SMI (the main Sun - umbrella company) would put a stop to it. However, this is - unlikely, since FreeBSD mostly meets the needs of a different market - sector than Solaris. Solaris does wonderful things on big MP - servers. FreeBSD is fast and lean for small servers. It is also - useful for certain types of embedded applications, which is actually - the main reason SME is interested in seeing a port of FreeBSD to - UltraSPARC.

+ compete with each other. The Solaris people at + Sun may not like having a FreeBSD port to compete with, but their + power to prevent it is somewhat diminished due to the business + model. Of course, if the FreeBSD port were a major threat, SMI + (the main Sun umbrella company) would put a stop to it. However, + this is unlikely, since FreeBSD mostly meets the needs of a + different market sector than Solaris. Solaris does wonderful + things on big MP servers. FreeBSD is fast and lean for small + servers. It is also useful for certain types of embedded + applications, which is actually the main reason SME is interested + in seeing a port of FreeBSD to UltraSPARC.

A while back, SME approached the FreeBSD core team and offered - monetary compensation of some nature (I don't know the details) in - exchange for an official UltraSPARC port. The core team turned down - this offer. Once again, I don't know details, but one of the main - statements made (actually somewhat inferred) by Jordan Hubbard was - that SME's offer was not of major interest since to be of long term - use to FreeBSD, such a proposal would need to include support for a - number of years from someone internal to Sun.

- -

Jordan's statement makes a great deal of sense. I've traced down - documentation in preparation for this port that people external to - Sun would have had a difficult, perhaps impossible time procuring. - Without such access, it is very difficult to make continual progress - on such a project.

- -

Now it's time to mingle some of my background into this narrative. - I started working at SME in September of 1997. During my first - week, I caught wind of the negotiations SME was making with the core - team. I expressed extreme interest in working on the project. - Through a bit of persistence (and the failure of the proposal made - by SME), I was given permission to begin work on the port.

- -

My other duties at SME include finding information for software - vendors who are porting their OSes/RTOSes to the UltraSPARC. This - puts me in a good position to gather hardware information pertinent - to the FreeBSD port.

- -

So here's the catch. I have access to documentation, a machine to - develop on, but very little low-level OS or hardware experience. I - learn quickly, but I've got a lot to learn. Already several people - have been able to help me grasp concepts that are key to porting - FreeBSD, but there is much, much more to learn.

- -

So, I can use the following types of help (not exclusively, of - course:

- -
    -
  1. Answer my questions about kernel and hardware details. For - example, I have documentation on the MMU, but have never actually - dealt with one, so John Dyson has volunteered to get me through - the rough spots having to do with memory management, as well as - discussing design issues due to the difference in nature between - PCs and Suns.
  2. + monetary compensation of some nature in exchange for an official + UltraSPARC port. The core team turned down this offer. The exact + reasons are known only to the core team, but Jordan Hubbard + implied taht SME's offer was not of major interest since to be of + long term use to FreeBSD, such a proposal would need to include + support for a number of years from someone internal to Sun.

    + +

    Jason Evans started working at SME in September of 1997. During + the first week, he caught wind of the negotiations SME was making + with the core team. Jason expressed extreme interest in working + on the project. Through a bit of persistence (and the failure of + the proposal made by SME), he was given permission to begin work + on the port.

    + +

    Jason's other duties SME included finding information for + software vendors who are porting their OSes/RTOSes to the + UltraSPARC. This put him in a good position to gather hardware + information pertinent to the FreeBSD port.

    + +

    Jason was instrumental in getting the FreeBSD/sparc64 port done, + and doing much of the initial planning. Sun Microsystems has + since backed out of their support for the FreeBSD/sparc64 effort, + and Jason Evans eventually left Sun.

    -
  3. Actually write code.
  4. - -
  5. Various administrative things, such as a web page, bug tracking, - FAQ, etc.
  6. +

    Paolo Di Francesco was the next "father" of the port. Paolo + attempted, for the first time in the history of the port, to + organize information, developers, and tasks into a structure that + can only be known as project management. If not for the 98-99 + holiday season and a few overspoken individuals on the mailing list, + Paolo would have continued on. During his tenure, a number of + people stepped up to work on the older Sun SPARC architectures. + This did cause a slight chasm in the project, and many of the more + qualified individuals were on the side of the UltraSPARC family of + machines. Luckily, this didn't end up a period of quiet on the + mailing list, as Telecom Italia provided us with a list keep-alive. + A glitch in their system caused one of Paolo's posts to keep coming + back and back and back and back... This repeat post continued well + into 1999, when the list did once again become mostly silent.

    -
  7. Whatever you can do to help.
  8. -
+

In 2000, Jake Burkholder and Thomas Moestl have made an + incredible amount of work on the sparc port. Most of the + development has taken place in the Perforce repository on + freefall, and has only been merged to the HEAD (-CURRENT branch) + of CVS after more careful testing. David O'Brien has done a lot + of work to provide a usable toolchain for FreeBSD/sparc64 + development. Until one of the above mentioned people updates this + paragraph, please see the mailing list archives. ;)


Frequently Asked Questions

  1. What happened to the old FAQ?
  2. What is the status of the port?
  3. What machines will FreeBSD/sparc64 run on?
  4. Does FreeBSD/sparc64 support device X?
  5. Will FreeBSD/sparc64 run Solaris/SunOS binaries?

What happened to the old FAQ?

It's right here. The old FAQ is SME-centeric, and sun4u-specific. These traits do not reflect the current state of the port, since SME has pulled their official support from the port and the majority of the development equipment now consists of older Sun SPARC hardware. Furthermore, there haven't been a lot of frequently asked questions of late. Most of the items in the old FAQ date back to before the mailing list was being archived.

What is the status of the port?

-

While we're in the early stages, and to help keep people interested - in the porting effort, you can view the status - online.

+

It is possible to boot a number of newer UltraSparc hardware + platforms into FreeBSD with time and patience. Please see the FreeBSD/sparc64 + Hardware Notes for more information.

What machines will FreeBSD/sparc64 run on?

-

Currently? None. The port is a long way away from running on - anything. We have plans to support every machine we can. It is - safe to assume that FreeBSD/sparc64 will run on at least all PCI / IDE - based workstations.

+

Please see the FreeBSD/sparc64 + Hardware Notes for more information.

Does FreeBSD/sparc64 support device X?

See question #3.

Will FreeBSD/sparc64 run Solaris/SunOS binaries?

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 answer this any more specifically.

&footer;