ChangeLog
From Openmoko
Note that this page covers the changelog for 2007.1. Version 2007.2 is under development, and early alpha versions should be released late August, 2007.
Contents |
Development
2007-06-03
close topmost app with short press on power button
The topmost application can now be closed with a short press on the power button. Hold it for 1 second to display a popup menu and hold it for 8 seconds to trigger a shut down.
2007-06-02
stylus main menu working
Finally, after months of desparation and lots of struggle, the stylus-based main menu is functional, i.e. it can be used to start applications ;)
2007-05-29
kernel 2.6.21.3
The default kernel has been updated from 2.6.21.1 to 2.6.21.3 (in svn rev. 2095). As usual, this will render your modules (in the roofs) incompatible with a more recent kernel. Pleas install a new rootfs image, or update the modules manually using ipkg.
2007-05-19
u-boot DFU image trailer
We have added some code to our u-boot patchset that tags every u-boot image that is generated in "deploy/images" with information on product/vendorid and hardware revision. This means, if you have updated beyond a svn rev. 2040 u-boot image, then you can no longer accidentially flash a u-boot for a wrong hardware revision into your device.
This unfortunately also means that you can no longer downgrade your u-boot to an earlier version using DFU. If you want to do that, we suggest you load the u-boot image via DFU into ram "-a 0" and then manually call "nand erase u-boot; nand write 0x32000000 u-boot; dynenv set u-boot_env".
The implementation uses a small 16byte signature at the end of the file, called u-boot dfu trailer (udfu trailer). This is _NOT_ related at all to the "DFU file suffix" as described in the DFU spec.
Upgrading to this new u-boot version is as smooth as always. just use dfu-util.
2007-05-03
u-boot DFU upload fix
From April 19 (svn rev. 1803) to today (svn rev. 1897) the u-boot DFU upload function was broken. This resulted in devirginator failure. The bug has now been fixed.
u-boot 500mA charging
Ever since u-boot received support to switch to 500mA charging support automatically during USB enumeration, the function had a race condition in the i2c driver code resulting in "i2c read timeout" bug messages, as well as follow-up errors such as dfu-util or devirginator instability. This is fixed now.
2007-04-15
Hold the power button for one second to see a popup menu.
2007-03-19
gsmd gets a start script
The gsmd package features a start script now that properly sets up the gsmd infrastructure. Using this start script, performing phone calls with the openmoko-dialer works out of the box (when called twice -- I'm going to add AUX button awareness asap).
2007-03-14
New u-boot adds 500mA charging
u-boot svn rev. 1364 and later now export two separate USB configurations which are 99% identical. The only difference between those two configurations is the MaxPower field which indicates 100mA and 500mA, respectively.
u-boot now also automatically switches between 100mA and 500mA charging modes in a USB specification compliant way.
However, timeout-based wall outlet charger heuristics are not yet implemented. In other words: You still cannot use the 500mA charging when using the wall outlet charger / power supply. It is therefore recommended to always use a USB Host (PC) to charge your Neo1973 for the time being.
2007-03-11
New u-boot fixes memory corruption
All new u-boot versions >= 1.2.0-moko6 fix an important memory corruption issue when used on the GTA01Bv2 and GTA01Bv3 device revisions. If you have been running into any system stability problems (kernel oops, ...), please try updating your u-boot image to a version >= moko6.
2007-03-10
Update to kernel 2.6.20.2
Since the vanilla kernel 2.6.20.2 has been released, we have migrated our patchset onto 2.6.20.2. This means if you use kernels -moko8 or higher (e.g. http://buildhost.openmoko.org/tmp/deploy/images/uImage-2.6-moko8-r1_0_1288_0-fic-gta01.bin), you should also upgrade your modules in userspace!
2007-03-09
U-Boot: No timeout during DFU
Boot menu timeouts are now disabled while in DFU mode, thus long downloads will not longer be interrupted. Note that U-Boot stays in DFU mode until a reset, power off, boot, or dfu-util -R.
U-Boot boot menu improvements
The boot menu can now also be invoked after a reset or when starting from RAM, by pressing and holding down AUX.
The boot menu screen now includes the U-Boot version string and build date.
Changes to the environment variable boot_menu_timeout affect the boot menu immediately. Before, they were only picked up after restarting the boot menu (i.e., by executing one of the options).
U-Boot no longer prints garbage for microSD CID
The card identification data printed by the command mmcinit assumed that the card was in MMC format. The updated driver supports and uses the SD format if the card is an SD card.
Failed DFU download to U-Boot no longer leaks memory
If a download to the U-Boot partition was interrupted, the download buffer was not freed, causing the next attempt be rejected due to lack of memory. The buffer is now freed when retrying.
dfu-util accepts partition names
The -a option of dfu-util now accepts partition names, not only numbers, e.g., ... -a rootfs ... Names are much safer to use than numbers, so this use is strongly recommended. (This change was already made several days ago, but only finalized today.)
DFU clears end of rootfs partition
After downloading to a rootfs partition, the remaining blocks are cleared with the equivalent of "nand erase clear". This prevents data from surviving a partition "rewrite from scratch" and should also speed up the first mount.
2007-03-08
kernel console now disabled automatically when GSM powered up
Kernel builds with svn patchset 1288 and later now automatically disable the console output to /dev/ttySAC0 once you power up GSM via sysfs.
AUX button and headphone jack now working in input event driver
There was a bug in gta01kbd.c that caused the AUX button event reporting to not work. Headphone jack detection was not yet implemented and has been added in kernel patchset svn >= 1287
2007-03-07
new bitbake upstream revision dependency code
We have committed code changes to our OE base.bbclass to add better dependency tracking, i.e. our openmoko packages will now only be re-built if there actually have been any source code or patch changes.
In order to benefit from this feature, please apply the following patch to your bitbake installation: http://people.openmoko.org/henryk/bitbake-1.6.6-om2.patch
This is a temporary relief. We're working on implementing fetcher support for git and others, as well as discussing this with the bitbake authors and merging something like this upstream to the current bitbake development branch.
2007-03-06
sync with upstream OE
We have synced with upstream OE revision 'e2dbb52fe39df7ef786b6068f6178f29508dfded'
Our old '/oe' directory can be found at http://svn.openmoko.org/branches/oe/pre-20070305/
Updating
First, you have to update your upstream OE repository to the current snapshot by updating your OE.mtn database
mtn --db=/path/to/your/OE.mtn pull monotone.openembedded.org org.openembedded.dev
then change into your 'openembedded' directory and do
mtn update -r e2dbb52fe39df7ef786b6068f6178f29508dfded
to update the actual recipie tree from the OE.mtn database.
Next, you have to do a usual 'svn update' in your 'oe' directory to get our updated recipies.
[If you're using MokoMakefile, just "make update" to do all of the above.]
Changes
Since for many packages we're now using upstream OE recipes rather than our own, the contents of openmoko-devel-image has slightly changed. The most noticable change is that there is no automatic xterm starting when X11 is started. I don't consider this a problem. However, what's more of an issue is that ther is no way from the menu/desktop to start a terminal ;)
Anyone interested in submitting a fix for that: You're most welcome.
new package revision numbering
We're currently testing some [still incomplete] bitbake modifications that allow us to put the svn revision numbers into PR. This basically assures that our openmoko-* and uboot/kernel packages only get rebuilt if there was a change in our subversion tree. Gone are the days of always ending up rebuilding u-boot and kernel, even if there was not a single code change meanwhile.
A package name of
openmoko-dates_0.1+svnnow-r4_326_armv4t.ipk
means that this is the bitbake recipe revision 'r4' packaging subversion revision '326'. while
u-boot-gta01bv3-r2_0_1229.bin
means that this is bitbake recipe revision 'r2' with upstream revision '0' (we don't have implemented git revision support yet, this will be the md5 git revision of the u-boot git repostory soon) plus our patches from svn revision 1229.
As soon as we've completed this testing internally, we'll commit the respective bitbake patch and base.bbclass change to our svn repository (and post it to oe-devel for discussion).
2007-03-05
new buildhost.openmoko.org
buildhost.openmoko.org has been re-installed following the recent hardware problem and fs corruption issues. You can find the old-to-current packages at http://buildhost-old.openmoko.org/.
The new buildhost.openmoko.org has a new ssh key, fingerprint is 41:9f:a4:3d:39:cc:3e:26:8a:b2:17:9b:c2:95:0c:7e[[Category:Openmoko]
