| 00:15.55 | *** join/#qi-hardware wolfspraul (~wolfsprau@221.220.188.212) |
| 00:20.07 | *** join/#qi-hardware LunaVorax (~LunaVorax@ABordeaux-651-1-162-97.w90-5.abo.wanadoo.fr) |
| 00:41.10 | *** join/#qi-hardware guanucoluis (~luis@200.127.180.65) |
| 01:09.07 | qi-bot | The build was successful: http://fidelio.qi-hardware.com/~xiangfu/build-nanonote/openwrt-xburst.minimal-20120827-2243 |
| 01:16.49 | *** join/#qi-hardware Ayla (~paul@pc-40-79-120-200.cm.vtr.net) |
| 01:25.17 | *** join/#qi-hardware panda|x201 (~hzhang@123.114.46.197) |
| 01:30.02 | *** join/#qi-hardware rejon (~rejon@jp.fabricatorz.com) |
| 01:47.55 | *** join/#qi-hardware xiangfu (~xiangfu@fidelio.qi-hardware.com) |
| 02:08.53 | *** join/#qi-hardware nikescar (~nikescar@114.199.131.108) |
| 02:36.33 | *** join/#qi-hardware Hoolxi (~Openfree@116.228.88.131) |
| 05:08.51 | *** join/#qi-hardware jekhor (~jek@leased-line-46-53-195-83.telecom.by) |
| 05:30.27 | *** join/#qi-hardware scientes (~scientes@unaffiliated/scientes) |
| 05:38.57 | *** join/#qi-hardware xiangfu (~xiangfu@fidelio.qi-hardware.com) |
| 06:20.43 | *** join/#qi-hardware jluis|work (~jpddb@83.247.136.72) |
| 06:24.51 | *** join/#qi-hardware porchao (~hato@eatkyo306096.adsl.ppp.infoweb.ne.jp) |
| 06:41.22 | *** join/#qi-hardware jluis|work (~jpddb@83.247.136.72) |
| 06:44.44 | *** join/#qi-hardware kilae (~chatzilla@109.205.205.99) |
| 06:46.16 | *** join/#qi-hardware rejon (~rejon@jp.fabricatorz.com) |
| 07:03.37 | *** join/#qi-hardware Textmode (~boneidle@adsl-syd-4-18.ozonline.com.au) |
| 07:28.40 | *** join/#qi-hardware Textmode (~boneidle@adsl-syd-4-18.ozonline.com.au) |
| 08:01.17 | *** join/#qi-hardware kuribas (~user@d54C43503.access.telenet.be) |
| 08:36.21 | *** join/#qi-hardware jurting (~jurting@ip-47-47-179-93.dialup.ice.net) |
| 08:41.21 | *** join/#qi-hardware GNUtoo (~gnutoo@ABordeaux-152-1-56-251.w82-125.abo.wanadoo.fr) |
| 08:56.58 | *** join/#qi-hardware Fallenou (~fallen@yozora-irc.net) |
| 09:36.57 | *** join/#qi-hardware Jay7 (jay@128-73-75-119.broadband.corbina.ru) |
| 09:43.26 | *** join/#qi-hardware jivs (~jivs@nat-sta-slph1.tvu.ac.uk) |
| 09:56.17 | *** join/#qi-hardware panda|x201 (~hzhang@116.213.117.66) |
| 10:00.42 | *** join/#qi-hardware GNUtoo (~gnutoo@ABordeaux-152-1-56-251.w82-125.abo.wanadoo.fr) |
| 10:10.59 | *** join/#qi-hardware jekhor (~jek@178.120.8.173) |
| 11:22.57 | larsc | mth: to be honest I have no idea, I guess it does this because everybody else does it as well |
| 11:43.19 | mth | that was exactly my reason for doing it for the JZ4770 :) |
| 11:44.49 | wpwrak | cargo cult programming at its finest ;-) |
| 11:45.09 | wpwrak | (and no, i don't know either :) |
| 12:11.03 | *** join/#qi-hardware cladamw (~adamwang@host-184.183-235-182.cable.dynamic.kbtelecom.net) |
| 12:20.26 | whitequark | wpwrak: just like the cache tricks magic in the initialization code |
| 12:20.32 | whitequark | I've stripped them and nothing has changed |
| 12:21.29 | wpwrak | those mistreated caches will wait for you in the afterlife ;-) |
| 12:21.50 | whitequark | haha |
| 12:22.20 | whitequark | imagines several poor cache lines in the Charon's boat |
| 12:46.11 | mth | gdb aborts the process I'm debugging because it allegedly receives signal 128 pretty close to startup |
| 12:46.34 | mth | but if I run the process outside gdb it starts up fine, the thing I'm debugging happens much later |
| 12:46.42 | mth | and there doesn't seem to be a singal 128 |
| 12:46.52 | mth | s/singal/signal |
| 12:46.53 | qi-bot | mth meant: "and there doesn't seem to be a signal 128" |
| 12:48.54 | *** join/#qi-hardware aisa (~a@209.234.140.58) |
| 12:55.20 | *** join/#qi-hardware LunaVorax (~LunaVorax@cau33-2-82-227-183-10.fbx.proxad.net) |
| 12:55.49 | *** join/#qi-hardware aisa (~a@209.234.140.58) |
| 13:06.19 | *** join/#qi-hardware LunaVorax (~LunaVorax@cau33-2-82-227-183-10.fbx.proxad.net) |
| 13:11.13 | *** join/#qi-hardware erikkugel (~ekugel@216.183.91.254) |
| 13:12.33 | mth | maybe gdb is seeing ghosts: the signal does not come from __send_signal in the kernel |
| 13:13.17 | mth | could it be a tortured cache line? |
| 13:14.03 | DocScrutinizer51 | is that process maybe skype? ;-P |
| 13:14.41 | mth | no, gmenu2x |
| 13:30.55 | mth | it is certainly something inside gdb: when trying to attach to a non-existing pid, the same "signal" occurs |
| 13:33.19 | lindi- | mth: on ARM? |
| 13:35.16 | *** join/#qi-hardware urandom__ (~user@p548A3B05.dip.t-dialin.net) |
| 13:35.17 | mth | on MIPS: JZ4770 |
| 13:35.19 | Fallenou | wolfspraul: I've just read an email from you dating from 2009 about marvell combo chip 88w8688 , do you have more intel about what bugs are encountered or what's wrong with the chip etc ? |
| 13:35.34 | Fallenou | or some guy I could shoot an email about this chip ? |
| 13:35.35 | mth | but it happens on JZ4740 too |
| 13:35.38 | lindi- | mth: ok, no such hardware here |
| 13:35.44 | lindi- | mth: it doesn't happen on arm or x86? |
| 13:36.04 | Fallenou | on my daily job we happen to use this chip (connected to an OMAP 3630), and indeed we have a lot of troubles with bluetooth :/ |
| 13:36.13 | Fallenou | I am referring to this email http://lists.en.qi-hardware.com/pipermail/discussion/2009-November/001108.html |
| 13:36.39 | mth | I don't have an ARM device, on my x86_64 desktop everything is fine but that's an entirely different system (different gdb version, glibc vs uClibc) |
| 13:37.50 | mth | it even happens on /bin/ls (busybox), so it's not related to the application that is being debugged |
| 14:00.20 | *** join/#qi-hardware aisa (~a@173-10-243-253-Albuquerque.hfc.comcastbusiness.net) |
| 14:06.05 | *** join/#qi-hardware jurting (~jurting@ip-47-47-179-93.dialup.ice.net) |
| 14:47.06 | *** join/#qi-hardware hypermodern_ (~pete@netblock-68-183-242-2.dslextreme.com) |
| 14:51.53 | wolfspraul | Fallenou: oh my, no I don't :-) |
| 14:52.11 | wolfspraul | that's a looong time ago and I learned many things, primarily to stay away from such chips :-) |
| 14:53.17 | *** join/#qi-hardware DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg) |
| 14:53.21 | wolfspraul | if you are still fixing bugs on that chip today, that's itself a bug already. but other than such non-helpful 'suggestions' I don't have anything, sorry about that |
| 14:54.19 | Fallenou | yes marvell shipped a new firmware a few days ago to us |
| 14:54.29 | Fallenou | and it has a lot of regressions |
| 14:54.30 | Fallenou | it's a nightmare |
| 14:54.38 | wpwrak | ;-) |
| 14:55.46 | wolfspraul | all I can say about these things will not help you |
| 14:56.17 | wpwrak | there's indeed a bit of a message in "oh, we'll fix [many flaws] in the next firmware update", when that comes for a chip that's been around for so many years :) |
| 14:56.18 | wolfspraul | but: GOOD LUCK! |
| 14:56.58 | wolfspraul | wpwrak: the chip was never designed and made for companies like fallenous, imho |
| 14:57.12 | wolfspraul | so by now both marvell and fallenou's company are in a loose-loose situation on this |
| 14:57.38 | wolfspraul | fallenou can just "try his best" and be happy about his pay check, which is hopefully comforting... |
| 14:58.03 | wolfspraul | Fallenou: don't start drinking :-) |
| 14:58.10 | Fallenou | ahah I won't |
| 14:58.15 | Fallenou | it's just annoying |
| 14:58.25 | wolfspraul | you are paid for the annoyance? |
| 14:58.28 | wolfspraul | the enjoy the money... |
| 14:58.30 | Fallenou | I don't care that much deep inside |
| 14:58.31 | wolfspraul | it's all you will get :-) |
| 14:59.00 | Fallenou | Marvell seems to only have 2 automotive chips |
| 14:59.07 | Fallenou | and the 88w8688 is one of them |
| 14:59.10 | Fallenou | too bad it's just crap |
| 14:59.24 | Fallenou | I wonder what will happen when we will try to use te 3.0 features :) |
| 14:59.26 | Fallenou | the* |
| 14:59.27 | wolfspraul | it probably works for the 1 or 2 customers that are being directly supported |
| 14:59.39 | Fallenou | well we have kind of support |
| 14:59.47 | wolfspraul | you are not bmw, afaik |
| 14:59.50 | Fallenou | we have conf calls and firmware fixes/kernel driver shipping |
| 15:00.09 | Fallenou | wolfspraul: no we are not but we may ship to bmw/volvo/mclaren/whatever :) |
| 15:00.20 | wpwrak | reminds me of the times at openmoko ... an epic struggle with that wireless chip, yet it never quite worked. in the end, it came down to fatal firmware bugs nobody could be bothered to fix. |
| 15:00.47 | wolfspraul | the economics are tough for everyone |
| 15:00.58 | Fallenou | add Android on top of all this, and coexistence between wifi and bluetooth |
| 15:01.00 | Fallenou | and there you go |
| 15:01.02 | wolfspraul | anyway, all blurb that won't help fallenou, I'm afraid |
| 15:01.05 | Fallenou | head banging against the wall :) |
| 15:01.21 | wolfspraul | in a few years it's all forgotten |
| 15:01.39 | Fallenou | anyway thank you for the human conforting support ! |
| 15:01.51 | wolfspraul | read the leaked apple genius thing today |
| 15:02.01 | wolfspraul | "I understand why you feel that way" |
| 15:03.07 | wpwrak | you should tell your bosses to find some small company that makes some halfway decent wifi chip, buy that company, then open the design - at least at the register level, deeper if you can - and let the hacker world work on it for a few years |
| 15:03.28 | Fallenou | that sounds like a good idea |
| 15:03.36 | wpwrak | then you could hope for having, say, decent 802.11g in a couple of years |
| 15:03.49 | Fallenou | I'm not high enough in the company hierarchy yet to give this kind of advice |
| 15:04.55 | wpwrak | apple genius ? |
| 15:21.56 | *** join/#qi-hardware Openfree (~Openfree@120.204.178.125) |
| 15:21.58 | *** join/#qi-hardware emeb (~ericb@ip72-201-79-123.ph.ph.cox.net) |
| 15:22.07 | *** join/#qi-hardware rejon (~rejon@122.70.120.150) |
| 15:26.42 | *** join/#qi-hardware mth (sdbfvzue@dhcp-089-098-069-120.chello.nl) |
| 15:45.45 | *** join/#qi-hardware kristoffer (~kristoffe@c-35d8e555.010-30-6c6b7012.cust.bredbandsbolaget.se) |
| 15:49.20 | *** join/#qi-hardware kuribas (~user@d54C43503.access.telenet.be) |
| 16:52.46 | *** join/#qi-hardware rejon (~rejon@122.70.120.150) |
| 16:55.15 | *** join/#qi-hardware aisa (~a@173-10-243-253-Albuquerque.hfc.comcastbusiness.net) |
| 17:01.19 | *** join/#qi-hardware rejon (~rejon@jp.fabricatorz.com) |
| 17:24.38 | *** join/#qi-hardware jurting (~jurting@ip-47-47-179-93.dialup.ice.net) |
| 17:43.50 | *** join/#qi-hardware LunaVorax (~LunaVorax@cau33-2-82-227-183-10.fbx.proxad.net) |
| 17:56.47 | *** join/#qi-hardware Ayla (~paul@pc-40-79-120-200.cm.vtr.net) |
| 18:38.45 | *** join/#qi-hardware LunaVorax (~LunaVorax@cau33-2-82-227-183-10.fbx.proxad.net) |
| 19:11.51 | *** join/#qi-hardware LunaVorax (~LunaVorax@cau33-2-82-227-183-10.fbx.proxad.net) |
| 19:51.10 | *** join/#qi-hardware guanucoluis (~luis@2001:470:e450:0:225:56ff:fea1:2064) |
| 20:13.58 | *** join/#qi-hardware jekhor (~jek@leased-line-46-53-195-83.telecom.by) |
| 20:50.41 | *** join/#qi-hardware LunaVorax (~LunaVorax@cau33-2-82-227-183-10.fbx.proxad.net) |
| 20:55.01 | *** join/#qi-hardware Jurting (~chatzilla@ip-47-47-179-93.dialup.ice.net) |
| 21:08.54 | *** join/#qi-hardware guanucoluis (~luis@2001:470:e450:0:225:56ff:fea1:2064) |
| 21:23.18 | *** join/#qi-hardware jurting (~jurting@ip-47-47-179-93.dialup.ice.net) |
| 21:34.15 | *** part/#qi-hardware erikkugel (~ekugel@216.183.91.254) |
| 22:09.00 | *** join/#qi-hardware guanucoluis (~luis@200.127.180.65) |
| 22:19.50 | *** join/#qi-hardware aisa (~a@209.234.140.58) |
| 23:06.05 | *** join/#qi-hardware LunaVorax (~LunaVorax@cau33-2-82-227-183-10.fbx.proxad.net) |
| 23:50.07 | *** join/#qi-hardware wej (~j@nl3x.mullvad.net) |