Topic for #qi-hardware is now Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs
urandom__ has joined #qi-hardware
<wolfspraul> xiangfu: we should also try to find out whether anyone is still using ks7010 or plans to use it
<wolfspraul> I think it's time to retire this officially, it's totally dead-end.
<wolfspraul> kyak had some, but I think all I heard from him about them was trouble :-)
<xiangfu> ks7010 ok.
<wolfspraul> xiangfu: let's see whether anyone still uses them
<wolfspraul> my point is that we may be wasting time on something that is entirely worthless
<wolfspraul> and then I much rather spend the same time on wpan which has a future
<wolfspraul> the successor of the crazy spectec wifi solution is the equally crazy solution of backpacking the ben onto a MR11U wifi router :-)
<wolfspraul> but more practically, the Ben remains a device with only USB-networking, and an experimental ben-wpan
<kristianpaul> nice, MR11U looks like portable workaround solution
<wolfspraul> yes and no, not to me
<wolfspraul> I believe in easy to use products, something cheap and simple and just super easy to use.
<wolfspraul> and that's not going in the right direction
<wolfspraul> can you or anyone hack it up? of course
<wolfspraul> like 1000 other things
<kristianpaul> yes i got you point
<wolfspraul> but I believe we can make integrated and easy to use products
<kristianpaul> and of course not the right direction
<kristianpaul> for us
<wolfspraul> it's a long and hard path to get there though, but we are on it
<kristianpaul> integrated, yes good point !
<kristianpaul> ha even works as a battery
panda|x201 has joined #qi-hardware
antgreen has joined #qi-hardware
liuqi has joined #qi-hardware
jekhor has joined #qi-hardware
pabs3 has joined #qi-hardware
rejon has joined #qi-hardware
Ayla has joined #qi-hardware
<Ayla> hi
<Ayla> looks like LLVM/MIPS is progressing: http://lists.cs.uiuc.edu/pipermail/llvmdev/2012-March/048131.html
<kyak> wolfspraul: yeah, i gave up on ks7010
<wolfspraul> kyak: yes, that's what I remembered and it make sense
<wolfspraul> you were probably the last holdout ks7010 user :-)
<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...
<wolfspraul> kyak: do you have atben & atusb?
jekhor has joined #qi-hardware
LunaVorax has joined #qi-hardware
panda|x201 has joined #qi-hardware
<viric> whitequark: two years ago, xburst-tools built fine with libusb 0.1 :)
DocScrutinizer has joined #qi-hardware
Ornotermes has joined #qi-hardware
kilae has joined #qi-hardware
kyak has joined #qi-hardware
kyak has joined #qi-hardware
<viric> whitequark: Now that I supplied libusb 1.0.0, it tells me it wants libusb 0.1! :D
<viric> xiangfu: ^ any idea? What does xbursttools want, libusb 0.1 or libusb 1.0?
<viric> or both?
<viric> (sorry, I supplied libusb 1.0.8, not 1.0.0)
<lindi-> viric: maybe it needs both?
<viric> I'm supposing that xiangfu did not care about some detail, and made it depend on both
<lindi-> jzboot needs 1.0
<lindi-> maybe usbboot needs 0.1
<viric> mh ok
<lindi-> it's a different API
<viric> I'll supply both then
<larsc> maybe it's just time to get rid of usbboot and just provide a thin wrapper which maps usbboot commands to jzboot commands
<viric> well, that's xbursttools from december. I don't know if much changed.
<Ayla> or just trash usbboot and force people to use jzboot :)
<viric> I only know to use usbboot :)
<xiangfu> viric, it's needs both.
<xiangfu> viric, jzboot : libusb 1.0
<larsc> Ayla: you can't break backwards compatibility if you don't want to annoy people
<xiangfu> viric, usbboot: libusb 0.1
<viric> ok
<viric> I hope I get it to build now
<viric> thank you!
<larsc> xiangfu: is there anything in usbboot which jzboot can't do?
<Ayla> booting linux? :p
<xiangfu> larsc, I don't know the detail. I think kyak do some test on jzboot
<larsc> ok, i'll give it a try and come up with something thats usbboot compatible but uses the jzboot codebase
<Ayla> perhaps a script is enough?
<viric> this week we updated libc, gcc, ... and all that at nixpkgs. I've still to test the up to date nanonixos.
<larsc> Ayla: probably not, if you want to support the interactive mode
pabs3 has joined #qi-hardware
<larsc> and usbboot uses a different config format
<Ayla> ok
<xiangfu> larsc, just quit check the command subset mostly same. usbboot: nprog, jzboot: nprogram and usbboot have two more gpio and reset command
<larsc> xiangfu: ok, sounds promising
<larsc> but first some grocery shopping
<xiangfu> and jzboot and usbboot both usb '-c' for run semicolon-separated commands.
<viric> job nixpkgs:trunk:xbursttools has
<viric> changed from 'Failed with non-zero exit code' to 'Success'
<viric> perfect!
<whitequark> viric: libusb-1.0 ships with a shim
<whitequark> that is, a "libusb-0.1" which actually uses 1.0, but is api-compatible with 0.1
<viric> not our libusb1
<whitequark> er
<whitequark> there's maybe a libusb-0.1-compat package or something like this
<viric> I'll check
<viric> maybe that would be better than using the old libusb
<viric> whitequark: our build log: http://hydra.nixos.org/build/2189755/nixlog/1/raw
<kristianpaul> wolfspraul: http://oshwgnss.blogspot.com/ ;)
<kristianpaul> and here are the sources eagle afaik http://www.sensorcomm.co.jp/osqzss/fpga/max2769/
<wolfspraul> oh wow
<wolfspraul> how did you get this?
<kristianpaul> i'll ask takuji ebinuma for licensenses
<kristianpaul> Artyom asked for some sources to him, i'll followed the thread ;-)
<wolfspraul> grea
<wolfspraul> great
<wolfspraul> :-)
<kristianpaul> good, pcb design is simple, hope not simpler ;)
<kristianpaul> s/design/layout
<qi-bot> kristianpaul meant: "good, pcb layout is simple, hope not simpler ;)"
<wpwrak> hmm, is "hope" used as a verb or a noun here ? :)
<kristianpaul> verb
<kristianpaul> why?
<wpwrak> i was pondering the philosophical implication of interpreting it as a noun :)
<kristianpaul> i can imagine :-)
<kristianpaul> better not ;)
<wpwrak> the result of twisting my mind around logic where A < B and B > A can be true at the same time :)
<larsc> depends on the definition of '<' and '>' ;)
<kristianpaul> lol
<wpwrak> yup ;-)
<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.
<wpwrak> the tricky bit is using such a logic for searching. and for detecting redundant conditions.
<larsc> are you using that for the flickernoise compiler?
<wpwrak> oh dear, no :)
<wpwrak> that's for boom
<larsc> boom?
<wpwrak> the BOM processor. the thing that takes component descriptions from the schematics and turns them into a shopping list
<larsc> hm, interesting
<kristianpaul> argh, the mix og being and end inside multiple if else statements begin to get messier :S
<kristianpaul> s/og/of
<qi-bot> kristianpaul meant: "argh, the mix of being and end inside multiple if else statements begin to get messier :S"
<wpwrak> ah, more philosophy. now we approach the continuity of existence, to be or to end, this is the question ;)
<kristianpaul> indeed ! :)
<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 ? :)
<kristianpaul> s/being/begin
<wpwrak> bah, now you're trivializing it
<larsc> beging and end, the eternal circle of life
<larsc> begining
wej has joined #qi-hardware
jow_laptop has joined #qi-hardware
rozzin has joined #qi-hardware
DocScrutinizer51 has joined #qi-hardware
panda|x201 has joined #qi-hardware
FrankBlues has joined #qi-hardware
emeb has joined #qi-hardware
mstevens has joined #qi-hardware
mth has joined #qi-hardware
jekhor has joined #qi-hardware
GNUtoo has joined #qi-hardware
wej has joined #qi-hardware
wej has joined #qi-hardware
LunaVorax_ has joined #qi-hardware
<whitequark> DocScrutinizer: re GSM modules
<whitequark> I just discovered an AT+CRLP command which allows you to set radio link settings
<whitequark> Internetworking window size, Mobile window size, Ack timer T1, Retransmission attempts N2, RLP version, T4
<whitequark> can anything interesting be done with this?
<DocScrutinizer> probably yes
<DocScrutinizer> highly intriguing anyway
wej has joined #qi-hardware
wej has joined #qi-hardware
<whitequark> DocScrutinizer: also, I have read the changelog
<whitequark> 11.Solved the problem of DNS crash while using ”AT+CIPSHUT” in decrypting process
<whitequark> afaik by "crash" they mean a buffer overflow in the module itself
<whitequark> ... which should be in privileged code
<DocScrutinizer> LOL
<DocScrutinizer> which gives you some ideas?
<whitequark> exactly.
<whitequark> combined with the fact that I have SDK where I have endpoints to write to UART, etc...
<whitequark> this is _very_ interesting
<whitequark> (well, I don't really have it atm, but it won't be hard to get. a few letters maybe.)
qwebirc50089 has joined #qi-hardware
<whitequark> to be honest, I'm quite certain that their software has zillions of buffer overflows waiting to be exploited anyway
<whitequark> given how it's written and what often appears in changelog
<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.
<tickrate> I lost the failsafe on 2.6.38+ kernel. How do you get it back? Not important, but would like to know.
wej has joined #qi-hardware