Hello Johan,

If the linux kernel is up and running with all drivers in.
(particularly touchscreen and display) it shouldn't be too bad.

IHMO, the easiest way to get you running is to aggregate the initial
ramfs built into the kernel with the Android build, the root Android
root filesystem (system), and the user data section (mounted as /data
I believe) into one root filesystem.

You can then take that root filesystem as one tarball.

Modify the NAND partitioning of the kernel to set aside space for the
whole Android rootfs, and of course rebuild the kernel. (Be sure yaffs
support is in the kernel) Also no need for a ramfs at this point, just
have the kernel look to mtd2 for it's root filesystem, which will be

Create yourself a busybox root filesystem too. Make that into a jffs2

So your partitioning would look something similar to this (you'll have
to decide on the sizes of course):
mtd0: bootloader
mtd1: kernel
mtd2: rootfs (jffs2)
mtd3: Android rootfs.

Erase everything on the NAND.
Burn the normal Chumby bootloader to mtd0.
Burn the the new kernel into mtd1.
Burn the jffs2 rootfs image to mtd2.

Boot the device. Hopefully you get yourself to a prompt.

Once you have that prompt mount mtd3 to /mnt/android as a yaffs2
Untar your Android rootfs into /mnt/android.
Chown and chgrp everything under /mnt/android to "root"
chroot to that mount point "chroot /mnt/android /init"

At this point you should see Android trying to run.

I know that's a bit to chomp on, but it's more of an outline of what
you will need to do. Of course it's assuming you have the ability to
erase the whole nand and put down images amongst other assumptions,
but it should help get your mind around a little bit of the
requirements to get Android running on your device.

Regarding your bootloader question, I'd just stick with the current
one. You'll only need to modify that if/when you go into having
everything compatible with the recovery system. Which is a completely
different discussion.

Good luck!


On Aug 21, 1:16 am, Johan de Koning <ikbennu...@gmail.com> wrote:
> Hello,
> Now that building cupcake for dream is working I was looking for a new
> research topic :)
> One of the problems with the HTC Dream is that it makes use of closed
> prorietary files and that the hardware specification is not available.
> Because I am interested in porting Android to different devices I was
> looking at hardware for which the specification is available. Then I
> found the cute device called Chumby (www.chumby.com). It looks to me
> as a device for which it should be possible to run Android on it. The
> software (which also uses the linux kernel) and hardware
> specifications are available. So I want to give it a try.
> My question to you is where to start with porting Android? In one of
> the Android presentation there is mentioned that you should first get
> the kernel running. Is this a good starting point? And can I use the
> bootloader which Chumby uses or should I replace it with a different
> one?
> Hopefully you can supply me with some pointers where to look/start.
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

Reply via email to