[BACK]Return to hppa.html CVS log [TXT][DIR] Up to [local] / www

File: [local] / www / hppa.html (download) (as text)

Revision 1.117, Fri Feb 13 20:52:31 2004 UTC (20 years, 3 months ago) by mickey
Branch: MAIN
Changes since 1.116: +4 -2 lines

a couple more unspported thingies

<!DOCTYPE HTML PUBLIC  "-//W3C//DTD HTML 4.01 Transitional//EN"
	"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>OpenBSD/hppa</title>
<link rev="made" href="mailto:www@openbsd.org">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="resource-type" content="document">
<meta name="description" content="the OpenBSD/hppa page">
<meta name="keywords" content="openbsd,hppa">
<meta name="distribution" content="global">
<meta name="copyright" content="This document copyright 1996-2004 by OpenBSD.">
</head>

<body bgcolor="#ffffff" text="#000000" link="#23238e">
<a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>
<p>
<h2><font color="#e00000">OpenBSD/hppa</font></h2>

<hr>

<p>
OpenBSD/hppa runs on a large set of the 32-bit Hewlett Packard Precision
Architecture workstations and servers (HP PA-RISC).
</p>

<p>
A mailing list dedicated to the OpenBSD/hppa port is available at
<u><font color="#23238e">hppa@openbsd.org</font></u>.
To join the OpenBSD/hppa mailing list, send a message body of <b>"subscribe
hppa"</b> to <a href="mailto:majordomo@openbsd.org">majordomo@openbsd.org</a>.
Please be sure to check our <a href="mail.html">mailing list policy</a> before
subscribing.
</p>

<p>
The current port maintainer is
<a href="mailto:mickey@openbsd.org">Michael Shalayeff</a>.
Others are definitely welcome to contribute!
</p>

<a href="#toc"></a>
<h3><font color="#0000e0"><i>Table of contents</i></font></h3>
<p>
<ul>
  <li><a href="#history">History of the port</a>
  <li><a href="#status">Current status</a>
  <li><a href="#projects">Project list</a>
  <li><a href="#hardware">Supported hardware list</a>
  <li><a href="#hwdocs">Hardware documentation</a>
  <li><a href="#install">Getting and installing OpenBSD/hppa</a>
  <li><a href="#netboot">Netbooting the installation media</a>
</ul>

<hr>
<a name="history"></a>
<h3><font color="#0000e0"><strong>History:</strong></font></h3>

<p>
This project was started in those days when the only
open source operating systems for HP PA-RISC computers were
<a href="http://www.cs.utah.edu/projects/flux/lites/html">Lites</a> and
<a href="http://www.mklinux.org">MkLinux</a>.
These two sources were a major supply of information and
code for initial development of the OpenBSD/hppa port.
<a href="http://www.cs.utah.edu/~mike/hpbsd/hpbsd.html">HPBSD</a>
is encumbered by HP proprietary code and USL licensing and is
not publicly available.
One of the major direct benefits from previous porting efforts
(besides the code, of course) was support for HP PA-RISC in GCC and
binutils, which allowed quick building of a cross-tools environment
for development.
</p>

<p>
Later on, Hewlett-Packard decided to sponsor a
<a href="http://www.parisc-linux.org/">Linux</a> port to the PA-RISC
family, which actually resulted in some proprietary documentation
being released, even though their target was a different class of 9000
machines back then.
</p>

<hr>
<a name="status"></a>
<h3><font color="#0000e0"><strong>Current status:</strong></font></h3>

<p>
Currently, all the supported systems boot multi-user, although not all of them
can boot off disk. In addition to the release, full snapshots are made
periodically, and work is ongoing to provide better hardware support.
</p>

<hr>
<a name="projects"></a>
<h3><font color="#0000e0"><strong>Projects (in no particular order):
</strong></font></h3>

<p>
<ul>
  <li>Improve overall stability
  <li>Support the NCR53C700 SCSI Narrow SE controller
  <li>Support the NCR53C720 SCSI FWD controller
  <li>Improve installation procedures
  <li>Improve port-specific documentation
  <li>Support booting from tape and CD-ROM
  <li>Support for 8x00 CPUs
  <li>Support for 7000 CPUs (the "original snakes" machines)
  <li>HP-UX emulation
  <li>PARISC/Linux emulation
  <li>Shared libraries
  <li>X11 support
  <li>Support for multiprocessor systems
