<qi-bot>
[commit] Werner Almesberger: labsw/mech/Makefile: updated board location for #2 face plate run (master) http://qi-hw.com/p/wernermisc/d39fbee
<qi-bot>
[commit] Werner Almesberger: labsw/mech/front.fpd: reduced width from 104 to 103.6 mm, LED hole from 6.9 to 6.2 mm (master) http://qi-hw.com/p/wernermisc/1717be8
<qi-bot>
[commit] Werner Almesberger: labsw/fw/: make loop use all front panel elements; set CH1/2 opto to open-drain (master) http://qi-hw.com/p/wernermisc/149be29
<wpwrak>
rejon: btw, in terms of logo style, is what we've cooked up so far enough for what you need ?
<wpwrak>
bleech
<optimistic>
Any special trick to getting dingux software o work on the Ben? Everything I've tried has failed in one way or another (usually seg faults).
<Ayla>
the compatibility should be the same than with opendingux
<Freemor>
could it be lack of memory probs? do dingux machines have more then 32MB
<Freemor>
if so some swap might help
<Ayla>
it wouldn't segfault then
<Freemor>
hasn't had a chance to play with the Dingux stuff yet. (been too busy with frotz :) )
<wejp>
the A320 has 32 MB of RAM just like the Ben, so that shouldn't be the problem
<optimistic>
Frotz sounds fun on the Ben, any recommendations? Or other ideas about Dingux?
<lekernel>
When evaluating EnerChip Solid State Batteries for your designs, it is important to review the Effective Capacity (EC) of each device. Since EnerChips can be charge cycled many thousands of times, an EnerChip has a similar energy storage equivalency per volume of much larger coin cell batteries. For example, the 50uAh EnerChip CBC3150 is rechargeable 5000 times at a 10% depth of discharge to 80% of rated capacity. This yields an EC of
<lekernel>
25mAh using the conservative datasheet charge cycle specifications for this device. Therefore, the 10x smaller footprint EnerChip has the same effective capacity per unit volume of a much larger problematic coin cell battery.
<lekernel>
uhm
<lekernel>
this sounds a bit like number manipulation, no?
<lekernel>
"10x more energy density per volume! oh, yeah, I forgot, when recharged regularly" ...
<wpwrak>
yeah, i couldn't quite figure out why anyone would want to use these critters. they seem to be perfectly useless.
<lekernel>
for small RTCs?
<lekernel>
oh, and "Powering Internet of Things" of course :-)
<wpwrak>
dunno. i once did the calculations and they still fell short of a similar primary cell.
<lekernel>
though it doesn't explain how you are supposed to drive an ethernet cable or a wifi antenna on a 50uAh 3.8V battery
<wpwrak>
yes yes, new hypes need new snake oil ;-)
<solrize_>
50 uah could retain critical volatile data in some device while you change the main battery.  main application i can think of would be security keys since anything else could be written to flash.
<aisa>
.i coi ro do
<aisa>
How do I quit out of qemu and/or access a terminal?
<aisa>
I figured out how to access the terminal by using the wiki docs.  Still don't know how to quit gmenu2x.
<aisa>
qemu was a typo, above, I meant gmenu2x.
<C-Keen>
aisa: I usually switch to a different console (before I commented out the entry in ttys)
<aisa>
thank you, excellent.
<qi-bot>
[commit] Werner Almesberger: m1/jtag-boot/: quick hack to boot an M1 with the "regular" bitstream (from NOR) (master) http://qi-hw.com/p/wernermisc/87aa1e7
<aisa>
yay!  Two NanoNotes flashed to the latest firmware.
<C-Keen>
aisa: I have decided not to start gmenu2x as it does not do anything useful for me
<aisa>
nods
<C-Keen>
aisa: this comes at a price, like writing your own automount stuff
<C-Keen>
for the microsd
<aisa>
I agree, I like booting right into the terminal, that's what I want when I boot my Nano.
<aisa>
I boot from microSD to do the upgrade,
<aisa>
meaning I got myself into gmenu2x a bit by surprise while doing the upgrade.
<C-Keen>
I wonder whether one could deploy the kernel as a bootlet so to get rid of uboot and to speed up boot time a bit but that's probably not worth the hassle
<aisa>
I barely keep up with development on this thing as it is, yeah.
<C-Keen>
aisa: I still need to port chicken
<aisa>
I used to keep a copy of OpenWRT all ready to go, so I could compile things; make changes; &c.
<aisa>
But it kept getting diddled with. :-/
<C-Keen>
heh
<aisa>
I'd really like chicken on this device.
<aisa>
I got stopped there for lack of a compiler.
<C-Keen>
me too
<aisa>
working compiler*
<C-Keen>
aisa: well it should work with the sdk's toolchain
<C-Keen>
but I need to set up a linux machine for that
<C-Keen>
qemu is too slow for me
<C-Keen>
(with openbsd's kqemu)
<aisa>
that actually turrns out to be my biggest problem, heh.  I have an OpenBSD box and a Mac, but no Linux box, save one running in VMWare, and that just doesn't cut it for fiddling with devices.
<qi-bot>
[commit] Werner Almesberger: m1/jtag-boot/mkboot: added comments with pointers to information sources (master) http://qi-hw.com/p/wernermisc/f3b2894
<qi-bot>
[commit] Werner Almesberger: m1/jtag-boot/: moved explanation from mkboot to README and added more details (master) http://qi-hw.com/p/wernermisc/bcd12fe
<wpwrak>
hmm, somehow TI are a little smarter with their spam than STM. do they really think i'll fire up a web browser to read that HTML gibberish ?
<qi-bot>
[commit] Werner Almesberger: labsw/LOG: labsw occasionally doesn't do what it's told; described remedies (master) http://qi-hw.com/p/wernermisc/17ec8fa