hppa

---

Status and History:

This project was started in one of those days when the only open source operating systems for HP PA-RISC computers were Lites and MkLinux. These two sources were a major supply of information and code for initial development of the OpenBSD/hppa port. The HPBSD 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 build of 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 they target different class of 9000 machines.

Supported Hardware:

• CPUs (intro and (cpu)):
  • PA7000-based: 705, 710, 720, 730, 750 (currently under development)
  • 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
• bus/IO controllers:
  • GSC (gsc): LASI (lasi), ASP (asp)
• SCSI controllers (currently under development):
  • NCR53C710 SCSI I/O Processors (osiop)
  • NCR53C720 SCSI I/O Processors (siop)
• SGC/GSC graphics (sti):
  • Artist (as found on 712)
  • CRX-8, CRX-24, HCRX-8, HCRX-24
• RS-232 devices:
  • On-board ns16550 or similar (com)
• Input devices (currently under development):
  • PS/2 keyboard and mouse
  • HIL keyboard and mouse

• PA2.0 systems (in 32-bit mode);
• HP 9000 834, 835, 836, 844, 845, 846;
• HP 9000 E23, E25, E35, E45, E55;
• HP 3000 908, 918, 928, 938;
• Hitachi VQ200, VQ210, and some other non-HP workstations;
• Precision Book from RDI Computer Corporation (well, unlikely)
• HP VME and VXI single board systems (requires VME at least)

Documentation

1. HP PA-RISC CPUs
   1. PA7100LC CPU ERS
   2. PA7300LC CPU ERS
2. Processor Dependent Code/I/O Dependent Code Interface
   (selected chapters from "PA-RISC I/O Architecture Specification")
   1. PDC 1.1
   2. IODC 1.1
   3. Version and Identification Number Allocation
   4. Memory Data Formats 2.0
   5. PDC Procedures 2.0
   6. PDC Entry Points 2.0
   7. OS Interface 2.0
3. Bus controllers/bridges/adaptors
   1. ASP
   2. LASI Core Bus Adapter (including lan, scsi, serial, lpt controllers)
   3. Dino PCI bridge, and Errata
   4. Elroy ERS (Edited for Open Source)
   5. Astro Overview, Error handling,R2I Operations, Registers Map, Runway Interface, System Mamory Map
4. Stinger graphics
5. NCR 53C700/710/720 SCSI I/O Processors (the doc is actually for 770, which is claimed as compatible)
6. Intel i82596DX/SX and i82596CA Ethernet Controllers

Building Cross-Tools

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.

1. 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:

    	8:0:9:70:c4:11    boot.lif    # 9000/720
    	8:0:9:19:fb:a0    boot.lif    # 9000/725
    	

• Recent machines (712, new 715, 725) won't look for rbootd at all, but require a bootp setup.
  
  • /etc/bootptab contains an information block for each machine. For example:

    	# 9000/715
    	boron:\
            	ha=0800095f5a6e:\
            	bf=boot.lif:\
            	hd=:\
            	ht=ethernet:\
            	ip=10.0.1.143:\
            	rp=/usr/local/exports/boron/root:\
            	sm=255.255.255.0:\
            	td=/tftpboot:
    	

  • Create directory /tftpboot and put the boot.lif in it.
    
  • Write an entry for your hppa in the /etc/ethers file:
    

    	08:00:09:5f:5a:6e	boron
    	

  • Write an entry for 'boron' in the /etc/hosts file:
    

    	10.0.1.143	boron
    	

  • Create directory /usr/local/exports/boron/root and put /dev/MAKEDEV, /sbin/init, /bin/ksh in their relative locations.
  • Write an entry in /etc/exports so the root directory gets exported to the client:

    	/usr/local/exports/boron/root boron
    	

  • Remember you will have to enable bootpd and tftpd in /etc/inetd.conf, and restart inetd.
  • Also remember to enable nfs_server , rarpd and portmap in /etc/rc.conf.
• For further reading on server setup for network booting in general, see also: diskless(8).
2. 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!