</ul>

<hr>
<a name="hardware"></a>
<h3><font color="#0000e0"><strong>Supported hardware:</strong></font></h3>

<p>
<h4>Supported models</h4>

<p>
<ul>
  <li>PA7100-based: 715/33, 715/50, 715/75, 725/50, 725/75, 735/100, 742i, 745i, 747i, 755/100
  <li>PA7100LC-based: 712, 715/64, 715/80, 715/100, 715/100XC, 725/64, 725/100, 743i, 748i, SAIC Galaxy 1100
  <li>PA7150-based: 735/125, 755/125
  <li>PA7200-based: J200, J210, J210XC, C100, C110
  <li>PA7300LC-based: 744, 745, 748, A180[C], B132L[+], B160L, B180L+, C132L, C160L, RDI PrecisionBook (C160L)
</ul>

<p>
<h4>Supported peripherals</h4>

<p>
The list of supported hardware below is not meant to be exhaustive.
Hardware is needed for developers, to further help development and testing.
Please see our <a href="want.html">"Wanted List"</a>
(contact <a href="mailto:mickey@openbsd.org">mickey</a>).
</p>

<p>
<ul>
<li><strong>
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=io&amp;sektion=4&amp;arch=hppa">Bus/IO
controllers</a></strong>
  <ul>
  <li>Phantom PseudoBC GSC+ Port
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=phantomas&amp;sektion=4&amp;arch=hppa">phantomas</a>)
  <li>GSC
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=gsc&amp;sektion=4&amp;arch=hppa">gsc</a>):
  LASI
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=lasi&amp;sektion=4&amp;arch=hppa">lasi</a>),
  ASP
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=asp&amp;sektion=4&amp;arch=hppa">asp</a>)
  <li>PCI Dino and Cujo bridges
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=dino&amp;sektion=4&amp;arch=hppa">dino</a>)
  </ul>
<li><strong>SGC/GSC graphics</strong>
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=sti&amp;sektion=4">sti</a>)
  <ul>
  <li>Artist (as found on 712)
  <li>CRX-8, CRX-24, HCRX-8, HCRX-24
  </ul>
<li><strong>Serial ports</strong>
  <ul>
  <li>On-board ns16550 and compatibles
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=com&amp;sektion=4">com</a>)
  </ul>
<li><strong>Parallel ports</strong>
  <ul>
  <li>On-board parallel port
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=lpt&amp;sektion=4">lpt</a>)
  </ul>
<li><strong>SCSI controllers</strong>
  <ul>
  <li>NCR53C710 SCSI Narrow SE controller
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=osiop&amp;sektion=4">osiop</a>)
  <li>NCR53C8xx SCSI I/O Processors
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=siop&amp;sektion=4">siop</a>)
  <li>Adaptec AIC-7770-based SCSI host adapters (not bootable)
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ahc&amp;sektion=4">ahc</a>)
  </ul>
<li><strong>Ethernet</strong>
  <ul>
  <li>On-board Intel i82596 ethernet
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ie&amp;sektion=4&amp;arch=hppa">ie</a>)
  <li>Intel/DEC 21443 "Tulip" clones (onboard on A, B and C class)
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=dc&amp;sektion=4">dc</a>)
  <li>Intel i8255x-based (except the i82556) PCI adapters (not bootable)
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=fxp&amp;sektion=4">fxp</a>), including:
	<ul>
	<li>Intel EtherExpress PRO/10+  
	<li>Intel EtherExpress PRO/100, PRO/100B, and PRO/100+
	<li>Intel EtherExpress PRO/100+ "Management Adapter"
	<li>Intel EtherExpress PRO/100 Dual Port
	<li>Intel PRO/100 VE, PRO/100 VM, and PRO/100 S
	</ul>
  </ul>
<li><strong>Audio devices</strong>
  <ul>
  <li>On-board harmony CS4215/AD1849
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=harmony&amp;sektion=4&amp;arch=hppa">harmony</a>)
  </ul>
