<wolfspraul>
the old versions have no value, and are hard to distinguish/ignore for newcomers
<wpwrak>
you never know when they may be useful to track some regression
<wolfspraul>
true, and if there were an easy way to move them out of sight into a /obsolete/ folder or so I would prefer that
<wpwrak>
that's always an option :)
<wolfspraul>
but given that they are all in one flat list, protecting newcomers from being lost is of higher value
<wolfspraul>
we know the theoretical value of keeping old binaries around, no doubt
<wpwrak>
mkdir attic; mv * attic  then cherry-pick the good ones back doesn't sound all that hard
<wolfspraul>
but we also know practically the chances for that are very low, while the long list is frustrating for anybody who goes there and tries to understand and download the right one...
<wolfspraul>
wpwrak: it's a lovely web interface :-)
<wolfspraul>
I don't think Indefero supports the concept of folders in the downloads section
<wpwrak>
hah, web interfaces. making it easy to do the trival and impossible to do the difficult ;-)
<wolfspraul>
sure
<wolfspraul>
but that's the point, focus on what matters :-)
<wolfspraul>
if there is too much discussion, maybe I just take the lead, play benevolent dictator, and delete the old junk :-)
<wolfspraul>
let's hope nobody feels we are doing a 'bad thing' for moving the old binaries out of sight...
<wolfspraul>
if so, please speak up still
<wolfspraul>
for example I would never advocate this for the entire images. first the folder structure there is much cleaner, with 'latest' symlink etc.
<wolfspraul>
and then there are much more likely reasons someone wants to go at least one image back, if not multiple. because the chance of real regressions there is high, with so many packages going in and out, changes, etc.
<qi-bot>
[commit] Werner Almesberger: tools/atrf-gpio/atusb.c: if ATUSB_GPIO fails, show the attempted setting http://qi-hw.com/p/ben-wpan/a73a8a2
<qi-bot>
[commit] Werner Almesberger: tools/atrf-gpio/atusb.c (gpio): _exit after USB error, to avoid futile cleanup http://qi-hw.com/p/ben-wpan/e9debdd
<wpwrak>
hmm, protocol jokes. apparently, it started with "The great thing about TCP jokes is that you always get them." what followed was ... http://attrition.org/misc/ee/protolol.txt
<jluis_>
going home
<kyak>
wpwrak: the sad thing about protolol.txt is that noone reads it from start to the end, otherwise they would've found a bunch of same jokes
<dvdk>
now we can start porting liballegro games :)
<dvdk>
btw, try the allegro demo.  very nice sound (sw synthesized midi)
<kyak>
sure, it's interesting :)
<Jay7>
hm..
<whitequark>
thinks about linux.conf.au
<mth>
kyak: by the way, good that you found the gmenu2x skin bug
<mth>
I thought the alpha might be the problem, but it was actually a lack of red ;)
<qi-bot>
[commit] Werner Almesberger: atrf-gpio: option -c to cycle through the pattern sequence with pass/fail input http://qi-hw.com/p/ben-wpan/7a2e091
<tuxbrain>
I have just flashed with whatever are in the instructions
<wpwrak>
if the spectrum works, the line should appear nearly instantly (< 1 s). but if it doesn't work, it can take a while before you get an error
<tuxbrain>
yes was that one
<wpwrak>
perfect :)
<tuxbrain>
so it doen't work at least in the arm based laptop
<wpwrak>
you may also want to pull the latest test scripts. i just added the last missing pieces.
<tuxbrain>
all installation is fresh from an hour ago
<wpwrak>
the last commit is just some 5 min old :) haven't even sent the update to the mailing list
<wpwrak>
well, last push. the commits are a bit older
<tuxbrain>
what was the command to refresh the git? (oh lord I'm so oxidated)
<wpwrak>
in the "make spectrum", when you press "Q" to quit, you'll get another window (for the opposite direction). does that one also fail to work ?
<wpwrak>
git pull
<wpwrak>
then cd tools
<wpwrak>
make clean all install
<wpwrak>
make TARGET=ben_openwrt clean all upload
<tuxbrain>
no reaction to q nor d
<wpwrak>
ah, you have to do this with the focus in the window
<tuxbrain>
it has
<tuxbrain>
it has the focus
<wpwrak>
that is, until you install the latest version, which will also accept input from the console :)
<wpwrak>
hmm, then it's stuck
<tuxbrain>
maybe your code is no ARM proof
<tuxbrain>
I will redo on the desktop
<wpwrak>
before starting the spectrum setup again, let's do a few preliminary checks too
<tuxbrain>
ok
<wpwrak>
1) is the ben connected and reachable via "ping ben" ? (or if you have it another name, did you set that name in Makefile (ATBEN_DUT and ATUSB_REF) ?
<wpwrak>
2) did you stop the kernel's MMC driver on the ben ?  echo jz4740-mmc.0 >/sys/bus/platform/drivers/jz4740-mmc/unbind
<wpwrak>
2a) does the kernel contain the WPAN code with the at86rf230/1 driver ?
<tuxbrain>
ping ben ok
<wpwrak>
2b) if yes, did you disable it immediately after booting ? echo spi2.0 >/sys/bus/spi/drivers/at86rf230/unbind
<wpwrak>
(if the asnwer to 2a is "no", that's good. you don't need the kernel code for the testing)
<wpwrak>
(if you're just running a regular distribution kernel, it won't have the wpan driver, so you only need to knock out the mmc driver)