Hi Bill,

A1) The BDK from Sharp adds an entire userland: including libraries, applications and a full Qt-based gui (looks a lot like a zarus). So while you don't strictly need it to boot the linux kernel supplied, you wont be able to do anything without a "userland".

A2) We have never used it, so couldn't comment.

A3) The .tgz file provided by Logic includes full source for the kernel only, and the BDK from Sharp includes full source for the userland mentioned above.

regards,
mt

1.0.0c is coming, the changes are as follows. you can safely make
these changes to the 1.0.0b release by hand.

-removed a few files that are created during the kernel build:
src/linux/scripts/mkdep
src/linux/scripts/split-include
src/linux/scripts/tkparse
src/linux/scripts/kconfig.tk
src/linux/scripts/MAKEDEV.ide

-fixed typo in LPD-README

-changed one line in scripts/build.sh so that the config stage of the
build is run by default. After the make is run once, you can safely
change the 'LPDCFG=' line back to 'LPDCFG=X' to prevent subsequent
kernel builds from running the config stage.

another thing to note about the linux kernel builds is that
a build results in two separate binaries for the kernel, both
of which get named 'vmlinux', but one is a compressed image
with a small gunzipper attached to it, while the other is an
image suited for loading directly into ram and running.

the 'vmlinux' created in src/linux is the ram image, and the
'vmlinux' created in src/linux/arch/arm/boot/compressed is
the compressed version, built to be burned into flash and
run from there.

i can only justify this strange naming by saying that it's standard.

The standard is for compressed linux kernels to be called "vmlinuz". The z is used to signify compression as you would see it, for example, when uncompressing a tar archive: "tar zxvf filename.tgz"

ok, i'll change my wording... replace 'standard' with 'it came that way'.

cheers
mt