Thank you for the reply.

Unfortunately I only have linux installed (2.4.2 ac-16 originally via RH
7)... the cross build certainly wouldn't be feasible under linux, would it?

That's why I'm interested in publicly available netbsd boxes.. As an
alternative, if you could post the Jornada kernel used in the dmesgs shown
on the hpcarm website, that would be great too. 

Incidentally, I see you posted your reply to the hpcarm-port list which I
subscribed to. I received your message via the port-arm32 list.. I dont
think the port-hpcarm list is working yet.

Regards,
Greg

-----Original Message-----
From: IWAMOTO Toshihiro [mailto:iwamoto@sat.t.u-tokyo.ac.jp]
Sent: Friday, March 09, 2001 9:33 PM
To: Greg Berenfield
Cc: port-hpcarm@netbsd.org; port-arm32@netbsd.org
Subject: Re: Jornada 720


At Fri, 9 Mar 2001 20:18:37 -0500 ,
Greg Berenfield wrote:
> I'm new to netbsd but am very interested in what's being done with the
> arm-32 port to the jornada 720 handheld.  I have such a device and am
eager
> to try the hpcarm kernel on it.
> I've already downloaded the hpcboot source code and got it to build
> successfully using the ms embedded dev kit although it doesn't want to
boot
> kernels unless I 'tell' it that my device is an 820.. (was careful to
build

I think I've experienced this problem.
I'll look at it later. Thanks for reporting.

> Are there open NetBSD boxes that I could use to compile the hpcarm port?
> Such a setup exists for the IPAQ-linux hh.org work being done
> (skiffclusters) and I was hoping that some open NetBSD boxes exist too for
> development.

Well, there is no "official" build tool yet.
I think you can use vanilla gcc and binutils which are configured
using --target=arm-elf. (not confirmed)

I'll create a cross build package when I finished some more
hardware support.

If you are really willing to play now, here is the list what I've done.
This can be misleading and I'm rather ashamed to document such a gross
thing, but it might be better than nothing...

	1. install cross/arm-netbsd package
	   (build from pkgsrc or install binary package)
	2. get and extract binutils-2.10.1.tar.gz
	3. pass appropriate configure option and build
	   binutils-2.10.1/binutils and binutils-2.10.1/gas.
	   I don't exactly remember what I've done, but 
	   my binutils-2.10.1/config.status says:

#!/bin/sh
# This file was generated automatically by configure.  Do not edit.
# This directory was configured as follows:
./configure --host=i386-unknown-netbsdelf1.5K --target=i386-netbsd
--enable-targets=arm-netbsd arm-elf arm-wince-pe i386-cygwin i386-pe
--norecursion 
# 

	   This fails to build gas, IIRC.
	   My binutils-2.10.1/gas/config.status says I ran

./configure --target=arm-elf

	   in binutils-2.10.1/gas.

	4. Create a directory, say /home/toshii/gcc-armelf, and copy
           all files from
/usr/pkg/cross/lib/gcc-lib/arm-netbsd/egcs-2.91.60/.

	   Then replace /home/toshii/gcc-armelf/as with gas created in
	   step 3.

	5. cd /sys/arch/hpcarm/conf; config WHATSOEVER
	   cd ../compile/WHATSOEVER
	   and run the following script to modify generated Makefile.

#!/bin/sh

cat Makefile |sed '/^[AC]FLAGS/s@$@ -B/home/toshii/gcc-armelf/@' > $$
mv -f $$ Makefile

	6. Build the kernel.  You'll need to at least set
           MACHINE=hpcarm, MACHINE_ARCH=arm32 and
	   CC=/usr/pkg/cross/bin/arm-netbsd-cc.
	   And AS, LD, RANLIB, SIZE should point to executables built
           in step 3.

--
IWAMOTO Toshihiro