- 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,
- to solve certain stability issues.
This project was started in those days when the only
open source operating systems for HP PA-RISC computers were
Lites and
--- 1,64 ----
!
OpenBSD/hppa
!
+
!
+
+
OpenBSD/hppa
+ OpenBSD/hppa runs on a large set of the 32-bit Hewlett Packard Precision
+ Architecture workstations and servers (HP PA-RISC).
+
+
+
+ A mailing list dedicated to the OpenBSD/hppa port is available at
+ hppa@openbsd.org.
+ To join the OpenBSD/hppa mailing list, send a message body of "subscribe
+ hppa" to majordomo@openbsd.org.
+ Please be sure to check our mailing list policy before
+ subscribing.
+
+
+
+ The current port maintainer is
+ Michael Shalayeff.
+ Others are definitely welcome to contribute!
+
This project was started in those days when the only
open source operating systems for HP PA-RISC computers were
Lites and
***************
*** 33,110 ****
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 ;) is
! support for HP PA-RISC in GCC and binutils, which allowed quick
! building of a cross-tools environment for development.
! Later on HP decided to sponsor a
! Linux port to PA-RISC
! machines which actually resulted in some proprietary documentation
! release, even though they target a different class of 9000 machines.
IODC 1.1
--- 69,255 ----
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.
!
!
! Later on, Hewlett-Packard decided to sponsor a
! Linux 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.
!
!
!
!
!
Current status:
!
+ Although there have been no official releases of this port yet,
+ the supported systems boot to multi-user and full snapshots are made
+ periodically.
+
!
! Currently, no storage devices are supported, so the only way to run this
! port is in a diskless environment.
!
+
+
+
Projects (in no particular order):
+
+
+
!
Improve overall stability
!
Support the on-board SCSI controller (NCR 53c7xx)
!
Standalone boot blocks (once SCSI support is ready)
!
Support keyboard and mouse (PS/2 and HIL) natively
!
! 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 "Wanted List"
(contact mickey).
+
! cd /usr/src
! sudo make TARGET=hppa cross-tools
!
! cross-tools build process may fail in the libc stage, consider that's
! all right, since libc support is not finished yet.
-
-
Build boot.lif file using cross-tools:
!
! cd /sys/arch/hppa/stand
! make obj
! set cross=(/usr/cross/hppa/usr/bin)
! make MACHINE=hppa MACHINE_ARCH=hppa \
! "AS=$cross/as" "CC=$cross/cc" "CXX=$cross/c++" \
! "CPP=$cross/cpp" "LD=$cross/ld" \
! "AR=$cross/ar" "STRIP=$cross/strip" \
! "LORDER=$cross/lorder" "NM=$cross/nm" \
! "RANLIB=$cross/ranlib" "SIZE=$cross/size"
!
!
!
! One will have a boot.lif
! file to boot then in the obj-directory.
! That image may include diskless kernel image if one was available
! in the sys/arch/hppa/compile/SHEPHERD_PIE/bsd.
!
! Kernel cross-build process is similar to the one for boot, consult
! config(8)
! and
! options(8)
! for kernel build options and configuration.
! In order to use the boot.lif files
! you must prepare your server and instruct your machine to boot off the network:
Server setup
!
For older machines (705, 7[1235]0, old 715)
! rbootd must be setup and started.
!
/etc/rbootd.conf
! 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:
! The boot.lif file contains both a bootloader and a kernel.
! To boot it from the network, a server machine has to be setup so as to
! let the hppa machine retrieve it:
Server setup
!
For older machines (705, 7[1235]0, old 715)
! rbootd
! must be setup and started.
!
/etc/rbootd.conf 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 /usr/mdec/rbootd).
! For example:
For further reading on server setup for network booting in general, see also: diskless(8).
Client Network Boot
BOOT_ADMIN
! In order to get to the BOOT_ADMIN prompt, you must hit <esc> as the
! machine is coming up. Once it probes bootable devices, type 'a' for
! the 'BOOT_ADMIN' prompt.
!
network boot command
! Once at the 'BOOT_ADMIN' prompt, type:
BOOT_ADMIN> boot lan isl
! ... and you are on your way to booting boot.lif!
!
! Create directory /tftpboot and put the
! boot.lif file in it.
! Write an entry for the hppa in /etc/ethers:
08:00:09:5f:5a:6e boron
! Write another entry for it in /etc/hosts:
10.0.1.143 boron
! Create directory /usr/local/exports/boron/root and unpack
! at least base32.tgz and etc32.tgz in it.
! After the sets are unpacked, create device nodes in dev/ by
! running MAKEDEV and alter the configuration files in
! /etc (refer to the installation notes for details).
!
!
! Finally, add an entry to /etc/exports in order to export
! the root directory to the client:
/usr/local/exports/boron/root boron
+ You might want to also create and export a swap area.
! The last step is to enable the necessary daemons for all of this to
! work.
! bootpd
! and
! tftpd
! are usually run from
! inetd,
! so /etc/inetd.conf has to be modified and
! inetd
! restarted.
For further reading on server setup for network booting in general,
! please refer to the
! diskless(8)
! manual page.
!
Client Network Boot
BOOT_ADMIN
! In order to get to the BOOT_ADMIN prompt, hit the <esc>
! key as the machine is coming up. Once it has probed bootable devices,
! a menu will be displayed; if the prompt is notBOOT_ADMIN,
! it will be necessary to type ``a'' to access it.
!
Network boot command
! Once at the 'BOOT_ADMIN' prompt, the command
BOOT_ADMIN> boot lan isl
+ will proceed to the bootstrap of boot.lif.
!
+
+
!
!
Cross-compiling kernels:
+
+ The OpenBSD source tree provides some cross-compilation facilities.
+ First, a set of hppa cross tools (cross compiler, cross binutils, etc) must
+ be created:
+
+ # cd /usr/src
+ # make TARGET=hppa cross-includes cross-binutils cross-gcc
+
+ This will build and install the various utilities in /usr/cross/hppa.
+ Note that this step must be run as root, or using
+ sudo.
+
+
+
+
Building boot.lif using cross-tools
+
+
+
+
Building mkboot
+
+ mkboot is the only specific host tool needed for the boot.lif build.
+
+ $ cd /usr/src/sys/arch/hppa/stand/mkboot
+ $ MACHINE=hppa make obj depend all
+
+
+
Building the kernel
+
+ The kernel can be configured as usual, and then built using the cross-tools.
+