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
<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.