Re: Qi vs U-boot
Ivan Matveev imatvee...@nm.ru writes:
As always with automatic someone has to build the mechanism. Qi has
it already. Why shell I bother with u-boot numerous(poorly documented)
options?
I don't intend to flame but u-boot has a long manual:
http://www.denx.de/wiki/DULG/Manual
I will see much more than 1% of kernel parameters in the file.
That's indeed complex partly because it is a template that can be used
to generate different configuration files.
I keep my u-boot configuration in /etc/uboot.conf that reads
#!/bin/sh
set -e
fw_setenv bootargs_base 'g_ether.host_addr=00:1F:11:01:1F:6B
g_ether.dev_addr=00:1F:11:01:1F:6B panic=20 mem=127M loglevel=8 rootfstype=ext2
root=/dev/mmcblk0p2 rootdelay=5
mtdparts=physmap-flash:-(nor);neo1973-nand:0x0004(u-boot),0x0004(u-boot_env),0x0080(kernel),0x000a(splash),0x0004(factory),0x0f6a(rootfs)
ro'
fw_setenv bootcmd 'setenv bootargs ${bootargs_base}; mmcinit; ext2load mmc 1:2
0x3200 boot/stable.bin; bootm 0x3200'
fw_setenv menu_1 'stable: setenv bootargs ${bootargs_base}; mmcinit; ext2load
mmc 1:2 0x3200 boot/stable.bin; bootm 0x3200'
fw_setenv menu_2 'testing: setenv bootargs ${bootargs_base}; mmcinit; ext2load
mmc 1:2 0x3200 boot/testing.bin; bootm 0x3200'
fw_setenv menu_3 'unstable: setenv bootargs ${bootargs_base}; mmcinit; ext2load
mmc 1:2 0x3200 boot/unstable.bin; bootm 0x3200'
fw_setenv menu_4 'failsafe: setenv bootargs g_ether.host_addr=00:1F:11:01:1F:6B
g_ether.dev_addr=00:1F:11:01:1F:6B panic=20 mem=127M loglevel=8 rootfstype=ext2
root=/dev/mmcblk0p2 rootdelay=5 ro
mtdparts=physmap-flash:-(nor);neo1973-nand:0x0004(u-boot),0x0004(u-boot_env),0x0080(kernel),0x000a(splash),0x0004(factory),0x0f6a(rootfs)
rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 panic=10; mmcinit; ext2load
mmc 1 0x3200 boot/failsafe.bin; bootm 0x3200'
fw_setenv menu_5 'fast charge: neo1973 charger fast; neo1973 backlight off;
neo1973 led 0 on; setenv boot_menu_timeout 3600'
fw_setenv menu_6 'Set console to USB: setenv stdin usbtty; setenv stdout
usbtty; setenv stderr usbtty'
fw_setenv menu_7 'Set console to serial: setenv stdin serial; setenv stdout
serial; setenv stderr serial'
fw_setenv menu_8 'Power off: neo1973 power-off'
fw_setenv menu_9 'experimental: setenv bootargs ${bootargs_base}; mmcinit;
ext2load mmc 1:2 0x3200 boot/experimental.bin; bootm 0x3200'
fw_setenv splashimage 'nand read.e 0x3200 splash 0x5000; unzip 0x3200
0x880 0x96000'
fw_setenv stdin 'usbtty'
fw_setenv stdout 'usbtty'
fw_setenv stderr 'usbtty'
fw_setenv usbtty 'cdc_acm'
fw_setenv quiet '1'
fw_setenv bootdelay '1'
fw_setenv boot_menu_timeout '300'
echo DONE
where fw_setenv is the command for modifying u-boot environment
variables from command-line. I use the
stable/testing/unstable/experimental menu entries mostly to test new
kernels so that I always can fallback to a working version if I hit a
critical bug :-)
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Qi vs U-boot (was Re: QtMoko v30; UBIFS; can't boot)
Hi, Ivan, В Втр, 28/12/2010 в 06:04 +0300, Ivan Matveev пишет: Lets burn some linux.org.ru style flame! Hey, such foreword spoils good talk, so i'll try to be short. It's also possible to setup u-boot like qi, 'read kernel first from sd part 1, boot if loads, then try from sd part 2, boot if loads, then from nand'. All with 10 lines in config file. Just noone need it. No one needs the good stuff :). Cause is that this stuff is not good :) Does every FR user have to develop a bootloader? Process of changing configuration is not development. Process of looking up something in C sources of Qi is development ;) Please tell me how to do this! I have no religious bind to Qi. To hell with minimalism, let us all use the bootloader that is standard, smart, configurable and well supported. I think easiest way is to use fw_setenv. I rethought, need relatively trivial modification to u-boot to support loading plain file to env variable with something like 'ext2loadvar location [var]'. But this brain-dead by design idea require bootloader to support all possible fses (how does qi reads ubifs for kernel parameters, if it has no support for ubi?) I'm waiting for Radek's comment on this. Qi's sources are not easy, no stdlib functions. Local Qi pontiff is Paul Fertser. Please do not be offended. I was frustrated by FR suddenly not booting. It's impossible to offend me with good arguments. Gennady. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Freerunner's contribution to /dev/random entropy
Hello all happy holidays, With the recent thread that mentions the noisiness of the accelerometers, I was reminded that the Freerunner has lots of sensors that are capable of being good sources of entropy for Linux's random number generator, especially with the Nav board installed. The accelerometers actually already contribute entropy (the input device framework takes care of it), but the new devices on the Nav board do not. Do you think it would be a good idea to add that? I think that the BMP085 probably should not (sensor readings too predictable and hardly changing from one reading to the next) but the other two should be good candidates, especially the rate gyros. -Phil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v30; UBIFS; can't boot
Ivan Matveev wrote:
That's the sources I'v looked at to learn how Qi uses NAND partitions.
Funny
find ./ -exec grep -H ubi '{}' ';'
finds nothing relevant. Am I looking at the right sources?
Ahh sorry, i forgot you need to be on the right branch:
https://github.com/radekp/qi/tree/qtmoko-v28
I think it wold be ideal if Qi wold treat NAND as a regular partition,
i.e. wold read kernel options from identity-ext2/append-GTA2.
I think I could implement that. Looking for the place in the sources
where Qi reads append-GTA02. Have a little difficulty understanding
the sources.
I might be wrong, but that would involve reading jffs2/ubifs/yaffs and
whathever
else filesystem. This goes quite against the idea of qi to keep it simple.
Regards
Radek
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v30; UBIFS; can't boot
On Tue, 28 Dec 2010 22:40:10 +0100
Radek Polak pson...@seznam.cz wrote:
Ivan Matveev wrote:
That's the sources I'v looked at to learn how Qi uses NAND
partitions. Funny
find ./ -exec grep -H ubi '{}' ';'
finds nothing relevant. Am I looking at the right sources?
Ahh sorry, i forgot you need to be on the right branch:
https://github.com/radekp/qi/tree/qtmoko-v28
Thank you.
I think it wold be ideal if Qi wold treat NAND as a regular
partition, i.e. wold read kernel options from
identity-ext2/append-GTA2. I think I could implement that. Looking
for the place in the sources where Qi reads append-GTA02. Have a
little difficulty understanding the sources.
I might be wrong, but that would involve reading jffs2/ubifs/yaffs
and whathever else filesystem. This goes quite against the idea of qi
to keep it simple.
My idea was to put NAND kernel options in to append-GTA02 file on
identity-ext2(mtd5, dfu-util calls it factory) NAND partition.
The partition contains ext2 file system so we don't have to
add jffs/ubifs support to Qi.
Qi already mounts the partition and reads usb file from it.
See:
radekp-qi-b214400/src/cpu/s3c2442/gta02.c
char * append_device_specific_cmdline_gta02(char * cmdline)
[...]
if (!ext2fs_mount()) {
[...]
len = ext2fs_open(usb);
Also Qi already has a parser for append-[device] files.
So we cold just add identity-ext2 partition to the list of partitions
that Qi search for /boot/append-GTA2
and immediately have configurable kernel options for NAND boot.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Qi vs U-boot (was Re: QtMoko v30; UBIFS; can't boot)
On Tue, 28 Dec 2010 16:45:56 +0300 Gennady Kupava g...@bsdmn.com wrote: Please tell me how to do this! I have no religious bind to Qi. To hell with minimalism, let us all use the bootloader that is standard, smart, configurable and well supported. I think easiest way is to use fw_setenv. I rethought, need relatively trivial modification to u-boot to support loading plain file to env variable with something like 'ext2loadvar location [var]'. But this brain-dead by design idea The brain-dead idea is not mine :) /boot/grub/menu.lst require bootloader to support all possible fses (how does qi reads ubifs for kernel parameters, if it has no support for ubi?) No it doesn't require jffs/ubifs support. The identity-ext2(mtd5, dfu-util calls it factory) NAND partition contains ext2 fs. So on linux runing from NAND echo /dev/mtdblock5 /boot ext2 defaults /etc/fstab Navigate to /boot, edit append-GTA02... Natural way for people used to PC bootloader like grub. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Qi vs U-boot
On Tue, 28 Dec 2010 12:01:41 +0200 Timo Juhani Lindfors timo.lindf...@iki.fi wrote: Ivan Matveev imatvee...@nm.ru writes: As always with automatic someone has to build the mechanism. Qi has it already. Why shell I bother with u-boot numerous(poorly documented) options? I don't intend to flame but u-boot has a long manual: http://www.denx.de/wiki/DULG/Manual Thank you. I will see much more than 1% of kernel parameters in the file. That's indeed complex partly because it is a template that can be used to generate different configuration files. I keep my u-boot configuration in /etc/uboot.conf that reads I agree that passing kernel params is just a small part of u-boot functionality. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Wikireader FAQ draft
Christoph Pulster wrote: Any comments welcome ! Chris Openmoko Wikireader - Frequently asked questions - dimensions ? The Wikireaders size is 10x10cm with 2cm depth, Weight: 120g. Compare it here: PICTURES - handling ? The unit has only three buttons and is very easy to use. The touchscreen display can be navigated with the fingers (no need for a stylus) and is easy to read indoors and out. The case is very robust and the organic shape is a joy to hold. Explicit Wikipedia content can be protected with a password. So the Wikireader is kid-safe. - manual ? The unit comes with a small printed manual. Please find a PDF copy here: http://thewikireader.com/files/WR_Manual_V4_en.pdf - power ? The Wikireader uses two standard batteries (size AAA) which last for a full year of usage. No annoying discharged battery, no fittling with power adapters. fittling fiddling This makes the device helpful while travelling in the Australian outbacks. Rechargeable 1.2V AAA batteries can be used in place of standard 1.5V ones. - Languages ? Please see a list of available languages here: http://dev.thewikireader.com/language-packs Several languages can be used simultaneously. Additional languages can be installed with the Update application from Openmoko: http://www.thewikireader.com/update/ After installation, you can choose language on the Wikireader by touching the globe symbol on the search page. - Quickupdate GERMAN ? Remove memory card from Wikireader, insert it in your PC-cardreader. Download FILE, extract and copy directory depedia to the memory card. Put the card back to the Wikireader and German language is now available ! - Update ? Please download the Openmoko Update Application here: http://www.thewikireader.com/update The Wikireader content is updated quaterly from Openmoko and is always free to download ! - eBooks ? Next to Wikipedia you can use simultaneously the eBooks from Project Gutenberg. Project Gutenberg on WikiReader contains the eBooks from http://gutenberg.org (but not http://gutenberg.cc). You will need to upgrade to a 16 GB memory card. The Gutenberg eBooks can be downloaded with the Openmoko Update Application: http://www.thewikireader.com/update - Other kinds of content ? Any wiki that runs on MediaWiki software ( http://www.mediawiki.org/wiki/MediaWiki ) can be converted to the WikiReader format and copied to the memory card. In addition to many language versions of Wikipedia and the eBooks from Project Gutenberg, the English Wiktionary ( http://en.wiktionary.org/wiki/Wiktionary:Main_Page ) and Wikiquote ( http://www.wikiquote.org/ ) have already been converted and are available on the Update page ( http://dev.thewikireader.com/language-packs/ ). There is enough room on a 16GB card to fit one Wikipedia, Gutenberg, Wikiquote and Wiktionary, all at the same time, with gigabytes to spare. There are many other language versions of Wikipedia that have not been converted to WikiReader format yet, and many other kinds of useful wikis that are suitably licensed for free redistribution as well. WikiReader users who have the required skills, and an itch to scratch, are encouraged to convert these and offer them to the community. - Custom content? For more technically inclined users: You can put custom content in your WikiReader by first uploading it into a wiki running on MediaWiki and then doing an xml dump as described at http://www.mediawiki.org/wiki/XML_dump#XML_dump . The dump is then converted to WikiReader format using the Python program found in the WikiReader git tree ( https://github.com/wikireader/wikireader ) . Creating an empty private wiki is easy, and it only takes minutes to get started. First install VirtualBox ( http://www.virtualbox.org/ ) and then within it, install a MediaWiki appliance ( http://www.turnkeylinux.org/mediawiki ). When you start the appliance, it displays a URL that you enter into your web browser. Then you add content and edit it in the usual wiki way. - more functionality ? Calculator = press and hold History-button while powering the Wikireader on. System applications = press and hold Search-button while powering the Wikireader on. Debug console (GPIO) for developers = press and hold Random-button while powering on. Forth programms - the Wikireader can execute Forth written code (check *.4th, *.4mu files in root dir on the memory card) - developement ? You can find source code, technical specifications etc. here: https://github.com/wikireader/wikireader A SDK can be found here: http://wrdk.seabright.co.nz/ (C) Wikireader Shop www.pulster.de Christoph ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list
Re: QtMoko v30; UBIFS; can't boot
Ivan Matveev wrote:
My idea was to put NAND kernel options in to append-GTA02 file on
identity-ext2(mtd5, dfu-util calls it factory) NAND partition.
The partition contains ext2 file system so we don't have to
add jffs/ubifs support to Qi.
Qi already mounts the partition and reads usb file from it.
See:
radekp-qi-b214400/src/cpu/s3c2442/gta02.c
char * append_device_specific_cmdline_gta02(char * cmdline)
[...]
if (!ext2fs_mount()) {
[...]
len = ext2fs_open(usb);
Also Qi already has a parser for append-[device] files.
So we cold just add identity-ext2 partition to the list of partitions
that Qi search for /boot/append-GTA2
and immediately have configurable kernel options for NAND boot.
Ahh oki, that makes sence then.
Regards
Radek
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
