www/hppa.html - diff

Return to hppa.html CVS log

Up to [local] / www

Diff for /www/hppa.html between version 1.65 and 1.66

version 1.65, 2002/11/08 20:05:32

version 1.66, 2002/11/11 19:42:11

Line 1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html>

<head>

<title>OpenBSD/hppa</title>

Line 13

Line 14

<hr>

<h3><font color=#0000e0><strong>Status and History:</strong></font></h3>

<h3><font color="#0000e0"><strong>Status and History:</strong></font></h3>

Systems boot to multi-user and full snapshots are made periodically.

There are several projects being under development to support

SCSI controllers and input devices,

Line 23

Line 25

<p>

This project was started in one of 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.cs.utah.edu/projects/flux/lites/html">Lites</a> and

<a href=http://www.osf.org/mall/os/pa-mklinux>MkLinux</a>.

<a href="http://www.osf.org/mall/os/pa-mklinux">MkLinux</a>.

These two sources were a major supply of information and

code for initial development of the OpenBSD/hppa port.

The <a href=http://www.cs.utah.edu/~mike/hpbsd/hpbsd.html>HPBSD</a>

The <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

Line 36

Line 38

build of cross-tools environment for development.

<p>

Later on HP decided to sponsor a

<a href=http://www.parisc-linux.org/>Linux</a> port to PA-RISC

<a href="http://www.parisc-linux.org/">Linux</a> port to PA-RISC

machines which actually resulted in some proprietary documentation

release, even they target different class of 9000 machines.

<p>

<h3><font color=#0000e0><strong>Supported Hardware:</strong></font></h3>

<h3><font color="#0000e0"><strong>Supported Hardware:</strong></font></h3>

<ul>

<li>CPUs (<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=intro&sektion=4&arch=hppa">intro</a> and (<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=cpu&sektion=4&arch=hppa">cpu</a>)):

<ul>

<li>PA7000-based: 705, 710, 720, 730, 750 (currently under development)

<li>PA7100-based: 715/33, 715/50, 715/75, 725/50, 725/75, 735/100, 755/100

Line 54

Line 56

</ul>

<li>bus/IO controllers:

<ul>

