Re: [oe] [PATCH 01/12] fso-image.inc: add an even shorter alias, for ls -l
Op 7 jun 2010, om 09:50 heeft Martin Jansa het volgende geschreven: > On Mon, Jun 07, 2010 at 09:24:54AM +0200, Antonio Ospite wrote: >> On Mon, 31 May 2010 13:19:30 +0200 >> Koen Kooi wrote: >> >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA1 >>> >>> On 31-05-10 11:55, Antonio Ospite wrote: >>>> 'l' is a must have along with 'll'. >>>> >>>> Signed-off-by: Antonio Ospite >> [...] >>> diff --git a/recipes/images/fso-image.inc b/recipes/images/fso-image.inc >> [...] >>>> +echo "alias l='ls -l'" >>./etc/profile >>>> echo "alias ll='ls -al'" >>./etc/profile >>>> # nfs >>>> mkdir -p ./local/pkg >>> >>> And what happens if you opkg upgrade base-files? You suddenly lost all >>> your tweaks to /etc/profile. >> >> Right, /etc/profile would be overwritten, but that's quite independent >> from this very patch, it's the whole fso-image.inc approach which >> should be revised, so I'd like this one could still make it. >> >> Or if you can point to the right way to do what >> recipes/images/fso-image.inc::fso_rootfs_postprocess() is doing I can >> try to implement that. > FYI: I removed similar postprocess tweaks from shr images about a month > ago, because of those reasons... I removed them when I started developing narcissus (late 2008), since I couldn't reproduce OE images from their packages... regards, Koen
Re: [PATCH 07/12 v2] motorola-ezx-base.inc: refresh machine definition
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 31-05-10 16:28, Antonio Ospite wrote: > Reorder sections to a more logic scheme, following magician.conf, other > cleanups: > > * sort MACHINE_FEATURES alphabetically > * add ezx-gen-blob to EXTRA_IMAGEDEPENDS > * use MODUTILS=26 > * Add needed kernel modules for BP > > Signed-off-by: Antonio Ospite Acked-by: Koen Kooi > --- > > Changes since v1: > > Drop the IMAGE_DEV_MANAGER = "" bit, as Koen remarked this belongs to > image not machine. > > Regards, >Antonio > > conf/machine/include/motorola-ezx-base.inc | 43 +-- > 1 files changed, 27 insertions(+), 16 deletions(-) > > diff --git a/conf/machine/include/motorola-ezx-base.inc > b/conf/machine/include/motorola-ezx-base.inc > index 9ad2f14..3fb42f4 100644 > --- a/conf/machine/include/motorola-ezx-base.inc > +++ b/conf/machine/include/motorola-ezx-base.inc > @@ -1,7 +1,16 @@ > +# use this for overrides > +MACHINE_CLASS = "motorola-ezx" > + > +# > +# Hardware-based properties > +# > TARGET_ARCH = "arm" > > -PREFERRED_PROVIDER_virtual/xserver = "xserver-kdrive" > -PREFERRED_PROVIDER_virtual/kernel ?= "openezx-kernel" > +# Use tune-xscale per default. Machine independent feeds should be built > with tune-strongarm. > +require conf/machine/include/tune-xscale.inc > + > +# Uncomment this to use iwmmxt optimizations. Remove the above xscale stuff > first > +#require conf/machine/include/tune-iwmmxt.inc > > #cat /proc/mtd > #dev:size erasesize name > @@ -10,34 +19,36 @@ PREFERRED_PROVIDER_virtual/kernel ?= "openezx-kernel" > #mtd2: 0058 0002 "VFM_Filesystem" > #mtd3: 0002 0002 "Logo" > > -MACHINE_FEATURES = "kernel26 touchscreen apm alsa bluetooth usbgadget > usbhost keyboard screen phone" > -MACHINE_FEATURES += " iwmmxt" > - > +ROOT_FLASH_SIZE = "24" > +MACHINE_GUI_CLASS = "smallscreen" > MACHINE_DISPLAY_WIDTH_PIXELS = "240" > MACHINE_DISPLAY_HEIGHT_PIXELS = "320" > MACHINE_DISPLAY_ORIENTATION = "0" > MACHINE_DISPLAY_PPI = "180" > +MACHINE_FEATURES = "alsa apm bluetooth kernel26 keyboard phone screen > touchscreen usbgadget usbhost vfat" > +MACHINE_FEATURES += " iwmmxt" > > -# use this for overrides > -MACHINE_CLASS = "motorola-ezx" > - > +# > +# Software/packages selection > +# > +PREFERRED_PROVIDER_virtual/kernel ?= "openezx-kernel" > +MODUTILS = "26" > XSERVER = "xserver-kdrive-fbdev" > - > -ROOT_FLASH_SIZE = "24" > +PREFERRED_PROVIDER_virtual/xserver = "xserver-kdrive" > > IMAGE_FSTYPES ?= "jffs2" > EXTRA_IMAGECMD_jffs2 = "--pad=14680064 --little-endian --eraseblock=0x2 > -n" > > -EXTRA_IMAGEDEPENDS += "ezx-boot-usb-native" > +EXTRA_IMAGEDEPENDS += "ezx-boot-usb-native ezx-gen-blob" > > -# the EZX phones need a userspace daemon to stop the BP from shutting down > the phone > -MACHINE_ESSENTIAL_EXTRA_RDEPENDS += "ezxd" > +IMAGE_INSTALL_append += "\ > + kernel-module-ohci-hcd \ > + kernel-module-moto-usb-ipc \ > + kernel-module-ts27010mux \ > +" > > # Ezxd needs to be started very early so we need the mux devices in static > /dev > IMAGE_DEVICE_TABLES = "files/device_table-minimal.txt \ > files/device_table-ezx.txt" > > -# Use tune-xscale per default. Machine independent feeds should be built > with tune-strongarm. > -require conf/machine/include/tune-xscale.inc > - > SERIAL_CONSOLE = "115200 ttyS0" -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFMA+ShMkyGM64RGpERAqwmAJ0VVAVvp2Hl/iQRTXaHz9jBnsLZTwCglWF3 nIrYQcobWkB002urMk8kN58= =69z5 -END PGP SIGNATURE-
Re: [PATCH 01/12] fso-image.inc: add an even shorter alias, for ls -l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31-05-10 11:55, Antonio Ospite wrote:
> 'l' is a must have along with 'll'.
>
> Signed-off-by: Antonio Ospite
> ---
> recipes/images/fso-image.inc |1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/recipes/images/fso-image.inc b/recipes/images/fso-image.inc
> index cc626f3..704d267 100644
> --- a/recipes/images/fso-image.inc
> +++ b/recipes/images/fso-image.inc
> @@ -110,6 +110,7 @@ fso_rootfs_postprocess() {
> echo "alias fso='cd /local/pkg/fso'" >>./etc/profile
> echo "alias ipkg='opkg'" >>./etc/profile
> echo "alias vim=vi" >>./etc/profile
> +echo "alias l='ls -l'" >>./etc/profile
> echo "alias ll='ls -al'" >>./etc/profile
> # nfs
> mkdir -p ./local/pkg
And what happens if you opkg upgrade base-files? You suddenly lost all
your tweaks to /etc/profile.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMA5tCMkyGM64RGpERAvTLAKCoiQEUoCu0JGj/uOrp7iyRxAMj6ACglhn0
PHnpQdgGf53SuA5JG1DDIiw=
=ZVr0
-END PGP SIGNATURE-
Re: Merge plan for the .29 window
Op 19 nov 2008, om 00:14 heeft Stefan Schmidt het volgende geschreven: Hello. On Sun, 2008-11-16 at 00:59, Stefan Schmidt wrote: In preparation for a patchset for the next merge window I would like to get some feedback. Daniel and others, looking at our tree I think the following could be prepared and sumbmitted for review and inclusion: Thanks to the feedback the updated version looks like this: ezx/removefixup.diff -p1 ezx/mach/gpio.diff -p1 ezx/mach/keypad.diff -p1 ezx/mach/i2c.diff -p1 ezx/pcap.diff -p1 ezx/pcap_rtc ezx/mach/pcap.diff -p1 ezx/mach/mci.diff -p1 ezx/pcap_ts.diff -p1 ezx/mach/pcap_ts.diff -p1 ezx/pcap_leds.diff -p1 ezx/mach/pcap_leds.diff -p1 ezx/mach/pcap_rtc ezx/defconfig.diff -p1 If anything is missing or should not be there, let me now. A list with todo we need to address before sending it out on friday: - Lindent run (I think Wyrm did this already) Checkpatch.pl and sparse are also nice to run, although they can give false positives. regards, Koen PGP.sig Description: This is a digitally signed message part
mtn2git mirror down again
Hi, Is the mtn2git mirror down again and has it been moved to amythyst yet? regards, Koen PGP.sig Description: This is a digitally signed message part
Re: Time for git.openezx.org?
Op 15 jul 2008, om 08:57 heeft Stefan Schmidt het volgende geschreven: Hello. On Mon, 2008-07-14 at 18:25, Antonio Ospite wrote: as stated several times on the list[1,2] Harald had always had in mind to setup a git server for OpenEZX, and in fact the web server at git.openezx.org worked since the start of the project. What about the actual git server? It is now time to push for it ;) Would be good, indeed. Now that we are in the process of preparing our patches for mainline submission, using git could save us some time and headaches. Well, I'm thinking about this for three weeks now. It can also mean to switch from one headache to another. ;) But let me explain a bit more. Our tools should help us to produce patches for the upstream kernel. It should allow us to work on such a patch for a longer time. There are often many commits before we feel a patch is ready for review or submission. In quilt we handle this with a patchstack we go up and down. Making changes at the right place of the stack, refresh and test it out. This way we always have a nice stack of separated patches we just need to prepare with headers and can send away. But there are also some con of quilt. We have to use svn as quilt has now version control. The problem is here that we already have diffs and don't let svn make the diffs between code, but patches. Looking at the commit mails which show me diffs of diffs makes them pretty hard to review for example. Also using git + svn + quilt gives me often a headache. Doing something like this for an update is somewhat strange :) quilt pop -a && cd patches/ && svn up && cd .. && git pull && quilt push -a Also I'm sometimes being at the wrong 'height' of the stack while doing a change, which let the hunk appear in the wrong patch. Yes, that's problem form my side, but annoying anyway. So how we can use git for us? To have different commits appear in one, needed if we want to send it upstream as one patch, I see three different features which git offer us: git commit --amend This allows you to easy make changes to the last commit. git add --interactive Allows you to 'merge' some of your uncommited hunks into older commits git rebase --interactive Allows you to change the history, squash commits together and more. To see if these features help us, we need to test them. So once the server is running I would like to have a two weeks period to let people try out the new workflow. The other bonus we get with git is working with the upstream SCM. Means easier updates, eassier (speak not manual) rebase against upstream changes and perhaps later even the option to let upstream pull a branch from us. Keep in mind that RMKs git tree is not intended to be worked against, since RMK is prone to rebasing (it's a reflection of his patchsystem) which makes using it as a branch painfull. Working of linus' git tree will be easier, but has the disadvantage of not having all the latest ARM goodies. regards, Koen Ah, one word about stgit which often is named when coming from quilt to git. As long as it does not allow to share the meta information, patchstack to git commits mapping, between developers it seems not a good choice for us. We need a tool were more then one dev has the same set of information. Harald, can you please tell us if you can find some time to bring it up? Thanks in advance. I cc'ed him as I think he doesn't read this list every day. Harald, do you have time to setup a git server for OpenEZX? We are using Stefan Schmidt's server to host 2.4 kernels released by Motorola, we could also move them to git.openezx.org once it is ready. That's the plan. :) That was long. Sorry. I just had thought about this for some time and liked to share my thoughts. In short: Let's try it, but be carefull if it really helps us. :) regards Stefan Schmidt PGP.sig Description: This is a digitally signed message part
Re: [patch 0/3] Status for the first mainline merge batch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Op 11 jun 2008, om 21:38 heeft Szefan Schmidt het volgende geschreven: Now to the remaining four items on my todo list: 4. What is CKEN = ... in ezx_init about? Didn't RMK just remove CKEN from the kernel? regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFIUEJQMkyGM64RGpERAgEjAJ48L68rHYOzPrrFef94s7P2sc84KACfR0Xk Pl3iSOFh4ysQKAplcCm5ilo= =Rpl1 -END PGP SIGNATURE-
Re: Mux testing report
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Op 8 jun 2008, om 15:20 heeft Stefan Schmidt het volgende geschreven: But now some words about using the AT command set. Of the most interesing question for Mickey was on what channel we could send what kind of AT commands. From the small tests I was able to do it looks like we can send out AT commands on every channel but only get USC(?), like RING and CLIP, on mux0. At least I was able tosend AT+CFUN and ATD on the channels I tested. That is correct, command sent into any mux get passed on to the modem, responses come out through seperate muxes. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFIS+IFMkyGM64RGpERAlT4AJ4/LIaJ5xMH1t3PxH958WWVkN+7CQCfdzzD DKjF0atN8HyBqSec8UyvlJk= =bl0e -END PGP SIGNATURE-
Re: Coordination of the linux-2.6-arm branch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Op 6 jun 2008, om 10:44 heeft Stefan Schmidt het volgende geschreven: Hello. As you guys may have seen I have started a branch to work with a very small part of our patchset directly on Russel Kings git tree, linux-2.6-arm. The goal is to get some basic functionality in a state we can send it out for review and inclusion. We have spend far to much time yet without doing this. One of the problems is that we have tons of patches that are just not ready. So I try to improve the quality of same basic patches and have them submitted before working more on the other patches. Is there a plan on what to submit first? Something like: * submit e680, a780 and a1200 board files as seperate patches * submit pcap * submit eoc * etc.. Maybe we should pick _one_ phone as the test target and try get support for that upstream and base support for other phones on that later. regards, Koen Today morning I liked to continue the work I have stopped yesterday. But after an update I had to spent more then an hour to fiddle out that wyrm has started to help working on this. While I appreciate this, I think some more coordination is needed. First of all ezx-machids.patch is not commited which lets to a missing machine_is_ezx_e680(), etc. The other problem with machids is that they are generated from Russel and we are not able to send patcheѕ for changes. To get our machid problems sorted out we have to mail Russel and get the machine registry updated. This dependency blocks the whole submit for review process. So, if we like to have machid sorted out before, we need to do it now. Wyrm, how would you like to work on this? regards Stefan Schmidt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFISQCFMkyGM64RGpERAo8eAJ9KGSQYwj1QKuvRkTEA+XvIlQsIEQCfePdI 2ZcS2SpGiBeAfDS8m6m4m+M= =0ynK -END PGP SIGNATURE-
Re: blob2 status on A1200 (etc.)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Op 4 jun 2008, om 13:39 heeft Michael 'Mickey' Lauer het volgende geschreven: Hi Ho, thanks to rapid progress on the Openmoko Framework initiative (see wiki page and my blog posts), within the next couple of months, we will have a userland that looks nice and works as a phone and sms application on EZX phones. The time has come for me to do work on the integration of the EZX specifics into ophoned (the open phone server), since the way EZX multiplexes the GSM is quite different from the way the TI Calypso (found in the Openmoko Neos) work. Therefore, I need a device where I can talk to the BP. I want to use my A1200 for these experiments. What's the status of blob2 on this device? And related to that: what's the status of blob2 on a780 phones? I'm eager to try 2.6.25, but it seems that won't work due to machine id changes. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFIRoj/MkyGM64RGpERAgkvAJ9IowkS+0I0c9Cffe0tktanGZlq5wCgtg7c NIkuTGniQ/1uWJE0XLhd0tQ= =n6ux -END PGP SIGNATURE-
Re: Driver for A910 FunLight chip.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Op 14 apr 2008, om 18:13 heeft Antonio Ospite het volgende geschreven:
I attach the code here before committing, this is the first driver I
write from scratch, so please _be_rude_ on the first attached patch
and
make all the comments you can think of.
This is what checkpatch.pl has to say:
[EMAIL PROTECTED]:/usr/src/linux-2.6.24$ scripts/checkpatch.pl /tmp/fun/
lp3944.patch
total: 0 errors, 0 warnings, 405 lines checked
/tmp/fun/lp3944.patch has no obvious style problems and is ready for
submission.
[EMAIL PROTECTED]:/usr/src/linux-2.6.24$ scripts/checkpatch.pl /tmp/fun/a910-
funlight-i2c-boardinfo.patch
ERROR: Missing Signed-off-by: line(s)
total: 1 errors, 0 warnings, 10 lines checked
/tmp/fun/a910-funlight-i2c-boardinfo.patch has style problems, please
review. If any of these errors
are false positives report them to the maintainer, see
CHECKPATCH in MAINTAINERS.
[EMAIL PROTECTED]:/usr/src/linux-2.6.24$ scripts/checkpatch.pl /tmp/fun/a910-
funlight.patch
WARNING: externs should be avoided in .c files
#9: FILE: drivers/leds/leds-a910.c:21:
+extern int lp3944_dim_set(int dim, int period, int duty_cycle);
WARNING: externs should be avoided in .c files
#10: FILE: drivers/leds/leds-a910.c:22:
+extern int lp3944_led_set(int led, int status);
ERROR: no space after that open parenthesis '('
#22: FILE: drivers/leds/leds-a910.c:46:
+ value = ( value != 0 );
ERROR: no space before that close parenthesis ')'
#22: FILE: drivers/leds/leds-a910.c:46:
+ value = ( value != 0 );
ERROR: no space after that open parenthesis '('
#23: FILE: drivers/leds/leds-a910.c:47:
+ printk( KERN_DEBUG "a910led_flash_set: %d\n", value );
ERROR: no space before that close parenthesis ')'
#23: FILE: drivers/leds/leds-a910.c:47:
+ printk( KERN_DEBUG "a910led_flash_set: %d\n", value );
ERROR: no space after that open parenthesis '('
#31: FILE: drivers/leds/leds-a910.c:55:
+ value = ( value != 0 );
ERROR: no space before that close parenthesis ')'
#31: FILE: drivers/leds/leds-a910.c:55:
+ value = ( value != 0 );
ERROR: no space after that open parenthesis '('
#32: FILE: drivers/leds/leds-a910.c:56:
+ printk( KERN_DEBUG "a910led_red_set: %d\n", value );
ERROR: no space before that close parenthesis ')'
#32: FILE: drivers/leds/leds-a910.c:56:
+ printk( KERN_DEBUG "a910led_red_set: %d\n", value );
ERROR: no space after that open parenthesis '('
#39: FILE: drivers/leds/leds-a910.c:63:
+ value = ( value != 0 );
ERROR: no space before that close parenthesis ')'
#39: FILE: drivers/leds/leds-a910.c:63:
+ value = ( value != 0 );
ERROR: no space after that open parenthesis '('
#40: FILE: drivers/leds/leds-a910.c:64:
+ printk( KERN_DEBUG "a910led_green_set: %d\n", value );
ERROR: no space before that close parenthesis ')'
#40: FILE: drivers/leds/leds-a910.c:64:
+ printk( KERN_DEBUG "a910led_green_set: %d\n", value );
ERROR: no space after that open parenthesis '('
#47: FILE: drivers/leds/leds-a910.c:71:
+ value = ( value != 0 );
ERROR: no space before that close parenthesis ')'
#47: FILE: drivers/leds/leds-a910.c:71:
+ value = ( value != 0 );
ERROR: no space after that open parenthesis '('
#48: FILE: drivers/leds/leds-a910.c:72:
+ printk( KERN_DEBUG "a910led_blue_set: %d\n", value );
ERROR: no space before that close parenthesis ')'
#48: FILE: drivers/leds/leds-a910.c:72:
+ printk( KERN_DEBUG "a910led_blue_set: %d\n", value );
ERROR: no space after that open parenthesis '('
#181: FILE: drivers/leds/leds-a910.c:228:
+ a910vibrator_set( &a910_flash, 0 );
ERROR: no space before that close parenthesis ')'
#181: FILE: drivers/leds/leds-a910.c:228:
+ a910vibrator_set( &a910_flash, 0 );
ERROR: no space after that open parenthesis '('
#182: FILE: drivers/leds/leds-a910.c:229:
+ a910vibrator_set( &a910_red_led, 0 );
ERROR: no space before that close parenthesis ')'
#182: FILE: drivers/leds/leds-a910.c:229:
+ a910vibrator_set( &a910_red_led, 0 );
ERROR: no space after that open parenthesis '('
#183: FILE: drivers/leds/leds-a910.c:230:
+ a910vibrator_set( &a910_green_led, 0 );
ERROR: no space before that close parenthesis ')'
#183: FILE: drivers/leds/leds-a910.c:230:
+ a910vibrator_set( &a910_green_led, 0 );
ERROR: no space after that open parenthesis '('
#184: FILE: drivers/leds/leds-a910.c:231:
+ a910vibrator_set( &a910_blue_led, 0 );
ERROR: no space before that close parenthesis ')'
#184: FILE: drivers/leds/leds-a910.c:231:
+ a910vibrator_set( &a910_blue_led, 0 );
ERROR: Missing Signed-off-by: line(s)
total: 25 errors, 2 warnings, 176 lines checked
/tmp/fun/a910-funlight.patch has style problems, please review. If
any of these errors
are false positives report them to the maintainer, see
CHECKPATCH in MAINTAINERS.
[EMAIL PROTECTED]:/usr/src/linux-2.6.24$
regards,
Koen
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.
Re: [RFC] Prebuild OE toolchains for kernel hacking without an OW setup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Ribeiro schreef: | Paul Sokolovsky wrote: |> Angstrom was made to rectify that situation. So, once you're |> interested, and ready, it is there. |> And feel free to consider this as the downstream distro coming to you, |> begging for collaboration ;-). | Is Angstrom really calling us to maintain the EZX devices? | Why dont you guys start with a more gentle approach? I'm already doing | some "distro integrator" work for OpenEZX on svn.openezx, why dont | Angstrom just uses the defconfigs and patches from svn.openezx? It already does that, if you had bothered to check | Just to point some benefits: | 1. Immediate support to Angstrom users from the OpenEZX kernel hackers. | 2. Kernel builds which are actively tested on all OpenEZX supported | devices (not only a780). | 3. Avoid duplicate work in both directions. | | You (and other OErs) can review our builds/defconfigs/patches and make | suggestions here, im sure most of your requests would be accepted. | I cannot guarantee that I will have enough time to play with | OE/Angstrom but if OE built kernels behave at least similar to the | kernels that i build, i will recommend OE and stop asking users to build | kernels outside of OE. | Its that simple! Isnt it great? | - -- [EMAIL PROTECTED] will go go away in december 2007, please use [EMAIL PROTECTED] instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHuXlOMkyGM64RGpERAktyAJ996k09ZqbnnQjfjxDN6VqbFBFISgCdGKWR p1jMcdWQWR+wBVJInhcfUfU= =8ZJf -END PGP SIGNATURE-
Re: branches/kernel-2.6.24.x-patches to come
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Antonio Ospite schreef: | On Mon, 28 Jan 2008 12:31:29 +0100 | Koen Kooi <[EMAIL PROTECTED]> wrote: | |> -BEGIN PGP SIGNED MESSAGE- |> Hash: SHA1 |> |> Antonio Ospite schreef: |> | Hi, |> | |> | linux-2.6.24 was released yesterday, and I'm going to port the |> | current patches to it during the weekend. |> |> I just added recipe for linux-ezx 2.6.24 to org.openembedded.dev, |> people can try: |> |> http://www.angstrom-distribution.org/unstable/autobuild/a780/zImage-2.6.24-ezxdev-r0-a780.bin |> http://www.angstrom-distribution.org/unstable/autobuild/a780/modules-2.6.24-ezxdev-r0-a780.tgz |> |> on their a780. It should boot from mmcblk0p2. |> | | Thanks very much Koen. | Please can you test and check the recent autobuilt openmoko images? | I had a problem logging in with ssh. I solved it using an older image. I still have the 2007.12 release openmoko-image on my a780, but haven't tried the .24 with that yet. regards, Koen - -- [EMAIL PROTECTED] will go go away in december 2007, please use [EMAIL PROTECTED] instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHn3IDMkyGM64RGpERAv1vAKCqU1FNwU9/OKt0DVIMTxaOLgp14ACfec62 nyzRa8okrFAcN8GsV5n2aHM= =SbKk -END PGP SIGNATURE-
Re: branches/kernel-2.6.24.x-patches to come
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Antonio Ospite schreef: | On Fri, 25 Jan 2008 12:56:15 +0100 | Antonio Ospite <[EMAIL PROTECTED]> wrote: | |> Hi, |> |> linux-2.6.24 was released yesterday, and I'm going to port the current |> patches to it during the weekend. |> So, if you have any changes you could choose to commit them, so to |> save some effort of merging them back later. Or, I can hold the |> porting work if you have any reason for delaying it. |> | | Ok, done in r2093. | The code compiles fine for all the phones, but it has been tested only | on a780. | |> In 2.6.24 there are some changes in pxafb about 18bpp interface, and |> SDIO support was added, so we can even try to play with SDIO wlan |> cards (A910 has one builtin). |> | | Other things I noted in linux-2.6.24 that could be useful: | | Generic (aka Sharp Corgi) Backlight Driver | CONFIG_BACKLIGHT_CORGI | | Can we replace drivers/video/backlight/ezx_bl.c with | drivers/video/backlight/corgi_bl.c ? | | CONFIG_MTD_PXA2XX | CFI Flash device mapped on Intel XScale PXA2xx based boards | | Can we replace our drivers/mtd/maps/ezx-flash.c with | drivers/mtd/maps/pxa2xx-flash.c ? | | Since some time there is also a pxa-keyboard driver in mainline, | but we haven't tested it yet. Don't forget to add http://thread.gmane.org/gmane.comp.video.video4linux/36469 if they apply cleanly. regards, Koen - -- [EMAIL PROTECTED] will go go away in december 2007, please use [EMAIL PROTECTED] instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHnMirMkyGM64RGpERAi2oAJ9N6ETYKoLARX3U2CXcUofoel850gCgvCzA DEUqiKvNGfkguQrXuqpELvE= =rgng -END PGP SIGNATURE-
Re: branches/kernel-2.6.24.x-patches to come
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Antonio Ospite schreef: | On Fri, 25 Jan 2008 13:11:31 +0100 | Stefan Schmidt <[EMAIL PROTECTED]> wrote: | |> There is also a pending patch about pxafb 18bpp on linux-arm-kernel. I |> haven't looked at it yet, so I don't know what is still missing for |> our use case. |> |> http://www.spinics.net/lists/arm-kernel/msg46235.html |> | | Well, the pxa27x_overlay patch we use also adds support for >= 18bpp | formats, so maybe we already have all the pieces, I'm testing right | now. Also take note of the pxa270 camera interface patches going around LAK and the linux video lists this week. regards, Koen - -- [EMAIL PROTECTED] will go go away in december 2007, please use [EMAIL PROTECTED] instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHme9uMkyGM64RGpERAl45AJ91Xi3mfQJJGW22Ufy4kC/OGN2R3gCgkojg hUg0NLV+Jfy5iUWgb5OdfXU= =XdMN -END PGP SIGNATURE-
Re: EZX machine types (was Re: What is needed for getting ezx-core.patch ready for upstream submission?)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Harald Welte schreef: >> o When submitting this patches as RFC to the arm kernel ml we should >> also ask about how we should handle the different phones with regards >> to the machine registry. I would prefer to discuss this with some >> code in the back instead of a theoretical discussion. > > I have had a quick look at the patch and it seems like they all share > one machine type? This is bad. > > As far as I know, the motorola bootloader doesn't set the machine type > in the register (r7?) correctly before jumping into the kernel. > > I personally believe that every hardware model should have its own > machine type, and the kernel should just do 'as usual'. > > At some point we might have our own bootloader on the devices, at which > we can do this 'correctly', i.e. specify the machine type from the > bootloader. > > Until we get there, I propose either: > > 1) some kind of object code snippet that we can put between bootloader >and kernel (sounds ugly) See 'arm-kernel-shim' by Marc Singer in OE regards, Koen > 2) some ugly local (non-mainline) patch that modifies head.S (like now), >but with the difference that it is somehow user-configurable which >machine type should be hard-coded into head.S > > Comments? - -- [EMAIL PROTECTED] will go go away in december 2007, please use [EMAIL PROTECTED] instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHaidmMkyGM64RGpERAmd0AJ9Ttkb5651STGy1G6mhYIRRYDrUSgCfSXiP TNWDVur6I4vkHCzSXLGvY18= =UH2h -END PGP SIGNATURE-
Re: no progress after mounting mmcblk0p2 with zImage-a780-intoxicated
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 jtd schreef: > the > config file for zImage-2.6.23-ezxdev-r2-a780-20071101192618.bin. > diffing the two might give me a clue. zcat /proc/config.gz - -- [EMAIL PROTECTED] will go go away in december 2007, please use [EMAIL PROTECTED] instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHPrWuMkyGM64RGpERAnpmAKCcBUjWgioWIEdU7BhJGiT7WCZU6ACgtplk cRrLplvUOtKTCYi3bzIifa0= =sJuF -END PGP SIGNATURE-
Re: no progress after mounting mmcblk0p2 with zImage-a780-intoxicated
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 jtd schreef: > Hi all, > my first post to the list. > I am trying to boot an a780. > i have used the zImage-a780-intoxicated kernel from > http://people.openezx.org/wyrm/ > and rootfs > http://people.openezx.org/mickeyl/images/opie-image-a780-20060529204745.rootfs.tar.gz Why are you using such an old rootfs? The canonical place for a780 rootfses is http://www.angstrom-distribution.org/unstable/images/a780/ - -- [EMAIL PROTECTED] will go go away in december 2007, please use [EMAIL PROTECTED] instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHPW0nMkyGM64RGpERAr0YAJ9XBMVT09Vd9f6LD1+cyQZyPIpUcQCcCi/W kNRP9ieugiySWC6JI88N3uA= =CS+f -END PGP SIGNATURE-
Re: sound on e680
Alain2210 schreef: > Hello, > > I'm using angstrom x11 image and a kernel 2.6.21-4 ezx on a e680. The e680 has > not been flashed and I boot with boot_usb. > > I cannot get the sound working : > > in dmesg I can see : > <6>ASoC version 0.13.0 > <6>pcap2-codec: PCAP2 Audio Codec 0.1 > <6>asoc: PCAP2 STEREO <-> pxa2xx-ssp3 mapping ok > <6>asoc: PCAP2 MONO <-> pxa2xx-ssp3 mapping ok > <6>asoc: PCAP2 BP <-> Baseband mapping ok > <6>ALSA device list: > <6> #0: Motorola EZX (PCAP2 Audio) > > But when I try to play a mp3 file with mplayer I get : > [AO OSS] audio_setup: Can't open audio device /dev/dsp: No such file or > directory > [AO OSS] audio_setup: Can't open audio device /dev/dsp: No such file or > directory > and mplayer do as if it was playing the file. You to load the snd-pcm-oss kernel module for oss emulation or use a player that supports alsa natively. regards, Koen
Re: ezxd changes.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Ribeiro schreef: > Koen Kooi wrote: > > gsmd sadly expects a character device, how can we hook ezxd up to gsmd? >> And does it fake ATZ already? > See > http://blogs.gnome.org/thos/2007/10/30/turning-the-neo1973-into-an-expensive-external-gsm-modem/ > > Thanks to o-hand/OpenMoko! > Ok, I installed pty on my a780: [EMAIL PROTECTED]:~# pty localhost 7100 /dev/pts/1 changed /etc/default/gsmd: "Motorola Ezx Platform") GSMD_OPTS=" -F -v ti" GSM_DEV="/dev/pts/1" and on another terminal did: [EMAIL PROTECTED]:/etc/default# /etc/init.d/gsmd stop Stopping GSM daemon: stopped /usr/sbin/gsmd (pid 986). gsmd. [EMAIL PROTECTED]:/etc/default# /etc/init.d/gsmd start Starting GSM daemon: gsmd. [EMAIL PROTECTED]:/etc/default# tail -f /tmp/gsm.log Thu Nov 1 16:56:08 2007 <1> machine.c:72:gsmd_machine_plugin_load() loading machine plugin "generic" Thu Nov 1 16:56:08 2007 <1> vendor.c:75:gsmd_vendor_plugin_load() loading vendor plugin "ti" Thu Nov 1 16:56:08 2007 <1> machine.c:56:gsmd_machine_plugin_find() selecting machine plugin "generic" Thu Nov 1 16:56:09 2007 <1> uart.c:41:uart_drain() c_iflag = 0x0500, c_oflag = 0x0005, c_cflag = 0x800010b2, c_lflag = 0x8a3b Thu Nov 1 16:56:09 2007 <1> vendor.c:59:gsmd_vendor_plugin_find() selecting vendor plugin "TI Calypso" Thu Nov 1 16:56:09 2007 <1> atcmd.c:562:atcmd_submit() submitting command `ATZ' As expected it hangs on ATZ :( regards, Koen - -- [EMAIL PROTECTED] will go go away in december 2007, please use [EMAIL PROTECTED] instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHKfgCMkyGM64RGpERAjzmAJ466o7qjG/PwxQJg+G5lAURrWI4ZQCffD7v lvJK/E70au3LrmnAl8GAa8I= =7Vzs -END PGP SIGNATURE-
Re: ezxd changes.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Ribeiro schreef: > Koen Kooi wrote: > > gsmd sadly expects a character device, how can we hook ezxd up to gsmd? >> And does it fake ATZ already? > See > http://blogs.gnome.org/thos/2007/10/30/turning-the-neo1973-into-an-expensive-external-gsm-modem/ > > Thanks to o-hand/OpenMoko! http://ewi546.ewi.utwente.nl/tmp/pty_0.0-r0_armv5te.ipk - -- [EMAIL PROTECTED] will go go away in december 2007, please use [EMAIL PROTECTED] instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHKfFtMkyGM64RGpERAnezAJ9Mjdrj7zSZeElLLb+5GxJCJBlrgQCfd7Yo PngcS3N+8UK0P65ZB6WH+eI= =9g0r -END PGP SIGNATURE-
Re: ezxd changes.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Ribeiro schreef: > Hi. > > Targeting quick integration with gsmd, i changed ezxd to act as an AT > command proxy and hijacker. Here is an example ezxd session with the > last revision: [snip] gsmd sadly expects a character device, how can we hook ezxd up to gsmd? And does it fake ATZ already? regards, Koen - -- [EMAIL PROTECTED] will go go away in december 2007, please use [EMAIL PROTECTED] instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHJui9MkyGM64RGpERAkykAKCu5auNMLV9nOjs78JfXUl+32aQ1gCgjJG4 gbLySOgXkHoCr9fJYsLk2DE= =HX6f -END PGP SIGNATURE-
Re: Mux cli weirdness
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Koen Kooi schreef: > Hi, > > Since yesterday I'm getting this: > > <4>usb_ipc_probe: completed probe! > <6>drivers/char/ts0710_mux_usb.c: usb_ipc_probe: Only two endpoints > supported. > <4>usb ipc: probe of 1-3:1.6 failed with error -1 > <6>drivers/char/ts0710_mux_usb.c: usb_ipc_probe: Only two endpoints > supported. > <4>usb ipc: probe of 1-3:1.7 failed with error -1 > > which ends up giving SABM timeouts to ezxd and triggers the watchdog to > shutdown the AP :( > > I didn't change kernel the last two weeks, so I have no clue what could > have caused this. <4>Reading max 1984 bytes from ts0710_mux_usb inbuf. <4>Reading max 1984 bytes from ts0710_mux_usb inbuf. <4>Read 15 bytes. <4>Reading max 1969 bytes from ts0710_mux_usb inbuf. <4>nonzero read bulk status received: -104 <4>EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended <4>BP rdy irq <4>Reading max 2048 bytes from ts0710_mux_usb inbuf. <4>Read 18 bytes. <4>Reading max 2030 bytes from ts0710_mux_usb inbuf. <4>nonzero read bulk status received: -104 <4>MUX mux_flush_buffer: line is:0 <4>Reading max 2048 bytes from ts0710_mux_usb inbuf. <4>Read 25 bytes. <4>Reading max 2023 bytes from ts0710_mux_usb inbuf. <4>nonzero read bulk status received: -104 <4>BP Lowered WDI line. This is not good :( [EMAIL PROTECTED]:~$ cat /tmp/ [EMAIL PROTECTED]:~$ cd [EMAIL PROTECTED]:~$ date Mon Oct 29 15:56:25 UTC 2007 [EMAIL PROTECTED]:~$ echo "charger on" | nc localhost 7100 - -ERR [EMAIL PROTECTED]:~$ cat /etc/ezxd.conf # comment load log load raw #load pm load clock load bt mux open [EMAIL PROTECTED]:~$ So don't load the pm module, since something is wrong with the uinput module. - -- [EMAIL PROTECTED] will go go away in december 2007, please use [EMAIL PROTECTED] instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHJgbXMkyGM64RGpERAkAoAKC52NFHocHuu6kZj0CDzuoN4eFnvACgsX01 OmI2p8WupwY4EJK7uh2TMg0= =lVhr -END PGP SIGNATURE-
Re: Qtopia-4.3.0 on A780
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 GoXbox Live schreef: > Hi. > > I can see that it exist Openmoko, x11, Opie, Gpephone images, and you > name it for A780. But i cant see that someone have made a Qtopia-4.3.0 > image yet. So i did somemething about it :-) . If you *really* want to do something about it, make a qtopia-phone-image.bb for OpenEmbedded. - -- [EMAIL PROTECTED] will go go away in december 2007, please use [EMAIL PROTECTED] instead. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHJee4MkyGM64RGpERAh0/AJ9EomngpyOg6A/4oRtnty/71YTRDACcD8Cn PlApFWuqZ+l8nnE+5uYpQvw= =nM15 -END PGP SIGNATURE-
kernel 2.6.23
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Antonia ported the patches to .23 and I get: <5>Linux version 2.6.23.1-ezxdev ([EMAIL PROTECTED]) (gcc version 4.1.2) #1 PREEMPT Thu Oct 25 12:17:53 CEST 2007 <4>CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=397f <4>Machine: Motorola Ezx Platform <4>Warning: bad configuration page, trying to continue <4>Memory policy: ECC disabled, Data cache writeback <7>On node 0 totalpages: 12288 <7> DMA zone: 416 pages used for memmap <7> DMA zone: 0 pages reserved <7> DMA zone: 11872 pages, LIFO batch:1 <7> Normal zone: 0 pages used for memmap <7> Movable zone: 0 pages used for memmap <6>Run Mode clock: 195.00MHz (*15) <6>Turbo Mode clock: 292.50MHz (*1.5, active) <6>Memory clock: 195.00MHz (/2) <6>System bus clock: 195.00MHz <4>CPU0: D VIVT undefined 5 cache <4>CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets <4>CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets <4>Built 1 zonelists in Zone order. Total pages: 11872 <5>Kernel command line: console=tty1 root=/dev/mmcblk0p2 rootfstype=ext2 rootdelay=1 ip=192.168.0.202:192.168.0.200:192.168.0.200:255.255.255.0 debug [EMAIL PROTECTED] [EMAIL PROTECTED] <4>PID hash table entries: 256 (order: 8, 1024 bytes) <4>Console: colour dummy device 80x30 <6>console [tty1] enabled <6>Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) <6>Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) <6>Memory: 32MB 16MB = 48MB total <5>Memory: 45972KB available (2340K code, 178K data, 164K init) <7>Calibrating delay loop... 291.63 BogoMIPS (lpj=1458176) <4>Mount-cache hash table entries: 512 <6>CPU: Testing write buffer coherency: ok <6>NET: Registered protocol family 16 <6>usbcore: registered new interface driver usbfs <6>usbcore: registered new interface driver hub <6>usbcore: registered new device driver usb <6>Bluetooth: Core ver 2.11 <6>NET: Registered protocol family 31 <6>Bluetooth: HCI device and connection manager initialized <6>Bluetooth: HCI socket layer initialized <6>Time: oscr0 clocksource has been installed. <6>NET: Registered protocol family 2 <6>IP route cache hash table entries: 1024 (order: 0, 4096 bytes) <6>TCP established hash table entries: 2048 (order: 2, 16384 bytes) <6>TCP bind hash table entries: 2048 (order: 1, 8192 bytes) <6>TCP: Hash tables configured (established 2048 bind 2048) <6>TCP reno registered <4>bp handshake entered! <4>ezx-bp: handshake step 2 <4>ezx-pcap: ssp driver registered <5>EMU: Switching to USB <6>io scheduler noop registered <6>io scheduler deadline registered (default) <4>pxa2xx-fb pxa2xx-fb: machine LCCR0 setting contains illegal bits: 00200878 <4>pxa2xx-fb pxa2xx-fb: machine LCCR3 setting contains illegal bits: 0038 <4>Console: switching to colour frame buffer device 60x53 <6>Load PXA Overlay driver successfully! <6>usbcore: registered new interface driver usb ipc <6>drivers/char/ts0710_mux_usb.c: USB Host(Bulverde) IPC driver registered. <6>drivers/char/ts0710_mux_usb.c: 1.0alpha1:USB IPC Driver (TS07.10 lowlevel) <6>pxa2xx-uart.0: ttyS0 at MMIO 0x4010 (irq = 22) is a FFUART <6>pxa2xx-uart.1: ttyS1 at MMIO 0x4020 (irq = 21) is a BTUART <6>pxa2xx-uart.2: ttyS2 at MMIO 0x4070 (irq = 20) is a STUART <4>Probing PXA27x flash at physical address 0x (16-bit bankwidth) <6>PXA27x flash: Found 1 x16 devices at 0x0 in 16-bit bank <4> Intel/Sharp Extended Query Table at 0x010A <4> Intel/Sharp Extended Query Table at 0x010A <4> Intel/Sharp Extended Query Table at 0x010A <4> Intel/Sharp Extended Query Table at 0x010A <4> Intel/Sharp Extended Query Table at 0x010A <6>Using buffer write method <5>cfi_cmdset_0001: Erase suspend on write enabled <7>erase region 0: offset=0x0,size=0x8000,blocks=4 <7>erase region 1: offset=0x2,size=0x2,blocks=255 <7>PXA27x flash: 1 set(s) of 1 interleaved chips --> 16 partitions of 2048 KiB <5>RedBoot partition parsing not available <5>cmdlinepart partition parsing not available <5>Using static partition definition <5>Creating 6 MTD partitions on "PXA27x flash": <5>0x-0x0002 : "Bootloader" <5>0x0002-0x0010 : "Kernel" <5>0x0012-0x01a0 : "rootfs" <5>0x01a0-0x01f8 : "VFM_Filesystem" <5>0x01fa-0x01fc : "setup" <5>0x01fc-0x01fe : "Logo" <7>ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver <6>pxa27x-ohci pxa27x-ohci: PXA27x OHCI <6>pxa27x-ohci pxa27x-ohci: new USB bus registered, assigned bus number 1 <6>pxa27x-ohci pxa27x-ohci: irq 3, io mem 0x4c00 <6>usb usb1: configuration #1 chosen from 1 choice <6>hub 1-0:1.0: USB hub found <6>hub 1-0:1.0: 3 ports detected <6>pxa27x_udc: version 28-Jun-2007 <5>USB cmd disconnect <4>ether gadget: using random self ethernet address <4>ether gadget: using random host ethernet address <6>usb0: Ethernet Gadget, version: May Day 2005 <6>usb0: using pxa27x_udc, OUT Bulk-out-2 IN Bulk-in-1 <6>usb0: MAC 46:1c:c0:e0:39:a2 <5>USB cmd connect <6>input: gpio-keys as /device
Re: Mux cli weirdness
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Ribeiro schreef: > Koen Kooi wrote: >> Decreasing the root delay didn't help, I still get: > Do you still have the motorola firmware? Does it work? No, and no idea. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHHeTbMkyGM64RGpERAnALAJ9vZDnj405oNxLaBHZkjn1OaiRR5wCgqD3c YoPtrN2HZhnmUOhEXQGvQw8= =LHfl -END PGP SIGNATURE-
Re: Mux cli weirdness
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Ribeiro schreef: > Koen Kooi wrote: >> I think the rootdelay is messing things up, I going to build a new >> kernel to see if that's the case. I can say that I can do stuff in X >> before it shuts down, so openmoko boots within a minute ;) > Agreed! :) > Please disable the rootdelay for now. Later, i will try (again) to > compile the handshake code as a module, delaying step2, and all this > timing issues will vanish. Decreasing the root delay didn't help, I still get: <4>usb_ipc_probe: completed probe! <6>drivers/char/ts0710_mux_usb.c: usb_ipc_probe: Only two endpoints supported. <4>usb ipc: probe of 1-3:1.6 failed with error -1 <6>drivers/char/ts0710_mux_usb.c: usb_ipc_probe: Only two endpoints supported. <4>usb ipc: probe of 1-3:1.7 failed with error -1 That's even before it tries to mount the rootfs. and later: <4>MUX DLCI:0 Send SABM timeout! <4>MUX DLCI:0 Send SABM timeout! <4>MUX DLCI:0 Send SABM timeout! <4>MUX DLCI:0 Send SABM timeout! <4>MUX DLCI:0 Send SABM timeout! <4>MUX DLCI:0 Send SABM timeout! <4>MUX DLCI:0 Send SABM got signal! <4>MUX: Can't connect server channel 0! <4>MUX mux_close: tapisrv might be down!!! Close DLCI 1 <4>MUX DLCI:0 Send SABM timeout! regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHHaOGMkyGM64RGpERAtJ9AJwM4FHcXys1qxgUNoSEdJGIJUZhuQCeOzPV ixn73awLL+ipDe5YpB5lrkk= =C8tc -END PGP SIGNATURE-
Re: Mux cli weirdness
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Ribeiro schreef:
> Koen Kooi wrote:
>> I didn't change kernel the last two weeks, so I have no clue what could
>> have caused this.
>
> Latency added by userspace changes, between step3 and step4.
>
> Quick summary about the 4 steps needed for successful BP communication..
>
> Step1: (bootloader)
> The Power Button needs to be pressed.
>
> Step2: (kernel)
> The watchdog starts the countdown at this step.
> step1->step2 is *NOT* timing dependent.
>
> Step3: (kernel)
> BP is ready for communication.
rootdelay=
> Step4: (userspace)
> Userspace has to open mux0-mux8 quickly (not sure how
> quickly, i think that in less than 5 seconds after
> step3).
>
>
> If Step3 or Step4 fails for any reason, you will get errors trying to
> communicate with BP, and the watchdog turns off the phone ~40 seconds
> after step2.
I think the rootdelay is messing things up, I going to build a new
kernel to see if that's the case. I can say that I can do stuff in X
before it shuts down, so openmoko boots within a minute ;)
> Another possibility is that your battery is discharged, in this case,
> the kernel will show a "BP lowered WDI line, this is not good :(", or a
> "BP request poweroff", and the phone will turn off after a random amount
> of time (normally, much less than 40 seconds).
>
> If the above explanation didnt help, please send me a full dmesg output. :)
[EMAIL PROTECTED]:~$ dmesg
<5>Linux version 2.6.21.4-ezxdev ([EMAIL PROTECTED]) (gcc version 4.1.2) #1
PREEMPT Mon Oct 1 12:21:48 CEST 2007
<4>CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=397f
<4>Machine: Motorola Ezx Platform
<4>Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 12288
<7> DMA zone: 416 pages used for memmap
<7> DMA zone: 0 pages reserved
<7> DMA zone: 11872 pages, LIFO batch:1
<7> Normal zone: 0 pages used for memmap
<6>Run Mode clock: 195.00MHz (*15)
<6>Turbo Mode clock: 292.50MHz (*1.5, active)
<6>Memory clock: 195.00MHz (/2)
<6>System bus clock: 195.00MHz
<4>CPU0: D VIVT undefined 5 cache
<4>CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
<4>CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets
<4>Built 1 zonelists. Total pages: 11872
<5>Kernel command line: console=tty1 root=/dev/mmcblk0p2
rootfstype=ext2 rootdelay=5
ip=192.168.0.202:192.168.0.200:192.168.0.200:255.255.255.0 debug
[EMAIL PROTECTED] [EMAIL PROTECTED]
<4>PID hash table entries: 256 (order: 8, 1024 bytes)
<4>Console: colour dummy device 80x30
<4>Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
<4>Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
<6>Memory: 32MB 16MB = 48MB total
<5>Memory: 45900KB available (2376K code, 203K data, 176K init)
<7>Calibrating delay loop... 291.63 BogoMIPS (lpj=1458176)
<4>Mount-cache hash table entries: 512
<6>CPU: Testing write buffer coherency: ok
<6>NET: Registered protocol family 16
<6>usbcore: registered new interface driver usbfs
<6>usbcore: registered new interface driver hub
<6>usbcore: registered new device driver usb
<6>Time: pxa_timer clocksource has been installed.
<6>NET: Registered protocol family 2
<4>IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
<4>TCP established hash table entries: 2048 (order: 2, 16384 bytes)
<4>TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
<6>TCP: Hash tables configured (established 2048 bind 2048)
<6>TCP reno registered
<4>bp handshake entered!
<4>ezx-bp: handshake step 2
<4>BP rdy irq
<4>bp handshake entered!
<5>ezx-bp: handshake passed
<4>ezx-pcap: ssp driver registered
<5>EMU: Switching to disconnected
<6>io scheduler noop registered
<6>io scheduler deadline registered (default)
<4>pxa2xx-fb pxa2xx-fb: machine LCCR0 setting contains illegal bits:
00200878
<4>pxa2xx-fb pxa2xx-fb: machine LCCR3 setting contains illegal bits:
0038
<4>Console: switching to colour frame buffer device 60x53
<6>Load PXA Overlay driver successfully!
<6>usbcore: registered new interface driver usb ipc
<6>drivers/char/ts0710_mux_usb.c: USB Host(Bulverde) IPC driver registered.
<6>drivers/char/ts0710_mux_usb.c: 1.0alpha1:USB IPC Driver (TS07.10
lowlevel)
<6>pxa2xx-uart.0: ttyS0 at MMIO 0x4010 (irq = 22) is a FFUART
<6>pxa2xx-uart.1: ttyS1 at MMIO 0x4020 (irq = 21) is a BTUART
<6>pxa2xx-uart.2: ttyS2 at MMIO 0x4070 (irq = 20) is a ST
Mux cli weirdness
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Since yesterday I'm getting this: <4>usb_ipc_probe: completed probe! <6>drivers/char/ts0710_mux_usb.c: usb_ipc_probe: Only two endpoints supported. <4>usb ipc: probe of 1-3:1.6 failed with error -1 <6>drivers/char/ts0710_mux_usb.c: usb_ipc_probe: Only two endpoints supported. <4>usb ipc: probe of 1-3:1.7 failed with error -1 which ends up giving SABM timeouts to ezxd and triggers the watchdog to shutdown the AP :( I didn't change kernel the last two weeks, so I have no clue what could have caused this. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHGMKyMkyGM64RGpERAgfqAKCZU4YY2R5yb2KoKzS+JvIP8YEm2ACgkeAs B3GuoDhzbuCMoYCMDY91XJE= =f5t5 -END PGP SIGNATURE-
Re: Preparing discussion with gsmd developers.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Ribeiro schreef: > 2007/10/4, Koen Kooi <[EMAIL PROTECTED]>: >> Daniel's suggestion of a named pipe that gsmd talks to and ezxd forwards to >> /dev/mux* >> would be the easiest thing to start with. Has anyone figured out how to >> reset the modem, >> since atz doesn't seem to be present? > Yes, i think that an unix socket would be the easiest way-to-go for > the A option. > > We can reset the modem in kernel space by asserting BB_RESET high for > 1ms, but i think this is not what you want :) > Any particular reason that requires the modem reset?? Or just because > gsmd thinks that it should reset the modem? > If the reset is *really* necessary, and there is no other way to do it > via an AT command, we could have an ioctl for this task. gsmd hardcodes an ATZ, which is perfectly legal, but moto seems to have removed atz. since we're talking thru ezxd anyway, we can intercept that atz :) regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHBUXuMkyGM64RGpERAmbbAJwI5FLCwvuPSlZt9zwC0P0gJoCxYQCffCnr icf6vZpa1nzcoZqc+FjkUyE= =D4QN -END PGP SIGNATURE-
Re: Preparing discussion with gsmd developers.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Antonio Ospite schreef: > On Thu, 27 Sep 2007 10:45:33 +0200 > Antonio Ospite <[EMAIL PROTECTED]> wrote: > >> AFAIR presently there are mainly two ways we see a possible >> integration: >> >> a. have ezxd talk with mux devices and act like a proxy between gsmd >>and the modem. This way we handle all the non-GSM stuff in ezxd. >>This should be feasible right now. >> >> b. have gsmd talk with mux devices, and use ezxd to query non-GSM >> stuff via the libgsmd passthrough mode. Since there are some infos >> that can't be obtained on request, we should find a way to ask to to >> gsmd some data stored by the plugin on startup. We propose to let >> plugin define custom AT commands, so to have a very high level API. >> > > Ok, let's turn pragmatic, since there are some overlaps between a. > and b. anyway, what about starting with a. and convert to b. when > feasible? I think Harald is too busy at the moment to comment about our > ezx integration, and we do not know gsmd too well to touch it in its > main loop. Daniel's suggestion of a named pipe that gsmd talks to and ezxd forwards to /dev/mux* would be the easiest thing to start with. Has anyone figured out how to reset the modem, since atz doesn't seem to be present? regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHBQ9mMkyGM64RGpERAsD5AJ9D2Og0Qlr9i1wCRR1QeVv8JogpRwCeLhYv 0ZPYcrivyEfYgFP11U+oDNk= =F+Gg -END PGP SIGNATURE-
Re: a780 at command set
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Ribeiro schreef: > Koen Kooi wrote: > | Sat Sep 22 16:03:24 2007 <1> atcmd.c:562:atcmd_submit() submitting > command `AT' > | Sat Sep 22 16:03:24 2007 <1> atcmd.c:260:ml_parse() buf=`+CME ERROR: > 100'(15) > AT doesn't fail with ezxd. It doesn't always fail :( > How are you dealing with /dev/mux* files? I give the AT commands on mux0 > Are you opening which device > on gsmd? Running ezxd and gsmd at the same time? Killing ezx and relaunching gsmd doesn't seem to make a difference. Do you know how to reset the modem to a known state? ATZ doesn't seem to work :( regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG9VnkMkyGM64RGpERArgSAJ9nsnkMWe0WdvH1O/C0y15oV13lpwCePQ+z Q13pd2Oh+H4+eUHlUiIs2d4= =RpxD -END PGP SIGNATURE-
Re: a780 at command set
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Koen Kooi schreef: > Hi, > > Could anyone tell me how correct http://wiki.openezx.org/AT_commands is and > how that > information was obtained? I'm trying to get gsmd from the openmoko project to > work and > simple commands like 'ATZ' 'AT+CLAC' 'AT+CFUN' and 'AT+COPS' error out with > CME ERROR: 4 > (Operation not supported) or CME ERROR: 100 (Unknown error). > > I heard people about 'stracing tapisrv' and 'stracing lapisrv', could those > people be so > kind to strace them while making a call and hanging up and send them to the > list or me > directly? Moto seemed to have removed 'ATZ', so I patched gsmd to substitute it with 'AT' and get this: [EMAIL PROTECTED]:~# ./gsmd -p /dev/mux0 -s 115200 -F -v tihtc gsmd - (C) 2006-2007 by OpenMoko, Inc. and contributors This program is FREE SOFTWARE under the terms of GNU GPL Sat Sep 22 16:03:23 2007 <1> machine.c:72:gsmd_machine_plugin_load() loading machine plugin "generic" Sat Sep 22 16:03:23 2007 <1> vendor.c:75:gsmd_vendor_plugin_load() loading vendor plugin "tihtc" Sat Sep 22 16:03:23 2007 <1> machine.c:56:gsmd_machine_plugin_find() selecting machine plugin "generic" Sat Sep 22 16:03:24 2007 <1> uart.c:41:uart_drain() c_iflag = 0x, c_oflag = 0x, c_cflag = 0x800010b2, c_lflag = 0x Sat Sep 22 16:03:24 2007 <1> vendor.c:59:gsmd_vendor_plugin_find() selecting vendor plugin "TI Calypso / HTC firmware" Sat Sep 22 16:03:24 2007 <1> atcmd.c:562:atcmd_submit() submitting command `AT' Sat Sep 22 16:03:24 2007 <1> atcmd.c:260:ml_parse() buf=`+CME ERROR: 100'(15) Sat Sep 22 16:03:24 2007 <1> atcmd.c:331:ml_parse() error number 100 Sat Sep 22 16:03:24 2007 <1> atcmd.c:482:ml_parse() Calling final cmd->cb() Sat Sep 22 16:03:24 2007 <7> gsmd.c:209:firstcmd_atcb() response '+CME ERROR: 100' to initial command invalidSat Sep 22 16:03:24 2007 <1> atcmd.c:562:atcmd_submit() submitting command `ATE0V1' Sat Sep 22 16:03:24 2007 <1> atcmd.c:562:atcmd_submit() submitting command `AT+CRC=1' Sat Sep 22 16:03:24 2007 <1> atcmd.c:562:atcmd_submit() submitting command `AT+CREG=2' Sat Sep 22 16:03:24 2007 <1> atcmd.c:562:atcmd_submit() submitting command `AT+CMEE=1' Sat Sep 22 16:03:24 2007 <1> atcmd.c:562:atcmd_submit() submitting command `AT+CLIP=1' Sat Sep 22 16:03:24 2007 <1> atcmd.c:562:atcmd_submit() submitting command `AT+COLP=1' Sat Sep 22 16:03:24 2007 <1> atcmd.c:562:atcmd_submit() submitting command `AT+CMGF=0' Sat Sep 22 16:03:24 2007 <1> atcmd.c:562:atcmd_submit() submitting command `AT+CMGF=0' Sat Sep 22 16:03:24 2007 <1> atcmd.c:562:atcmd_submit() submitting command `AT%CPRI=1' Sat Sep 22 16:03:24 2007 <1> atcmd.c:562:atcmd_submit() submitting command `AT%HTCCSQ=1' Sat Sep 22 16:03:24 2007 <1> atcmd.c:562:atcmd_submit() submitting command `AT%CUNS=0' Sat Sep 22 16:03:24 2007 <1> atcmd.c:562:atcmd_submit() submitting command `AT%CPI=?' Sat Sep 22 16:03:24 2007 <1> atcmd.c:491:ml_parse() Clearing mlbuf Sat Sep 22 16:03:24 2007 <1> atcmd.c:260:ml_parse() buf=`+CME ERROR: 25'(14) Sat Sep 22 16:03:24 2007 <1> atcmd.c:331:ml_parse() error number 25 Sat Sep 22 16:03:24 2007 <1> atcmd.c:482:ml_parse() Calling final cmd->cb() Sat Sep 22 16:03:24 2007 <1> gsmd.c:153:gsmd_test_atcb() `ATE0V1' returned `+CME ERROR: 25' Sat Sep 22 16:03:24 2007 <1> atcmd.c:491:ml_parse() Clearing mlbuf Sat Sep 22 16:03:44 2007 <1> atcmd.c:562:atcmd_submit() submitting command `AT+CFUN=1' Sat Sep 22 16:04:14 2007 <1> atcmd.c:562:atcmd_submit() submitting command `AT+COPS=0' full talloc report on 'GSMD' (total 68347 bytes in 23 blocks) operator_cache contains 1 bytes in 1 blocks (ref 0) gsmd_user contains 2185 bytes in 3 blocks (ref 0) struct gsmd_user contains 1092 bytes in 1 blocks (ref 0) struct gsmd_user contains 1092 bytes in 1 blocks (ref 0) ucmd contains 1 bytes in 1 blocks (ref 0) atcmds contains599 bytes in 14 blocks (ref 0) atcmd.c:541contains 46 bytes in 1 blocks (ref 0) atcmd.c:541contains 46 bytes in 1 blocks (ref 0) atcmd.c:541contains 45 bytes in 1 blocks (ref 0) atcmd.c:541contains 46 bytes in 1 blocks (ref 0) atcmd.c:541contains 48 bytes in 1 blocks (ref 0) atcm
a780 at command set
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Could anyone tell me how correct http://wiki.openezx.org/AT_commands is and how that information was obtained? I'm trying to get gsmd from the openmoko project to work and simple commands like 'ATZ' 'AT+CLAC' 'AT+CFUN' and 'AT+COPS' error out with CME ERROR: 4 (Operation not supported) or CME ERROR: 100 (Unknown error). I heard people about 'stracing tapisrv' and 'stracing lapisrv', could those people be so kind to strace them while making a call and hanging up and send them to the list or me directly? thanks, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG9Rc4MkyGM64RGpERAnkMAJ9aPPA9YVnb4gMXoOPKyBrHaLb4tgCeKVkO 8xlYh8kmdB3X09+EaRFDVmg= =N0lz -END PGP SIGNATURE-
Pxa270 overlay driver working
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I added a patch to enable the overlay capabilities to the linux-ezx kernel in OE (r18), and I can confirm it's working on the a780. People with a1200/e6/e2/e680 need to add this to defconfig to try it: +CONFIG_FB_PXA_LCD_QVGA=y +# CONFIG_FB_PXA_LCD_VGA is not set +CONFIG_FB_PXA_OVERLAY=y And install the mplayer from the angstrom iwmmxt feed and use -vo pxa. share and enjoy, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG8/BQMkyGM64RGpERAi3KAKCUomwQC0FQuH6pnTzOuZBKR+YYwACeKH1X D5ZDA/dOLceVC4xU2MCKL1A= =AOhj -END PGP SIGNATURE-
Re: a1200 and rokre6 build error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Ribeiro schreef: > Koen Kooi wrote: > | I'm having trouble building a kernel for rokre6 and a1200: > | http://bugs.openembedded.org/attachment.cgi?id=2469&action=edit > This compile log lacks the compilation of ezx-eoc.c. Maybe you forgot > CONFIG_EZX_EOC It was something more stupid: I changed the defconfig to have CONFIG_EZX_EOC=y, but forgot to change the I2C ones, so make oldconfig changed it to CONFIG_EZX_EOC=m, which doesn't compile. Fixed now in OE and it now has the 18bpp patch for a1200 as well. regards, Koen zImage: http://www.angstrom-distribution.org/unstable/images/rokre6/20070915/ you can use the images from the a780 directory and untar the modules-*something*-rokre6.tgz over that to have working modules. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG7BuyMkyGM64RGpERAig9AJ92a8jCosaZMHKA7KBKieeUIyvd/QCfWoR1 jVpxxTq9DGJ/m5Uo217TKv4= =K0kn -END PGP SIGNATURE-
a1200 and rokre6 build error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm having trouble building a kernel for rokre6 and a1200: http://bugs.openembedded.org/attachment.cgi?id=2469&action=edit AFAICS the patches in OE are in sync with svn. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG6+WgMkyGM64RGpERAjBaAJ0Vpy54m+Anh6b7Ujm+4J1OhPsxxwCeNIF7 lnBHrxwUCUQ5vCPngWOxCCU= =fGtQ -END PGP SIGNATURE-
Testing image and kernel for a780 available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, You can find a zImage and rootfs at http://www.angstrom-distribution.org/unstable/images/a780/20070914/ you need an ext3 partition on the first partition of your microsd card (/dev/mmcblk0p1) and then untar the rootfs (as root) on to that. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG64uUMkyGM64RGpERAgnSAJ9zIs7FXlWVmMSxumV9Q4akNAY9oQCfeVyY GwU6O/F/HDQcytCjxpHBaVc= =ESNA -END PGP SIGNATURE-
Re: using gsmd on an a780
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Antonio Ospite schreef: > On Wed, 12 Sep 2007 11:31:07 +0200 > Koen Kooi <[EMAIL PROTECTED]> wrote: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> with >> GSMD_OPTS="-s 115200 -F" >> GSM_DEV="/dev/mux1" >> >> I get: >> > ... >> Is mux1 the correct channel? > >>From drivers/char/ts0710_mux.h > > #define MUX_CMD_FILE_VOICE_CALL "/dev/mux0" > #define MUX_CMD_FILE_SMS_MO "/dev/mux1" > #define MUX_CMD_FILE_SMS_MT "/dev/mux2" > #define MUX_CMD_FILE_PHONEBOOK"/dev/mux3" > #define MUX_CMD_FILE_MISC "/dev/mux4" > #define MUX_CMD_FILE_CSD "/dev/mux5" > #define MUX_CMD_FILE_GPRS1"/dev/mux6" > #define MUX_CMD_FILE_GPRS2"/dev/mux7" > > You can try with mux0, RGH! I confused DLC and channel from http://wiki.openezx.org/Mux_cli :( > but I think that a ezx specific plugin for gsmd > is needed. I think so too, but I want to see how far I can get without it :) regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG6AquMkyGM64RGpERArShAKCSd5fRDMX+JaSK6Sm1NM9SNI1FMgCcDoP2 I3I8AXbSmiyZ9Nvpb+69UYs= =GylY -END PGP SIGNATURE-
using gsmd on an a780
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 with GSMD_OPTS="-s 115200 -F" GSM_DEV="/dev/mux1" I get: gsmd - (C) 2006-2007 by OpenMoko, Inc. and contributors This program is FREE SOFTWARE under the terms of GNU GPL Wed Sep 12 11:24:46 2007 <1> machine.c:72:gsmd_machine_plugin_load() loading machine plugin "generic" Wed Sep 12 11:24:46 2007 <1> vendor.c:75:gsmd_vendor_plugin_load() loading vendor plugin "ti" Wed Sep 12 11:24:46 2007 <1> vendor.c:75:gsmd_vendor_plugin_load() loading vendor plugin "tihtc" Wed Sep 12 11:24:46 2007 <1> vendor.c:75:gsmd_vendor_plugin_load() loading vendor plugin "qc" Wed Sep 12 11:24:46 2007 <1> vendor.c:75:gsmd_vendor_plugin_load() loading vendor plugin "bcm" Wed Sep 12 11:24:46 2007 <1> machine.c:56:gsmd_machine_plugin_find() selecting machine plugin "generic" Wed Sep 12 11:24:47 2007 <1> atcmd.c:561:atcmd_drain() c_iflag = 0x, c_oflag = 0x, c_cflag = 0x800010b2, c_lflag = 0x Wed Sep 12 11:24:47 2007 <1> vendor.c:59:gsmd_vendor_plugin_find() selecting vendor plugin "Broadcom BCM2132" Wed Sep 12 11:24:47 2007 <1> atcmd.c:545:atcmd_submit() submitting command `ATZ' Wed Sep 12 11:25:47 2007 <1> atcmd.c:545:atcmd_submit() submitting command `AT+CFUN=1' Wed Sep 12 11:26:07 2007 <1> atcmd.c:545:atcmd_submit() submitting command `AT+COPS=0' Wed Sep 12 11:26:07 2007 <1> atcmd.c:210:ml_parse() buf=`+CME ERROR: 25'(14) Wed Sep 12 11:26:07 2007 <1> atcmd.c:259:ml_parse() error number 25 Wed Sep 12 11:26:07 2007 <1> atcmd.c:406:ml_parse() Calling final cmd->cb() Wed Sep 12 11:26:07 2007 <7> gsmd.c:210:firstcmd_atcb() response '+CME ERROR: 25' to initial command invalidWed Sep 12 11:26:07 2007 <1> atcmd.c:545:atcmd_submit() submitting command `ATE0V1' Wed Sep 12 11:26:07 2007 <1> atcmd.c:545:atcmd_submit() submitting command `AT+CRC=1' Wed Sep 12 11:26:07 2007 <1> atcmd.c:545:atcmd_submit() submitting command `AT+CREG=2' Wed Sep 12 11:26:07 2007 <1> atcmd.c:545:atcmd_submit() submitting command `AT+CMEE=1' Wed Sep 12 11:26:07 2007 <1> atcmd.c:545:atcmd_submit() submitting command `AT+CLIP=1' Wed Sep 12 11:26:07 2007 <1> atcmd.c:545:atcmd_submit() submitting command `AT+COLP=1' Wed Sep 12 11:26:07 2007 <1> atcmd.c:545:atcmd_submit() submitting command `AT+CMGF=0' Wed Sep 12 11:26:07 2007 <1> atcmd.c:545:atcmd_submit() submitting command `AT+CMGF=0' Wed Sep 12 11:26:07 2007 <1> atcmd.c:415:ml_parse() Clearing mlbuf Wed Sep 12 11:26:07 2007 <1> atcmd.c:210:ml_parse() buf=`OK'(2) Wed Sep 12 11:26:07 2007 <1> atcmd.c:406:ml_parse() Calling final cmd->cb() Wed Sep 12 11:26:07 2007 <1> usock.c:249:phone_powerup_cb() Radio powered-up Wed Sep 12 11:26:07 2007 <1> atcmd.c:415:ml_parse() Clearing mlbuf Is mux1 the correct channel? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG57HbMkyGM64RGpERAtzzAKC2ED3Z9IMzEZQwvD4QKSH3F1h9pACfQTUJ MlC8olq+LGoi7KgWiMjZpRw= =NG+b -END PGP SIGNATURE-
Re: Battery charging in kernel 2.6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Ribeiro schreef: > Update ezxd to r2048, echo "charger on" | nc localhost 7100. > You need bp in normal mode to charge. Does that work with any mini-usb cable, or only with the motorola-that-has-an-extra-resistor-mini-usb cable? regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG56myMkyGM64RGpERAhkMAJ4ne2mYNdAL5ubZIYHWTdTfm3tZAACfdX1G H1MLsW5myVLkiAxFRJ9MsCI= =l/9f -END PGP SIGNATURE-
[PATCH] fix oops on mtdaccess
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Attached patch allowed me to install blob2 and flash a zImage to mtd4 using the
alternate
mtd config in the kernel
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFG5U06MkyGM64RGpERAksrAKCT2Igd/75MhyJ+c8bTe9+7YuqGwgCguwcg
2J2TcnpLDwZAEltZ+sJRqZg=
=jIbj
-END PGP SIGNATURE-
--- /tmp/cacheflush.h 2007-09-10 15:22:58.188856413 +0200
+++ linux-2.6.21/include/asm-arm/cacheflush.h 2007-09-10 15:23:14.009757994 +0200
@@ -418,6 +418,14 @@
*/
#define flush_icache_page(vma,page) do { } while (0)
+inline static void flush_ioremap_region(unsigned long phys, void __iomem *virt,
+unsigned offset, size_t size)
+{
+ const void *start = virt + offset;
+ dmac_inv_range(start, start + size);
+}
+
+
#define __cacheid_present(val) (val != read_cpuid(CPUID_ID))
#define __cacheid_vivt(val) ((val & (15 << 25)) != (14 << 25))
#define __cacheid_vipt(val) ((val & (15 << 25)) == (14 << 25))
--- /tmp/ezx-flash.c 2007-09-10 15:22:58.192856640 +0200
+++ linux-2.6.21/drivers/mtd/maps/ezx-flash.c 2007-09-10 15:23:24.878377362 +0200
@@ -21,6 +21,8 @@
#include
#include
+#include
+
#include
#include
#include
@@ -51,11 +53,10 @@
"sub pc, pc #4"
:"=r"(j));
#else
- consistent_sync((char *)map->cached + from, len, DMA_FROM_DEVICE);
+flush_ioremap_region(map->phys, map->cached, from, len);
#endif
}
-
struct map_info pxa27x_map = {
.name = "PXA27x flash",
.size = WINDOW_SIZE,
Re: Bug in mtd driver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Ribeiro schreef: > 2007/9/10, Koen Kooi <[EMAIL PROTECTED]>: > >> drivers/built-in.o: In function `pxa27x_map_inval_cache': >> hid-input.c:(.text+0x3c93c): undefined reference to `flush_ioremap_region' > #include Great! but: [EMAIL PROTECTED]:/boot$ cat /proc/mtd dev:size erasesize name mtd0: 0002 8000 "Bootloader" mtd1: 000e 0002 "Kernel" mtd2: 018e 0002 "rootfs" mtd3: 0058 0002 "VFM_Filesystem" mtd4: 0002 0002 "setup" mtd5: 0002 0002 "Logo" [EMAIL PROTECTED]:/boot$ flash_unlock /dev/mtd1 [EMAIL PROTECTED]:/boot$ flash_eraseall /dev/mtd1 Erasing 128 Kibyte @ c -- 85 % complete. [EMAIL PROTECTED]:/boot$ flashcp -v /boot/zImage-2.6.21-ezxdev-r10-a780-20070910122500.bin /dev/mtd1 /boot/zImage-2.6.21-ezxdev-r10-a780-20070910122500.bin won't fit into /dev/mtd1! [EMAIL PROTECTED]:/boot$ du /boot/* -k 0 /boot/zImage 1268/boot/zImage-2.6.21-ezxdev-r10-a780-20070910122500.bin 1166/boot/zImage-2.6.21.4-ezxdev -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG5TuhMkyGM64RGpERAhkLAKCJedcVIGATUQxlDd6/3ECe+WvwTgCfdP9k eJBccNtdisLI4D/0sDVrAx4= =HJip -END PGP SIGNATURE-
Re: Bug in mtd driver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Koen Kooi schreef: > Simon Neininger schreef: >> Hi! > >> On Montag, 10. September 2007, Koen Kooi wrote: >>> <1>Unable to handle kernel NULL pointer dereference at virtual >> http://lists.openezx.org/pipermail/openezx-devel/2007-September/001452.html > > Ah! I know about that one, thanks for reminding me :) I patched the kernel > and will try it > later today. drivers/built-in.o: In function `pxa27x_map_inval_cache': hid-input.c:(.text+0x3c93c): undefined reference to `flush_ioremap_region' :( -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG5TJ8MkyGM64RGpERAu8mAKCqRCZcKy6vIeI458zaTPZ8nyyTfwCdHXlH SUMfqEn17YQ1FVLrDMJvUXc= =Ci2B -END PGP SIGNATURE-
Re: Bug in mtd driver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Simon Neininger schreef: > Hi! > > On Montag, 10. September 2007, Koen Kooi wrote: >> <1>Unable to handle kernel NULL pointer dereference at virtual > > http://lists.openezx.org/pipermail/openezx-devel/2007-September/001452.html Ah! I know about that one, thanks for reminding me :) I patched the kernel and will try it later today. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG5SR6MkyGM64RGpERAlCvAKCpL/3VM0gSrQihp2carOkLTurcGACfZ2s7 FNORG1mRZcIAbDGOmK2XVWc= =/LSs -END PGP SIGNATURE-
Bug in mtd driver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I can't free my a780 :( <1>Unable to handle kernel NULL pointer dereference at virtual address <1>pgd = c07a4000 <1>[] *pgd=acb95031, *pte=, *ppte= <4>Internal error: Oops: 817 [#6] <4>Modules linked in: <4>CPU: 0 <4>pc : []lr : []Not tainted <4>sp : cc97bd20 ip : cc97bd30 fp : cc97bd2c <4>r10: r9 : 0003 r8 : cc97a000 <4>r7 : c04de838 r6 : 0002 r5 : c02ac7a8 r4 : 0002 <4>r3 : r2 : 0002 r1 : 0004 r0 : 0002 <4>Flags: nzcv IRQs on FIQs on Mode SVC_32 Segment user <4>Control: 397F <4>Table: A07A4000 DAC: 0015 <4>Process flash_erase (pid: 1843, stack limit = 0xcc97a260) <4>Stack: (0xcc97bd20 to 0xcc97c000) <4>bd20: cc97bd3c cc97bd30 c018278c c003b138 cc97bd74 cc97bd40 c02abbf4 c0182778 <4>bd40: 0002 cc97bd84 0002 0004 0002 <4>bd60: c038a58c c04de838 cc97bdc4 cc97bd78 c017ffbc c02abb74 cc97bd88 <4>bd80: 000c c02abb68 c04de800 c02ac7a8 c038a580 0001 c1eccbe0 <4>bda0: c1eccbe0 cc97bef0 c03341a0 c1eccbe0 cc97a000 cc97bde4 cc97bdc8 <4>bdc0: c0181710 c017fe10 c03341a0 c1eccbe0 cc97bdfc cc97bde8 <4>bde0: c017dd14 c01816ec cc97a000 40084d02 cc97bf2c cc97be00 c017f354 c017dccc <4>be00: c0079f14 c014152c c035b560 c004412c c002640c <4>be20: 0100 c0779344 004d 004d acc4f05f <4>be40: c0779330 c10d8968 cc97bebc cc97be60 cc97be84 cc97be68 <4>be60: c005684c c003ada0 00f6 cc97a000 c035b560 0015 cc97be9c cc97be88 <4>be80: c00575c0 c0056828 cca5e01c c035b560 cc97bedc cc97bea0 c0034c68 c00575a8 <4>bea0: cc97bebc 6093 a013 cc3a7000 4001b036 0036 cc97a000 <4>bec0: cc97beec cc97bed0 c0044404 c0042ea4 cc3a7000 cc97bf04 cc3a700c <4>bee0: cc97bf04 cc97bef0 c0157138 c00443d0 cc97bef0 cc97bef0 cc97bf4c cc97bf08 <4>bf00: c01586c0 c01570d8 c096f940 c126ce60 40084d02 bebcdc78 0036 c0034e28 <4>bf20: cc97bf4c cc97bf30 c009f058 c017f030 0036 c126ce60 0003 bebcdc78 <4>bf40: cc97bf7c cc97bf50 c009f334 c009efe8 c096f940 c126ce60 <4>bf60: fff7 40084d02 c0034e28 cc97a000 cc97bfa4 cc97bf80 c009f3a4 c009f080 <4>bf80: c003bf10 40123650 0003 cc97bfa8 <4>bfa0: c0034c80 c009f370 0003 0003 40084d02 bebcdc78 0001 <4>bfc0: 0003 0036 bebcde18 40123000 <4>bfe0: bebcdc58 86d8 400c3cbc 6010 0003 e28ee001 e1a06000 <4>Backtrace: <4>Function entered at [] from [] <4>Function entered at [] from [] <4>Function entered at [] from [] <4>Function entered at [] from [] <4>Function entered at [] from [] <4> r5 = C1ECCBE0 r4 = C03341A0 <4>Function entered at [] from [] <4> r5 = 40084D02 r4 = CC97A000 <4>Function entered at [] from [] <4> r8 = C0034E28 r7 = 0036 r6 = BEBCDC78 r5 = 40084D02 <4> r4 = C126CE60 <4>Function entered at [] from [] <4> r6 = BEBCDC78 r5 = 0003 r4 = C126CE60 <4>Function entered at [] from [] <4> r9 = CC97A000 r8 = C0034E28 r6 = 40084D02 r5 = FFF7 <4> r4 = C126CE60 <4>Function entered at [] from [] <4> r6 = r5 = r4 = 0003 <4>Code: 9a01 e15c0003 3a01 e3a03000 (e5833000) <6>note: flash_erase[1843] exited with preempt_count 2 <3>BUG: scheduling while atomic: flash_erase/0x4002/1843 regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG5QEgMkyGM64RGpERAtVnAJ4r2rLXs+TxkA8Q4d1Sj/6SEV5EBQCgubx9 p62ff+Gtz2Q+YbHPXLdALv4= =VoBm -END PGP SIGNATURE-
Re: Battery charging in kernel 2.6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Ribeiro schreef: > Update ezxd to r2048, echo "charger on" | nc localhost 7100. > You need bp in normal mode to charge. Thanks! ezxd r2050 is now in the angstrom feeds as well. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG5L+UMkyGM64RGpERAvJrAJ4md/P21QZZNGuGfQMLtrB9505PuACaAuwn 3XSrmWp4+8XQq0Yes13hlxU= =fkrm -END PGP SIGNATURE-
Kernel defconfigs in svn and OE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Today I update the a780 defconfig in OE to be more usefull to userspace hacking and pretty much blindly updated a1200, e680, rokre2 and rokre6 defconfigs. Could devices owners slash kernel hackers have a look at the ones in OE and tell me if something needs changing. regards, Koen PS: In case you haven't seen: http://dominion.kabel.utwente.nl/koen/cms/angstrom-running-on-an-motorola-a780 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG5Ap3MkyGM64RGpERAkHcAJ9N5tWeOcJvUSN02pI7JuDI8lW+jwCglbN9 EwzUTQE4eCPyBbVCCUgFwus= =kSoR -END PGP SIGNATURE-
Battery charging in kernel 2.6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Can kernel 2.6 charge the battery, and if so, how can I make it do that? I vaguely remember hearing something about EMU, pcap and AT commands, but I forgot the details. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG49y7MkyGM64RGpERAqgoAKC3fbu9bxw3tBRtrW/HYmzd6RyJUgCgtsDY gZ3zDK8jOw3G6wRVtKlPTxo= =sMTB -END PGP SIGNATURE-
Ezxd and asoc patch now in OE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Ezxd and the asoc patch are now in OE, and asoc is turned on in the a780 defconfig. share and enjoy, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG4QzcMkyGM64RGpERAs5dAJwJ7EtXE708dd1YNPiUFvmfvpxQqgCgnIRA FkQlncBBH6NfBrgs3jQWaPg= =BxT/ -END PGP SIGNATURE-
Battery charging in kernel 2.6
Hi, Can kernel 2.6 charge the battery, and if so, how can I make it do that? I vaguely remember hearing something about EMU, pcap and AT commands, but I forgot the details. regards, Koen
Ezxd and asoc patch now in OE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Ezxd and the asoc patch are now in OE, and asoc is turned on in the a780 defconfig. share and enjoy, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFG4Q1eMkyGM64RGpERAlRdAKCfBpTbF78qozVYKl3FVYPUgiS1lgCgiJZb ZVQk37iTNX8lRK68aT4sbJo= =iODf -END PGP SIGNATURE-
Re: enabling OABI_COMPAT in defconfigs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Antonio Ospite schreef: > On Fri, 24 Aug 2007 12:40:11 -0500 > "Michael Kramer" <[EMAIL PROTECTED]> wrote: > >> in the .config that Alex had shared the OABI_COMPAT and FPE_FASTFPE >> items are set, however >> in all of the defconfig- files included in from rev >> 2047 this is not set - is this something >> that could/should be updated, or is mine just a pathalogical case. >> > > Hi Michael, you are right, we have to add OABI_COMAPT and Floating point > emulation. We can wait for these "refinement" until after the commit > expected by Daniel, just to not encumber him in any way. No, you only have to add a FPE (be it fast- or nw-, nw is better), not a compat mode. If you need a compat mode, you compile mono wrong, which is easier to fix than handing out replacement kernels. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGz0DdMkyGM64RGpERAirAAKCJBRZ6GRbdb8EL3PmmIHe42MT9nwCgh+hq KJwG8I3SGlwuTrFezPgLNoY= =OCZ/ -END PGP SIGNATURE-
Re: Doubt about a780-mci code.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Antonio Ospite schreef: > On Fri, 20 Jul 2007 14:19:28 -0300 > "Daniel Ribeiro" <[EMAIL PROTECTED]> wrote: > >> Hi Antonio, >> >> IIRC our e680 code uses just one voltage too. >> >> I did some quick tests, and with my a780 and a sandisk 2gb TF card the >> pcap voltage regulator is always configured to provide 3.6V. >> I dont know exactly how this works, but i think that it is the card >> that says at which voltage it should work. >> >> I think it is good to support all the other voltages. How other >> projects deal with this? >> >> > > Ok, thanks. For now I leave the code as is, and I will give a look at > how this is handled in other projects. > > Expect a commit of the 2.6.22 changes soon. I will commit to the trunk. 2.6.22 breaks SD in a _very_ bad way. You can basically never resume if you have an sd card inserted that was mounted on suspend. I think it's better to wait for .23 than go through .22 hell. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGoy81MkyGM64RGpERAueeAJ4wftIqdnX0lJ6yFcM2GqRNsrsXZwCfZdLs vhMoeFQve+V0sJVd0NoebA8= =ofHQ -END PGP SIGNATURE-
Re: Get the right bdaddr in OpenEZX
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Ribeiro schreef: > 2007/7/3, Koen Kooi <[EMAIL PROTECTED]>: >> Sound like you want HAL + OHM > > I dont know how HAL+OHM works, i will read something about it.. Can > you point me to some newbie introduction? > > We need something that integrates all the GSM stuff and some > hardware/system related functions. > Can we integrate gsmd and OHM? OHM is pretty new and open to suggestions, so check http://ohm.freedesktop.org/wiki/ and make yourself heard on the ohm mailinglist :) regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGilyhMkyGM64RGpERAsnmAKCkQkuDvJYym4Wzs4ZORjbmpMSBrACgrPJ0 ZU/JOQYywYEwofaAs7VFdsA= =1FH8 -END PGP SIGNATURE-
Re: Get the right bdaddr in OpenEZX
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Ribeiro schreef: > 2007/6/30, Stefan Schmidt <[EMAIL PROTECTED]>: >> Besides that we still need some kind of hardware daemon, yet >> un-speced, which handles: >> >> o Get the BT address from gsmd and store it for BlueZ hcid and or >> other apps. >> o Get GPS data from gsmd and pass to gpsd >> o Audio routing (_very_ hard to get right) >> o... > > o Control BlueTooth power-off/power-on operations. > o Read power button state from BP and request AP shutdown. > o Send power-off request to BP when AP shutdown. > o Set the system date/time based on BP info when powering-on. > o Set system wake up events (for alarm, etc..) on BP. > o Sure there is more... :) Sound like you want HAL + OHM regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGik3mMkyGM64RGpERAv0pAJ9RABwsGFFieF9laFpkMjlMEQP90QCdGZTM L3bmOh/REGo+i8IEjSFQulM= =C+k9 -END PGP SIGNATURE-
Re: A1200 development
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Ribeiro schreef: > 2007/6/22, Konstantin Svist <[EMAIL PROTECTED]>: >> Update: looks like I forgot the patching.. :) >> Can anyone give me a quick rundown on using quilt? > "quilt push -a" for applying all patches on series. > >> Did my error happen because I didn't apply the patches or is it >> unrelated?] > It is unrelated. > >> Also, is there a quicker/easier way of asking questions to the group? >> Maybe an IRC channel or direct IM? > #openezx on irc.freenode.net > >> > Got an error - see http://nopaste.org/p/a1TqMmvb5 > This is an error when compiling gcc-cross, i have no clue on this one. > Try asking koen on IRC, he can help you better than i. 'dpkg-reconfigure dash' and choose 'bash' as link to /bin/sh regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGe7x1MkyGM64RGpERAizYAJ9yHHVRNd4xps41IezxWlh/XwLw7ACeIO4w ol7mmkaQmVUiXLt+LtrmP38= =dE2g -END PGP SIGNATURE-
Re: angstrom build fails on rootfs creation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Kramer schreef: I suspect this is http://bugs.openembedded.org/show_bug.cgi?id=2381 regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGWuL4MkyGM64RGpERAkVZAJ9WuMlHZa/RMn/+2HkT3uBHMRB3ZQCgj2wL d46+fbP0AbCj2G0bfvtmQWk= =t/Vk -END PGP SIGNATURE-
Re: Kernel updated in OE, new image for a780 available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Antonio Ospite schreef: > On Sat, 19 May 2007 11:47:58 +0200 > Koen Kooi <[EMAIL PROTECTED]> wrote: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Hi, >> >> The ezx kernel has been updated to r2011 in OE: >> http://lists.linuxtogo.org/pipermail/openembedded-commits/2007-May/005595.html >> >> You can find a zImage and matching rootfs at >> http://www.angstrom-distribution.org/unstable/images/a780/20070519/ >> >> share and enjoy, >> >> Koen > > Thanks koen, but for now we have to disable serial console in > CONFIG_CMDLINE, because the needed code has been disabled in compress.c > to achieve a faster boot. > > The attached patch could do that, but: > Note that drWyrM is also working on an optional kernel patch to > re-enable this code, so you may want to wait a bit ;P before changing > CONFIG_CMDLINE the way I proposed. I applied your patch, thanks! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGUZ/6MkyGM64RGpERAoiSAKCD/7dk2UnG2+L3kL9wI1Wh/cGwvACcCm4n 356ghOFslZOz1LdlpbRPVCw= =UEFJ -END PGP SIGNATURE-
Kernel updated in OE, new image for a780 available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, The ezx kernel has been updated to r2011 in OE: http://lists.linuxtogo.org/pipermail/openembedded-commits/2007-May/005595.html You can find a zImage and matching rootfs at http://www.angstrom-distribution.org/unstable/images/a780/20070519/ share and enjoy, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGTsfOMkyGM64RGpERAqm4AKCFbfR0dCuP+ETONVakyMQ1jIxngwCbBWIt u+iyM+3kdLuQ2Dn3nf5j9SQ= =Y9fE -END PGP SIGNATURE-
Re: bp tests.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Ribeiro schreef: > couldnt wait until tomorrow... > > partially confirmed. > > replaced opentapi with a > echo -e "atz\r" > /dev/mux4 > phone DO turn off. > > echo -e "at+usbstat=255,1\r" > /dev/mux4 > phone DO turn off. > > changed opentapi.c to send "atz\r" > phone DO NOT power off. > > so, at+usbstat is not keeping the phone on. i think that what keeps > the phone on is opening() some mux device. i will try opening() > individual mux devices and not writing anything to see if its a > particular mux device or anything else that opentapi does. > > koen, my crosstool guru, can oe build gdb-cross for arm7? i had gdb > for arm7tdmi but it was nokiafree.org and 3310 legacy age... if the arm7 is armv4 or armv5 you should be able to use the gdb-cross OE builds. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGSGmKMkyGM64RGpERAj8wAJ9z3khLZoZ66gwHZkQiOzt59fkrqQCfd9BN xpgJCCao6+Cp5OrRr/gxcEs= =zqIt -END PGP SIGNATURE-
Re: 2.6.21 branch development status.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Antonio Ospite schreef: > I was still not able to test an angstrom-x11-image, the calibration > program crashes... is this a userspace problem? koen? Yes, although I have to dig out my a780 to see why it crashes. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGOuJLMkyGM64RGpERAqJ8AKCJLe9WZvXKMTf0SqN7Z+3MfZ9x0wCguQ0d nUgTRayKvDUYjkc3otX4CJY= =s2tz -END PGP SIGNATURE-
Re: usb working on 2.6.21
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Ribeiro schreef: > hi all. > > i found some time to work on openezx today and changed the pxa27x_udc > patch to Rodolfo Giometti's version. His patch applies cleanly to > 2.6.21 and requires no other fixes. The Openzaurus version we were > using no longer compiles. > > anyone with a windows box can test if it works with rndis? (dont > forget to enable rndis support on .config) the .21 patches in svn (r1995) are in OE now, you can test a prebuilt kernel from http://www.angstrom-distribution.org/unstable/images/a780/20070501/ regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGN652MkyGM64RGpERAu/7AJ9Gkd4vjpIuEj/6v+KdBQT0RySzaQCffCso KhwKS/SFLqAo39kmYm5Eiho= =eD1L -END PGP SIGNATURE-
Re: Experimental 2.6.20.7 kernel added to OE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Koen Kooi schreef: > Hi, > > To stop people from inflicting massive amounts of pain on themselves with > crosstool, I've > added the 2.6.20.7 branch to OE: > http://lists.linuxtogo.org/pipermail/openembedded-commits/2007-April/005099.html And OE now has r1988[*] of the 2.6.21 branch as well. regards, Koen [*] the one with a working mux_cli -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGMvpVMkyGM64RGpERAslpAKC8vPuXqvs8Fub912sF66ZMH7O/CwCgjjQw wSgvIJg/uCuPtf5NLt0JKRQ= =2FLS -END PGP SIGNATURE-
Experimental 2.6.20.7 kernel added to OE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, To stop people from inflicting massive amounts of pain on themselves with crosstool, I've added the 2.6.20.7 branch to OE: http://lists.linuxtogo.org/pipermail/openembedded-commits/2007-April/005099.html regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFGLMQmMkyGM64RGpERAtVqAJ0bUrwP3paMmT5+ZppokOgLSZXSkQCfTnpn EHQDqa3ThwjFed9ctNVpE2k= =VRyA -END PGP SIGNATURE-
Re: FYI: PXA27x-Linux project
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] schreef: > Hello list, > > I am pleased to share the information about PXA27x-Linux project: > http://sourceforge.net/projects/pxa27x-linux/ Fun to see my and other peoples work being taken and have the copyright statements removed. A good way to start a community project. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFF//BZMkyGM64RGpERApUiAJ9twQB7QBTwyVDwDA7lDGwLFg+0EwCgt6sD 0I+PwMM1d8E+VnKzKBzQc/U= =UddC -END PGP SIGNATURE-
Re: Unable to get the mux devices to work on A780/ezx9
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Willmann schreef: > On Mon, 26 Feb 2007 18:51:18 +0100 > Koen Kooi <[EMAIL PROTECTED]> wrote: > >> Daniel Willmann schreef: >> >>> In my experience it was often not enough - especially with debug >>> output enabled. On our dev phone I moved the initscript to the >>> first place even before udev (which means you have to add the muxN >>> devices to the static dev dir). >> That's the reason I decided to let it start after udev, it's just a >> small change to OE to make it start at s0[1] and have the muxN >> devices statically present[2]. > > I have verified that this patch builds a working userspace for the E680 > (and A780) phones. > > Following changes: > * Move opentapi initscript to first position and add/correct .bb > metadata > * Call start-stop-daemon with --background and sleep for 15 seconds > This is done because opening the mux devices takes ages and we don't > want udev to be started (taking us away the static mux devices) too > early. > * Add info to device-table-minimal > * conf/machine/ changes. We now only have a780.conf for all devices. I committed the patches in seperate commits, and I forgot to credit you for the second one, sorry. Anyway, the patches are in. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFF5/ubMkyGM64RGpERArMkAKCUXaFaWEwlhDvwCT57r8MKxIwNXQCgvRya R1x2zDIxOoFHjUcpBLkRpDg= =he57 -END PGP SIGNATURE-
Re: Unable to get the mux devices to work on A780/ezx9
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Willmann schreef: Last step is to open the mux device as one on the first steps you do in userspace. There are still many timing problems. >>> Is the default startup order provided by the OE package sufficient >>> (rcS.d/S04opentapi)? I am still getting timeouts and the phone >>> powers down quickly after startup. >> Daniel, can you comment here? This was mainly your area. > > In my experience it was often not enough - especially with debug output > enabled. On our dev phone I moved the initscript to the first place > even before udev (which means you have to add the muxN devices to the > static dev dir). That's the reason I decided to let it start after udev, it's just a small change to OE to make it start at s0[1] and have the muxN devices statically present[2]. regards, Koen [1] http://www.openembedded.org/repo/org.openembedded.dev/packages/ezx/opentapi_svn.bb [2] http://www.openembedded.org/repo/org.openembedded.dev/files/device_table-minimal.txt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFF4x4WMkyGM64RGpERAmDwAJ9zwMr6OawtteKQ3Ei+Bd4tIHMbrgCgpxD4 o+hPBriK5jOF5FvpKzTqIDk= =gMp3 -END PGP SIGNATURE-
Re: Unable to get the mux devices to work on A780/ezx9
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan Schmidt schreef: > Hello. > > On Mon, 2007-02-26 at 14:59, Jeremy Lain? wrote: >>> Once the 2.6 kernel is flashed you need to pres the power on button >>> for something like 20s (until the LCD shows kernel messages) to get t >>> he phone through handshake. 2.4 only needs some seconds. >> OK, it is indeed incredibly slow, I wonder why. > > No optimizations until now. > >>> Last step is to open the mux device as one on the first steps you do >>> in userspace. There are still many timing problems. >> Is the default startup order provided by the OE package sufficient >> (rcS.d/S04opentapi)? I am still getting timeouts and the phone powers >> down quickly after startup. > > Daniel, can you comment here? This was mainly your area. > >> By the way, there are some typos in the init script, the attached >> patch should improve things. > > Koen, can you care about update it in oe? Done, thanks for the patch. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD4DBQFF4wW5MkyGM64RGpERAhRIAJ9+S0P22N8GjpPuHKD7HN9Phr84qQCY/FJU 1BFexRYurZRlBBUwkQeR9A== =risi -END PGP SIGNATURE-
Re: [ANNOUNCE] 2.6.16.13-ezx8 release
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan Schmidt schreef: > Hello. > > It's time again. I picked up all recent patches and release a > patchset. > > http://www.openezx.org/download/patches-2.6.16-2.6.16.13-ezx8.tar.bz2 This in in OE now, including the xscale cache workaround, gcc4 fixes and an updated defconfig. A precompiled image with opentapi can be found at http://www.angstrom-distribution.org/unstable/images/20070120/a780/ regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFszkQMkyGM64RGpERAvGpAKCKP2AjDDELUAGq7tJ/dOfkOmu2cgCfSOZr 2qOB3VE0xCmBnzkaCJVYubI= =ktkI -END PGP SIGNATURE-
Re: [ANNOUNCE] 2.6.16.13-ezx8 release
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan Schmidt schreef: > o I put up a pending patches folder on my people account. Patches > inside are considered for merging, but have not been tested yet or > were even not able to apply at all. > http://people.openezx.org/stefan/patches/pending-patches/ Could you put the 2 gcc4 fixes I sent in after ezx7 there as well? regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFsy+JMkyGM64RGpERAjXeAKCaiDYGwR8I6G4yneMpBJjiHmKB0gCfURU8 Uba8Yg0qS9pD00pz9fd7j6g= =uSHz -END PGP SIGNATURE-
Re: mux_cli 2.6: Phone stays alive
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan Schmidt schreef: > Hello. > > It's mostly done. We have now a mux_cli driver for 2.6 which keeps the > phone, together with opentapi, alive. yay! > Still no phone calls possible, but we are on the way fixing this up. > > The remaining problem was the use of the tty flip buffer. They way > Motorola used it within the 2.4 driver is no more doable with 2.6. > > We changed it to use a kernel implemented list instead and a function > to append the data. This way it works. yay! > The last word how to implement this is of course not spoken yet. It's > a question how we have to add our usb-serial glue to the ts0710 line > descipline Harald is developing. > > Our next steps are fixing up mux_cli and opentapi to be able to doing > regular AT commands. Perhaps even phone calls if the BP is handling > voice on their own for calls. > > You can find the patches here: > http://people.openezx.org/stefan/patches/mux-cli/ > > They will be merged into ezx8 which I hopefully will release during > the weekend. yay! keep up the good work :) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFricSMkyGM64RGpERAsl+AJsHqS9XJupYaGhVo+RHmuwj2k4LAgCfSURu QI8SpiO5C5dhoMIMa1nLpnY= =vngV -END PGP SIGNATURE-
Re: problem when porting udc code!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Harald Welte schreef: > On Thu, Jan 11, 2007 at 10:31:23PM +0800, 王永来 wrote: >> hello >> I have compiled the udc code successfully,but after the kernel booting,I >> just see there are a lot of interrupts says "ep0 Busy",it's in handle_ep0 >> function,so I tracked the kernel,and found the interrupt is introduced by >> ep0 FIFO ERROR,but even if I clear that,I would found the same >> error.Iguessed that maybe caused by BP(I am not familiar with >> BP),maybe BP send >> siganl to UDC? Is that with out without http://rpsys.net/openzaurus/patches/usb_add_epalloc-r3.patch applied? PXA270 udc is pretty buggy and needs some patching. Note that g_ether is broken when using it with MS windows, but works with linux. regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFpnumMkyGM64RGpERAqEsAKCLDWc1+lFvNrrIxgc7niU6dNS7ugCfdEyB LUfa4xBsMO8SULCs4hFpsBo= =fg+J -END PGP SIGNATURE-
Re: Good News:Me E2 boots kernel 2.6.20_rc2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Koen Kooi schreef: > Stefan Schmidt schreef: >> Hello. > >> On Wed, 2007-01-03 at 10:45, ?? wrote: >>>> Without any EZX patches? Interesting. >>> yes,the patch is very small,and simlar with EZX7,maybe just the codes about >>> UART is different.I dont know why uart couldn't work so I just comment it >>> out and use LCD to print msgs.And found the patch to head.S is not >>> needed.Ididn't do any change on it and E2 boots well. >> Short sidenote: > >> The patches against 2.6.20-rc2 are now available at dotmonkeys openezx >> account: > >> http://people.openezx.org/dotmonkey/patch/ > >> They don't base on the ezx7 patchset. Only 2.6.19 + 2.6.20-rc2-patch >> are needed. > >> Just keep in mind that a gcc >= 3.4.4 is needed for a kernel >= >> 2.6.18. This means it does not work with ezx-crosstool, but works fine >> with the oe crosstoolchain. :) > > http://www.openembedded.org/viewmtn/revision.psp?id=b70835047eaf8f744110cd87ee076c90d4f0950f > > so in your local.conf: > > MACHINE=a1200 > DISTRO=angstrom-2007.1 > > then do 'bitbake virtual/kernel' > > That will give you something like > http://www.angstrom-distribution.org/unstable/images/20070104/a1200 *cough* I didn't have enough coffee today. MACHINE=rokr-e2 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFnigfMkyGM64RGpERAh/dAJ9oXkdSEynTDCFv4Z6HUJjXkmFvgwCgnXQQ tBGKV/frJRIwjXitrxuvW6Q= =j8lw -END PGP SIGNATURE-
Re: Good News:Me E2 boots kernel 2.6.20_rc2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan Schmidt schreef: > Hello. > > On Wed, 2007-01-03 at 10:45, ?? wrote: >>> Without any EZX patches? Interesting. >> yes,the patch is very small,and simlar with EZX7,maybe just the codes about >> UART is different.I dont know why uart couldn't work so I just comment it >> out and use LCD to print msgs.And found the patch to head.S is not >> needed.Ididn't do any change on it and E2 boots well. > > Short sidenote: > > The patches against 2.6.20-rc2 are now available at dotmonkeys openezx > account: > > http://people.openezx.org/dotmonkey/patch/ > > They don't base on the ezx7 patchset. Only 2.6.19 + 2.6.20-rc2-patch > are needed. > > Just keep in mind that a gcc >= 3.4.4 is needed for a kernel >= > 2.6.18. This means it does not work with ezx-crosstool, but works fine > with the oe crosstoolchain. :) http://www.openembedded.org/viewmtn/revision.psp?id=b70835047eaf8f744110cd87ee076c90d4f0950f so in your local.conf: MACHINE=a1200 DISTRO=angstrom-2007.1 then do 'bitbake virtual/kernel' That will give you something like http://www.angstrom-distribution.org/unstable/images/20070104/a1200 regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFniRZMkyGM64RGpERAtrdAJ90Apj5qahRK2o2+UZQmJKyHwmRpwCfX3G5 HUuw4n/KFyVwWsLtV3SPAJ0= =gACi -END PGP SIGNATURE-
Re: [Gpe-list] poritn gpe to motorola a1200 ( cross-compiler query )
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ritesh Khadgaray schreef: > On Wed, 2007-01-03 at 13:29 +0100, Koen Kooi wrote: > Ritesh Khadgaray schreef: >>>> Heya, >>>> >>>> Has anyone built cross compiler based on gcc 4.x series ? > Yes, using openembedded. > >> Thanks. > >> Finally hit : >> http://kegel.com/crosstool/current/doc/crosstool-howto.html#arm-iwmmxt >> Will check if this script helps me build gcc cross compiler. I do not recommend using crosstool to generate a toolchain to build multiple apps. You're much better off using openembedded to build gpe. With openembedded it's a matter of saying 'bitbake gpe-image' to build a complete rootfs with gpe. If you want to use iwmmxt or ntpl you can use DISTRO=angstrom-2007.1 with MACHINE=a780 regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFnV6sMkyGM64RGpERAlZAAJ9S+KWqWuaRCNFzeLH9YYs6WFIEaQCbBMXM ydZK5z+UYnOk3jdJU094r0I= =Dm6Z -END PGP SIGNATURE-
Re: Who works on E2 please give me a reply~Now I my E2 boots kernel 2.6.20!~
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 王永来 schreef: > Hello. > I need a root filesystem to test drivers,give me a reply if you has done > it or you can do well in that. Try one from http://www.angstrom-distribution.org/unstable/images/20070101/a780/ These were built with openembedded with MACHINE="a780" and DISTRO="angstrom-2007.1" regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFm97fMkyGM64RGpERAj9gAJ9dpwBrkej/odAtZ/5Zt64oNCZuDgCguwYk gsLB8SKsrppmaVLqnxgaV08= =wYeB -END PGP SIGNATURE-
Re: [Gpe-list] poritn gpe to motorola a1200 ( cross-compiler query )
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ritesh Khadgaray schreef: > Heya, > > Has anyone built cross compiler based on gcc 4.x series ? Yes, using openembedded. regards, Koen > > On Sun, 2006-11-12 at 20:01 +0100, Florian Boor wrote: >> Hi, >> >> Ritesh Khadgaray wrote: >>> i'am very interested in porting gpe to motorola a1200. I was looking >>> around to see if there a platform that i can use to build gpe and test >>> the same. Something like a emulator, where i can run gpe application. >> sounds good, i managed to make GPE run on a A780 some days ago. Not perfect >> but >> usable to some extend at least. I have an A1200 as well and therefore have >> some >> interest in this myself... >> >> You can run GPE applications on a PC just compiling them natively. If you >> want >> to emulate the device (screen size, buttons) you should take a look at Xoo >> (http://projects.o-hand.com/xoo/). If you want to have a more complete system >> emulation you could use Qemu and build a complete filesystem for it with e.g. >> OpenEmbedded. >> >> Greetings >> >> Florian >> >> >> >> >> >> ___ >> Gpe-list mailing list >> [EMAIL PROTECTED] >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/gpe-list -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFm6GxMkyGM64RGpERAiPWAJ9+ZsSloNQ98wMBH1R8HTONXGWAjwCaAj+i dSN9YcH9Bd/aY0K5QhFeTT4= =LKo6 -END PGP SIGNATURE-
Re: tapisrv command set
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Harald Welte schreef: > On Mon, Dec 18, 2006 at 02:38:48PM +0100, Florent THIERY wrote: >> In fact i'm realizing that a lot of listed commands (on the wiki) aren't >> described in the pdf file. Which is about the G24: >> http://www.avnet.co.za/New_Products/Motorola/GSM/g24/g24_Module.htm >> >> I can add generic information, in order to add a human readable explanation >> of a related command set, assuming that the command is the same for EZX. >> >> ex: >> >> AT+CCWA: >> AT+CCWA=1,%d,1 >> AT+CCWA=,2 >> AT+CCWA:%8D,%8D >> >> This command controls the Call Waiting supplementary service, including >> settings and querying of the network. When the Call Waiting indication is >> enabled and >> there is a waiting call, a +CCWA: indication is sent from the BP to the AP. >> >> The questions are: >> - how verbose should i go? >> - what if it's only G24 specific info? > > please don't copy / re-phrase commands that are specified in GSM TS > 07.07 (such +CCWA). Unless motorola messed things up and do different things than 07.07 specifies... regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFhrkJMkyGM64RGpERAnsEAJ4mpdoU8uiBNeWkh7JkmXrp2DuwewCeNUwW mT4di4k2oV595jNoU84JocY= =9vAM -END PGP SIGNATURE-
Re: Weekendly hacking report #3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Willmann schreef: > After that we worked on a tapisrv reimplementation that does only the > minimal thing to keep the phone powered. > The result is in http://svn.openezx.org/trunk/src/userspace/opentapi/ It's now available in OE as well, so people can avoid crosstools hell: http://www.openembedded.org/filebrowser/org.openembedded.dev/packages/ezx and as a binary for the Ångström distribution: http://www.angstrom-distribution.org/repo/?action=details&pnm=opentapi regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFhlx6MkyGM64RGpERApI8AJ4rEfzHr3QxNAv6k0tOWJfRG0WzGwCfcorM DPZTRABq/EjqjqqnEWodQtE= =WK9Y -END PGP SIGNATURE-
Re: Another hacking weekend report.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan Schmidt schreef:
> Hello.
>
> On Wed, 2006-12-13 at 02:21, Harald Welte wrote:
>> On Tue, Dec 12, 2006 at 11:07:31AM +0100, Stefan Schmidt wrote:
>>> 2.4 and Tapisrv:
>>>
>>>
>>> The most interesting information we got this sunday is that a userspace
>>> program,
>>> tapisrv, is needed in 2.4 to keep the phone alive.
>>>
>>> If the tapisrv can not connect to the mux_cli the device will still turn
>>> off.
>>>
>>> We tested this with our selfcompiled kernel and an init=/bin/bash kernel
>>> commandline. Some further investigations offered us tapisrv as the needed
>>> userpsace program.
>>>
>>> We have not yet captured the communication to find the magic needed to be
>>> send.
>>> This is our next step.
>> thanks, this is defintely a most interesting discovery. This means
>> that there is at least one higher level 'watchdog' that we didn't know
>> of. This might be the same problem that we've experienced with the
>> "phone turns off" and so far attributed to some problem in AP-BP
>> handshake implementation. However, it also might be the case that those
>> are actually two different problems, resulting in the same phenomenon
>> ('phone turns off').
>
> Yeah, two different problems with the same effect are ugly to debug.
> We keep this in mind.
Which will bring the question "How will we solve this inside the openezx
framework?". I
think we'll need our own daemon at least till gsmd gets released.
regards,
Koen
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFFf9waMkyGM64RGpERAp7PAJ4j/DEubjxMVXZCITDJKr7MdlVUcwCghxx4
D+hLSc0m+nIVpFEsJPZH/AU=
=OvAa
-END PGP SIGNATURE-
Re: Another hacking weekend report.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan Schmidt schreef: > Hello. > > Sunday we had another full day of hacking around the EZX problems. Great work! > 2.4 and Tapisrv: > > > The most interesting information we got this sunday is that a userspace > program, > tapisrv, is needed in 2.4 to keep the phone alive. I guess we don't have the source for tapisrv? I did come across http://inhex.net/dion/tapi.tar.gz, which seems to be able to monitor tapisrv communication. > 2.6 status: > --- > > Some other hacking was needed to get the mux_cli port working built into a 2.6 > kernel. Just minor changes and we will offer another small patch on top of > Harald's incomplete mux_cli for it. into 2.6.19? regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFfoTQMkyGM64RGpERAgwyAJ44buLfq72qVQcI/R2KBkYLKjSI3ACfV1Zm CzjRn5cMMFiKGRsG3kNektE= =A9bb -END PGP SIGNATURE-
Re: Hacking weekend efforts. Testpads, JTAG, passthrough mode
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan Schmidt schreef: > Hello. > > On Tue, 2006-12-05 at 11:00, Stefan Schmidt wrote: >> This issue still remains. But we have no a sweet little tool to speed >> up the testing. >> >> http://svn.openezx.org/trunk/src/passthrough-mode/ > > I can add another tool for testing this: > > http://people.openezx.org/stefan/code/passthrough.tar.gz > > It's a hacked boot_usb sent to me by some kind developer. Big thanks > for it. I need to compile that for my host, not the target (a780), right? > It connects to the usb device and is able to send and _recieve_ frames > to the BP. It uses code from the 2.6 ported driver for this. > > Just frames yet, no AT commands. So it needs demuxing in userspace? regards, Koen -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFdWy/MkyGM64RGpERArkiAKCtWh1hdrj2l4T/IfyLILzPoe2Z9ACePfi9 IV3qwH97I+rQnsfwAtyYbKM= =R5/k -END PGP SIGNATURE-