<li><strong>Input devices</strong>
  <ul>
  <li>HIL keyboards
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=hilkbd&amp;sektion=4">hilkbd</a>)
  <li>HIL mice and graphics tablet
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=hilms&amp;sektion=4">hilms</a>)
  <li>PS/2 keyboards
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=gsckbd&amp;sektion=4&amp;arch=hppa">gsckbd</a>)
  <li>PS/2 mice
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pms&amp;sektion=4">pms</a>)
  </ul>
<li><strong>Miscellaneous devices</strong>
  <ul>
  <li>Battery-backed real time clock
  <li>Soft power button as available on some models
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=power&amp;sektion=4&amp;arch=hppa">power</a>)
  </ul>
</ul>

<p>
<h4>Unsupported models</h4>

<p>
The following systems may eventually work:
<ul>
  <li>PA7000-based machines: 705, 710, 720, 730, 750
  <li>PA2.0 systems (in 32-bit mode): C160, C180, C180XP, C180+, C200+, C230, C240+
  <li>HP 9000 E-Class (with limited I/O)
  <li>HP 9000 D-Class, at least the 32-bit models
  <li>HP 9000 K100, K200, K210, K220, K400, K410, K420
  <li>Hitachi VQ200, VQ210, and some other non-HP workstations
  <li>Hitachi 9000V 3050RX/* workstations and 3500/* servers
  <li>HP VME and VXI single board systems (requires VME at least)
</ul>

<p>
The following systems are very unlikely to be supported since they either have
incompatible firmware (the 3000s) or almost completely undocumented I/O
subsystems (the 8x7s). 
<ul>
  <li>HP 3000 900
  <li>HP 9000 8x7 (F, G, H, I-Class)
</ul>

<p>
These Convex systems are NUMA supercomputing clusters
consisting of one or more 8-way SMP nodes with PA7100 or PA7200 CPUs.
They are very unlikely to be ever supported.
<ul>
  <li>Convex Exemplar SPP1000/{CD,XA}
  <li>Convex Exemplar SPP1200/{CD,XA}
  <li>Convex Exemplar SPP1600/{CD,XA}
</ul>

<p>
These systems will, probably, never be supported by this port since
they are of 1.0 PA-RISC architecture, which is substantially
inferior to the 1.1:
<ul>
  <li>HP 9000 600, 635, 645
  <li>HP 9000 800, 808, 810, 815, 822, 825, 832, 834, 835, 836, 840, 842, 844, 845, 846, 850, 852, 855, 860, 865, 870, 890
  <li>HP 9000 900, 920, 922, 925, 930, 932, 935, 948, 949, 950, 950S, 955, 958, 960, 980, 990, 992
</ul>

<p>
<h4>Unsupported peripherals</h4>

<p>
This list is not meant to be exhaustive either, but sums up the most commonly
encountered devices on hppa machines.
<ul>
<li><strong>Bus/IO controllers</strong>
  <ul>
  <li>Dino in card mode
  <li>EISA bus
  <li>Runway IOC
  <li>VME controller
  </ul>
<li><strong>SCSI controllers</strong>
  <ul>
  <li>NCR53C720 SCSI I/O Processors
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=siop&amp;sektion=4">siop</a>)
  </ul>
<li><strong>On-board floppy controller</strong>
<li><strong>Dino's ps/2 keyboard and mouse controller</strong>
</ul>

<hr>
<a name="hwdocs"></a>
<h3><font color="#0000e0"><strong>Hardware documentation:</strong></font></h3>

<p><small>
Most of the following documents have been released by Hewlett-Packard for
the <a href="http://www.parisc-linux.org/">PA-RISC Linux</a> project.
</small></p>

<p>
<ol type=1>
<li>HP PA-RISC CPUs
	<ol type=a>
<li><a href="http://ftp.parisc-linux.org/docs/chips/PCXL_ers.ps">PA7100LC CPU ERS</a>
<li><a href="http://ftp.parisc-linux.org/docs/chips/pcxl2_ers.ps">PA7300LC CPU ERS</a>
	</ol>
<li>Processor Dependent Code/I/O Dependent Code Interface<br> <small>(selected chapters from "PA-RISC I/O Architecture Specification")</small>
	<ol type=a>
<li><a href="http://ftp.parisc-linux.org/docs/arch/pdc32.pdf">PDC 1.1</a>
<li><a href="http://ftp.parisc-linux.org/docs/arch/iodc.pdf">IODC 1.1</a>
<li><a href="http://ftp.parisc-linux.org/docs/arch/ver_nums.pdf">Version and Identification Number Allocation</a>
<li><a href="http://ftp.parisc-linux.org/docs/arch/data_formats.pdf">Memory Data Formats 2.0</a>
<li><a href="http://ftp.parisc-linux.org/docs/arch/pdc.pdf">PDC Procedures 2.0</a>
<li><a href="http://ftp.parisc-linux.org/docs/arch/pdce.pdf">PDC Entry Points 2.0</a>
<li><a href="http://ftp.parisc-linux.org/docs/arch/os_interface.pdf">OS Interface 2.0</a>
	</ol>
<li>Bus controllers/bridges/adaptors
	<ol type=a>
<li><a href="http://ftp.parisc-linux.org/docs/chips/hardball_ers.pdf">ASP</a>
<li><a href="http://ftp.parisc-linux.org/docs/chips/lasi_ers.ps">LASI Core Bus Adapter (including lan, scsi, serial, lpt controllers)</a>
<li><a href="http://ftp.parisc-linux.org/docs/chips/dino_ers.ps">Dino PCI bridge</a>,
and <a href="http://ftp.parisc-linux.org/docs/chips/Dino_3_1_Errata.html">Errata</a>
<li><a href="http://ftp.parisc-linux.org/docs/chips/elroy_ers.ps">Elroy ERS (Edited for Open Source)</a>
<li>Astro
<a href="http://ftp.parisc-linux.org/docs/chips/astro_intro.ps">Overview</a>,
<a href="http://ftp.parisc-linux.org/docs/chips/astro_errors.ps">Error handling</a>,
<a href="http://ftp.parisc-linux.org/docs/chips/astro_ioc.ps">R2I Operations</a>,
<a href="http://ftp.parisc-linux.org/docs/chips/astro_regmap.ps">Registers Map</a>,
<a href="http://ftp.parisc-linux.org/docs/chips/astro_runway.ps">Runway Interface</a>,
<a href="http://ftp.parisc-linux.org/docs/chips/astro_sysmap.ps">System Mamory Map</a>
	</ol>
<li><a href="http://ftp.parisc-linux.org/docs/arch/sti.pdf">Stinger
graphics</a>
<li><a href="http://www.lsilogic.com/techlib/techdocs/storage_stand_prod/SCSIControllers/770.pdf">NCR
53C700/710/720 SCSI I/O Processors</a>
    <small>(the doc is actually for 770, which is claimed as compatible)</small>
<li><a href="http://www.lsilogic.com/techlib/marketing_docs/storage_stand_prod/integrated_circuits/lsi53c875e_pb.pdf">LSI
53C875 SCSI I/O Processor</a>
<li>Intel
<a href="http://developer.intel.com/design/network/datashts/290219.htm">i82596DX/SX</a>
and
<a href="http://developer.intel.com/design/network/datashts/290218.htm">i82596CA</a>
Ethernet Controllers
</ol>

<p>
Of course, no hppa page, be it OpenBSD or not, could pretend to be serious
without linking to the essential <a href="http://www.openpa.net/">OpenPA</a>
reference website.
</p>

<hr>
<a name="install"></a>
<h3><font color="#0000e0">
<strong>Getting and installing OpenBSD/hppa:</strong>
</font></h3>

<p>
The latest supported OpenBSD/hppa release is
<a href="34.html">OpenBSD 3.4</a>.
Here are the
<a href="ftp://ftp.OpenBSD.org/pub/OpenBSD/3.4/hppa/INSTALL.hppa">
OpenBSD/hppa 3.4 installation instructions
</a>.
</p>

<p>
Snapshots are made available from time to time, in
<a href="ftp://ftp.OpenBSD.org/pub/OpenBSD/snapshots/hppa">this location</a>
as well as in a few
<a href="ftp.html">mirrors</a>.
Here are the
<a href="ftp://ftp.OpenBSD.org/pub/OpenBSD/snapshots/hppa/INSTALL.hppa">
OpenBSD/hppa snapshot installation instructions
</a> as well.
</p>

<hr>
<a name="netboot"></a>
<h3><font color="#0000e0"><strong>Netbooting the installation media:</strong></font></h3>

<p>
The <tt>lif34.fs</tt> file contains both a bootloader and an installation
miniroot.
To boot it from the network, a server machine has to be setup so as to
let the hppa machine retrieve it:
<ol>
  <li>Server setup
    <ul>
    <li>For older machines (705, 7[1235]0, old 715)
	<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=rbootd&amp;sektion=8">rbootd</a>
	must be setup and started.
      <ul>
      <li><tt>/etc/rbootd.conf</tt> contains a single line per machine
      needing to boot from the server. Each line contains the ethernet
      address of the client hppa machine, and the filename to be loaded from
      the tftp server (relative to <tt>/usr/mdec/rbootd</tt>).
      For example:
	<pre>
	8:0:9:70:c4:11    lif34.fs    # 9000/720
	8:0:9:19:fb:a0    lif34.fs    # 9000/725
	</pre>
      </li>
      </ul>
    </li>
    <li>Recent machines (712, newer 715, 725) will not look for rbootd at all,
    but instead require a <b>bootp</b> setup.
      <ul>
      <li><tt>/etc/<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=bootptab&amp;sektion=5">bootptab</a></tt>
      contains an information block for each machine.  For example:
	<pre>
	# 9000/715
	boron:\
        	ha=0800095f5a6e:\
        	bf=lif34.fs:\
        	hd=:\
        	ht=ethernet:\
        	ip=10.0.1.143:\
        	sm=255.255.255.0:\
        	td=/tftpboot:
	</pre>
      </li>
	<li>
	Create directory <tt>/tftpboot</tt> and put the
	<tt>lif34.fs</tt> file in it.<br>
	</li>
	<li>
	Write an entry for the hppa in <tt>/etc/ethers</tt>:
	<pre>
	08:00:09:5f:5a:6e	boron
	</pre>
	</li>
	<li>
	Write another entry for it in <tt>/etc/hosts</tt>:
	<pre>
	10.0.1.143	boron
	</pre>
	</li>
	<li>
	The last step is to enable the necessary daemons for all of this to
	work.
	<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=bootpd&amp;sektion=8">bootpd</a>
	and
	<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=tftpd&amp;sektion=8">tftpd</a>
	are usually run from
	<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=inetd&amp;sektion=8">inetd</a>,
	so <tt>/etc/inetd.conf</tt> has to be modified and
	<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=inetd&amp;sektion=8">inetd</a>
	restarted. Also,
	<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=rarpd&amp;sektion=8">rarpd</a>
	needs to be enabled in
	<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=rc.conf&amp;sektion=5">rc.conf</a>.
	</li>
	</ul>
    </li>
    <li>For further reading on server setup for network booting in general,
    please refer to the
    <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=diskless&amp;sektion=8">diskless(8)</a>
    manual page.
    </li>
    </ul>
 <p>
  <li>Client Network Boot
  <ul>
    <li>BOOT_ADMIN<br>
	In order to get to the BOOT_ADMIN prompt, hit the <em>&lt;esc&gt;</em>
	key as the machine is coming up. Once it has probed bootable devices,
	a menu will be displayed; if the prompt is <i>not</i> <b>BOOT_ADMIN</b>,
	it will be necessary to type <i>``a''</i> to access it.
    </li>
    <li>Network boot command<br>
	Once at the 'BOOT_ADMIN' prompt, the command
<pre>
	BOOT_ADMIN&gt; boot lan isl
</pre>
        will proceed to the bootstrap of lif34.fs.
  </ul>
  </li>
</ol>

<hr>
<a href="plat.html">
<img height="24" width="24" src="back.gif" border="0" alt="Supported platforms">
</a>
<br>
<small><a href="mailto:www@openbsd.org">www@openbsd.org</a></small>
<br>
<small>$OpenBSD: hppa.html,v 1.117 2004/02/13 20:52:31 mickey Exp $</small>
</body>
</html>