<li> GSC (<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=gsc&sektion=4&arch=hppa">gsc</a>): LASI (<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=lasi&sektion=4&arch=hppa">lasi</a>), ASP (<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=asp&sektion=4&arch=hppa">asp</a>)

</ul>

<li>SCSI controllers (currently under development):

<ul>

<li>NCR53C710 SCSI I/O Processors (<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=osiop&sektion=4">osiop</a>)

<li>NCR53C720 SCSI I/O Processors (<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=siop&sektion=4">siop</a>)

</ul>

<li>SGC/GSC graphics (<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=sti&sektion=4">sti</a>):

<ul>

<li>Artist (as found on 712)

<li>CRX-8, CRX-24, HCRX-8, HCRX-24

</ul>

<li>RS-232 devices:

<ul>

<li>On-board ns16550 or similar (<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=com&sektion=4">com</a>)

</ul>

<li>Input devices (currently under development):

<ul>

Line 89

Line 91

<br>

Hardware is needed for this project,

see <a href="want.html">"Wanted List"</a>

(contact <a href=mailto:mickey@openbsd.org>mickey</a>).

(contact <a href="mailto:mickey@openbsd.org">mickey</a>).

<h3><font color=#0000e0><strong>Documentation</strong></font></h3>

<h3><font color="#0000e0"><strong>Documentation</strong></font></h3>

<small>(most of which was released by HP for the

<a href=http://www.parisc-linux.org/>Linux/parisc</a> project)</small>:

<a href="http://www.parisc-linux.org/">Linux/parisc</a> project)</small>:

<li>HP PA-RISC CPUs

</ol>

<li><b>Processor Dependent Code/I/O Dependent Code Interface</b><br> <small>(selected chapters from "PA-RISC I/O Architecture Specification")</small>

<li><a href=http://ftp.parisc-linux.org/docs/ver_nums.pdf>Version and Identification Number Allocation</a>

<li><a href="http://ftp.parisc-linux.org/docs/ver_nums.pdf">Version and Identification Number Allocation</a>

<li><a href=http://ftp.parisc-linux.org/docs/data_formats.pdf>Memory Data Formats 2.0</a>

<li><a href="http://ftp.parisc-linux.org/docs/data_formats.pdf">Memory Data Formats 2.0</a>

<li><a href=http://ftp.parisc-linux.org/docs/pdc.pdf>PDC Procedures 2.0</a>

<li><a href="http://ftp.parisc-linux.org/docs/pdc.pdf">PDC Procedures 2.0</a>

<li><a href=http://ftp.parisc-linux.org/docs/pdce.pdf>PDC Entry Points 2.0</a>

<li><a href="http://ftp.parisc-linux.org/docs/pdce.pdf">PDC Entry Points 2.0</a>

<li><a href=http://ftp.parisc-linux.org/docs/os_interface.pdf>OS Interface 2.0</a>

<li><a href="http://ftp.parisc-linux.org/docs/os_interface.pdf">OS Interface 2.0</a>

</ol>

<li><b>Bus controllers/bridges/adaptors</b>

<li><a href=http://ftp.parisc-linux.org/docs/lasi_ers.ps>LASI Core Bus Adapter (including lan, scsi, serial, lpt controllers)</a>

<li><a href="http://ftp.parisc-linux.org/docs/lasi_ers.ps">LASI Core Bus Adapter (including lan, scsi, serial, lpt controllers)</a>

<li><a href=http://ftp.parisc-linux.org/docs/dino_ers.ps>Dino PCI bridge</a>,

<li><a href="http://ftp.parisc-linux.org/docs/dino_ers.ps">Dino PCI bridge</a>,

and <a href=http://ftp.parisc-linux.org/docs/Dino_3_1_Errata.html>Errata</a>

and <a href="http://ftp.parisc-linux.org/docs/Dino_3_1_Errata.html">Errata</a>

<li><a href=http://ftp.parisc-linux.org/docs/elroy_ers.ps>Elroy ERS (Edited for Open Source)</a>

<li><a href="http://ftp.parisc-linux.org/docs/elroy_ers.ps">Elroy ERS (Edited for Open Source)</a>

<li>Astro <a href=http://ftp.parisc-linux.org/docs/astro_intro.ps>Overview</a>, <a href=http://ftp.parisc-linux.org/docs/astro_errors.ps>Error handling</a>,<a href=http://puffin.external.hp.com/docs/astro_ioc.ps>R2I Operations</a>, <a href=http://puffin.external.hp.com/docs/astro_regmap.ps>Registers Map</a>, <a href=http://puffin.external.hp.com/docs/astro_runway.ps>Runway Interface</a>, <a href=http://puffin.external.hp.com/docs/astro_sysmap.ps>System Mamory Map</a>

<li>Astro <a href="http://ftp.parisc-linux.org/docs/astro_intro.ps">Overview</a>, <a href="http://ftp.parisc-linux.org/docs/astro_errors.ps">Error handling</a>,<a href="http://puffin.external.hp.com/docs/astro_ioc.ps">R2I Operations</a>, <a href="http://puffin.external.hp.com/docs/astro_regmap.ps">Registers Map</a>, <a href="http://puffin.external.hp.com/docs/astro_runway.ps">Runway Interface</a>, <a href="http://puffin.external.hp.com/docs/astro_sysmap.ps">System Mamory Map</a>

</ol>

<li><a href=http://ftp.parisc-linux.org/docs/sti.pdf>Stinger graphics</a>

<li><a href="http://ftp.parisc-linux.org/docs/sti.pdf">Stinger graphics</a>

<li><a href=http://www.lsilogic.com/techlib/techdocs/old_storage/770_2_0.pdf>NCR 53C700/710/720 SCSI I/O Processors</a>

<li><a href="http://www.lsilogic.com/techlib/techdocs/old_storage/770_2_0.pdf">NCR 53C700/710/720 SCSI I/O Processors</a>

<small>(the doc is actually for 770, which is claimed as compatible)</small>

<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

<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>

Or see more information at <a href=http://www.openpa.net/>OpenPA</a>.

Or see more information at <a href="http://www.openpa.net/">OpenPA</a>.

<hr>

<h3><font color=#0000e0><strong>Building Cross-Tools</strong></font></h3>

<h3><font color="#0000e0"><strong>Building Cross-Tools</strong></font></h3>

<pre>

cd /usr/src

sudo make TARGET=hppa cross-tools

</pre>

</p>

<p>

cross-tools build process may fail in the libc stage, consider that's

all right, since libc support is not finished yet.

</p>

<h4>Build boot.lif file using cross-tools:</h4>

<p>

Line 153

Line 154

"LORDER=$cross/lorder" "NM=$cross/nm" \

"RANLIB=$cross/ranlib" "SIZE=$cross/size"

</pre>

</p>

<p>

One will have a <a href=http://hppa.lucifier.net/#boot_lif><em>boot.lif</em></a>

One will have a <a href="http://hppa.lucifier.net/#boot_lif"><em>boot.lif</em></a>

file to boot then in the obj-directory.

That image may include <em>diskless</em> kernel image if one was available

in the <em>sys/arch/hppa/compile/SHEPHERD_PIE/bsd</em>.

<br>

Kernel cross-build process is similar to the one for boot, consult

<a href=http://www.openbsd.org/cgi-bin/man.cgi?query=config&apropos=0&sektion=0

<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=config&apropos=0&sektion=0

&manpath=OpenBSD+Current&format=html>config(8)</a>

&manpath=OpenBSD+Current&format=html">config(8)</a>

and

<a href=http://www.openbsd.org/cgi-bin/man.cgi?query=options&apropos=0&sektion=0&manpath=OpenBSD+Current&format=html>options(8)</a>

<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=options&apropos=0&sektion=0&manpath=OpenBSD+Current&format=html">options(8)</a>

for kernel build options and configuration.

</p>

<hr>

In order to use the <a href=http://hppa.lucifier.net/#boot_lif>boot.lif</a> files

In order to use the <a href="http://hppa.lucifier.net/#boot_lif">boot.lif</a> files

you must prepare your server and instruct your machine to boot off the network:

<ol>

<li>Server setup</li><br>

<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&apropos=0&sektion=0&manpath=OpenBSD+Current&format=html>rbootd</a> must be setup and started.<br>

<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=rbootd&apropos=0&sektion=0&manpath=OpenBSD+Current&format=html">rbootd</a> must be setup and started.<br>

<ul>

<li><b>/etc/<a href=http://www.openbsd.org/cgi-bin/man.cgi?query=rbootd&apropos=0&sektion=0&manpath=OpenBSD+Current&format=html>rbootd</a>.conf</b>

<li><b>/etc/<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=rbootd&apropos=0&sektion=0&manpath=OpenBSD+Current&format=html">rbootd</a>.conf</b>

contains a single line per machine you entered 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. For example:

<pre>

8:0:9:70:c4:11 <a href=#boot_lif>boot.lif</a> # 9000/720

8:0:9:70:c4:11 <a href="#boot_lif">boot.lif</a> # 9000/720

8:0:9:19:fb:a0 <a href=#boot_lif>boot.lif</a> # 9000/725

8:0:9:19:fb:a0 <a href="#boot_lif">boot.lif</a> # 9000/725

</pre>

</li>

</ul>

Line 190

Line 191

<li>Recent machines (712, new 715, 725) won't look for rbootd at all, but require a

<b>bootp</b> setup.<br>

<ul>

<li><b>/etc/<a href=http://www.openbsd.org/cgi-bin/man.cgi?query=bootptab&apropos=0&sektion=5&manpath=OpenBSD+Current&format=html>bootptab</a></b> contains an information block for each machine. For example:

<li><b>/etc/<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=bootptab&apropos=0&sektion=5&manpath=OpenBSD+Current&format=html">bootptab</a></b> contains an information block for each machine. For example:

<pre>

# 9000/715

boron:\

Line 205

Line 206

</pre>

</li>

<li>

Create directory /tftpboot and put the <a href=#boot_lif>boot.lif</a> in it.<br>

Create directory /tftpboot and put the <a href="#boot_lif">boot.lif</a> in it.<br>

</li>

<li>

Write an entry for your hppa in the <b>/etc/ethers</b> file:<br>

Line 220

Line 221

</pre>

</li>

<li>

Create directory /usr/local/exports/boron/root and put <a href=http://hppa.lucifier.net/root/dev/MAKEDEV>/dev/MAKEDEV</a>,

Create directory /usr/local/exports/boron/root and put <a href="http://hppa.lucifier.net/root/dev/MAKEDEV">/dev/MAKEDEV</a>,

in their relative locations.

</li>

<li>

Line 231

Line 232

</pre>

</li>

<li>

Remember you will have to enable <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=bootpd&apropos=0&sektion=8&manpath=OpenBSD+Current&format=html>bootpd</a>

Remember you will have to enable <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=bootpd&apropos=0&sektion=8&manpath=OpenBSD+Current&format=html">bootpd</a>

and <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=tftpd&apropos=0&sektion=8&manpath=OpenBSD+Current&format=html>tftpd</a>

and <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=tftpd&apropos=0&sektion=8&manpath=OpenBSD+Current&format=html">tftpd</a>

in /etc/inetd.conf, and restart <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=inetd&apropos=0&sektion=8&manpath=OpenBSD+Current&format=html>inetd</a>.

in /etc/inetd.conf, and restart <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=inetd&apropos=0&sektion=8&manpath=OpenBSD+Current&format=html">inetd</a>.

</li>

<li>

Also remember to enable <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=nfsd&apropos=0&sektion=8&manpath=OpenBSD+Current&format=html>nfs_server</a>

Also remember to enable <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=nfsd&apropos=0&sektion=8&manpath=OpenBSD+Current&format=html">nfs_server</a>

, <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=rarpd&apropos=0&sektion=8&manpath=OpenBSD+Current&format=html>rarpd</a>

, <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=rarpd&apropos=0&sektion=8&manpath=OpenBSD+Current&format=html">rarpd</a>

and <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=portmap&apropos=0&sektion=8&manpath=OpenBSD+Current&format=html>portmap</a>

and <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=portmap&apropos=0&sektion=8&manpath=OpenBSD+Current&format=html">portmap</a>

in <a

href=http://www.openbsd.org/cgi-bin/man.cgi?query=rc.conf&apropos=0&sektion=8&manpath=OpenBSD+Current&format=html>/etc/rc.conf</a>.

href="http://www.openbsd.org/cgi-bin/man.cgi?query=rc.conf&apropos=0&sektion=8&manpath=OpenBSD+Current&format=html">/etc/rc.conf</a>.

</li>

</ul>

</li>

<li>For further reading on server setup for network booting in general, see also: <a href=http://www.openbsd.org/cgi-bin/man.cgi?query=diskless&apropos=0&sektion=0&manpath=OpenBSD+Current&format=html>diskless(8)</a>.</li>

<li>For further reading on server setup for network booting in general, see also: <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=diskless&apropos=0&sektion=0&manpath=OpenBSD+Current&format=html">diskless(8)</a>.</li>

</ul>

<li>Client Network Boot</li><br>

<p>

<li>Client Network Boot

<ul>

<li>BOOT_ADMIN<br>

In order to get to the BOOT_ADMIN prompt, you must hit <em><esc></em> as the

machine is coming up. Once it probes bootable devices, type 'a' for

the 'BOOT_ADMIN' prompt.

</li>

<li>network boot command <br>

<li>network boot command

Once at the 'BOOT_ADMIN' prompt, type:

<pre>

BOOT_ADMIN> boot lan isl

</pre>

</ul>

... and you are on your way to booting boot.lif!

</li>

</ul>

</ol>

<hr>

<a href=mailto:www@openbsd.org>www@openbsd.org</a>

<a href="mailto:www@openbsd.org">www@openbsd.org</a>

<br>

<small>$OpenBSD$</small>