Testing 2.6.26 on a GTA01
Cesar Eduardo Barros
cesarb at cesarb.net
Sun Aug 3 00:36:30 CEST 2008
To see if I can base my cpufreq work on 2.6.26, I compiled a 2.6.26
kernel and successfully booted it both on both qemu and a real GTA01Bv4.
I used:
- The "August snapshot" u-boot[1]
- A kernel based on the stable-2.6 branch[2] with the following changes
to defconfig-2.6.26[3] (which I used as the .config):
CONFIG_S3C_LOWLEVEL_UART_PORT=0
CONFIG_MTD_NAND_S3C2410_DEBUG is not set
CONFIG_DEBUG_S3C_UART=0
- An openmoko-devel-image from today (compiled from the org.openmoko.dev
branch)[4]
I haven't tested the peripheral chips (GSM, BT, GPS); however, sound
works (this defconfig has everything built-in instead of using modules,
which is much better than having sound as a module).
The only problem I found so far is that the battery status icon seems to
be broken; it's displaying an exclamation icon and an almost-empty red
battery icon (I don't know if it's the fault of the kernel or the
userspace). To check that it's not the kernel that's broken, I took a
look at sysfs:
root at om-gta01:/sys/class/i2c-adapter/i2c-0/0-0008# cat chgmode
fast_cccv
root at om-gta01:/sys/class/i2c-adapter/i2c-0/0-0008# cat chgcur
255
root at om-gta01:/sys/class/i2c-adapter/i2c-0/0-0008# cat chgstate
fast_enabled present fast_ok
root at om-gta01:/sys/class/i2c-adapter/i2c-0/0-0008# cat battemp
37
root at om-gta01:/sys/class/i2c-adapter/i2c-0/0-0008# cat battvolt
4037
After some time (while typing this message in fact), battemp is now at 40.
I have attached the dmesg output (copied via ssh over usb ethernet)[5],
which is probably more informative than anything else on this message ;-) .
If you want me to do some other test on it, just ask[6].
[1] Yes, it's that old, but it's the last "officially recommended"
u-boot version for the GTA01 AFAIK. I'm playing with the kernel, not
with u-boot.
[2] Currently pointing at 0535fda1958587000a4abe711a50d221e0f82379.
[3] It also has a few local changes to the cpufreq core, which were not
compiled in.
[4] Tried ASU, but it suspended within qemu in a few seconds, and I
didn't find out yet how to recover from that on qemu.
[5] Yes, the clock is wrong. Nothing in userspace seems to have ever set
it correctly, and I didn't ever set it manually.
[6] However, I don't expect much help from the userspace on testing things.
--
Cesar Eduardo Barros
cesarb at cesarb.net
cesar.barros at gmail.com
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dmesg
Url: http://lists.openmoko.org/pipermail/openmoko-kernel/attachments/20080802/f1406c5f/attachment.txt
More information about the openmoko-kernel
mailing list