Openmoko Monotone Changes
Hi, There have been some major changes in the Openmoko monotone repository. The scheme before became unmaintainable back to org.openembedded.dev so Openmoko has chosen to branch off the main org.openembedded.dev to a new branch org.openmoko.dev. I will state this is not a fork of OE by any means, it is there due to openmoko needing space to develop new features that on their first commit are not suitable for mainline OE.dev yet. monotone users just need to pull the new branch from monotone.openmoko.org. Then mtn --db=OE.mtn co --branch org.openmoko.dev MokoMakefile users need to make update-makefile make update then follow instructions to remove patches and openembedded directories. Thanks for the patience Graeme (XorA) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Openmoko Monotone Changes
Graeme Gregory wrote: There have been some major changes in the Openmoko monotone repository. ... MokoMakefile users need to make update-makefile make update then follow instructions to remove patches and openembedded directories. You'll end up running make update twice - see below for details. When you do this update, the makefile will ask you to remove the patches directory and the stamps/patches file. This is to ensure that you get a correct checkout from the new svn.projects.openmoko.org location. Make sure you have no local changes in the patches directory (cd patches ; svn status) before doing this (it's unlikely that you will, but I have to say this so no-one is surprised that their local patches get deleted). Then you will be asked to run make setup-patches - this will checkout the empty patches directories from the new home of MokoMakefile into your patches directory. Then when you run make update again, the makefile will ask you to remove the openemebedded directory and the stamps/openembedded file. This is to ensure that you get a correct checkout from the new branch. Make sure you have no local changes in the openembedded directory (mtn status ; mtn list unknown) before doing this. Then you will be asked to run make setup-openembedded - this will checkout the new org.openmoko.dev branch into your openembedded directory. Then you're ready to build. BTW, I have also moved MokoMakefile back to projects.openmoko.org (it was there originally, but anon svn checkout was broken so I had to move it to nslu2-linux.org), so that OM staff and other well-respected developers can have commit access to fix problems when I'm not available. [That's the reason why the patches directory had to be updated] -- Rod ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Qemu on GTA02, the problem still here
Thank you! I deleted my .bin and .jfs2 copied the build you linked to into the folder, ran download.sh and then flash.sh... and now it works... Hope this helps others to know what to do! Best Regards, Jens On Mon, 2008-03-24 at 02:46 +0800, John Lee wrote: On Sun, Mar 23, 2008 at 10:53:45AM +0100, Jens Fursund wrote: On Sun, 2008-03-23 at 02:55 +0300, Evgeny Ginzburg wrote: In current builds this bug exists, patch inserted in revision 4230, but i really don't know which revision OE use now how migrate to 4230. It's on buildhost already: http://buildhost.openmoko.org/daily/neo1973/deploy/glibc/images/neo1973/u-boot-gta01bv4-1.3.1+git0+b29661fc115106454288051bc9a488351ce8+svn4230-r3.bin the default env used by download.sh and flash.sh should be able to use the latest files automatically, so MokoMakefile will also work. I think you can use these images (u-boot, kernel, rootfs) first and update it by your ipkg/binary later to ease the trouble. Well svn up says revision 4241, and the bug is still there... :( No, it's not. Check console-ansi.patch http://svn.openmoko.org/trunk/src/target/u-boot/patches/console-ansi.patch svn update the openmoko directory under /moko is not equivalent to updating the package built from OE. maybe you can enable moko-autorev.inc or download from the uri above. Regards, John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
help:Neo1973 emulation using mokomakefile
Dear sir,
i am using ubuntu-7.10 in my PC.when i am trying to install using
mokomakefile i got this error,please help me.here i give what i
done,what error i got.
Step 1:
i installed all required packages to my machine
.including gcc-3.4
step 2:
$ sudo dpkg-reconfigure dash
choosed NO upon question about installing /bin/sh
step 3:
$mkdir openmoko
$cd openmoko
$wget http://www.rwhitby.net/files/openmoko/Makefile
$make qemu
=
when using this command it downloads all but finally
gives error message some thing like this
svn: REPORT request failed on '/!svn/vcc/default'
svn: REPORT of '/!svn/vcc/default': 200 OK
(http://svn.openmoko.org)
make: *** [stamps/openmoko] Error 1
when i run $make qemu i got the following error
[EMAIL PROTECTED]:~/openmoko$ make qemu
[ -e setup-env ] || \
echo 'export OMDIR='`pwd`'' setup-env
echo \
'export BBPATH=${OMDIR}/build:${OMDIR}/openembedded' \
setup-env
echo \
'export PYTHONPATH=${OMDIR}/bitbake/libbitbake' \
setup-env
echo \
'export PATH=${OMDIR}/bitbake/bin:${PATH}' \
setup-env
[ -e stamps/patches ] || \
( svn co
http://svn.projects.openmoko.org/svnroot/mokomakefile/trunk/patches
patches )
Apatches/bitbake-HEAD
Apatches/openmoko-HEAD
Apatches/openembedded-HEAD
Checked out revision 14.
[ -d stamps ] || mkdir stamps
touch stamps/patches
[ -e openmoko ] || ( mkdir openmoko )
[ -e stamps/openmoko ] || [ -e openmoko/trunk/.svn/entries ] || \
( cd openmoko svn co -r HEAD http://svn.openmoko.org/trunk )
Atrunk/doc
Atrunk/doc/hardware
Atrunk/doc/hardware/HXD8v011
Atrunk/doc/hardware/HXD8v011/gpio.txt
Atrunk/doc/hardware/HXD8v011/pmu-voltage.txt
Atrunk/doc/hardware/GTA02v1
Atrunk/doc/hardware/GTA02v1/gpio.txt
Atrunk/doc/hardware/GTA01v3
Atrunk/doc/hardware/GTA01v3/lcm-init-regs.txt
Atrunk/doc/hardware/GTA01v3/gpio.txt
Atrunk/doc/hardware/GTA01v3/pmu-voltage.txt
Atrunk/doc/hardware/GTA02v2
Atrunk/doc/hardware/GTA02v2/gpio.txt
Atrunk/doc/hardware/GTA01Bv2
Atrunk/doc/hardware/GTA01Bv2/gpio.txt
Atrunk/doc/hardware/GTA01Bv2/pmu-voltage.txt
Atrunk/doc/hardware/GTA01v4
Atrunk/doc/hardware/GTA01v4/gpio.txt
Atrunk/doc/hardware/GTA01v4/pmu-voltage.txt
Atrunk/doc/hardware/GTA02v3
Atrunk/doc/hardware/GTA02v3/gpio.txt
Atrunk/doc/hardware/GTA01Bv3
Atrunk/doc/hardware/GTA01Bv3/gpio.txt
Atrunk/doc/hardware/GTA01Bv3/pmu-voltage.txt
Atrunk/doc/hardware/GTA02v4
Atrunk/doc/hardware/GTA02v4/gpio.txt
Atrunk/doc/hardware/GTA01Bv4
Atrunk/doc/hardware/GTA01Bv4/gpio.txt
Atrunk/doc/hardware/GTA01Bv4/pmu-voltage.txt
Atrunk/doc/hardware/SMDK2440
Atrunk/doc/hardware/SMDK2440/gpio.txt
Atrunk/src
Atrunk/src/target
Atrunk/src/target/kernel
Atrunk/src/target/kernel/config
Atrunk/src/target/kernel/config/defconfig-2.6.22.5
Atrunk/src/target/kernel/patches
Atrunk/src/target/kernel/patches/s3c24xx-nand-largepage.patch
Atrunk/src/target/kernel/patches/s3c2410_fb-truecolor.patch
Atrunk/src/target/kernel/patches/s3c_mci_platform.patch
Atrunk/src/target/kernel/patches/asoc-kconfig-fix.patch
Atrunk/src/target/kernel/patches/s3cmci-unfinished-write-fix.patch
Atrunk/src/target/kernel/patches/s3cmci-stop-fix.patch
Atrunk/src/target/kernel/patches/gta01-inputdevice.patch
Atrunk/src/target/kernel/patches/lis302dl.patch
Atrunk/src/target/kernel/patches/s3c2410_fb-line_length.patch
Atrunk/src/target/kernel/patches/series
Atrunk/src/target/kernel/patches/s3c2410_udc_from_upstream.patch
Atrunk/src/target/kernel/patches/s3cmci_dbg.patch
Atrunk/src/target/kernel/patches/i2c-permit_invalid_addrs.patch
Atrunk/src/target/kernel/patches/ts0710.patch
Atrunk/src/target/kernel/patches/s3cmci-dma-free.patch
Atrunk/src/target/kernel/patches/smedia-glamo.patch
Atrunk/src/target/kernel/patches/hxd8-tsl256x.patch
Atrunk/src/target/kernel/patches/qt2410-s3c_mci-pdata.patch
Atrunk/src/target/kernel/patches/s3c2410-pwm.patch
Atrunk/src/target/kernel/patches/fix-hwecc-2410.patch
Atrunk/src/target/kernel/patches/gta01-vibrator.patch
Atrunk/src/target/kernel/patches/gta02-core.patch
Atrunk/src/target/kernel/patches/qt2410-base.patch
Atrunk/src/target/kernel/patches/s3c2410-bbt.patch
Atrunk/src/target/kernel/patches/gta01-jbt6k74.patch
Atrunk/src/target/kernel/patches/gta01-power_control.patch
A
trunk/src/target/kernel/patches/s3c2410_udc-2440_dual_packet-workaround.patch
Atrunk/src/target/kernel/patches/g_ether-highpower.patch
A
Re: community Digest, Vol 72, Issue 3
Subject: Re: Qemu on GTA02, the problem still here Thank you! I deleted my .bin and .jfs2 copied the build you linked to into the folder, ran download.sh and then flash.sh... and now it works... Hope this helps others to know what to do! Best Regards, Jens flash.sh also makes error openmoko/flash.sh: line 91: 13634 Aborted (core dumped) $qemu -mtdblock $script_dir/$flash_base -kernel $script_dir/$1 -serial stdio -nographic -usb -monitor null 00 U-boot failed to finish writing in 300 seconds, giving up. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Qemu on GTA02, the problem still here
Le 13961ième jour après Epoch, John Lee écrivait: On Sun, Mar 23, 2008 at 10:53:45AM +0100, Jens Fursund wrote: On Sun, 2008-03-23 at 02:55 +0300, Evgeny Ginzburg wrote: In current builds this bug exists, patch inserted in revision 4230, but i really don't know which revision OE use now how migrate to 4230. It's on buildhost already: http://buildhost.openmoko.org/daily/neo1973/deploy/glibc/images/neo1973/u-boot-gta01bv4-1.3.1+git0+b29661fc115106454288051bc9a488351ce8+svn4230-r3.bin the default env used by download.sh and flash.sh should be able to use the latest files automatically, so MokoMakefile will also work. But it doesn't :(... In fact, the most_recent function in download.sh use alpha sorting to determine the most recent images, so in the list: u-boot-gta01bv4-1.3.1+svnr4223+gitb29661fc115106454288051bc9a488351ce8-r3.bin u-boot-gta01bv4-1.3.1+git0+b29661fc115106454288051bc9a488351ce8+svn4230-r3.bin the first one is the winner :( Perhaps renaming the file on the server is a good bypass, then modifying the most_recent proc. Hope this help... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Qemu on GTA02, the problem still here
On Mon, Mar 24, 2008 at 02:12:00PM +0100, François TOURDE wrote: Le 13961ième jour après Epoch, John Lee écrivait: But it doesn't :(... In fact, the most_recent function in download.sh use alpha sorting to determine the most recent images, so in the list: u-boot-gta01bv4-1.3.1+svnr4223+gitb29661fc115106454288051bc9a488351ce8-r3.bin u-boot-gta01bv4-1.3.1+git0+b29661fc115106454288051bc9a488351ce8+svn4230-r3.bin the first one is the winner :( Perhaps renaming the file on the server is a good bypass, then modifying the most_recent proc. Hope this help... Seems I don't have enough files in my local deploy directory. :) Right now we have git hash in filename so the alpha sorting will not be correct, so the function needs to be updated anyway. Normally when I flash qemu I always modify openmoko/env to make sure it gets the file I wanted. Regards, John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
GSoC volunteer (as student)
Hi everyone! I have read all GSoC related topics at this mailing list and now I am wondering, what project idea I could take care of. I am also asking if someone is interested in mentoring me? Now something about me. I am from Wroclaw, POLAND, where studying computer engineering (very related to low level programming). I have 1 year left to Master of Science degree. I also have half-time job in programming GSM terminals, GSM modules (Telit [1], Wavecom [2]), telemetry devices, mobile devices. At job, my responsibility covers everything, starting with contacts with client, lots of research, planning steps, implementing, testing, documentation maintaining and client training (I am planning to give it up for a summer because of GSoC) . I am also experienced in working in multinational team (especially with Germans) and love programming Python! I use Linux for 4 years but I am not a kernel hacker. The technologies I feel most comfortable with are: GSM(in many attitudes), AT commands and Python programming (including lots of Django, GUI (QT), numeric, Python on telemetry devices, web crawlers, genetic algorithms...). If I had to choose something from the Ideas list [3] that would be (in decreasing order): * Support/documentation/tutorials/examples for building Applications in Python (so we could build apps as easily as on Symbian Python) * Ambient Noise Detection * Framework for Accelerometer Gestures (not a kernel driver) * Implementing a subset of http://wiki.openmoko.org/wiki/Wish_List#Text_Messaging If you think that there might be some interesting projects that a person with my knowledge and experience could achieve, please let me know ASAP so we could to put them under discussion. [1] http://www.telit.com/en/products/gsm-gprs.php [2] http://www.wavecom.com/modules/movie/scenes/products/index.php?fuseAction=articlerubric=productsarticle=products_quikSeries [3] http://wiki.openmoko.org/wiki/Summer_of_Code_2008 -- -- Patryk Szymczak ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
GSoC 2008
Hi, I'm a student in the french engineer school ENSIMAG, and I would like to work for OpenMoko during the Google Summer of Code. I'm interested in the accelerometers features [1]: Recognising gestures is a really important part of the interface between the user and the phone. With the two accelerometers in the FreeRunner, I think we can recognise lots of gestures, not only simple ones like a click (which is already recognised by the accelerometers used in the FreeRunner). The main difficulty is probably to extract the useful data from the gestures noise : calibration may take time. The goal is to have an almost pre-calibrated library (an idea from the wish-list in the Wiki is to allow the user to record its own gestures, but I think it's not easy to do it simple for the end-user). The accelerometers could provide not only small gestures recognition (like the ones listed on the Wiki: up-side-down, shaking, flipping, ...), but full 3D-space positioning from a start position (when the software is started). Then we can imagine lots of uses of the library : improvements in the control of the phone, programs specially created to use such control(little games for examples). The accelerometers gestures could be combined with the touchscreen for a better use. For example, the gesture navigation can be activated only when pressing the screen: if we are viewing a large picture, zoomed in, we could move through it by moving the phone, but we don't want it moves all the time. Other examples given on the Wiki [2] could be implemented by using the library. I looked at the driver for the accelerometers, and it seems it's not yet working. I don't think I'm able to work on the driver, so I hope it will work this summer. I'm also interested in working in the ambient noise detection in second choice. - [1] http://wiki.openmoko.org/wiki/Summer_of_Code_2008#Accelerometer_Gestures [2] http://wiki.openmoko.org/wiki/Wish_List#Accelerometer_wishes - I hope I'll be part of the OpenMoko project this summer, Thomas Riccardi ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Qemu on GTA02, the problem still here
Le 13962ième jour après Epoch, John Lee écrivait: Right now we have git hash in filename so the alpha sorting will not be correct, so the function needs to be updated anyway. The svn version is in the filename too, so it will be probably the good way to get the last version. Normally when I flash qemu I always modify openmoko/env to make sure it gets the file I wanted. I prefer using mokomakefile, to focus on writing C++ code instead of playing with the build chain, but you're right, modifying openmoko/env file was the solution for me... execpt on 'make qemu-local' :( Next step will be trying to run Xephyr version ... And I imagine it will be the same hard job :p Thanks anyway for your time and your help. And again, good job guys, for what you're doing on the free side of the world ! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: Price of the Freerunner spare parts
I thought about spare parts a while back. The Issue is this. 1. WHAT do I stock ( which parts) 2. How Many do I stock? 3. How do I sell them to you? 4. What will it cost? 5. how do you get them? I suppose I could Offer component kits for sale. That would be the quickest thing for me to do. Sell the whole bag of parts; fix it your self. or build a business around this service. Let me think about it. Throw rotten fruit at this idea if you like. Steve -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of joerg Sent: Sunday, March 23, 2008 8:44 AM To: [EMAIL PROTECTED]; List for Openmoko community discussion Subject: Price of the Freerunner spare parts Am So 23. März 2008 schrieb Sean Moss-Pultz: We will have our own hub in the EU. Neos will move directly from our factory to that hub. What's about availability and pricing of spare parts like LCM, battery, housing? Will there be any repair service? cheers jOERG ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Production status Update
Hi, I have some updates on production for everybody. To recap what I explained we have two Milestones to pass before flipping the Mass production switch. DVT and PVT. DVT. The phones from Design Verification Test have been characterized and have been passed back to engineering. So, we are proceeding with a series of PVT builds to test the production worthiness of the design. As those PVT runs get going, I'll update everyone on the results. Steve ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Price of the Freerunner spare parts
I think spare parts are things that should be available via the distributors. 1. What: there are some parts everybody needs to replace or restock at some point: battery (very important), stylus (not really important), front/back-cover (moderately important), headsets, pouches, cables/chargers (reasonably important) 2. How many: see importance (1.) for relative numbers 3. Bigger stocks for distributors, no direct selling in small numbers 4. Make it cheap :P 5. Same as (3.) I guess there are many people who need at least spare batteries and some who'd like to have extra pouches (me! :), so this are things that should be offered to the customers. The effort and prices can be reasonable by only selling larger numbers. Additional spare parts like displays, antennas and so on could be available in smaller number at the local hubs, so resellers can get it for their customers if really needed. On Tue, Mar 25, 2008 at 12:00 AM, steve [EMAIL PROTECTED] wrote: I thought about spare parts a while back. The Issue is this. 1. WHAT do I stock ( which parts) 2. How Many do I stock? 3. How do I sell them to you? 4. What will it cost? 5. how do you get them? I suppose I could Offer component kits for sale. That would be the quickest thing for me to do. Sell the whole bag of parts; fix it your self. or build a business around this service. Let me think about it. Throw rotten fruit at this idea if you like. Steve -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of joerg Sent: Sunday, March 23, 2008 8:44 AM To: [EMAIL PROTECTED]; List for Openmoko community discussion Subject: Price of the Freerunner spare parts Am So 23. März 2008 schrieb Sean Moss-Pultz: We will have our own hub in the EU. Neos will move directly from our factory to that hub. What's about availability and pricing of spare parts like LCM, battery, housing? Will there be any repair service? cheers jOERG ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Price of the Freerunner spare parts
Am Di 25. März 2008 schrieb steve: I thought about spare parts a while back. The Issue is this. 1. WHAT do I stock ( which parts) Obviously, NOT: Standard parts which are easily available elsewhere Parts which can't be replaced (chips) Parts too expensive in relation to cost of complete unit (mainboard) So it boils down to o- one set of complete housing plastics (maybe split if a special part breaks significantly more often than the others) o- LCM + associated parts o- battery o- accessories (charger/USB-host-power-adapter, headset, ...?) o- debug board / kit these should be available in reasonable quantity and pricing at your local (national) reseller o- other special parts (e.g. mini-usb to replace the one on mainboard, GSM/GPS antenna, screws / springs, flat cable etc) probably might be shipped once a month from Suzhou, prepaid - assuming this won't exceed 1 event/month per 5.000 units sold, for a figure of magnitude. More frequently needed parts shall migrate to reseller path. 2. How Many do I stock? ??? difficult question. Probably start of regular distribution GTA02 will yield some data after a couple of months. At this point in time there still should be sufficient production stock. 3. How do I sell them to you? The standard spare parts via resellers. Rarely needed parts via Suzhou, order by prepay. 4. What will it cost? Hmm, probably for Suzhou parts the costs of handling will exceed the price of the mere part. OTOH supplying spare parts is a service for customers to polish OM image, not a business. Many customers don't buy a device that's not backed by reasonable service and/or spare parts. 5. how do you get them? Wiki page with part descriptions and part numbers / price. Prepay by money order with part number + address. Surface delivery. cheers jOERG ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: Price of the Freerunner spare parts
On Mon, 2008-03-24 at 16:00 -0700, steve wrote: I thought about spare parts a while back. The Issue is this. 1. WHAT do I stock ( which parts) batteries 2. How Many do I stock? thousands ;-) 3. How do I sell them to you? via the resellers 4. What will it cost? free as in beer :°) 5. how do you get them? by postal service :) I suppose I could Offer component kits for sale. That would be the quickest thing for me to do. Sell the whole bag of parts; fix it your self. or build a business around this service. Let me think about it. Throw rotten fruit at this idea if you like. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
