On Wed, Jun 27 '01 at 22:48, Matt Kasdorf wrote:
> The "Familiar v0.4 Installation Instructions" mention bootldr v2.14.5
> but v2.14.8 is available, which should I use (as there is no
> "bigkernel-mono" for v2.14.8)?
Get the latest kernel (e.g. v2.14.8) but be carefull, there are two
versions of each bootloader:
1) bootldr-0000-x.yy.zz
^^^^ this one is to be loaded into flash with load bootloader
2) bootldr-C000-x.yy.zz
^^^^ this one is to be loaded by the windowsCE os loader
application (too load the bootloader into flash)
NEVER EVER BURN A C000 bootloader into flash, this will brick your iPaq
(I dont know what happens if you run a 0000 bootloader from winCE, but
most likely the iPaq just crashes)
> What is the difference between these kernels (what's rmk#, np#, hh#)?
> zImage-2.4.1-rmk1-np2-hh2
> zImage-2.4.2-rmk1-np1-hh2
> zImage-2.4.3-rmk2-np1
^ different kernel versions, the rmk, np, hh are "just"
patch levels done by rmk (this are just guesses: general arm patches),
np (ipaq specific patches) hh (additions by handhelds.org)
> Why the change from cramfs to jffs?
JFFS is read/write able, and does compression and journaling
cramfs allows for read only (and comes precompressed)
> Once the bootloader is installed can I switch from using the serial
> link cable to the USB link cable? Or is it the bootloader restricting
> me to serial?
Nop, you have to stick with the serial link till the familiar root image
is installed (at this point you could use USB networking, but the serial
line is needed for debugging every now and than)
> What is (specifically) in these "task"s? (Huh, does "task" mean
> something?)
a "task" is just a small ipkg that depends on all files needed to
forfill the given task
> task-bootstrap.jffs2
minimal set of files to get the ipaq booted
> task-familiar-complete.jffs2
all files to give familiar 0.4 the features 0.3 had
Goetz.
This archive was generated by hypermail 2.2.0 : Mon Jul 25 2005 - 17:12:27 EDT