2011-06-24 01:59 http://cryptome.org/0004/whatsup-mesh.htm 2011-06-24 02:18 kristianpaul: no problem. we're ready for ieee 802.15.4 ;-) 2011-06-24 03:24 [commit] Werner Almesberger: at86rf230: assorted fixes http://qi-hw.com/p/qi-kernel/06f03a7 2011-06-24 03:46 GNUtoo|bug20 what is the connectivity between BugBase and the add-on modules? 2011-06-24 07:43 hm. 2011-06-24 15:16 wow 2011-06-24 15:16 it only took three days to deliver a parcel via Fedex 2011-06-24 15:16 can't believe it 2011-06-24 15:17 i guess this is why delivery cost is bigger (50.98 EUR) than the parcel cost (50 EUR, atben+atusb) 2011-06-24 15:17 unfortunately, they didn't catch me at home 2011-06-24 15:17 so i'll get it on monday 2011-06-24 18:04 valhalla, hi 2011-06-24 19:02 hi GNUtoo 2011-06-24 19:03 I'll PM you 2011-06-24 19:13 <[g2]> rjeffries ping. 2011-06-24 19:16 just wondering 2011-06-24 19:16 !ping 2011-06-24 19:17 <[g2]> hey whitequark 2011-06-24 20:23 [g2]: hi 2011-06-24 20:23 <[g2]> whitequark, you were picking on me for "pinging" :) 2011-06-24 20:25 [g2]: nope, i was wondering if qi-bot will reply the command 2011-06-24 20:26 <[g2]> whitequark, Ah... didn't know a bot was running :) 2011-06-24 20:36 doesn't actually know what "hey" can mean, depending on the context 2011-06-24 20:37 <[g2]> whitequark, It's like "hi" 2011-06-24 22:22 GRRR. Maximum number of clients reachedError: Can't open display: :0.1 2011-06-24 22:22 traitor !! 2011-06-24 22:28 muhahah 2011-06-24 22:36 RichardSharpe: hi 2011-06-24 22:36 wpwrak: hi 2011-06-24 22:37 wpwrak: lokking through your spi master driver now 2011-06-24 22:37 wpwrak: does it contain the irq handling we talked about that could also be used for atusb? 2011-06-24 22:41 yes :) 2011-06-24 22:42 and behold its beauty - it even allocates irq 0 on the ben :) 2011-06-24 22:42 no idea how portable this is, though. maybe i was just incredibly lucky 2011-06-24 22:45 0 is always fun 2011-06-24 22:46 on cc2420 one irq is also on 0 2011-06-24 22:46 and trying to allocate the gpio freaks the gpio framework out 2011-06-24 22:46 not sure if this is fixed by now 2011-06-24 22:47 As the "alloc" is only for internal reference but not function I never came around to fix it :) 2011-06-24 22:47 ah ? didn't have any trouble with my irq 0. well, except in at86rf230.c 2011-06-24 22:47 wpwrak: hmm, let me check, moment 2011-06-24 22:47 or perhaps we're talking about different frameworks :) 2011-06-24 22:48 gpio_request 2011-06-24 22:48 not alloc 2011-06-24 22:48 not sure its also used on mips and if it may differ there 2011-06-24 22:48 i think i found the source of my memory corruption. it's packets with a bad PHR (> 127) 2011-06-24 22:49 PHR? 2011-06-24 22:49 now, if i throw them away and politely report back the problem, the whole thing hangs. hmm. more investigation needed. at least only the driver is dead, not the entire machine. 2011-06-24 22:49 frame length 2011-06-24 22:49 wpwrak: (memory) It was funny to read this. I somehow implicit thought that with partial struct declaration all other would be 0 2011-06-24 22:50 (frame length) ah 2011-06-24 22:50 over 127 is indeed bad in ieee802154 :D 2011-06-24 22:51 and the 128 bytes skb hates it too 2011-06-24 22:52 wpwrak: (spi master driver) How would we integrate this with atusb? Mapping the spi calls to ATUSB_REG_WRITE, etc? 2011-06-24 22:52 (skb) And I can fully understand that :) 2011-06-24 22:52 or ATUSB_SPI_... 2011-06-24 22:52 hmm 2011-06-24 22:53 see the dev_dbg statements in the classificator 2011-06-24 22:54 wpwrak: is there a list with available firmware commands? (I'm on latest here) 2011-06-24 22:56 atusb/fw/include/atusb/ep0.h 2011-06-24 22:56 ah, read the f*cking source, luke 2011-06-24 22:56 aye ;-) 2011-06-24 22:58 new error handling, new luck ... let's see how long until the first garbled packet this time 2011-06-24 23:01 wpwrak: greetings from Jan (shoragan) 2011-06-24 23:02 thanks ! greetings, too ! :) 2011-06-24 23:04 japan has a funny extra wlan channel. channel number is 14, but it's 2.4 times the usual channel spacing from channel 13 2011-06-24 23:07 wpwrak: there is even more funny things about the wifi channels 2011-06-24 23:07 wpwrak: at one linux kongress, if have only been at one, they had the wifi on channel 13 IIRC 2011-06-24 23:07 and my driver did think he was in US and used the smallest amount of channels... 2011-06-24 23:08 which did not include 13... 2011-06-24 23:09 correct. only 11 channels there :) 2011-06-24 23:11 _after_ the kongress I had a patch for it :) 2011-06-24 23:11 i wonder if i should color-code the critters for us/eu ... 2011-06-24 23:11 congresses are usually very fertile grounds for fixed for this sort of minor annoyances :) 2011-06-24 23:13 monday i should get my set of atben/atusb boards as well. finally, i'll have atusbs with a working reset line ;-) 2011-06-24 23:15 yay 2011-06-24 23:15 puts in some single malt whisky and starts coding 2011-06-24 23:16 interesting programming fuel :) 2011-06-24 23:17 wpwrak: normally its club mate (the icetea mate) 2011-06-24 23:17 Just remembered I have some left 2011-06-24 23:18 me, diet coke for a nice boost. else, tea. well, last night is was about a liter of coffee ... today was jittery 2011-06-24 23:19 I don't like the taste of coffee. 2011-06-24 23:19 i think that's part of the effect :) 2011-06-24 23:20 heh 2011-06-24 23:20 well, it was instant cappuccino. so the first half liter or so went down nicely. 2011-06-24 23:23 RichardSharpe: I would start on some work work with atusb now. based on wpwrak spi master driver. 2011-06-24 23:23 RichardSharpe: Any conflicts with this on your side? 2011-06-24 23:24 ah, i haven't mentioned the dark side yet 2011-06-24 23:25 for interrupt synchronization, i think we need to enqueue an URB to read, then wait for the maximum time within which it would get serviced 2011-06-24 23:25 wpwrak: you alway wait with this until I start... 2011-06-24 23:25 (this will get more predictable when switching to an interrupt EP. for now, 10 ms seems to be a good value.) 2011-06-24 23:26 not sure I really will hit irqs tonight 2011-06-24 23:26 now, the interrupt synchronization would have to be triggered by detecting writes to TRX_STATE 2011-06-24 23:26 would be happy to have some basic skeleton running for spi read and write 2011-06-24 23:26 so the driver would have to decode some of the requests 2011-06-24 23:27 yeah, with spi read/write, you can already make it through the chip identification 2011-06-24 23:27 and you'll also need reset 2011-06-24 23:27 and tx should not involve any sending as well, right? 2011-06-24 23:27 haven't hacked this into spi_atben yet 2011-06-24 23:27 tx ? 2011-06-24 23:27 transmit 2011-06-24 23:28 why would transmit not involve any sending ? 2011-06-24 23:28 how much single malt did you have left ? ;-) 2011-06-24 23:29 huh, you lost me 2011-06-24 23:29 transmit would not involve any irq 2011-06-24 23:29 ah ! well, there's an interrupt at the end of it 2011-06-24 23:30 TRX_END fires when a packet has been received and when a packet has been sent 2011-06-24 23:30 yeah, sure, but I can send without caring for it now :) 2011-06-24 23:30 yes, but at86rf230.c will not be very happy when it doesn't see the interrupt :) 2011-06-24 23:31 I'm not here to make at86rf230.c happy, hmm, atcualy I am ;) 2011-06-24 23:31 do not ask what at86rf230 can do for you - ask what you can do for at86rf230 ! ;-) 2011-06-24 23:40 [commit] Stefan Schmidt: ieee802154/atusb: Update command enum and comment. http://qi-hw.com/p/qi-kernel/047c9c8 2011-06-24 23:44 2770 pings and still no bad PHR. boring. the last time, i got one after 1080 ... 2011-06-24 23:45 would be happy to have 2770 pings 2011-06-24 23:46 i get a few "security support is not implemented". so there's some mild unhappiness. but nothing in the PHR yet 2011-06-24 23:47 ah, wrong. there's one. hehe. at86rf230 spi2.0: PHR 0xb2 >= buffer 128 bytes 2011-06-24 23:47 and nothing died. good boy ;-) 2011-06-24 23:47 heh 2011-06-24 23:48 hmm 2011-06-24 23:48 ah yes, of course. i turned off the serial console as much as possible. that's why such minor things didn't pop up there. 2011-06-24 23:49 wpwrak: is platform_driver an embedded only thing or can I use it on x86 as well? 2011-06-24 23:49 There is no place for platform_data 2011-06-24 23:49 is confused. 2011-06-24 23:50 To much embedded development and to less x86 2011-06-24 23:51 Hmm, on a second thought that does not need to get passed to the driver as it is wired in hw and can get set in the driver directly 2011-06-24 23:51 should work everywhere. the platform data should be inside spi->dev 2011-06-24 23:51 so you can tweak it there :) 2011-06-24 23:51 that's what i'll do for atben_reset. so if you want to wait a little ... 2011-06-24 23:52 wait, wait, I only hear wait around me ;) 2011-06-24 23:52 sure, can wait for it. :) 2011-06-24 23:53 (wait) first i want to see no PHR_related trouble for a bit. then i'll hack on the reset. so ~2 hours. 2011-06-24 23:55 wpwrak: heh, take your time 2011-06-24 23:55 hmm. do arcs look good of cheesy ? cheesy, i think 2011-06-24 23:56 http://downloads.qi-hardware.com/people/werner/wpan/tmp/rssi-wlan-arcs.png 2011-06-24 23:57 looks overloaded but gets the message over 2011-06-24 23:57 FISL slides? 2011-06-24 23:58 a bit of overload is good. makes you feel it does something important :) 2011-06-24 23:58 no no, that's atrf-rssi -g 2011-06-24 23:59 slides are tomorrow or so 2011-06-24 23:59 The build has FAILED, see log here: http://fidelio.qi-hardware.com/~xiangfu/compile-log/openwrt-xburst.full_system-06232011-2104/ 2011-06-24 23:59 ah 2011-06-24 23:59 naw, i don't like the arcs. i'll try lines instead