Diff for /wikisrc/ports/sun3.mdwn between versions 1.2 and 1.6

version 1.2, 2012/12/22 14:36:17 version 1.6, 2014/04/18 20:46:30
Line 1 Line 1
 [[!template id=port  [[!template id=port
 port="sun3"  port="sun3"
 cur_rel="6.0"    cur_rel="6.1.4"  
 future_rel="7.0"  future_rel="7.0"
   pkg_rel="6.0"
 changes_cur="6.0"  changes_cur="6.0"
 changes_future="7.0"  changes_future="7.0"
 thumbnail="http://www.netbsd.org/images/ports/sun3/110.gif"  thumbnail="http://www.netbsd.org/images/ports/sun3/110.gif"
 about="""  about="""
 NetBSD/sun3 is the port of NetBSD to the Sun Microsystems sun3, and sun3x series of computers, which are based on the Motorola [68020](http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MC68020) and [68030](http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MC68030) CPUs respectively, with a Sun-designed custom MMU. Sun sold these computers as both servers and desktop workstations from the mid to late 1980's. They were superseded by the sun4 SPARC RISC systems, which are supported by NetBSD as [NetBSD/sparc](/ports/sparc).  NetBSD/sun3 is the port of NetBSD to the [Sun Microsystems](http://www.sun.com/)
   **sun3**, and **sun3x** series of computers, which are based on the Motorola
   [68020](http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MC68020)
   and [68030](http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MC68030)
   CPUs respectively, with a Sun-designed custom MMU.
   Sun sold these computers as both servers and desktop workstations from
   the mid to late 1980's. They were superseded by the **sun4** SPARC RISC systems,
   which are supported by NetBSD as [[NetBSD/sparc|sparc]].
   
 Nathan Williams and Jeremy Cooper are the maintainers of NetBSD/sun3.   Nathan Williams and Jeremy Cooper are the maintainers of NetBSD/sun3. 
 """  """
 supported_hardware="""  supported_hardware="""
 ###Supported System Models  ###Supported System Models
   
 NetBSD/sun3 runs on these <span class="bold"><strong>sun3</strong></span> and  See [[Supported System Models|sun3_supported_system_models]] page.
 <span class="bold"><strong>sun3x</strong></span> architecture  
 machines:  
   
 <table border="2" cellpadding="4" cellspacing="0" id="sun3-supported">  
   <tr>  
     <th>Model</th>  
     <th>MHz</th>  
     <th>RAM</th>  
     <th>RAM Expansion</th>  
     <th>Bus</th>  
     <th>Slots</th>  
     <th>Type</th>  
   </tr>  
   <tr>  
     <td>Sun&nbsp;3/50</td>  
     <td align="right">15.7</td>  
     <td align="right">4</td>  
     <td>3rd party</td>  
     <td>n/a</td>  
     <td align="right">n/a</td>  
     <td>sun3</td>  
   </tr>  
   <tr>  
     <td>Sun&nbsp;3/60</td>  
     <td align="right">20</td>  
     <td align="right">24</td>  
     <td>24 30-pin SIMM: 1x9 100ns</td>  
     <td>P4 (video)</td>  
     <td align="right">1</td>  
     <td>sun3</td>  
   </tr>  
   <tr>  
     <td>Sun&nbsp;3/75</td>  
     <td align="right">16.67</td>  
     <td align="right">16</td>  
     <td>VME bus memory cards</td>  
     <td>VME bus</td>  
     <td align="right">2</td>  
     <td>sun3</td>  
   </tr>  
   <tr>  
     <td>Sun&nbsp;3/80</td>  
     <td align="right">20</td>  
     <td align="right">40/64</td>  
     <td>16 30-pin SIMM: 1x9 or 4x9 100ns</td>  
     <td>P4 (video)</td>  
     <td align="right">1</td>  
     <td>sun3x</td>  
   </tr>  
   <tr>  
     <td>Sun&nbsp;3/100 series</td>  
     <td align="right">16.67</td>  
     <td align="right">16</td>  
     <td>VME bus memory cards</td>  
     <td>VME bus</td>  
     <td align="right">3</td>  
     <td>sun3</td>  
   </tr>  
   <tr>  
     <td>Sun&nbsp;3/200 series</td>  
     <td align="right">25</td>  
     <td align="right">64</td>  
     <td>VME bus memory cards</td>  
     <td>VME bus</td>  
     <td align="right">12</td>  
     <td>sun3</td>  
   </tr>  
   <tr>  
     <td>Sun&nbsp;3/400 series</td>  
     <td align="right">33</td>  
     <td align="right">128</td>  
     <td>VME bus memory cards</td>  
     <td>VME bus</td>  
     <td align="right">12</td>  
     <td>sun3x</td>  
   </tr>  
   <tr>  
     <td>Sun&nbsp;3/E</td>  
     <td align="right">20</td>  
     <td align="right">4(?)</td>  
     <td>VME bus memory cards</td>  
     <td>VME bus</td>  
     <td align="right">n/a(?)</td>  
     <td>sun3</td>  
   </tr>  
 </table>  
   
 The RAM column is maximum supported RAM in megabytes.  
   
 Sun made a variety of VME bus cabinets with different numbers of bus slots; ultimate RAM and I/O expansion is more a matter of how many bus slots there, rather than the particular CPU you have.  
   
 The Sun3/80 RAM capacity varies with the boot ROM revision - 3.0.2 allows 40MB, 3.0.3 allows 64MB.  
   
 The Sun 3/50 has 4MB soldered on the motherboard; all RAM expansions for that workstation were provided by third-party solutions (read "hacks") of one kind or another.  
   
 The Sun 3/E is a 6U VME single-board computer intended as an embedded system component.  
   
 The Sun 3/80 workstation and Sun 3/400 series servers are sun3x architecture machines based on the [Motorola 68030 CPU](http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MC68030). They were Sun's last design using Motorola microprocessors, and were somewhat complicated by the fact that the mc68030 has an integrated MMU in the CPU chip.  
   
 Sun Microsystems stopped designing systems with Motorola microprocessors when their own SPARC CPU design became a commercial success.   
   
 ###Disk and RAM Requirements  
   
 Minimum  
   
     4MB RAM, ~80MB disk  
   
 Normal  ### Disk and RAM Requirements
   
     8MB RAM, 200MB disk  * Minimum
       * 4MB RAM, ~80MB disk
 Normal + X11  * Normal
       * 8MB RAM, 200MB disk
     16MB RAM, 300MB disk  * Normal + X11
       * 16MB RAM, 300MB disk
   
 The complete NetBSD sources without objects require 200MB of disk.  The complete NetBSD sources without objects require 200MB of disk.
   
 To run the X Window System or compile the NetBSD system sources (i.e. development), more RAM and disk are recommended. Good performance requires 8MB of RAM, or 16MB of RAM when running the X Window System.  To run the X Window System or compile the NetBSD system sources
   (i.e. development), more RAM and disk are recommended.
   Good performance requires 8MB of RAM, or 16MB of RAM
   when running the X Window System.
   
 ###Supported Hardware  ### Supported Hardware
   
 The following Sun3 devices are currently supported:  The following Sun3 devices are currently supported:
   
 * RS-232c Serial ports:  * RS-232c Serial ports:
   * built-in z8530 SCC as ttya, ttyb (zs)    * built-in z8530 SCC as ttya, ttyb (*zs*)
 * Sun Video adapters:  * Sun Video adapters:
   * 1 bpp framebuffer, (bwtwo)    * 1 bpp framebuffer, (*bwtwo*)
   * 8 bpp framebuffer (cgtwo)    * 8 bpp framebuffer (*cgtwo*)
   * 8 bpp (+overlay) framebuffer (cgfour)    * 8 bpp (+overlay) framebuffer (*cgfour*)
 * Network interfaces:  * Network interfaces:
   * On-board AMD LANCE Ethernet (le)    * On-board AMD LANCE Ethernet (*le*)
   * On-board Intel Ethernet (ie)    * On-board Intel Ethernet (*ie*)
   * VME Intel Ethernet board (ie)    * VME Intel Ethernet board (*ie*)
 * SCSI bus host adapters:  * SCSI bus host adapters:
   * On-board NCR 5380 SCSI Bus Controller (si)    * On-board NCR 5380 SCSI Bus Controller (*si*)
   * On-board Emulex SCSI controller on sun3x (esp)    * On-board Emulex SCSI controller on sun3x (*esp*)
   * Sun-3 VME SCSI (also NCR 5380 SBC, Sun part # 501-1236) (si)    * Sun-3 VME SCSI (also NCR 5380 SBC, Sun part # 501-1236) (*si*)
 * SMD Disks: (the big, heavy ones)  * SMD Disks: (the big, heavy ones)
   * Xylogics 450/451 (xy)    * Xylogics 450/451 (*xy*)
   * Xylogics 753/7053 (xd)    * Xylogics 753/7053 (*xd*)
 * Floppy drive:  * Floppy drive:
   * Sun 3/80 built-in floppy drive (fdc)    * Sun 3/80 built-in floppy drive (*fdc*)
 * Input devices:  * Input devices:
   * Sun keyboard (kbd) and mouse (ms)    * Sun keyboard (*kbd*) and mouse (*ms*)
 * Miscellaneous:  * Miscellaneous:
   * Battery-backed real-time clock.    * Battery-backed real-time clock.
   
 If you have a device that's not listed, it might be compatible with something else, or we might have simply forgotten it. If all else fails, maybe you could write a driver!  If you have a device that's not listed, it might be compatible with
   something else, or we might have simply forgotten it.
 Note: The Sun VME sc SCSI card is not yet supported.   If all else fails, maybe you could write a driver!
   
   
   Note: The Sun VME *sc* SCSI card is not yet supported. 
 """  """
 additional="""  additional="""
 Features of NetBSD/sun3  ### Features of NetBSD/sun3
   
 * Native boot programs for disk, network, and tape  * Native boot programs for disk, network, and tape
 * Automated installation tools (using a "miniroot")  * Automated installation tools (using a "miniroot")
Line 179  Features of NetBSD/sun3 Line 85  Features of NetBSD/sun3
 * Supports most SCSI devices (CD-ROM, disk, etc)  * Supports most SCSI devices (CD-ROM, disk, etc)
 * Diskless (network) boot capability  * Diskless (network) boot capability
 * Built-in kernel debugger  * Built-in kernel debugger
 * [SunOS 4.1 Compatibility](http://www.netbsd.org/ports/sun3/faq.html#sunos_compat)  * [SunOS 4.1 Compatibility](http://www.NetBSD.org/ports/sun3/faq.html#sunos_compat)
   
 ###links  ###links
 * [ILVSUN3](http://www.ilvsun3.com/) page by arthur also has various useful information about TME and Sun3 stuff.  * [ILVSUN3](http://www.ilvsun3.com/) page by arthur also has various useful information about TME and Sun3 stuff.
 * [The Machine Emulator (tme)](http://people.csail.mit.edu/fredette/tme/) can emulate a Sun 3/150 running NetBSD.  * [The Machine Emulator (tme)](http://people.csail.mit.edu/fredette/tme/) can emulate a Sun 3/150 running NetBSD.
   * [Frequently Asked Questions (FAQ)](http://www.NetBSD.org/ports/sun3/faq.html)
 <div id="content"><div class="fullWidth"><div class="rowOfBoxes">  
 <h1>NetBSD/sun3 Frequently Asked Questions</h1>  
 <h2 class="title">NetBSD/sun3 Frequently Asked Questions</h2>  
 <h3 class="title"><a name="general">General Questions</a></h3>  
 <ul>  
 <li><a href="#le0-not-multicast-capable">No multicast or IPv6 - "le0: not multicast capable" </a></li>  
 <li><a href="#3-80-esp-endless-reset">Running diskless 3/80 with ESP driver - "esp: SCSI bus reset." </a></li>  
 <li><a href="#sunos_compat">SunOS 4.1 Compatibility</a></li>  
 <li><a href="#boot-devices">Booting SCSI devices at different targets</a></li>  
 <li><a href="#sun3x-history">History of NetBSD/sun3x</a></li>  
 </ul>  
 <h3 class="title"><a name="info_sources">Other sources of information</a></h3>  
 <ul>  
 <li><a href="#sunhelp">SunHELP</a></li>  
 <li><a href="#hwreffaq">Sun Hardware Reference FAQ</a></li>  
 <li><a href="#hostidfaq">Sun NVRAM/Hostid FAQ</a></li>  
 <li><a href="#cdromfaq">Sun CD-ROM FAQ</a></li>  
 <li><a href="#installnotes">NetBSD 6.0 install notes</a></li>  
 <li><a href="#mailinglist">port-sun3 mailing list</a></li>  
 <li><a href="#disklesshowto">Diskless NetBSD HOW-TO</a></li>  
 <li><a href="#sun3arc">Sun3 Archive</a></li>  
 <li><a href="#techrat">Techrat's Sun 3/160 pages</a></li>  
 <li><a href="#netbsddocs">General NetBSD Documentation</a></li>  
 </ul>  
 <hr>  
 <h3 class="title">General Questions</h3>  
                 <h4 class="title">  
 <a name="le0-not-multicast-capable"></a>No multicast or IPv6 - "<code class="code">le0: not multicast capable</code>"  (<a href="#general">top</a>)  
   </h4>  
                 <p> The LANCE revision C chips used in  
                     some sun3s (not the sun3x) have a bug which sometimes results in garbage  
                     inserted where the first bits should be, with the correct bits shifted later. So  
                     instead of the destination MAC address at the beginning, you get something  
                     random looking. </p>  
                 <p> The workaround is to examine the beginning of the packet and throw away  
                     anything that's not for us (my MAC or broadcast). Unfortunately this prevents  
                     the use of multicast. </p>  
                 <p> The LANCE Rev. C chip was probably only used in the 3/50, so on other sun3  
                     machines you should be able to <a class="ulink" href="../../docs/kernel/#how_to_build_a_kernel" target="_top">build a  
                     kernel</a> without the line:</p>  
                 <pre class="programlisting">options LANCE_REVC_BUG</pre>  
               
                 <h4 class="title">  
 <a name="3-80-esp-endless-reset"></a>Running diskless 3/80 with ESP driver - <code class="code">"esp: SCSI bus reset."</code>  (<a href="#general">top</a>)  
   </h4>  
                 <p>  
                     This message is a symptom of a bug in the  
                     esp driver on diskless systems. The ESP (Emulex SCSI Processor) driver in  
                     NetBSD/sun3x has a bug that causes it to enter an endless loop when it probes an  
                     empty SCSI bus. To work around this problem, use a kernel which does not have  
                     the esp device driver, or plug in at least one powered SCSI device into the bus.</p>  
               
                 <h4 class="title">  
 <a name="sunos_compat"></a>SunOS 4.1 Compatibility (<a href="#general">top</a>)  
   </h4>  
                 <p> NetBSD/Sun3 features extensive binary compatibility with SunOS 4.1.x  
                     programs. Static SunOS executables will run without any extra setup. </p>  
                 <p> To run dynamic executables, you'll need to provide the dynamic libraries that  
                     came with your SunOS installation. SunOS programs that will  
                     <span class="emphasis"><em>not</em></span> work include those that use the SunOS kvm library,  
                     certain (low-level) disk manipulation utilities, and programs making explicit  
                     use of Sun's STREAMS subsystem. Check the <a href="http://netbsd.gw.com/cgi-bin/man-cgi?compat_sunos+8+NetBSD-6.0+i386">compat_sunos(8)</a> manual page  
                     for more details. </p>  
               
                 <h4 class="title">  
 <a name="boot-devices"></a>Booting SCSI devices at different targets (<a href="#general">top</a>)  
   </h4>  
                 <p> All sun3 and sun3x monitors support booting from SCSI devices. Most users  
                     will be familiar with booting from the monitor device <code class="code">sd(0,0,0)</code>,  
                     which they know means booting the SCSI disk at target zero. However, determining  
                     the monitor device name for booting an arbitrary SCSI device can be confusing. </p>  
                 <p> A monitor boot device takes the form  
                         <span class="emphasis"><em>dev</em></span><code class="code">(</code><span class="emphasis"><em>cntrl</em></span><code class="code">,</code><span class="emphasis"><em>unit</em></span><code class="code">,</code><span class="emphasis"><em>part</em></span><code class="code">)</code>.  
                         <span class="emphasis"><em>dev</em></span> is two letters, and <span class="emphasis"><em>cntrl</em></span>,  
                         <span class="emphasis"><em>unit</em></span>, and <span class="emphasis"><em>part</em></span> are hexadecimal  
                     numbers. </p>  
                 <p> For SCSI disks and CD-ROMs, <span class="emphasis"><em>dev</em></span> is <code class="code">sd</code>. For  
                     SCSI tapes, <span class="emphasis"><em>dev</em></span> is <code class="code">st</code>. </p>  
                 <p> For all SCSI devices, <span class="emphasis"><em>cntrl</em></span> is the number of the SCSI  
                     controller the device is attached to. For a machine with a single SCSI  
                     controller, <span class="emphasis"><em>cntrl</em></span> is <code class="code">0</code>. </p>  
                 <p> For all SCSI devices, <span class="emphasis"><em>unit</em></span> identifies the SCSI target  
                     and logical unit number of the device. Exactly how the SCSI target and logical  
                     unit number are combined into the single number <span class="emphasis"><em>unit</em></span>  
                     depends on your machine type and ROM revision, and whether or not the device is  
                     a disk, CD-ROM, or tape. Use the tables below to figure out how  
                     <span class="emphasis"><em>unit</em></span> works on your machine. </p>  
                 <p> For SCSI disks and CD-ROMs, <span class="emphasis"><em>part</em></span> selects the partition  
                     to boot on that disk or CD-ROM. The first partition is <code class="code">0</code>, the  
                     second partition is <code class="code">1</code>, etc. Normally, <span class="emphasis"><em>part</em></span> is  
                         <code class="code">0</code>, since the first partition on a disk is usually the bootable  
                     one. Common exceptions are booting a miniroot that has been written to the swap  
                     partition, in which case <span class="emphasis"><em>part</em></span> is <code class="code">1</code>, or booting  
                     a CD-ROM that contains different bootable partitions for different  
                     architectures, in which case you have to know which partition boots your  
                     architecture. </p>  
                 <p> For SCSI tapes, <span class="emphasis"><em>part</em></span> selects the tape segment (also  
                     called "tape file") to boot. The first tape segment is <code class="code">0</code>, the  
                     second tape segment is <code class="code">1</code>, etc. You will need to know which tape  
                     segment is bootable for your architecture in order to give the right  
                         <span class="emphasis"><em>part</em></span>. </p>  
                 <p> Finally, these are the tables that demonstrate how <span class="emphasis"><em>unit</em></span>  
                     works on various machines. They list <code class="code">sd</code> monitor devices for disks  
                     and CD-ROMs, and <code class="code">st</code> monitor devices for tapes, all at different  
                     SCSI targets. These tables assume that you want the first SCSI controller  
                         <code class="code">0</code>, and the first partition or first tape segment  
                     <code class="code">0</code>. Also, because many Sun 3 models use the same CPU board, to keep  
                     these tables simple Sun's CPU board code names are used wherever possible. </p>  
   
                 <div class="informaltable">  
 <a name="hw_model"></a>  
                     <table border="1">  
 <colgroup>  
 <col>  
 <col>  
 <col>  
 <col>  
 </colgroup>  
 <thead><tr>  
 <th>Model</th>  
 <th>CPU</th>  
 <th>Model</th>  
 <th>CPU</th>  
 </tr></thead>  
 <tbody>  
 <tr>  
 <td>3/75</td>  
 <td>  
                                     <span class="emphasis"><em>Carrera</em></span>  
                                 </td>  
 <td>3/140</td>  
 <td>  
                                     <span class="emphasis"><em>Carrera</em></span>  
                                 </td>  
 </tr>  
 <tr>  
 <td>3/150</td>  
 <td>  
                                     <span class="emphasis"><em>Carrera</em></span>  
                                 </td>  
 <td>3/160</td>  
 <td>  
                                     <span class="emphasis"><em>Carrera</em></span>  
                                 </td>  
 </tr>  
 <tr>  
 <td>3/180</td>  
 <td>  
                                     <span class="emphasis"><em>Carrera</em></span>  
                                 </td>  
 <td>&nbsp;</td>  
 <td>&nbsp;</td>  
 </tr>  
 </tbody>  
 </table>  
                 </div>  
                 <p> </p>  
   
                 <div class="informaltable">  
 <a name="hw_cpu_rom"></a>  
   
                     <table border="1">  
 <colgroup>  
 <col align="center" class="col1">  
 <col align="center" class="col2">  
 <col align="center" class="col3">  
 <col align="center" class="col4">  
 <col align="center" class="col5">  
 <col align="center" class="col6">  
 <col align="center" class="col7">  
 <col align="center" class="col8">  
 <col align="center" class="col9">  
 </colgroup>  
 <thead>  
 <tr>  
 <th rowspan="2" align="center">CPU/rev ROM</th>  
 <th colspan="8" align="center">Monitor device to  
                                     boot the disk or CD-ROM at target</th>  
 </tr>  
 <tr>  
 <th align="center">0</th>  
 <th align="center">1</th>  
 <th align="center">2</th>  
 <th align="center">3</th>  
 <th align="center">4</th>  
 <th align="center">5</th>  
 <th align="center">6</th>  
 <th align="center">7</th>  
 </tr>  
 </thead>  
 <tbody>  
 <tr>  
 <td align="center">3/60 rev 1.9 <span class="emphasis"><em>Carrera</em></span> rev 2.7</td>  
 <td align="center">  
                                     <code class="code">sd(0,0,0)</code>  
                                 </td>  
 <td align="center">  
                                     <code class="code">sd(0,4,0)</code>  
                                 </td>  
 <td align="center">  
                                     <code class="code">sd(0,8,0)</code>  
                                 </td>  
 <td align="center">  
                                     <code class="code">sd(0,C,0)</code>  
                                 </td>  
 <td align="center">  
                                     <code class="code">sd(0,10,0)</code>  
                                 </td>  
 <td align="center">  
                                     <code class="code">sd(0,14,0)</code>  
                                 </td>  
 <td align="center">  
                                     <code class="code">sd(0,18,0)</code>  
                                 </td>  
 <td align="center">N/A</td>  
 </tr>  
 <tr>  
 <td align="center">3/80 rev 2.9.2</td>  
 <td align="center">  
                                     <code class="code">sd(0,0,0)</code>  
                                 </td>  
 <td align="center">  
                                     <code class="code">sd(0,8,0)</code>  
                                 </td>  
 <td align="center">  
                                     <code class="code">sd(0,10,0)</code>  
                                 </td>  
 <td align="center">  
                                     <code class="code">sd(0,18,0)</code>  
                                 </td>  
 <td align="center">  
                                     <code class="code">sd(0,20,0)</code>  
                                 </td>  
 <td align="center">  
                                     <code class="code">sd(0,28,0)</code>  
                                 </td>  
 <td align="center">  
                                     <code class="code">sd(0,30,0)</code>  
                                 </td>  
 <td align="center">N/A</td>  
 </tr>  
 </tbody>  
 </table>  
                 </div>  
                 <p> </p>  
   
   
                 <div class="informaltable">  
 <a name="cpu_monitor"></a>  
                     <table border="1">  
 <colgroup>  
 <col class="col1">  
 <col class="col2">  
 <col class="col3">  
 <col class="col4">  
 <col class="col5">  
 <col class="col6">  
 <col class="col7">  
 <col class="col8">  
 <col class="col9">  
 </colgroup>  
 <thead>  
 <tr>  
 <th rowspan="2">CPU/rev ROM</th>  
 <th colspan="8" align="center">Monitor device to  
                                     boot the tape at target</th>  
 </tr>  
 <tr>  
 <th>0</th>  
 <th>1</th>  
 <th>2</th>  
 <th>3</th>  
 <th>4</th>  
 <th>5</th>  
 <th>6</th>  
 <th>7</th>  
 </tr>  
 </thead>  
 <tbody>  
 <tr>  
 <td>3/60 rev 1.9</td>  
 <td>???</td>  
 <td>  
                                     <code class="code">st(0,8,0)</code>  
                                 </td>  
 <td>  
                                     <code class="code">st(0,10,0)</code>  
                                 </td>  
 <td>  
                                     <code class="code">st(0,18,0)</code>  
                                 </td>  
 <td>  
                                     <code class="code">st(0,0,0)</code>  
                                 </td>  
 <td>  
                                     <code class="code">st(0,28,0)</code>  
                                 </td>  
 <td>  
                                     <code class="code">st(0,30,0)</code>  
                                 </td>  
 <td>N/A</td>  
 </tr>  
 <tr>  
 <td>3/80 rev 2.9.2</td>  
 <td>???</td>  
 <td>  
                                     <code class="code">st(0,8,0)</code>  
                                 </td>  
 <td>  
                                     <code class="code">st(0,10,0)</code>  
                                 </td>  
 <td>  
                                     <code class="code">st(0,18,0)</code>  
                                 </td>  
 <td>  
                                     <code class="code">st(0,0,0)</code>  
                                 </td>  
 <td>  
                                     <code class="code">st(0,28,0)</code>  
                                 </td>  
 <td>  
                                     <code class="code">st(0,30,0)</code>  
                                 </td>  
 <td>N/A</td>  
 </tr>  
 </tbody>  
 </table>  
                 </div>  
                 <p> The above tables also assume that you want SCSI logical unit number zero. The  
                     SCSI specification allows one SCSI target to contain different logical units  
                     (also called LUNs). Virtually no SCSI devices make use of this feature, and have  
                     only a single LUN, zero. However, if you know you have a disk at a LUN other  
                     than zero (early Sun SCSI disk setups do), you can add the LUN number to the  
                         <span class="emphasis"><em>unit</em></span> value, noting that <span class="emphasis"><em>unit</em></span> is a  
                     hexadecimal number. </p>  
               
                 <h4 class="title">  
 <a name="sun3x-history"></a>History of NetBSD/sun3x (<a href="#general">top</a>)  
   </h4>  
                 <p> The sun3x port of NetBSD was initiated by two independent groups of  
                     developers. The first group, headed by Gordon Ross and Jeremy Cooper, began work  
                     in March of 1996 with the (then) current sun3 port and the intent to create a  
                     new pmap system that was not based on the hp300 m68k code. Their work is the  
                     officially supported version of NetBSD/sun3x. </p>  
                 <p> The second group, headed by Tsubai Masanari, also began with the sun3  
                     distribution but instead choose to use the traditional hp300 m68k pmap. This  
                     approach allowed them to get a fully running system in a matter of weeks. They  
                     were the first to successfully integrate the SPARC Enhanced SCSI Processor  
                     driver into the kernel, proving that the Sun3x was indeed half SPARC, half Sun3. </p>  
                 <p> Although the currently supported NetBSD/sun3x is based on Gordon and Jeremy's  
                     work, they are indebted to the second group for their innovation. </p>  
                 <p> Between NetBSD 1.3 and 1.4 NetBSD/sun3x was merged into NetBSD/sun3. They  
                     build separate kernels, but share the same userland, and kernel build tree.  
                 </p>  
             <hr>  
 <h3 class="title">Other sources of information</h3>  
             <h4 class="title">  
 <a name="sunhelp"></a>SunHELP (<a href="#info_sources">top</a>)  
   </h4>  
                 <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">  
                     <a class="ulink" href="http://www.sunhelp.com/" target="_top">SunHELP</a> - much  
                     sun related information  
                 </li></ul></div>  
               
             <h4 class="title">  
 <a name="hwreffaq"></a>Sun Hardware Reference FAQ (<a href="#info_sources">top</a>)  
   </h4>  
                 <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">  
                     <a class="ulink" href="http://www.mso.anu.edu.au/~kim/faq/hardfaq.html" target="_top">Sun  
                     Hardware Reference FAQ</a> - overview of Sun hardware  
                     over the years  
                 </li></ul></div>  
               
             <h4 class="title">  
 <a name="hostidfaq"></a>Sun NVRAM/Hostid FAQ (<a href="#info_sources">top</a>)  
   </h4>  
                 <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">  
                     <a class="ulink" href="http://www.squirrel.com/squirrel/sun-nvram-hostid.faq.html" target="_top">Sun NVRAM/Hostid FAQ</a> - if your machine PROM's battery has gone dead  
                 </li></ul></div>  
               
             <h4 class="title">  
 <a name="cdromfaq"></a>Sun CD-ROM FAQ (<a href="#info_sources">top</a>)  
   </h4>  
                 <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">  
                     <a class="ulink" href="http://www.pimpworks.org/sun/cdrom.html" target="_top">Sun  
                     CD-ROM FAQ</a> - lists which CD-ROM drives can boot a  
                     Sun  
                 </li></ul></div>  
               
             <h4 class="title">  
 <a name="installnotes"></a>NetBSD 6.0 install notes (<a href="#info_sources">top</a>)  
   </h4>  
                 <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">  
                     <a class="ulink" href="ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-6.0/sun3/INSTALL.html" target="_top">NetBSD 6.0 install notes</a> - supported hardware and how to install.  
                 </li></ul></div>  
               
             <h4 class="title">  
 <a name="mailinglist"></a>port-sun3 mailing list (<a href="#info_sources">top</a>)  
   </h4>  
                 <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">  
                     <a class="ulink" href="../../mailinglists/#port-sun3" target="_top"> port-sun3 mailing list</a> -  
                         if you have any additional questions please subscribe.  
                 </li></ul></div>  
               
             <h4 class="title">  
 <a name="disklesshowto"></a>Diskless NetBSD HOW-TO (<a href="#info_sources">top</a>)  
   </h4>  
                 <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">  
                     <a class="ulink" href="../../docs/network/netboot/" target="_top">Diskless NetBSD  
                         HOW-TO</a>.  
                 </li></ul></div>  
               
             <h4 class="title">  
 <a name="sun3arc"></a>Sun3 Archive (<a href="#info_sources">top</a>)  
   </h4>  
                 <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">  
                     The <a class="ulink" href="http://www.sun3arc.org/" target="_top">Sun3 Archive</a> has lots of  
                         information about Sun3 hardware, PROM images, etc.  
                 </li></ul></div>  
               
             <h4 class="title">  
 <a name="techrat"></a>Techrat's Sun 3/160 pages (<a href="#info_sources">top</a>)  
   </h4>  
                 <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">  
                     <a class="ulink" href="http://www.obsolyte.com/sun3/" target="_top">Techrat's Sun 3/160  
                         pages</a> contains information on Techrat's 3/160, hardware information,  
                         lots of pictures of old Sun hardware, and links to various FAQs and  
                     things.  
                 </li></ul></div>  
               
             <h4 class="title">  
 <a name="netbsddocs"></a>General NetBSD Documentation (<a href="#info_sources">top</a>)  
   </h4>  
                 <div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">  
                     <a class="ulink" href="../../docs/" target="_top">General NetBSD Documentation</a> -  
                         for questions not specific to NetBSD/sun3.  
                 </li></ul></div>  
             <hr>Back to  <em><a href="./">NetBSD/sun3 Port Page</a></em>  
 </div></div></div>  
 """  """
   
 ]]  ]]
 [[!tag tier2port]]  [[!tag tier2port]]

Removed from v.1.2  
changed lines
  Added in v.1.6


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb