Re: [hppa-linux] Cross compile setup

Re: [hppa-linux] Cross compile setup

[Jason Eckhardt]

>
> Since PDC resides in a ROM, I assume you're talking about building
> something analogous to ISL, which resides in a LIF filesystem (see lif(4))
> ...
> I don't know how much of the boot process you want to replace, but if
> you're willing to use the HP-UX ISL and HPUX, at least to get started,
> you can fairly easily get things set up to boot your kernel over the net.

  Yes, my intention is to build a simple IPL for HPPA/Linux. It is a good
  idea to utilize the HP ISL to get started, but eventually I think we should
  not rely on any HP code. That way, people can "cold install" HPPA/Linux
  on a fresh disk and never worry about seeing or using any HPUX ugliness.

  In any case, until I get an IPL working, we can get a lot of work done with
  HPUX ISL as you mentioned.
 
  Jason.

----------------------------------------------------------------------
To unsubscribe: send e-mail to hppa-linux-request@puffingroup.com with
`unsubscribe' as the subject.

Re: [hppa-linux] Cross compile setup

[Bjorn Helgaas]

I wrote
>I think the ISL image is plain SOM, ...

BUT, come to think of it, I guess I never did anything with ISL; when I
fiddled in this area, I was only concerned about the kernel itself, so I
did things like rewrite the AUTO file to change the kernel image to boot.

I do still think the ISL image is pretty much straight SOM, though there
is a "-S" option on the ld(1) man page that talks about generating an
IPL auxiliary header, so you might need that.

-------------
Bjorn Helgaas   helgaas@rsn.hp.com  telnet 1-497-3069  (972)497-3069

----------------------------------------------------------------------
To unsubscribe: send e-mail to hppa-linux-request@puffingroup.com with
`unsubscribe' as the subject.

Re: [hppa-linux] Cross compile setup

[Bjorn Helgaas]

Jason Eckhardt wrote
> Also, a question to others:
> I have started to tinker with writing an IPL for the native
> port (i.e. bootstrap code). I've been compiling/assembling within HPUX,
> but I can't seem to ascertain how to get "ld" to generate a "straight"
> binary file rather than a SOM object. The bootstrap code obviously
> has to be a plain binary to work. Note that the version of gcc I picked
> up from www.software.hp.com utilizes the HP linker, not GNU ld.

If you haven't already seen them, careful examination of the following
HP-UX man pages will get you a long way toward understanding the typical
boot process:

	boot(1m)
	pdc(1m)
	isl(1m)
	hpux(1m)

Since PDC resides in a ROM, I assume you're talking about building
something analogous to ISL, which resides in a LIF filesystem (see lif(4))
on the boot media and is loaded by PDC.  I think the ISL image is plain
SOM, but you have to be careful to use the correct type when copying it
into the LIF filesystem.

I don't know how much of the boot process you want to replace, but if
you're willing to use the HP-UX ISL and HPUX, at least to get started,
you can fairly easily get things set up to boot your kernel over the net.
710's and 715's use a proprietary protocol called RMP (see rbootd(1m)),
while 712's and newer boxes use BOOTP (see bootpd(1m)).

Booting over the net, combined with using the serial port as the console,
makes things go a lot faster.

-------------
Bjorn Helgaas   helgaas@rsn.hp.com  telnet 1-497-3069  (972)497-3069

----------------------------------------------------------------------
To unsubscribe: send e-mail to hppa-linux-request@puffingroup.com with
`unsubscribe' as the subject.

Re: [hppa-linux] Cross compile setup

[Paul C. Janzen]

Bjorn Helgaas <helgaas@rsn.hp.com> writes:

> I don't know how much of the boot process you want to replace, but if
> you're willing to use the HP-UX ISL and HPUX, at least to get started,
> you can fairly easily get things set up to boot your kernel over the net.
> 710's and 715's use a proprietary protocol called RMP (see rbootd(1m)),
> while 712's and newer boxes use BOOTP (see bootpd(1m)).

RMP may be proprietary, but it's hardly a secret.  It's essentially
the same boot protocol that the HP 300's used, which was apparently
reverse-engineered by the NetBSD camp and subsequently ported to Linux
for the HP300 port.  It's also used on some 735's (it apparently
depends more on PDC revision than model number).

These patches to the rbootd at 
    http://www.tazenda.demon.co.uk/phil/linux-hp/files/rbootd-linux.tar.gz
allowed me to boot the HPUX kernel from the network on an 735/99 using
Linux/x86 as the server (well at least to the point where it looked
for a root filesystem).

diff -ur rbootd_orig/pcap.c rbootd/pcap.c
--- rbootd_orig/pcap.c	Sat Nov  9 12:54:45 1996
+++ rbootd/pcap.c	Mon Nov  2 20:38:22 1998
@@ -29,8 +29,11 @@
 #include "defs.h"
 
 #include <sys/socket.h>
-#include <linux/if.h>
-#include <linux/if_ether.h>
+#include <ioctls.h>
+#include <net/if.h>
+#define ETH_ALEN        6               /* Octets in one ethernet addr   */
+#define ETH_P_ALL       0x0003          /* Every packet (be careful!!!) */
+
 
 static pcap_t *pdesc = NULL;  /* packet capture descriptor */
 static char errbuf[PCAP_ERRBUF_SIZE]; /* buffer we use to get error msgs */
@@ -131,7 +134,7 @@
    caplen = h->caplen; /* max. captured bytes */
 
    /* First we ensure we got a complete packet of the right size! */
-   if (caplen <= datlen)
+   if (caplen < datlen)
       syslog(LOG_ERR, "bpf: truncated packet dropped (%d of %d bytes)",
              caplen, datlen);
    else if (datlen > sizeof(struct rmp_packet))
diff -ur rbootd_orig/rmpproto.c rbootd/rmpproto.c
--- rbootd_orig/rmpproto.c	Sat Nov  9 12:15:55 1996
+++ rbootd/rmpproto.c	Mon Nov  2 21:30:23 1998
@@ -353,6 +353,12 @@
 		if (STREQN(filename, filelist[i]))
 			goto match;
 
+	if (strlen(filename)==0) 
+	  { 
+	    strcpy(filename, filelist[0]); 
+	    goto match;
+	  }
+	
 	/*
 	 *  Invalid boot file name, set error and send reply packet.
 	 */

--
Paul C. Janzen
pcj@primenet.com

----------------------------------------------------------------------
To unsubscribe: send e-mail to hppa-linux-request@puffingroup.com with
`unsubscribe' as the subject.

Re: [hppa-linux] Cross compile setup

[Jason Eckhardt]

> From hppa-linux-request@puffingroup.com Thu Feb  4 03:45:11 1999
> From: "Strelow, Ulrich" <Ulrich.Strelow@Schering.DE>
> To: hppa-linux@puffingroup.com
> Date: Thu, 4 Feb 1999 11:59:00 +0100 
> Subject: [hppa-linux] Cross compile setup
>
...

>      Then the machine stops with the LEDs 123568 on which means "HPMC
> due 
>      to Bus Error".
>      
>      Unfortunately no one on the mklinux mailing list had any help for
> that 
>      problem (probably because the main developers were no longer
> working 
>      on/with mk-linux).
>      
>      So my question here is the following:
>      
>      Is the hppa-linux cross-compile setup for binutils and egcs 
>      possible from linux-x86 ?  
>      

 I have the same problem. Mklinux won't boot on my C160 (even in duplex
 mode through the serial port). So I'll have to
 be working from either an HPUX or Linux-x86 build environment. What build
 environment are most of you planning on using?

 Also, a question to others:
 I have started to tinker with writing an IPL for the native
 port (i.e. bootstrap code). I've been compiling/assembling within HPUX,
 but I can't seem to ascertain how to get "ld" to generate a "straight"
 binary file rather than a SOM object. The bootstrap code obviously
 has to be a plain binary to work. Note that the version of gcc I picked
 up from www.software.hp.com utilizes the HP linker, not GNU ld.

 I tried to use "objcopy -O binary some_file binary_file" with no luck. The
 resulting file was stripped of the SOM garbage, but unfortunately most
 of my code and data was also stripped away and the file was mostly zeroes!! 
 Any ideas on how to generate plain binary? Is the above behavior a objcopy
 bug or was this pilot error?

 Regards, Jason.




----------------------------------------------------------------------
To unsubscribe: send e-mail to hppa-linux-request@puffingroup.com with
`unsubscribe' as the subject.

[hppa-linux] Cross compile setup

[Strelow, Ulrich]

     Hi,
     
     I am very interested that someone finally tries to do a native port
of 
     Linux for PA-RISC. At work I have an old HP 715/33 workstation (the

     *one* machine that is not supported by mk-linux) which I would like
to 
     run linux on.
     
     OSF has never managed to get the mach kernel booting on that box
and 
     my question about the problems were answered that is has something
to 
     do with the ethernet chip.
     
     Some months ago I tried to cross-compile the mach-kernel under 
     Linux-x86. For private purposes I have bought a SCSI-MOD-drive
which 
     serves as the data transfer media between my home PC running linux
and 
     the HP 715/33 at work.
     
     I was not very successful with that cross-compiled mach-kernel.
After  
     booting the only messages I saw were from the secondary boot
loader: 
     
     OSF Mach boot
     [/mach]: -a
     text (0x11000) at 0x11000
     data (0x92610) at 0x5
     
     Then the machine stops with the LEDs 123568 on which means "HPMC
due 
     to Bus Error".
     
     Unfortunately no one on the mklinux mailing list had any help for
that 
     problem (probably because the main developers were no longer
working 
     on/with mk-linux).
     
     So my question here is the following:
     
     Is the hppa-linux cross-compile setup for binutils and egcs 
     possible from linux-x86 ?  
     
     If yes I would like to take part on the project as an "early
pre-alpha 
     stage"-tester :) in case you need one.
     
     Ulrich
     ----------------------
     Ulrich Strelow <ulrich.strelow@schering.de or
ulrich_strelow@csi.com>
     Berlin, Germany
      

----------------------------------------------------------------------
To unsubscribe: send e-mail to hppa-linux-request@puffingroup.com with
`unsubscribe' as the subject.