Very crude notes for the hppa adventurous person.

8 files changed, 241 insertions, 2 deletions

diff --git a/distrib/notes/Makefile b/distrib/notes/Makefile
index 8e2f3168e46..7771c0e9469 100644
--- a/distrib/notes/Makefile
+++ b/distrib/notes/Makefile
@@ -1,4 +1,4 @@
-#	$OpenBSD: Makefile,v 1.16 2002/10/07 19:31:01 miod Exp $
+#	$OpenBSD: Makefile,v 1.17 2002/12/19 01:00:11 miod Exp $
 
 NOPROG=
 NOMAN=
@@ -16,7 +16,7 @@ all:	$(TARG)
 
 allarchs:
 	@cd $(.CURDIR); \
-	for arch in alpha amiga hp300 i386 mac68k macppc mvme68k sparc \
+	for arch in alpha amiga hp300 hppa i386 mac68k macppc mvme68k sparc \
 	    sparc64 sun3 vax ; do ${MAKE} M=$$arch; done;
 
 $(TARG): $(DEP)
diff --git a/distrib/notes/hppa/contents b/distrib/notes/hppa/contents
new file mode 100644
index 00000000000..6c337d1d297
--- /dev/null
+++ b/distrib/notes/hppa/contents
@@ -0,0 +1,37 @@
+dnl	$OpenBSD: contents,v 1.1 2002/12/19 01:00:13 miod Exp $
+TopPart
+
+OpenBSDdistsets
+
+OpenBSDbsd
+
+OpenBSDrd
+
+		boot.lif	A LIF bootable kernel image, suitable for
+				network boot
+dnl
+dnl		installboot	The OpenBSD/MACHINE boot loader installation
+dnl				program
+dnl		bootxx		The OpenBSD/MACHINE LIF boot block
+
+DistributionDescription(six)
+
+OpenBSDbase(80.0,191.3)
+
+OpenBSDcomp(22.5,68.3)
+
+OpenBSDetc(1.5,5.6,noupgrade)
+
+OpenBSDgame(7.7,16.4)
+
+OpenBSDman(2.0,6.9)
+
+OpenBSDmisc(1.7,5.6)
+dnl
+dnl OpenBSDxbase
+dnl
+dnl OpenBSDxfont
+dnl
+dnl OpenBSDxserv
+dnl
+dnl OpenBSDxshare
diff --git a/distrib/notes/hppa/hardware b/distrib/notes/hppa/hardware
new file mode 100644
index 00000000000..f8016447575
--- /dev/null
+++ b/distrib/notes/hppa/hardware
@@ -0,0 +1,38 @@
+dnl	$OpenBSD: hardware,v 1.1 2002/12/19 01:00:13 miod Exp $
+OpenBSD/MACHINE OSREV runs on the following classes of HP9000 machines:
+dnl - PA7000-based
+dnl	705
+dnl	710
+dnl	720
+dnl	730
+dnl	750
+- PA7100-based
+	715/33, 715/50, 715/75
+	725/50, 725/75
+	735/100
+	755/100
+- PA7100LC-based
+	712
+	715/64, 715/80, 715/100, 715/100XC
+	725/64, 725/100
+- PA7150-based
+	735/125
+	755/125
+- PA7200-based
+	J200, J210, J210XC
+	C100, C110
+
+Supported devices {:-include-:}:
+dnl - SCSI controllers
+dnl 	built-in 53C710 or 53C720 SCSI
+- SGC/GSC graphics:
+	Artist (as found on 712)
+	CRX-8, CRX-24, HCRX-8, HCRX-24
+- RS-232 devices:
+	on-board NS16550 or similar serial ports
+dnl - Input devices:
+dnl	PS/2 keyboard and mouse
+dnl	HP/HIL keyboard and mouse
+
+If your hardware is not listed above, there is currently no support for it
+in this release.
diff --git a/distrib/notes/hppa/install b/distrib/notes/hppa/install
new file mode 100644
index 00000000000..a7fbbe3153d
--- /dev/null
+++ b/distrib/notes/hppa/install
@@ -0,0 +1,140 @@
+dnl	$OpenBSD: install,v 1.1 2002/12/19 01:00:13 miod Exp $
+dnl lots of texts coming from {mac68k,mvme68k,vax}/install intially
+
+At the moment, the only way to install OpenBSD is to use a diskless setup.
+No installation media is provided.
+
+
+Diskless Setup Configuration:
+
+In order to bootstrap via the network, you must provide a second system to
+act as a boot server. It is convenient if this is a second OpenBSD machine
+as the necessary services are already installed, although source code for
+such programs as mopd can be found in OpenBSD's source tree, and should be
+reasonably portable to other UN*X-like operating systems. More information
+on diskless booting can be found in the OpenBSD diskless(8) manual page.
+
+Your MACHINE expects to be able to download a so-called LIF (``Logical
+Interchange Format'') image, containing both the boot code and the kernel,
+via the HP rboot protocol, for older firmware, or via bootp or dhcp, for
+more recent firmware.
+
+
+Old firmware operation
+
+PDC ROM v1.4 and below are easily recognizable, as they will start with a
+text banner. There are two levels of interactive commands in this version.
+The first level is a short menu:
+
+	b)   Boot from specified device
+	s)   Search for bootable device
+	a)   Enter Boot Administration mode
+	x)   Exit and continue boot sequence
+
+	Select from menu:
+
+In this case, you will need to setup rbootd on the server. Start by creating
+an /etc/rbootd.conf file on the bootserver. The format of this file is the
+ethernet address followed by the LIF filename. Here is an example:
+
+	08:00:09:70:c4:11		boot.lif
+
+Then start rbootd (or configure /etc/rc.conf to always start rbootd). Once
+rbootd is running, the server name will then appear on the MACHINE as part of
+the possible boot choices in a boot device search (``s'' command).
+
+
+Modern firmware operation
+
+PDC ROM 1.5 and above will start with a small graphics window at the screen
+center (unless you are using a serial console). There is only one interactive
+mode, with a BOOT_ADMIN> prompt, which provides both boot settings and
+commands.
+
+In this case, you will need to setup either bootpd or dhcpd on the server.
+Assuming a bootp setup, start by editing the /etc/bootptab on the bootserver,
+and declare an information block. Here is an example:
+
+	boron:\
+		ha=08000970c411:\
+		bf=boot.lif:\
+		hd=:\
+		ht=ethernet:\
+		ip=10.42.42.42:\
+		rp=/export/MACHINE:\
+		sm=255.0.0.0:\
+		td=/tftpboot:
+
+Do not forget to enable bootpd, either as a standalone process, or via inetd.
+
+You will also need to enable tftpd, for the MACHINE to download its boot.lif
+(bf entry) image from the server in the /tftpboot (td entry) directory.
+
+
+Common operation
+
+Next you need to export a directory for your new machine to mount over
+NFS. This is accomplished by adding an entry to /etc/exports such as:
+
+	/export/MACHINE -maproot=root snake
+
+where ``snake'' is the hostname of your MACHINE.
+
+Finally, you need to add an entry for your MACHINE in /etc/bootparams.
+For example:
+
+	snake		root=myserver:/export/MACHINE
+
+Enable rpc.bootparamd either by turning it on in /etc/rc.conf and rebooting,
+or by running it manually.
+
+Unpack at least `base{:--:}OSrev.tgz' and `etc{:--:}OSrev.tgz' sets on the server in the
+root directory for your target machine, `/export/MACHINE' in this example. If
+you elect to use a separately NFS-mounted filesystem for `/usr' with your
+diskless setup, make sure the "./usr" base files in base{:--:}OSrev.tgz end
+up in the correct location. One way to do this is to temporarily use a
+loopback mount on the server, re-routing <root>/usr to your server's exported
+OpenBSD "/usr" directory.
+
+A few configuration files in <root>/etc need to be edited:
+
+	dhclient.conf
+		DHCP client information, if necessary, check dhclient.conf(5)
+		for the syntax.
+	fstab
+		Enter the entries for the remotely mounted filesystems.
+		For example:
+		  server:/export/root/client       /     nfs  rw 0 0
+		  server:/export/exec/MACHINE.OpenBSD /usr  nfs  rw 0 0
+		Be sure to add the server swap space, such as:
+		  server:/export/swap/client /swap swap sw,nfsmntpt=/swap 0 0
+		after creating the `<root>/swap' directory.
+	hostname.if (likely, hostname.ie0)
+		Configuration of the host adapter, check hostname.if(5)
+		for the syntax.
+	hosts
+		Add the IP addresses of both server and client.
+	mygate
+		This file contains the IP address of the default gateway.
+	myname
+		This file contains the client's hostname, with a
+		fully-qualified domain name.
+	resolv.conf
+		Name server configuration, check resolv.conf(5) for the
+		syntax.
+
+Now you must populate the the `/dev' directory for your client. After
+changing your working directory to `<root>/dev', run the MAKEDEV script.
+Depending on your host operating system, you may get error messages about
+unknown users and groups. These errors are inconsequential for the purpose
+of installing OpenBSD.  However, you will want to correct them after
+booting your machine. To do so, simply re-run MAKEDEV on your OpenBSD
+machine once it has booted.
+
+Once these files are configured, your system should be able to behave like
+any other OpenBSD system once booted. On your MACHINE, escape to a prompt and
+boot from the network by entering ``boot lan isl''. On old PDC firmware, you
+will need to enter administration mode first.
+
+dnl this is a bit hypocritical. Oh well.
+OpenBSDCongratulations
diff --git a/distrib/notes/hppa/prep b/distrib/notes/hppa/prep
new file mode 100644
index 00000000000..1bc22cd68b9
--- /dev/null
+++ b/distrib/notes/hppa/prep
@@ -0,0 +1,8 @@
+dnl	$OpenBSD: prep,v 1.1 2002/12/19 01:00:13 miod Exp $
+
+The MACHINE computers do not generally need any specific preparation.
+
+You might want to check that the console ``path'' in the PDC firmware points
+to the device you plan to use, and change it if necessary.
+
+dnl need to provide more details on how to do so! c'n'p boot(8)
diff --git a/distrib/notes/hppa/upgrade b/distrib/notes/hppa/upgrade
new file mode 100644
index 00000000000..30c2a281bd7
--- /dev/null
+++ b/distrib/notes/hppa/upgrade
@@ -0,0 +1,5 @@
+dnl	$OpenBSD: upgrade,v 1.1 2002/12/19 01:00:13 miod Exp $
+Since OpenBSD/OSREV is the first MACHINE release, there is no upgrade
+functionnality.
+dnl
+dnl OpenBSDUpgrade({:-the CD-ROM, the miniroot, or the installation floppy-:})
diff --git a/distrib/notes/hppa/whatis b/distrib/notes/hppa/whatis
new file mode 100644
index 00000000000..009b6f9b5ff
--- /dev/null
+++ b/distrib/notes/hppa/whatis
@@ -0,0 +1,4 @@
+dnl	$OpenBSD: whatis,v 1.1 2002/12/19 01:00:13 miod Exp $
+OpenBSD/MACHINE OSREV is a new port for the Hewlett-Packard HPPA computers.
+Despite its young age as a supported port, it already supports a wide range
+of machines and devices, and more hardware support is being worked on.
diff --git a/distrib/notes/hppa/xfer b/distrib/notes/hppa/xfer
new file mode 100644
index 00000000000..2b189857e16
--- /dev/null
+++ b/distrib/notes/hppa/xfer
@@ -0,0 +1,7 @@
+dnl	$OpenBSD: xfer,v 1.1 2002/12/19 01:00:13 miod Exp $
+
+Since there is no installation media for the MACHINE port, there is no need
+for specific media filling instructions. You will just need to be able to
+unpack the OpenBSD sets on the diskless boot server, as told in the
+``Installing the OpenBSD system'' below.
+