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
DocScrutinizer05 has quit [Read error: Connection reset by peer]
DocScrutinizer05 has joined #qi-hardware
<wpwrak>
heh, fun experiment: build the openwrt toolchain. it'll complain that STAGING_DIR isn't set. since you don't care about this mode of operation, just set it to "1"
<wpwrak>
then everything will go fine. for a very very long time. until you have a file called "1" in the current directory. then you get a highly mysterious "cc1: error: 1/usr/include: Not a directory"
urandom__ has quit [Quit: Konversation terminated!]
<DocScrutinizer05>
wolfspraul: actually with antibiotics it's exactly the other way round: if you take too small dosage or too short, the bacteria have a chance to adapt to them and then they're useless
<wpwrak>
i think he meant treatments. some people take antibiotics when they have a light cold ...
<DocScrutinizer05>
:nod:
<DocScrutinizer05>
wpwrak: any clue who's maintaining openmoko.org servers now?
<wpwrak>
dunno. harald ?
<wpwrak>
or maybe they're now fully on auto-pilot :)
<roh>
nobody afaik
<wpwrak>
DocScrutinizer05: perhaps you should maintain them. you seem to be the one who cares most about 'em :)
<wpwrak>
a few dd if=/dev/zero bs=1 of=/dev/null ? :)
<DocScrutinizer05>
wpwrak: I actually might ponder having a look wtf is wrong there, but I lost my root access
<DocScrutinizer05>
wiki.maemo.org is *incredibly* slow
<wpwrak>
zombies are often depicted as sluggish :)
<DocScrutinizer05>
;-D
megha has joined #qi-hardware
account has quit [Ping timeout: 245 seconds]
guanucoluis has quit [Ping timeout: 256 seconds]
megha is now known as database
FrankBlues has quit [Remote host closed the connection]
database has quit [Quit: WeeChat 0.3.9.2]
porchao has quit [Quit: Leaving...]
<wpwrak>
actually, the correct word would be "portrayed". may may, my language skills are fading ...
DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined #qi-hardware
porchao has joined #qi-hardware
rz2k has joined #qi-hardware
emeb has quit [Quit: Leaving.]
jekhor has joined #qi-hardware
panda|x201 has quit [Ping timeout: 276 seconds]
panda|x201 has joined #qi-hardware
xiangfu has joined #qi-hardware
jluis has joined #qi-hardware
wpwrak has quit [Ping timeout: 245 seconds]
wpwrak has joined #qi-hardware
rz2k has quit [Read error: Connection reset by peer]
megha has joined #qi-hardware
megha is now known as hack
xiangfu has quit [Ping timeout: 252 seconds]
xiangfu has joined #qi-hardware
xiangfu has quit [Quit: leaving]
panda|x201 has quit [Ping timeout: 245 seconds]
megha has joined #qi-hardware
hack has quit [Ping timeout: 264 seconds]
jekhor has quit [Ping timeout: 244 seconds]
jekhor has joined #qi-hardware
jekhor has quit [Ping timeout: 276 seconds]
megha has quit [Ping timeout: 252 seconds]
sivoais has quit [Read error: Connection reset by peer]
paul_boddie has joined #qi-hardware
megha has joined #qi-hardware
<C-Keen>
I have noticed that the .config file on the web is a bit out of sync with the git repo's buildroot
<C-Keen>
plus I get a wget: write error when trying to fetch the m4 sources...
<C-Keen>
ah that's due to my wget version for some reason
rz2k has joined #qi-hardware
panda|x201 has joined #qi-hardware
LunaVorax has joined #qi-hardware
<LunaVorax>
Hi!
<paul_boddie>
Hello LunaVorax! Anything new?
<LunaVorax>
Still lost my Ben
<paul_boddie>
Sorry to hear that!
<LunaVorax>
My girlfriend still use the Ben everyday
<LunaVorax>
use her* Ben
<LunaVorax>
I've ordered a GCW-Zero
<paul_boddie>
Well, I suppose there's some indirect benefit from your loss. :-)
<LunaVorax>
And I'm struggling with C++ classes at school
<LunaVorax>
(not "class" as in "C++" but as in "school")
<paul_boddie>
GCW-Zero looks like a refresh of the Dingoo or something.
<paul_boddie>
Well, I remember learning C++ and finding it nice compared to C and Pascal, but moving on via Java to Python I find the former languages (including Java) awkward and archaic.
<LunaVorax>
paul_boddie, it looks like a better Dingoo with all the features the Dingoo/Wiz/Caanoo couldn't get right.
<paul_boddie>
I have to say that wpwrak's frustration with STAGING_DIR is amusing given that I was compiling his code with the OpenWRT toolchain and it started complaining about it. At first I thought I'd actually have to do something about it, but it was just a warning.
<wpwrak>
paul_boddie: hmm, where did you run into my use of STAGING_DIR ? should be strictly a local phenomenon (unless - by sheer coincidence - you happened to do the same on your side)
<paul_boddie>
LunaVorax: It looks nice, and even has USB Host and will therefore please Ron (especially with Wi-Fi as well) and various other people.
<LunaVorax>
Indeed paul_boddie
<LunaVorax>
What have been Qi up too all theses months?
<paul_boddie>
wpwrak: You don't use it, but the mipsel-gnu-linux-gcc (or whatever it's called) seems to like STAGING_DIR for some reason.
<LunaVorax>
Looks like it's dormant
<paul_boddie>
I'm actually edging very slowly towards getting a program to talk SPI with an Arduino shield, but I want to make sure I know what I'm doing first.
<paul_boddie>
LunaVorax: wpwrak is the man of most action on the Qi front, I think.
<wpwrak>
paul_boddie: ah yes, for some mysterious reason, openwrt keeps that STAGING_DIR variable around. not sure if there's a "proper" way to transition the toolchain out of the openwrt world bubble into a normal environment. i also don't know what exactly a valid STAGING_DIR ought to point to :)
<paul_boddie>
The staging directory, maybe. Actually, I think it complained about that, too. :-)
<paul_boddie>
I'm also going to try and get cross-building for Debian to work, but that's not relevant for this project as Debian is running from the microSD card and it obviously won't be plugged in at the same time as the UBB.
<wpwrak>
don't you wish we had some more uSD slots ? :)
<paul_boddie>
Also, the Emdebian toolchain may not be completely compatible with my OpenWRT one, and I don't want to introduce more sources of error trying to deploy binaries built for Debian on OpenWRT.
<paul_boddie>
I noticed that SD is supposed to support daisy-chaining.
<wpwrak>
toolchains generally don't mix well. e.g., because you also have different libcs
<wpwrak>
daisy-chaining ? that's new to me. i've seen multiplexing, but not chaining.
<paul_boddie>
Maybe not daisy-chaining. I'll have to look at Wikipedia again.
<roh>
'supposed to support'... well.. thats... a interresting definition *g*
<roh>
so it means 'doesnt do it in reality'?
<roh>
*scnr* .. i havent seen daisy-chains there too... just hacky '2 sd on one controller' crap with extra 'select' lines
<paul_boddie>
"The SD protocol envisioned the ability to gang 30 cards together without separate chip select lines. The host device would broadcast commands to all cards and identify the card to respond to the command using its unique serial number. In practice, cards are rarely ganged together because open-collector operation has problems at high speeds and increases power consumption. Newer versions of the SD specification recommend separate lines to each c
<paul_boddie>
Given the relation to SPI, this doesn't surprise me that much.
<larsc>
there are even SD card multiplexer chips
<wpwrak>
larsc: yes, that's the sort of thing i've seen
<wpwrak>
paul_boddie: interesting ... an ID space wired-or approach. nice to see that used in real life. well, almost :)
<paul_boddie>
Just trying to keep you at the cutting edge. ;-)
<wpwrak>
btw, speaking of fun things, UBB can also sample external signals at a high constant speed. alas, not continuously. now trying to bring the trigger delay down ...
sivoais has joined #qi-hardware
<C-Keen>
in the wiki http://en.qi-hardware.com/wiki/Building_Software_Image there is a section talking about creating a symbolic link for buildroot but somehow the ln command is garbled, what's the correct step I need to do here?
<wpwrak>
hmm, odd. can't find my openwrt build notes :(
<C-Keen>
adding ones own stuff would be a lot easier if the stuff this wiki page talks about would be integrated in git already. The patches to upstream feeds for example or the feeds config
erikkugel has joined #qi-hardware
<wpwrak>
yeah. i don't know why there's such a long manual process
<wpwrak>
and to make things worse, it always gets out of sync, so you need to poke around to find the correct names and paths
<C-Keen>
do you know a better description on how to reproduce the last release images?
<wpwrak>
if i could find my darn build notes, then i would have one that's at least more up to date ...
<wpwrak>
but according to grep, they have vanished :-(
<C-Keen>
wpwrak: do you remember why you download the latest .config and then overwrite it with the minimal one from feeds?
<wpwrak>
heh, good point :) i was just following the instructions. didn't notice that dubious step
<paul_boddie>
As I recall, the build process does some fancy stuff with the .config anyway.
panda|x201 has quit [Ping timeout: 245 seconds]
urandom__ has joined #qi-hardware
* C-Keen
throws 16 cores at the build
<wpwrak>
wasn't that roughly what they did at chernobyl ? :)
<C-Keen>
the threw that against the building :)
panda|x201 has joined #qi-hardware
emeb has joined #qi-hardware
<C-Keen>
hm building glib-dbus is broken: /home/ckellerm/proj/nanonote/openwrt-xburst/staging_dir/target-mipsel_uClibc-0.9.33.2/usr/include/glib-2.0/glib/gquark.h:28:2: error: #error "Only <glib.h> can be included directly."
<C-Keen>
and feeds/qipackages/gs needs a +libpthread as dependency
<wpwrak>
the fragility of that process is scary
jekhor has joined #qi-hardware
<wpwrak>
it seems hard to get things right, though. i remember pretty much the same sort of issues from OE. there, it was worse, though, but that was probably because of the large number of packages in the system
<C-Keen>
I think the system in general grew too large for buildroot
<paul_boddie>
Anything related to Gtk+/Glib is probably going to be horrible.
<C-Keen>
there is no proper support for resuming builds, cleaning only custom targets and rebuilding them etc
<C-Keen>
paul_boddie: #t
<wpwrak>
are you building owrt just for the toolchain ? or do you need something else from that build ?
<C-Keen>
I want to use it as a demo for using buildroot but I don't think it will be a good example. And yes originally I just wanted the toolchain and I may go back to that
<wpwrak>
i wonder if we could trick xiangfu into making some pre-built cross-toolchain packages
<roh>
eh.. openwrt has a target to only build a toolchain afaik
<wpwrak>
getting the toolchain seems to be by far the most common reason for getting into that process. and basically all the weird things that happen then tend to quite overwhelm the respective victim
<roh>
i think they call it 'SDK'
<roh>
intended to be useable to build fitting binaries to installed images from the same release/snap
<wpwrak>
that's pretty much what we should have (packaged)
<roh>
actually i think the documentation is much better than what we had at openmoko for oe... also things are much easier ;) http://wiki.openwrt.org/doc/start is a good starting point
<wpwrak>
OE at OM was the mother of all clusterfucks :) but the basic flaw was the same: drag people who shouldn't have to worry about the distribution into having to build it
<wpwrak>
things got pretty smooth for me once i had figured out how to create a barrier between me and OE :) (with zecke providing the packages and my myroot combining them into a rootfs)
<roh>
yes and no. we had no seperation of distro maintainers and coders
<roh>
so yes that fucks stuff up
kilae has joined #qi-hardware
<C-Keen>
wpwrak: the toolchain isn't the problem he already provides those in the download folder together with the images
<roh>
and i dont think that was the coders fault or the distro guys.. that was a faulty management decision from what i see now.
<wpwrak>
C-Keen: ah, i see. looks good. let's see if it works :)
<roh>
i think management didnt understand that building a distro and developing sw is 2 different pair of shoes with different goals and or methods
<C-Keen>
I do wonder though why the releases aren't tagged. Together with all changes that were required to make the build
<wpwrak>
roh: yes, wolfgang never cracked that one. that mode of operation had existed from the very beginning, though.
<wpwrak>
one problem was also that developers developed inside the OE build system, basically running bitbake as if it was "make"
<roh>
wpwrak: ack. but i dont think it was his fault either... there was just no understanding from higher up that such a thing would have been neccessary.
<roh>
wpwrak: they should be free to do so if they want. but i think nobody should be forced to
<wpwrak>
roh: he simply inherited the mess. ordered it a little, but didn't kill it :)
<roh>
heh.. like we did with the admin stuff? *cough* ;)
<wpwrak>
yeah ;-)
panda|x201 has quit [Ping timeout: 245 seconds]
<wpwrak>
hmm, nice. i found a way to squeeze improvements in the order of 10-20 ns out of the trigger delay, by increasing the MSC clock speed. that's in the range of 1/4 to 1/3 of an MSC clock cycle. somehow, this doesn't seem to be worth it ... :)
FrankBlues has joined #qi-hardware
panda|x201 has joined #qi-hardware
wej has joined #qi-hardware
<wpwrak>
hmm. average trigger delay = 1 sample + 440 ns. kinda sluggish.