http://wiki.openmoko.org/api.php?action=feedcontributions&user=Jpkotta&feedformat=atomOpenmoko - User contributions [en]2024-03-28T10:36:47ZUser contributionsMediaWiki 1.19.24http://wiki.openmoko.org/wiki/Community_UpdatesCommunity Updates2007-11-14T16:27:00Z<p>Jpkotta: /* Delivery of a GSM firmware update for the 3G SIM bug (#666) */ link to bugzilla</p>
<hr />
<div>'''Community Updates'''<br />
<br />
As we strive to make our development progress as open as possible, we do not provide delivery dates. Instead, we continuously report on the project status here and on our mailing list. <br />
<br />
The status is usually updated at least twice a month, usually by [[User:Michaelshiloh|Michael Shiloh]]. Updates are also mailed to the community mailing list (see below for previous updates), and major updates are also sent to the announce list.<br />
<br />
You are invited to add questions or topics you think should be included in the Community Updates.<br />
<br />
==Current Status==<br />
<br />
===GTA02 hardware production and qualification===<br />
GTA02v3 is quite solid, but a flaw in power distribution required another revision. A very small number of GTA02v4 have been manufactured. Evaluation by internal OpenMoko engineers should start any day now (relative to October 31, 2007).<br />
<br />
===gllin GPS driver for GTA01===<br />
We have received permission to distribute this driver in binary-only form, but the legal teams of Global Locate and OpenMoko have not been able to agree on a method for doing so.<br />
<br />
November 13, 2007: We have heard that Global Locate is willing to let us release the binary without requiring any further legal steps, but we have not been able to confirm this with anyone of authority.<br />
<br />
Note that the binary format of the driver will be OABI, which is different from what we now use (EABI). There are various work-arounds (chroot, wrapper).<br />
<br />
===850 MHz band not supported in USA+Canada (e.g. comment 24 on bug #256)===<br />
<br />
The GSM chip set is capable of quad band operation but the circuit implemented only supports 3 bands. So, 850Mhz is not supported on the GTA01 board. Instead we support 900/1800/1900MHz.<br />
<br />
Anyone interested in more details is welcome to email me.<br />
<br />
===Delivery of a GSM firmware update for the 3G SIM bug ([http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=666 #666])===<br />
Background:<br />
<br />
A bug in the GSM firmware prevents some USA 3G SIM cards from working properly. The bug has been fixed, but since the GSM module is under extremely tight legal protection, it is not clear whether or how we can allow customers to perform this upgrade themselves.<br />
<br />
November 13, 2007:<br />
<br />
We have heard that TI has figured out a way to let you, our customers, upgrade the firmware, but we have not been able to get hold of the person at TI who can tell us how we should do this.<br />
<br />
We have permission to perform a Very Hacky Workaround: Get your Neo to me (Michael Shiloh), and I will perform the GSM firmware upgrade for you. Contact me for details.<br />
<br />
==Questions or Topics you think are missing==<br />
<br />
=== SMedia 3362 Documentation & OpenGL ES Drivers ===<br />
There is an open source kdrive driver being written for the GTA02 which will use hardware to accelerate the XRender extension. While the chip is capable of 3D graphics, no OpenGL ES driver/library is avaliable and OpenMoko developers will not be writing one in the near future (although they have not ruled it out in the long-term). <br />
<br />
Documentation for the SMedia 3362 has been promised ([http://lists.openmoko.org/pipermail/community/2007-September/010175.html see this post]). However, this refers to documentation OpenMoko developers will be writing themselves, not the technical documentation SMedia have provided OpenMoko with. The OpenMoko developers had to sign an NDA with SMedia to obtain this documentation and are therefore unable to pass this information on to community developers. (See [http://lists.openmoko.org/pipermail/community/2007-November/011349.html this post] for details)<br />
<br />
==Previous Community Updates==<br />
*[[September 28, 2007 Community Update]]<br />
*[[October 12, 2007 Community Update]]<br />
*[[October 13, 2007 Community Update]]<br />
*[[October 15, 2007 Community Update]]<br />
*[[October 16, 2007 Community Update]]<br />
*[[October 25, 2007 Community Update]]<br />
*[[October 31, 2007 Community Update]]<br />
*[[November 6, 2007 Community Update]]<br />
*[[November 13, 2007 Community Update]]<br />
<br />
[[Category:Community]]</div>Jpkottahttp://wiki.openmoko.org/wiki/Configuring_the_boot_splash_screensConfiguring the boot splash screens2007-11-14T01:06:32Z<p>Jpkotta: </p>
<hr />
<div>There are three splashes as of 13 Nov. 2007. The U-Boot splash is displayed until the kernel takes over. Presumably the kernel will eventually display a splash while it boots. When userspace initializes, psplash displays a splash. Finally X displays a splash when it starts.<br />
<br />
== U-boot Splash ==<br />
<br />
=== Original instructions ===<br />
Is a raw framebuffer bitmap that is gzipped.<br />
<br />
Here is a basic description: http://svn.openmoko.org/trunk/src/host/splash/README<br />
<br />
Use [[dfu-util]] to send to the OpenMoko.<br />
<br />
=== Instructions which worked for me ===<br />
The above instruction did not work, unfortunately, maybe there were for a previous release of u-boot. The following did work for me:<br />
<br />
* install the appropriate tools<br />
** download the README and the Perl script from http://svn.openmoko.org/developers/werner/splash/<br />
** chmod a+rx *.pl <br />
<br />
* how to use the tools<br />
** first, make a PNG 480x640x8 (or just get the original picture from http://wiki.openmoko.org/images/c/c2/), and name it System_boot.png<br />
** convert the System_boot.png into a compressed converted image file splash.gz, then download it to the splash partition (the net1973 must be in u-boot mode, and you need dfu-util)<br />
*** ./imghs.pl | gzip -9 > splash.gz<br />
*** sudo ../bin/dfu-util -a splash -R -D splash.gz<br />
** if the size of splash.gz is not exactly 0x5000, please see the next section.<br />
<br />
=== Modifying the size of the compressed splash image ===<br />
NOTE... the README states you must issue two U-Boot commands to enable the flashed splash image to appear on the screen at boot:<br />
<br />
''setenv splashimage nand read.e 0x32000000 splash 0x5000\; unzip 0x32000000 0x33d00000 0x96000''<br />
''saveenv''<br />
<br />
This is already a part of the U-Boot image received in the phone... however, if you make changes to your splash image, you may need to change the splashimage variable to compensate!<br />
<br />
0x5000 is the (maximum) size of the compressed file -- the splash.gz that gets created. If you've made changes to your image you may have increased the compressed size; if it exceeds 0x5000 (20480) bytes, the entire image will not load unless you increase this value in your splashimage U-Boot environment variable.<br />
<br />
== Linux kernel ==<br />
''To Do''<br />
<br />
== psplash ==<br />
You need to recompile psplash, because the picture is hardcoded. There is a script in the source for psplash for making a new header file. On Ubuntu, you need the libgtk2.0-dev package to run the script.<br />
<br />
make-image-header.sh my_image.png HAND<br />
mv my_image-img.h psplash-hand-img.h<br />
<br />
Then add your custom header to the OpenEmbedded recipe (org.openembedded.dev/packages/psplash/files/openmoko/psplash-hand-img.h), or rebuild psplash by hand.<br />
<br />
== X splash ==<br />
<br />
The X server accepts a -root-ppm option, which takes a plain old (raw) ppm file. Replace /usr/share/pixmaps/xsplash-vga.ppm on the phone or org.openembedded.dev/packages/xserver-kdrive-common/xserver-kdrive-common/openmoko/xsplash-vga.ppm in OpenEmbedded.<br />
<br />
[[Category:Developer software]]</div>Jpkotta