| 00:09.35 | jonwil | wlan on which phone? |
| 00:29.21 | *** join/#openezx flyhorse|linux (n=flyhorse@219.130.83.191) |
| 02:12.32 | *** part/#openezx BadCluste1 (n=badclust@190.50.209.50) |
| 02:39.40 | *** join/#openezx flyhorse1 (n=flyhorse@58.252.146.25) |
| 03:08.11 | *** join/#openezx flyhorse2 (n=flyhorse@219.130.83.191) |
| 03:50.23 | *** join/#openezx WM (i=wyrm@20158255223.user.veloxzone.com.br) |
| 04:46.00 | *** join/#openezx CIA-23 (n=CIA@208.69.182.149) |
| 06:39.59 | *** join/#openezx Guanjun (n=novell@61.14.130.203) |
| 06:41.52 | Guanjun | hello,every one.Does any one know the format of the binary zIamge on the website http://www.openezx.org/index.html? How to test the zImage? |
| 06:48.00 | Guanjun | I am running the Image 'zImage-2.6.21-ezx11-a1200' under qemu, it can not boot. |
| 07:09.30 | *** join/#openezx drath_ (i=vmaster@p5B07D22A.dip.t-dialin.net) |
| 07:30.22 | *** join/#openezx CIA-23 (n=CIA@208.69.182.149) |
| 07:30.39 | Guanjun | There is no initrd? |
| 07:56.24 | flyhorse2 | . |
| 07:56.53 | flyhorse2 | u must use it on a moto a1200 or a a1200 emu |
| 08:19.33 | *** join/#openezx flyhorse1 (n=flyhorse@58.252.146.21) |
| 08:21.24 | Guanjun | It can not be tested on a virtual hardware platform? |
| 08:27.09 | Guanjun | I try to run it with the command 'qemu-system-arm -pflash zImage-2.6.21-ezx11-a1200 -pflash zImage-2.6.21-ezx11-a1200 -kernel zImage-2.6.21-ezx11-a1200 -M mainstone -m 200',now the error message is : 'can not open root device,can not mount root fs on the root device'. |
| 08:55.33 | *** join/#openezx jonwil (n=jonwil@121.221.215.28) |
| 08:55.40 | jonwil | hi |
| 09:07.45 | *** join/#openezx flyhorse2 (n=flyhorse@219.130.83.191) |
| 09:28.48 | *** join/#openezx Guanjun (n=novell@61.14.130.203) |
| 09:33.00 | *** join/#openezx CIA-45 (n=CIA@208.69.182.149) |
| 09:38.42 | *** join/#openezx ade|desk (n=adavey@194.200.143.249) |
| 09:48.38 | *** join/#openezx yansa (n=yans@host-89-167-37-237.pronet.lublin.pl) |
| 10:22.52 | Hopscotch | good morning |
| 10:29.22 | *** join/#openezx flyhorse1 (n=flyhorse@58.252.146.21) |
| 10:30.58 | *** join/#openezx BadCluster (n=badclust@190.50.209.50) |
| 10:36.49 | jonwil | hi all |
| 10:39.14 | *** part/#openezx Guanjun (n=novell@61.14.130.203) |
| 10:40.35 | *** part/#openezx BadCluster (n=badclust@190.50.209.50) |
| 10:43.54 | *** join/#openezx WyrM (i=wyrm@201008081141.user.veloxzone.com.br) |
| 10:53.27 | jonwil | hi |
| 10:55.59 | WyrM | Hi jonwil. |
| 10:57.34 | *** join/#openezx flyhorse1 (n=flyhorse@219.130.83.191) |
| 11:01.46 | jonwil | if I had the skills (and the gear) I would open the phone and read the flash chip directly |
| 11:34.20 | *** join/#openezx florian (n=fuchs@217.146.132.69) |
| 11:39.31 | *** join/#openezx ao2 (n=u@2001:1418:117:0:0:0:0:1) |
| 11:41.26 | jonwil | hi |
| 11:45.18 | ao2 | hi |
| 11:58.10 | florian | heh |
| 11:59.55 | jonwil | heh yeah if anyone actually cared about those phones |
| 12:08.34 | jonwil | so far very few people seem to want to hack MOTOMAGX |
| 12:09.07 | jonwil | except for some limited "I want newer firmware/generic non-carrier firmware/foriegn languages" tyoe "hacking" being done |
| 12:09.19 | jonwil | which is really much the same as has been done for old moto p2k os before |
| 12:09.21 | jonwil | and not really hacking |
| 12:29.58 | *** join/#openezx WM|work (i=c88e3a12@gateway/web/ajax/mibbit.com/x-84eff8d04618caee) |
| 12:30.16 | WM|work | Hi. |
| 12:31.34 | jonwil | hi |
| 13:28.43 | *** join/#openezx yansa (n=yans@host-89-167-37-237.pronet.lublin.pl) |
| 13:37.26 | *** join/#openezx goxboxlive (n=goxboxli@134.84-48-212.nextgentel.com) |
| 13:42.34 | WM|work | jonwil: thats not true. |
| 13:43.12 | WM|work | jonwil: but currently the way to kernel hacking on Magx involves reflashing the bootloader area. |
| 13:43.49 | WM|work | If you dont mind risking to brick your phone i can prepare an "opened" bootloader for you. |
| 13:44.19 | WM|work | err, didnt saw the quit message :) |
| 13:46.14 | *** join/#openezx LuitvD (n=luitvd@beigetower/luitvd) |
| 13:48.25 | WM|work | ao2: see the message from Nicolas Pitre to arm-linux ML with "Re: SDIO Uart driver" on Subject. Your issues with the mmc driver may be related.. |
| 13:49.08 | LuitvD | mornin' |
| 13:50.46 | WM|work | LuitvD: good morning. |
| 13:58.24 | *** join/#openezx yansa_ (n=yans@host-89-230-209-154.lublin.mm.pl) |
| 14:17.30 | *** join/#openezx yansa__ (n=yans@host-89-167-37-237.pronet.lublin.pl) |
| 14:19.07 | ao2 | WM|work, I'll give a look. Is it the one about probing order? |
| 14:20.27 | *** join/#openezx BadCluster (n=badclust@200.26.114.37) |
| 14:20.36 | ao2 | anyway, wlan card shows some life, but I havent' tried it in action yet because the battery has discharged. |
| 14:20.58 | WM|work | ao2: It is about a limitation on the current code. |
| 14:21.17 | WM|work | it stops the code flow after detecting a sdio uart card. |
| 14:22.06 | WM|work | it may be the case, try disabling all the sdio code before trying MMC stuff. The main issue will probably be solved on mainline soon. |
| 14:22.08 | ao2 | so that could be the reason why it doesn't get to storage card, I see |
| 14:23.22 | ao2 | I disabled SDIO UART, but plain SDIO is part of the standard MMC stack, so even if I disable wlan driver the SDIO cardwill be found anyway |
| 14:24.56 | WM|work | ao2: hack the probing code to make it NOT work ;) Its generally easier than trying to make it work. |
| 14:25.09 | WM|work | Or use an older kernel, without sdio. |
| 14:25.17 | ao2 | I could give a try to 2.6.21 just to prove that MMC card _can_ be detected, do you think it is worth the effort? |
| 14:25.30 | ao2 | yes, ok, we thought the same thing :) |
| 15:22.37 | *** join/#openezx tombhadAC (n=tombhad@pD95DFFB5.dip.t-dialin.net) |
| 15:42.16 | *** join/#openezx Guanjun (n=novell@124.254.52.239) |
| 15:42.31 | *** part/#openezx Guanjun (n=novell@124.254.52.239) |
| 15:49.29 | *** join/#openezx TimRiker (n=timr@99.200.77.86) |
| 18:03.53 | *** join/#openezx pleemans (n=peter@d51A5E76A.access.telenet.be) |
| 18:08.21 | *** part/#openezx ade|desk (n=adavey@194.200.143.249) |
| 18:10.29 | *** join/#openezx LuitvD_ (n=luitvd@beigetower/luitvd) |
| 18:56.41 | *** join/#openezx hendryjh_ (n=jhendry@pool-72-83-104-182.washdc.fios.verizon.net) |
| 19:12.01 | *** join/#openezx stefan_schmidt (n=stefan@sirius.lasnet.de) |
| 19:17.46 | *** part/#openezx BadCluster (n=badclust@200.26.114.37) |
| 19:22.56 | *** join/#openezx tombhadAC (n=tombhad@pD95DDAE4.dip.t-dialin.net) |
| 19:35.01 | *** join/#openezx AndRAY (n=Miranda@fw1-4.itcn.ru) |
| 19:40.02 | *** join/#openezx tombhadAC (n=tombhad@pD95DFD44.dip.t-dialin.net) |
| 19:47.58 | *** join/#openezx drath_ (i=vmaster@p5B07DDAE.dip.t-dialin.net) |
| 19:55.53 | *** join/#openezx flo_lap (n=fuchs@f049168134.adsl.alicedsl.de) |
| 20:17.17 | *** join/#openezx tombhadAC (n=tombhad@pD95DD6AF.dip.t-dialin.net) |
| 20:32.25 | *** join/#openezx WM (i=wyrm@201008191147.user.veloxzone.com.br) |
| 20:35.04 | ds2 | oddesting happened on the A780 with the Asian firmware... it seems to work perfectly on the CNG/ATT network in the US but not with the TMO network |
| 20:46.16 | *** join/#openezx BadCluster (n=badclust@168.226.10.75) |
| 21:27.18 | *** join/#openezx flo_lap (n=fuchs@f049168134.adsl.alicedsl.de) |
| 21:38.08 | *** join/#openezx flo_lap (n=fuchs@f049168134.adsl.alicedsl.de) |
| 21:38.36 | *** join/#openezx BadCluster (n=badclust@168.226.10.75) |
| 21:38.37 | *** part/#openezx BadCluster (n=badclust@168.226.10.75) |
| 22:08.56 | *** join/#openezx flo_lap (n=fuchs@f049168134.adsl.alicedsl.de) |
| 22:19.44 | *** join/#openezx agd5f_ (n=alex@c-69-143-24-183.hsd1.va.comcast.net) |
| 22:20.32 | *** join/#openezx agd5f (n=alex@c-69-143-24-183.hsd1.va.comcast.net) |
| 23:20.33 | *** join/#openezx jonwil (n=jonwil@121.221.215.28) |
| 23:21.08 | jonwil | hi |
| 23:22.10 | flo_lap | hi jonwil |
| 23:22.46 | jonwil | still trying to find out just what I can DO with this new Z6 |
| 23:26.21 | flo_lap | yes indeed |
| 23:26.38 | flo_lap | unluckily i lack the time to do so... |
| 23:36.54 | *** join/#openezx agd5f (n=alex@c-69-143-24-183.hsd1.va.comcast.net) |