I'll put
something very simple on my very simple web directory ... and
also try my best to make this understandable :) I can't promise that
these numbered points are in any sort of relevent sequence though.
1) get
http://vaiprime.visibleassets.com/~cfriedt/linux-2.6.19-ts7xxx.tar.gz
2) take a look at all the stuff in there... particularly the
patch_and_build.sh script, and the iptables_for_arm_board.txt
file.
Breton Saunders, put together the discontig-memory patch, which i
thought was great, because it saved me a tonne of work ;-)
3)
What i've done is this:
with my laptop, i just use the wi-fi signal, and have a free ethernet
port, so i use the iptables routines in iptables_for_arm_board.txt
included in the above archive. It just sets up masquerading so that my
laptop is acting like a masquerading router / firewall for the board.
Thus the board can use my wireless connection too via packet forwarding.
You'll probably have to adjust the ETH0 variable for the _workstation_
section of the .txt file... which is also actually just another script.
In my kernel .config, i believe that i've set it to boot from an nfs
root by default. The line directly out of my config is this:
root=/dev/nfs nfsroot=192.168.0.1:/usr/gentoo_root,port=2049
ip=192.168.0.50:192.168.0.1:192.168.0.1:255.255.255.0:ts7250
init=/bin/bash
I think the ip= setting above is the default for the boards, so i just
stuck with that.
4)
You can use any method you want to upload the kernel image (tftp,
xmodem, etc). You just have to hit ctrl+c when the board boots and you
see a '+' sign on the terminal. That should be standard in the TS
documentation i think.
i use tftp to load my kernel these days, and with the above ip setting
(the default in redboot) i just type in
load -r -b 0x00218000 zImage-2.6.19
given that i have a tftp server running (inetd) on my laptop located in
/tftproot, with the (compiled via patch_and_build.sh) kernel image in
/tftproot/zImage-2.6.19
5)
but in this config, it expects an nfs root located at
192.168.0.1:/usr/gentoo_root ...
to export something via nfs, you'll need to append this line in
/etc/exports and restart your nfs service.
/etc/exports
============
/usr/gentoo_root 192.168.0.0/255.255.0.0(no_root_squash,rw,insecure,sync)
... i should add that you should make sure your network is secure. This
rw export with NFS, obviously, is not.
6)
hmm... this might already be apparent, but the 2.6.19 kernel works off
the shelf w/ the arm stage1 filesystem from embedded gentoo :) In a
couple of odd cases. You might want to change the CONFIG_CMDLINE in the
linux configuration to use init=/sbin/init instead, but i find that it
starts all of these unnecessary services.
7)
grab the stage1, or stage2, or stage3 armv4l filesystem, from
http://adelie.polymtl.ca/experimental/arm/stages/armv4l
or your favorite alternative for a gentoo mirror
http://www.gentoo.org/main/en/mirrors.xml
8)
Maybe it's a bit early to let this slip out, but I'm actually working on
a very highly portable buildroot based on portage and portage overlays.
This is a single bash script (that is quickly approaching 2500 lines ...
cough ... wheez) which automatically sets up a small folder to chroot
into a stage1 environment, so that you can build various things with
crossdev & xmerge, which are deliciously simple to use. It's got a heck
of a lot of fail-safe-ing too and will automatically back up all of your
configurations on each use.
It coallates & sorts all of your configurations / sysroots, etc ... i'm
hoping that it will start making me coffee in the morning too... just
kidding ;-)
What i find kindof cool about it, is that the script actually copies
itself into the chroot to give the illusion of a single continuous
program being run. (chroot'ing allows you to pass environment variables,
but by it's nature, it requires that you call another program upon
entering the new root)
... would any of you guys (or girls?) be interested in something like
that? ... please say yes :) I can only hope that this little utility
could help more people than just me.
You'd probably really appreciate it if you've ever used portage overlays
and ebuilds to automate your compiles.
I'm definitely looking for testers w/ the following architectures:
^ ( x86 | x86_64 ) ... so anything aside from your typical PC :)
be prepared to donate a good day or two to 96 or so permutations of
10-50 minute cross-toolchain trial compilations.
~/Chris