wolfspraul | xiangfu: we should also try to find out whether anyone is still using ks7010 or plans to use it | 00:31 |
---|---|---|
wolfspraul | I think it's time to retire this officially, it's totally dead-end. | 00:32 |
wolfspraul | kyak had some, but I think all I heard from him about them was trouble :-) | 00:32 |
xiangfu | ks7010 ok. | 00:49 |
wolfspraul | xiangfu: let's see whether anyone still uses them | 00:52 |
wolfspraul | my point is that we may be wasting time on something that is entirely worthless | 00:52 |
wolfspraul | and then I much rather spend the same time on wpan which has a future | 00:53 |
wolfspraul | the successor of the crazy spectec wifi solution is the equally crazy solution of backpacking the ben onto a MR11U wifi router :-) | 00:53 |
wolfspraul | but more practically, the Ben remains a device with only USB-networking, and an experimental ben-wpan | 00:54 |
kristianpaul | nice, MR11U looks like portable workaround solution | 01:09 |
wolfspraul | yes and no, not to me | 01:10 |
wolfspraul | I believe in easy to use products, something cheap and simple and just super easy to use. | 01:10 |
wolfspraul | and that's not going in the right direction | 01:10 |
wolfspraul | can you or anyone hack it up? of course | 01:10 |
wolfspraul | like 1000 other things | 01:10 |
kristianpaul | yes i got you point | 01:11 |
wolfspraul | but I believe we can make integrated and easy to use products | 01:11 |
kristianpaul | and of course not the right direction | 01:11 |
kristianpaul | for us | 01:11 |
wolfspraul | it's a long and hard path to get there though, but we are on it | 01:11 |
kristianpaul | integrated, yes good point ! | 01:11 |
kristianpaul | ha even works as a battery | 01:12 |
Ayla | hi | 08:58 |
Ayla | looks like LLVM/MIPS is progressing: http://lists.cs.uiuc.edu/pipermail/llvmdev/2012-March/048131.html | 08:58 |
kyak | wolfspraul: yeah, i gave up on ks7010 | 09:16 |
wolfspraul | kyak: yes, that's what I remembered and it make sense | 09:25 |
wolfspraul | you were probably the last holdout ks7010 user :-) | 09:25 |
wolfspraul | that's why I think we can officially retire ks7010 support to the code history, from where it will most likely never get resurrected... | 09:26 |
wolfspraul | kyak: do you have atben & atusb? | 09:26 |
viric | whitequark: two years ago, xburst-tools built fine with libusb 0.1 :) | 10:16 |
viric | whitequark: Now that I supplied libusb 1.0.0, it tells me it wants libusb 0.1! :D | 11:18 |
viric | http://hydra.nixos.org/build/2275155 | 11:18 |
viric | xiangfu: ^ any idea? What does xbursttools want, libusb 0.1 or libusb 1.0? | 11:18 |
viric | or both? | 11:19 |
viric | (sorry, I supplied libusb 1.0.8, not 1.0.0) | 11:20 |
lindi- | viric: maybe it needs both? | 11:21 |
viric | I'm supposing that xiangfu did not care about some detail, and made it depend on both | 11:22 |
lindi- | jzboot needs 1.0 | 11:23 |
lindi- | maybe usbboot needs 0.1 | 11:24 |
viric | mh ok | 11:24 |
lindi- | it's a different API | 11:24 |
viric | I'll supply both then | 11:25 |
larsc | maybe it's just time to get rid of usbboot and just provide a thin wrapper which maps usbboot commands to jzboot commands | 11:26 |
viric | well, that's xbursttools from december. I don't know if much changed. | 11:27 |
Ayla | or just trash usbboot and force people to use jzboot :) | 11:27 |
viric | I only know to use usbboot :) | 11:27 |
xiangfu | viric, it's needs both. | 11:30 |
xiangfu | viric, jzboot : libusb 1.0 | 11:30 |
larsc | Ayla: you can't break backwards compatibility if you don't want to annoy people | 11:30 |
xiangfu | viric, usbboot: libusb 0.1 | 11:30 |
viric | ok | 11:30 |
viric | I hope I get it to build now | 11:30 |
viric | thank you! | 11:30 |
larsc | xiangfu: is there anything in usbboot which jzboot can't do? | 11:30 |
Ayla | booting linux? :p | 11:31 |
xiangfu | larsc, I don't know the detail. I think kyak do some test on jzboot | 11:31 |
larsc | ok, i'll give it a try and come up with something thats usbboot compatible but uses the jzboot codebase | 11:32 |
Ayla | perhaps a script is enough? | 11:33 |
viric | this week we updated libc, gcc, ... and all that at nixpkgs. I've still to test the up to date nanonixos. | 11:33 |
larsc | Ayla: probably not, if you want to support the interactive mode | 11:36 |
larsc | and usbboot uses a different config format | 11:36 |
Ayla | ok | 11:37 |
xiangfu | larsc, just quit check the command subset mostly same. usbboot: nprog, jzboot: nprogram and usbboot have two more gpio and reset command | 11:38 |
larsc | xiangfu: ok, sounds promising | 11:38 |
larsc | but first some grocery shopping | 11:39 |
xiangfu | and jzboot and usbboot both usb '-c' for run semicolon-separated commands. | 11:40 |
viric | job nixpkgs:trunk:xbursttools has | 11:41 |
viric | changed from 'Failed with non-zero exit code' to 'Success' | 11:41 |
viric | perfect! | 11:41 |
whitequark | viric: libusb-1.0 ships with a shim | 12:02 |
whitequark | that is, a "libusb-0.1" which actually uses 1.0, but is api-compatible with 0.1 | 12:02 |
viric | not our libusb1 | 12:02 |
whitequark | er | 12:02 |
whitequark | there's maybe a libusb-0.1-compat package or something like this | 12:03 |
viric | I'll check | 12:03 |
viric | maybe that would be better than using the old libusb | 12:04 |
viric | whitequark: our build log: http://hydra.nixos.org/build/2189755/nixlog/1/raw | 12:04 |
kristianpaul | wolfspraul: http://oshwgnss.blogspot.com/ ;) | 12:08 |
kristianpaul | and here are the sources eagle afaik http://www.sensorcomm.co.jp/osqzss/fpga/max2769/ | 12:08 |
wolfspraul | oh wow | 12:09 |
wolfspraul | how did you get this? | 12:09 |
kristianpaul | i'll ask takuji ebinuma for licensenses | 12:09 |
kristianpaul | Artyom asked for some sources to him, i'll followed the thread ;-) | 12:09 |
wolfspraul | grea | 12:09 |
wolfspraul | great | 12:10 |
wolfspraul | :-) | 12:10 |
kristianpaul | good, pcb design is simple, hope not simpler ;) | 12:14 |
kristianpaul | s/design/layout | 12:15 |
wpwrak | hmm, is "hope" used as a verb or a noun here ? :) | 12:47 |
kristianpaul | verb | 12:49 |
kristianpaul | why? | 12:49 |
wpwrak | i was pondering the philosophical implication of interpreting it as a noun :) | 12:49 |
kristianpaul | i can imagine :-) | 12:50 |
kristianpaul | better not ;) | 12:50 |
wpwrak | the result of twisting my mind around logic where A < B and B > A can be true at the same time :) | 12:54 |
larsc | depends on the definition of '<' and '>' ;) | 12:55 |
kristianpaul | lol | 12:55 |
wpwrak | yup ;-) | 12:55 |
wpwrak | A and B can be sets. A < B means that there is at least one pair of elements a, b for which a < b. | 12:56 |
wpwrak | the tricky bit is using such a logic for searching. and for detecting redundant conditions. | 12:56 |
larsc | are you using that for the flickernoise compiler? | 13:02 |
wpwrak | oh dear, no :) | 13:03 |
wpwrak | that's for boom | 13:03 |
larsc | boom? | 13:04 |
wpwrak | the BOM processor. the thing that takes component descriptions from the schematics and turns them into a shopping list | 13:04 |
larsc | hm, interesting | 13:06 |
kristianpaul | argh, the mix og being and end inside multiple if else statements begin to get messier :S | 13:08 |
kristianpaul | s/og/of | 13:09 |
wpwrak | ah, more philosophy. now we approach the continuity of existence, to be or to end, this is the question ;) | 13:10 |
kristianpaul | indeed ! :) | 13:11 |
wpwrak | or maybe the choices aren't even mutually exclusive ? if we have a _mix_ of being and end ... where's schroedinger when you need them ? :) | 13:12 |
kristianpaul | s/being/begin | 13:12 |
wpwrak | bah, now you're trivializing it | 13:13 |
larsc | beging and end, the eternal circle of life | 13:14 |
larsc | begining | 13:15 |
whitequark | DocScrutinizer: re GSM modules | 22:24 |
whitequark | I just discovered an AT+CRLP command which allows you to set radio link settings | 22:24 |
whitequark | Internetworking window size, Mobile window size, Ack timer T1, Retransmission attempts N2, RLP version, T4 | 22:25 |
whitequark | can anything interesting be done with this? | 22:25 |
DocScrutinizer | probably yes | 22:44 |
DocScrutinizer | highly intriguing anyway | 22:44 |
whitequark | DocScrutinizer: also, I have read the changelog | 22:51 |
whitequark | 11.Solved the problem of DNS crash while using AT+CIPSHUT in decrypting process | 22:52 |
whitequark | afaik by "crash" they mean a buffer overflow in the module itself | 22:52 |
whitequark | ... which should be in privileged code | 22:52 |
DocScrutinizer | LOL | 22:53 |
DocScrutinizer | which gives you some ideas? | 22:53 |
whitequark | exactly. | 22:54 |
whitequark | combined with the fact that I have SDK where I have endpoints to write to UART, etc... | 22:54 |
whitequark | this is _very_ interesting | 22:54 |
whitequark | (well, I don't really have it atm, but it won't be hard to get. a few letters maybe.) | 22:55 |
whitequark | to be honest, I'm quite certain that their software has zillions of buffer overflows waiting to be exploited anyway | 22:57 |
whitequark | given how it's written and what often appears in changelog | 22:58 |
tickrate | hey guys. I haven't been here in a while. Gotta a Questions for ya. I've been playing with uboot and messed some things up. Got it all back except one thing. | 23:11 |
tickrate | I lost the failsafe on 2.6.38+ kernel. How do you get it back? Not important, but would like to know. | 23:11 |
--- Sun Mar 11 2012 | 00:00 |
Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!