Qi for S3C2410

Micael Henriksson micael.h at gmail.com
Tue Nov 11 17:43:38 CET 2008

> Another point for GTA01 users is, well, DFU support "has moved to Linux"
> in the form of nand_write into mtdblock devices.  But since you did the
> work for SD Card booting too then so long as Qi itself is not trashed
> (it has no dependency on environment) then it would always be possible
> to recover by boot to Linux from SD Card filesystem.

Hmm.. The way I work is to have NAND as backup and try new kernels on
SD card. Mostly since the NAND space is so limited I only have a small
"backup" system there that boot quick without X and allows me to
quickly recover the SD card / change kernel on it. (i.e. a
"replacement for u-boot").
With the NAND CRC error problems in the new kernels (hopefully fixed
by Werner) it has also been a necessity. But as you say, if NAND were
trashed the SD card could always be put in a card reader and be
updated with a working system.

> The NAND partition offsets passed to Kernel will also need to be chosen
> with the "bad block allowance" method used in GTA02 so they are at fixed
> offsets and we don't need to take care about dynparts.  Maybe you did
> this already.

I currently have not changed the partitioning since I had a working
system on it. But it would be an easy change.

> | I made it so that is skip SD card and boot from NAND if AUX is held so
> | I can select which kernel to boot without removing the SD card. The
> | command line is still hardcoded, but it would be nice to also read
> | this from a file in /boot or from NAND. But that can come later.
> Yes I intend to make a generic "UI button to skip" interface, that's
> fine.  But I like the hardcoded commandline, it has a big advantage it
> won't break.  If we do implement something that is going to impact the
> commandline from a filesystem, it would be best if it only appended to
> the hardcoded one.  That way things are more portable, the filesystem
> does not need to know its device coordinates for root= for example.

True. The way I was thinking was due to the way I use the NAND system
as backup. That is I like to have hardcoded command line for NAND and
SD, but would also like to be able to override the default for the
SD-card by reading a file in /boot...
But that's as I say due to the way I am used to work. I can always do
my own version for my needs.. =)


More information about the openmoko-kernel mailing list