<wpwrak> hehe, antenna fixed ;-) it was a bad solder joint. ant-120B4 now looks like its "good" twin, ant-120A. (both suck, but that's okay) http://downloads.qi-hardware.com/people/werner/tmp/ant120-fixed.png
<wolfspra1l> nice work
<wpwrak> trial and error at its best ;-)
<wolfspra1l> I'll add a thumbnail of this pic to the wiki homepage slider - we don't have any representation of antenna work yet, and this one looks nice :-)
<wpwrak> hmm, so i better find an antenna that actually looks good quickly :)
<wpwrak> what i'm doing is that i'm making a series of antennas with the size varying in steps of 10% from 90 to 120% of the reference design. i hope there'll be a good one among them, or at least a clear trend where i should look for the right size..
<wpwrak> rafa: hmm, how does jlime-pkg like packages for which multiple versions exist ? e.g., man-pages*, matchbox-common*, rxvt, xserver-kdrive-fbdev
<wolfspraul> wpwrak: do you have any tool recommendation off the top of your mind to convert dxf to an 'easily viewable' 2D representation like png/jpeg or so?
<rafa> wolfspraul: sorry the link is a spanish document..
<rafa> wolfspraul: we trust (arg linux peoñple like wer or me) trust at our politics
<rafa> from fundacion via libre
<wpwrak> wolfspraul: hmm, qcad should be able to read DXF
<rafa> wolfspraul: they work for free content and free technologies on many areas for the argentine legislation
<wpwrak> wolfspraul: and it can export to PNG (just looked it up :)
<rafa> wolfspraul: that documents is from beatriz busaniche.. an expert on thos matter
<rafa> s
<rafa> wolfspraul: the document says that we are okey to use public domain stuff without to ask to use it, but it also says that
<rafa> wolfspraul: if we use it for commercial we need to pay something. I am not going to use any stuff of that because I still do not do business with this kind of stuff
<rafa> wolfspraul: just checking to learn a bit about argentina crap laws
<wolfspraul> rafa: just make sure this really applies to you
<wolfspraul> it's so easy to get distracted, scarily easy almost
<rafa> wpwrak: I guess that there is just one version of every package.. and packages with different versions should be called different.. something like vim should be a a package and vim3 should be a vim package of another version.
<wpwrak> rafa: political idiocy at its finest
<rafa> wpwrak: but i am not sure if that is like I am telling you, maybe i am wrong..
<wolfspraul> and sometimes we may well be adding more oil into the fire that we claim to want to put out
<wpwrak> rafa: (packages) the examples above are from the jlime installation for qi-hw
<rafa> wolfspraul: no.. for me is okey.. I do not do any business at all
<wolfspraul> the question is even if you would, who would really come forward, and what the consequences and alternatives would be
<wolfspraul> but even that can be investigated once the situation becomes real
<wolfspraul> no time for this :-)
<rafa> wolfspraul: yes, of course.. but then I could apply the same ideas to use another problematic stuff until some real problem appears.. better if we do not use any of them
<rafa> wolfspraul: that is a real thing (the law or argentina resolution)
<rafa> wolfspraul: we=me.. argentine
<rafa> in argentina
<rafa> wolfspraul: i mean.. sorry, my english right now sucks... another example.. I could do business with mpeg* without pay anything.. until some real problem appears.. Well, no I do not want to do that
<rafa> wolfspraul: and the public domain thing looks similar from beatriz document
<rafa> wolfspraul: I can ask her anyway
<wpwrak> rafa: raises the interesting question of who would have to pay when you order a device containing public domain material from abroad for your own use
<wolfspraul> my first suspicion would be it's yet another case of engineers reading legal texts :-)
<rafa> wpwrak: no for your own use.. I mean.. if I sell stuff with public domain inside for example
<wolfspraul> which cases was this law meant for? and where and how is it currently enforced?
<wolfspraul> I would focus on that, if I had to...
<wpwrak> wolfspraul: it looks like a pretty neat concept. they apparently replaced public domain with a transfer of the rights to a state entity.
<rafa> wolfspraul: anyway.. that was (the document about public domain stuff for business in argentina) just a comment.. it does not scare me or something :) ... and like that maybe there are other crap things in the nice argentine lays
<rafa> laws*
<wolfspraul> see that's what I'm saying - we read things into this. but if we are interested, we should be interested in the practical consequences.
<wolfspraul> not in how much we can read into those texts...
<wolfspraul> when you see a device (say the Ben NanoNote), the #1 question is whether you are actually selling the content on it, or the device itself?
<wolfspraul> who determines the 'value percentage'?
<wpwrak> wolfspraul: it may be a problem for a reseller. not sure if it's a problem for a private importer.
<wolfspraul> maybe 90% is for the physical hardware, 10% for the content it's shipped with?
<rafa> wolfspraul: if I do some business with open source or CC technology we know where to ask for consequences ;) (fundacion via libre).. so I am fine until I need to do business.. and I will ask them :)
<wpwrak> wolfspraul: the exact figures would be argued over in court for the next few decades :)
<wolfspraul> this is also why it is still questionable whether/how the cc-nc clause is enforceable at all, afaik
<wolfspraul> if you sell a usb stick with 3gb of -nc content on it, what are you selling?
<wolfspraul> the usb stick or the content?
<wolfspraul> and so on
<rafa> me.. tired.. I need to sleep. have a nice day.. cya
<wolfspraul> I'm not paid for this kind of stuff, and not interesed. Lawyers get paid for every sentence they write, so I understand they are chatty :-)
<wolfspraul> yeah :-)
<wolfspraul> that's better!
<wolfspraul> get some new energy
<rafa> :)
<wpwrak> wolfspraul: you just have to admire the idea - it's a complete perversion of the concept that intellectual property rights eventually expire !
<wolfspraul> like I said, my first suspicion is we are reading things into it
<wolfspraul> ask someone working in the field what is really applied, and how
<wolfspraul> if human being A has money, human being B will start to develop an interest in that money :-)
<wolfspraul> I'd say those are some super basic 'eternal' laws and patterns...
<wpwrak> sure. just never heard of anyone going after the public domain by just installing a catchall. that's pretty clever, in a perverted way.
<kyak> kristianpaul: quite strange...
<kyak> kristianpaul: the problem is, i can't reproduce this error anywhere
<kyak> xiangfu: regarding the latest image.. there are several things:
<kyak> 1) trigger happy won't build
<kyak> 2) the gmenu2x brightness can't be adjusted
<kyak> 3) nanoterm is not usable
<wpwrak> wolfspraul, rafa: the origin of this appropriation of the public domain seems to be the protection of folklore. while, according to google, virtually unknown in the english-speaking world, the concept enjoys some popularity in latin america: http://www.educ.ar/educar/lm/1188223038496/kbee:/educar/content/portal-content/taxonomia-recursos/recurso/a2073f97-25e4-4cf6-b3a8-b390707f1655.recurso/6fd44608-dcbf-4210-974e-3155ec5bdd47/derechos_
<wpwrak> de_autor.pdf
<wpwrak> (lovely URL :)
<wolfspraul> wpwrak: so how is it applied? who pays? who determines how much? which 'public domain' content exactly is affected?
<wolfspraul> maybe if we would make a collection of traditional (public domain) Argentine folklore songs, and publish a CD, there would be some kind of tax on that CD?
<wolfspraul> btw, I could definitely imagine similar legislation elsehwere, there is a lot of debate in some countries about 'culture flat rate' etc.
<wpwrak> wolfspraul: e.g., things where the copyright has expired. not sure if it would also apply to things that are put into the public domain abroad, e.g. public works in the US.
<wpwrak> wolfspraul: it does apply to everything they can get their hands on, irrespective of origin
<wolfspraul> and storage media are taxed in many countries now, empty CDs, empty USB sticks, etc.
<wolfspraul> so one could definitely imagine that someone would take the Ben NanoNote because it is a 2GB storage medium
<wolfspraul> s/would take/would tax/
<wpwrak> the text i referenced mentions that they're thinking about such things also in europe
<wolfspraul> like I said, taxation for storage media already exists in many countries
<wpwrak> yeah, it could reproduce radio -> GEZ :)
<wolfspraul> empty CD-Rs are expensive in some countries :-)
<wolfspraul> I'm not sure any of this affects what 'we' (copyleft hardware) should deem 'inclusive' for our hardware
<wpwrak> (different sort of tax but still weird)
<wolfspraul> I feel pretty good following the wmf, in general
<wolfspraul> there are special taxes for many categories of devices now, in many countries
<wolfspraul> printers are taxed as a 'flat rate copyright' fee, because they are assumed to be printing copyrighted material
<wolfspraul> xerox as well
<wolfspraul> storage media are taxed under 'culture flat rate' regimes, who knows where the money goes :-)
<wpwrak> (who would have to pay) they mention the importer. not sure if it would apply to everyone in the chain (e.g., if you have importer, distributor, and maybe some public performance) or just the last element.
<wolfspraul> sometimes things are just taxed because there is or was a strong lobby to do so, for example the famous 'video cameras' in Europe, because the (now defunct) European video camera makers were hoping in the 60's it would help them stop the Japanese
<wolfspraul> then when the digital still cameras started to have video features, everybody was wondering whether they would be taxed this nice 20+% or whatever as well
<wolfspraul> then the smartphones
<wolfspraul> etc. etc.
<wpwrak> yeah, there are plenty of "because we can" taxes and para-taxes in that sector ...
<wolfspraul> I'm not following all of this.
<wolfspraul> I think there is a big difference between that kind of tax and a patent owned by someone like Sisvel.
<wpwrak> you're not an importer :)
<wolfspraul> massive difference :-)
<wpwrak> the taxes tend to be less intrusive
<wolfspraul> yes sure, the importer pays the import duties, although selection of the right tax category is a joint duty, I am very well part of that
<wolfspraul> they are applied equally
<wolfspraul> patents can be withheld, and (some) patent owners do not refrain at all from the most draconian measures they can get away with under the law
<wpwrak> yup. same thing for "regular" copyright.
<wolfspraul> so I don't think any of this type of public domain taxation, culture flat rate, storage capacity taxation etc. influences our decisions or selection of content or software much
<wolfspraul> whereas patent, copyright or trademark infringement would
<wpwrak> paraguay has an interesting model. there, the "public domain payant" must not cost more than the private royalties. i wonder what that would mean for things under the GPL, CC-BY-SA, etc. would they apply that work's historical record or invent some "standard value" ? well, should be fun for the courts in a few decades.
<wpwrak> uruguay seems to have the oldest and most draconian model. there, the state basically becomes the author and can actively "defend" the author's rights.
<wpwrak> well, maybe they'll introduce something similar in germany soonish. after all, there's a lot of nazi material they want to keep locked away, and they presently use copyright for some of that.
<wolfspraul> wpwrak: looking at qcad... how useful do you think it is?
<wolfspraul> where do you see it in the bigger free software toolchain and for what type of work?
<wpwrak> qcad .. it seems to be the principal free 2D cad
<wpwrak> i don't particularly like it, though. seems to be very clumsy to use.
<wpwrak> when i had to do some drawings for my apartment, i tried to do them with qcad. after a day of fumbling, i gave up in frustration and did them with fped.
<wpwrak> of course, fped has the home advantage in this case ...
<wpwrak> ah yes, qcad isn't parametric. so change one value and you get to redo everything that depends on it.
<wpwrak> also, there's a commercial and the free version. the latter lacks some features. (don't remember which)
<roh> wpwrak not for long anymore
<wolfspraul> I'm wondering which tool roh used to create the DXF files that he then used for laser-cutting the Milkymist One case
<wolfspraul> ahh, there he is :-)
<roh> there is somebody working on qcad. search for caduntu
<roh> first step was making it qt4
<wolfspraul> in the .dxf files, I see some references to c:/program files/autocad 2002/ etc. but that may be just there for compatibility...
<roh> i used qcad in the free version.
<wpwrak> roh: "not for long" what ? :)
<roh> what came packages with ubuntu
<wolfspraul> roh: btw, excellent work on that case!
<roh> wpwrak qt4 is so much better than qt3, alone from the looks
<wolfspraul> I cleaned up one picture a little, included it in the picture slider on the qi homepage, the 12/1 community news, etc.
<roh> n.p. i was quite tired and just wanted some shots
<roh> and the light was bad
<wolfspraul> indeed :-)
<wolfspraul> would you be interested to do a bit more work on this? I could pay for the costs.
<wolfspraul> Sebastien said he (or you) wanted to try to make one case with acrylic material.
<wolfspraul> also there is the issue of the microphone
<wolfspraul> and the 3 buttons
<wpwrak> roh: (qt) okay, but will also something in the functionality of qcad change ? i see better CAM support being mentioned. that's nice ... but we can do that with heekscad, too.
<wolfspraul> if we improve this a little more, maybe we have a good enough case to make 30-40 for our upcoming run
<wpwrak> acrylic tends to be fairly expensive. but perhaps that doesn't matter so much in this case.
<wolfspraul> I have one question for the current wood case, I can't really tell from the pictures. is the top wood part only lying down on the side walls? or are there screws to hold it down?
<wolfspraul> for cost, this case took 12 minutes on the cutter, that's 12 * 1 EUR = 12 EUR
<wolfspraul> plus material (wood), plus roh's work (priceless :-))
<wpwrak> there was also the manual groove-making :)
<wolfspraul> I'm far away from raumfahrtagentur, so I cannot do much more right now than to say this is awesome work, offer some money, and encourage people to continue.
<wolfspraul> when I'm in berlin, maybe I can dive into this myself as well, if raumfahrtagentur would be in Beijing I would be there already now :-)
<wpwrak> (groove-making) but i'm sure that can be automated with the CNC mill.
<wolfspraul> yes true, that's another thing that could be improved [groove]
<wolfspraul> so roh - what do you think?
<wpwrak> i think the structure is just a sandwich with long screws pushing the top/bottom plates onto the sidewalls. maybe there are spacers to carry the load, in which case the sidewalls would "float" (more or less)
<wpwrak> i think that case design is pretty ideal for this sort of board. it has lots of connectors, which makes it hard if not impossible to find a pre-made box of the right size
<wolfspraul> sebastien thinks (if I remember correctly) that the whole thing is not stable enough
<wolfspraul> so that was one big reason why he wanted to try acrylic
<wolfspraul> maybe we can get roh onto this a bit more, like I said I need cases anyway and could pay for the costs etc.
<wpwrak> how big is the board ?
<wolfspraul> 10x15 cm
<wpwrak> plywood should be okay for something that small
<wpwrak> but if there are no spacers (yet), then it may be a bit fragile
<wolfspraul> wrong, sorry. 12.5x15cm
<wpwrak> roh: so, are there spacers ? :)
<roh> nope. but its intended to fit with 5mm spacers
<roh> below the pcb
<wpwrak> none on top ?
<roh> not yet. one could use these metal spacers with machine screws
<wolfspraul> roh: are you planning any more work on this?
<wpwrak> not sure what you mean. but spacers come in all sizes, so there ought to be something that fits. just as long as the thread is long enough
<roh> wolfspraul i could. but i'd need a pcb ;)
<roh> wpwrak my initial idea was 'spaces and nice imbus-screws which also work as 'feet'
<wpwrak> roh: yup, that would be nice and tidy
<wpwrak> roh: if you can't find the right spacers, you could also use a piece of pipe (of whatever material you have around) cut to the right length and terminate it with washers
<wpwrak> (and a long screw through all this)
<wolfspraul> kyak: hetzner introduced a new virtual root server, going down to 7.90 EUR / month
<wolfspraul> for running an irc server, that should be perfectly fine
<xiangfu> kyak, about gmenu2x brightness, forget git push. sorry
<xiangfu> forget to update the package makefile in openwrt-xburst.git
<qi-bot> [commit] Xiangfu Liu: update gmenu2x http://qi-hw.com/p/openwrt-packages/0a2704c
<roh> wolfspraul i think irc ports were filtered or so at hetzner.. need to check
<kyak> wolfspraul: hey, thanks for information, i remember seeing it last time. Will ask them if the allow IRC
<kyak> xiangfu: np! thanks you
<xiangfu> kyak: the triggerhappy package error is strange. :(
<kyak> it's upstream already, so we can't fix it right away..
<kyak> xiangfu: i liked fn-handle :) small and nice, doing it's job
<xiangfu> kyak :) but it's way too simple :)
<kyak> xiangfu: what use cases for triggerhappy do you have in mind?
<xiangfu> kyak: my package version is triggerhappy-0.1.3. and md5 is 274807068ffa73166c7024f6334ac45a. maybe we compare the package
<kyak> $ md5sum dl/triggerhappy-0.1.3.tar.gz
<kyak> 19bc56dfff83e41431af1063f7cda926  dl/triggerhappy-0.1.3.tar.gz
<xiangfu> kyak: we can set some hotkey.
<kyak> xiangfu: you need to rm your triggerhappy-0.1.3.tar.gz -\
<xiangfu> kyak: then it's different.
<kyak> the same old problem - updated git commit, nto updated packages version
<kyak> therefore, openwrt won't checkout from git but wil use dl/
<kyak> xiangfu: i know about the hotkey, what i can't think of any use for it :)
<xiangfu> kyak: 1. delete   dl/triggerhappy-0.1.3.tar.gz , 2, make package/triggerhapply/compile V=99, compile fine.  can you make a diff, this is mine. (just download )http://downloads.qi-hardware.com/people/xiangfu/tmp/triggerhappy-0.1.3.tar.gz
<kyak> one sec
<kyak> $ md5sum dl/triggerhappy-0.1.3.tar.gz
<kyak> e1e4b403ec594e39dca649ce19b6f230  dl/triggerhappy-0.1.3.tar.gz
<kyak> what the hell
<kyak> differenet md5sums every time :)
<kyak> let me nwo get your triggerhappy-0.1.3.tar.gz
<kyak> $ md5sum dl/triggerhappy-0.1.3.tar.gz                   52b2f58ddb4d543ad3bc4731d284faf1  dl/triggerhappy-0.1.3.tar.gz
<kyak> xiangfu: your pacakge..
<kyak> same error
<kyak> oh, wait a second..
<wolfspraul> roh: why would hetzner filter irc ports? I mean I believe you but that sounds crazy to me.
<kyak> xiangfu: not working... i suggest a clean test:
<kyak> rm -rf dl/triggerhappy-0.1.3.tar.gz && make package/triggerhappy/{clean,compile} V=99
<kyak> then if it works for you, we next assumption is missing dependency
<kyak> evtable_KEY.h:244: error: 'KEY_RFKILL' undeclared here (not in a function)
<kyak> this is what i get.. and following errors
<xiangfu> kyak: oh. look into the triggerhappy makefile there is one line: evtable_%.h: /usr/include/linux/input.h
<kyak> xiangfu: diffing your and mine triggerhappy-0.1.3.tar.gz unpacked, shows nothing
<kyak> we have identical archives
<xiangfu> kyak: I think there is something different with your HOST input.h and mine.
<kyak> hmmm
<xiangfu> the evtable_KEY.h is create by HOST head file.
<kyak> why would it want to look into my host input.h? weird
<kyak> maybe i don't even have the lindex-headers.. is it an openwrt dependancy?
<kyak> *linux-headers
<xiangfu> kyak: I don't think it's an openwrt dependancy. just the wrong path in triggerhappy makefile
<xiangfu> we should path it to like $(KERNEL_DIR)/usr/include/linux/input.h in openwrt.
<kyak> $ grep KEY_RFKILL /usr/include/linux/input.h
<kyak> #define KEY_RFKILL              247     /* Key that controls all radios */
<kyak> does your /usr/include/linux/input.h any diferernt from my?
<kyak> you are right..
<xiangfu> kyak: there is no KEY_RFKILL in my .../input.h
<kyak> ok.. so what should we do now?
<xiangfu> kyak: send patch to Mirko and cc to upstream mailing list.
<kyak> xiangfu: ok. thanks!
<xiangfu> kyak: btw what is your HOST kernel version?
<kyak> Linux bas 2.6.33.7-desktop-2mnb #1 SMP Mon Sep 20 19:00:25 UTC 2010 i686 i686 i386 GNU/Linux
<xiangfu> seems this KEY is only show up after 2.6.33
<xiangfu> yes. there is no such key in 2.6.32
<kyak> xiangfu: wait a second.. since the change should be done in triggerhappy makefile (not the openwrt makefile)
<kyak> why should i send a patch to Mrko?..
<kyak> oh ok
<kyak> it would be an openwrt specific patch
<kyak> the one in patches/
<xiangfu> kyak: yes.
<kyak> works for me now.. could you please check?
<kyak> xiangfu: this is an svn diff output in feeds/packages directory
<kristianpaul> kyak: is  clean debian squeeze installation
<kristianpaul> i also stared over again with openwrtr repo according wiki doc
<kristianpaul> tell me what look for on my system i will give you the information
<kyak> kristianpaul: do you have locales installed in your system?
<kristianpaul> kyak: yes
<kyak> kristianpaul: can you compile this program?
<kyak> gcc prog.c -o prog && ./prog
<kristianpaul> paul@micro:~$ gcc locale.c -o locale
<kristianpaul> paul@micro:~$ ./locale
<kristianpaul> paul@micro:~$
<kyak> damn
<kyak> :")
<kristianpaul> do i need en-utf8 locale en my system?
<kristianpaul> s/en/in
<methril_work> morning all!
<kristianpaul> morning
<kyak> locale -a |grep en_US.UTF-8
<kyak> kristianpaul: what it says?
<kristianpaul> empty
<kyak> hm
<kristianpaul> setlocale(LC_CTYPE,"en_US.UTF-8") failed!
<kristianpaul> ahh
<kristianpaul> my fault
<kyak> what are your avaialble locales?
<kristianpaul> but i wonder why it compiled bwfore
<methril_work> here is where you miss dpkg (dpkg-reconfigure locale)
<kyak> let's install that locale for starters
<methril_work> :)
<kristianpaul> kyak: that locale never was in my system before and openwrt compiled ok..
<kyak> kristianpaul: openwrt now has wide character support
<kristianpaul> i never activate that local, i dont live in the US or english is my native language ;-)
<kristianpaul> kyak: ha !, that changes everything
<kristianpaul> good :=)
<kyak> kristianpaul: just intersting, what locales you have? (locale -a)
<kristianpaul> can i tell use my es_CO.utf8 instead of en_US.utf8?
<kristianpaul> kyak: es_CO.utf8
<kyak> just install those locales
<kyak> i guess this is the reason why uClibc developers used to distribute pregenerated locales
<kyak> so that people won't have to install it into their host systems
<kyak> but the download of pregeranted locales is broken and old
<kristianpaul> i see
<kristianpaul> ok compiling now
<kyak> mirko_: hi!
<mirko_> kyak: hey
<kyak> mirko_: triggerhappy won't compile if host's kernel is > 2.6.33
<kyak> i've a patch for it..
<kyak> thereis a hardcoded "/usr/include/linux/input.h" in triggerhappy's makefile, as noticed by xiangfu
<mirko_> kyak: ui.., ok
<mirko_> compield fine for me - thought it was kernel version > 2.6.33 as well
<mirko_> (verifying..)
<kyak> mmmm
<kyak> so it's just xiangfu's quess.. he doesn't have KEY_RFKILL in his /usr/include/linux/input.h
<mirko_> who's mark tuson btw? ..
<mirko_> kyak: will check it later - wanna complete some other tasks before
<kyak> sounds like "mike tyson"
<mirko_> ;)
<kyak> mirko_: np, take your time
<mirko_> everybody should use what he/she wants - but trying to tell, why you should/have to use this and this and _not_ to use this.. *sigh* :)
<kyak> mirko_: the patch that can be applied cleanly: http://downloads.qi-hardware.com/people/kyak/tmp/trigger.patch
<kyak> pastebin breaks something
<mirko_> kyak: btw - if you're sending patches to the openwrt-dev list, please attach them as file
<mirko_> they get screwed up, especially in regard of tabs <-> spaces, newlines, etc.
<kyak> yeah, that's probably what happens
<mirko_> tested once again
<mirko_> triggerhappy compiles fine with kernel 2.6.35.8 _without_ this patch
<kyak> hm..
<mirko_> will get a shower, be back for a couple of minutes and then need to go (jfyi, when i'm not answering (anymore))
<kyak> ok!
<kyak> with this patch, however, it builds fine on my machine (2.6.33.7) and also on buildhost
<kyak> so it does no harm :)
<kyak> and it doesn't build on 2.6.33.7 _without_ this patch
<Cavy> Hi.
<Cavy> Should i buy a notebook or stay with the desktop ?
<Cavy> I have no experience with longevity of notebooks.
<xiangfu> kyak: hi
<kyak> xiangfu: hi
<xiangfu> we will try to create a package name: triggerhappy-fixed in openwrt-package.git , apply your patch
<kyak> aÕ?Õa
<xiangfu> this hardcode is definitely a bug. the openwrt package should not read the HOST file
<kyak> xiangfu: i just asked mirko to have a look at that patch (http://downloads.qi-hardware.com/people/kyak/tmp/trigger.patch)
<kyak> so maybe we won't have to create additional packages
<kyak> though mirko says that it builds fine on 2.6.35.8
<xiangfu> kyak: need look into why it's builds fine in Mirko's 2.6.35.8 , but according to this HARDCODE, the patch is good for openwrt. :)
<kyak> xiangfu: i also tested both on my machine and build host with this patch, build fine
<larsc> kyak: in my opinion a better fix would be to use something like `echo "#include <linux/input.h>" | $(CC) $(CFLAGS) -E - | awk ...`
<xiangfu> kyak: ok. let's just create a package triggerhappy-fixed, when this patch goto upstream we remove the triggerhappy-fixed. :)
<kyak> larsc: oh! in fact, is a good idea
<kyak> larsc: but then, it should better be fixed upstream in triggerhappy
<kyak> and we don't have to change the openwrt makefile
<mirko_> kyak: well, the git rev you have to ;)
<lekernel> "Read the white paper: Building an IP Surveillance Camera System with a Low-Cost FPGA"
<mirko_> inside the openwrt makefile
<lekernel> well, I guess that's where the money is :)
<mirko_> need to go
<kyak> mirko_: right..
<xiangfu> larsc: great.
<kyak> xiangfu: do i recall correctly that it is a pain to make triggerhappy developers accept a patch?
<kyak> it's very tempting to create just triggerhappy-fixed :)
<xiangfu> kyak: sorry. what you mean "do I recall correctly " (sorry for bad English)
<kyak> instead of asking both openwrt and triggerhappy developers to do something
<kyak> do i remember it right
<kyak> that you were discussing with wolfspraul about it..
<mirko_> need to go now to univeristy
<mirko_> see you later
<xiangfu> kyak: i just take a look of triggerhappy. it's already go to 0.1.4
<kyak> did they change that hardcoded path?
<xiangfu> kyak: no
<kyak> xiangfu: then i will prepare the patch for triggerhappy makefile like larsc suggested
<kyak> let's see if they accept it fast
<larsc> kyak: one minor change, use $(CPPFLAGS) instead of $(CFLAGS)
<kyak> afterwards, we will ask someone to update the triggerhappy git revision in openwrt :)
<rafa> wpwrak: (packages) from the examples what you gave me I have two categories: 1) there as you said some packages with different versions. One live under all/ repo dir, and another version under mipsel/ repo dir. I do not know exactly why are them there.. and how to manage that yet. ON this category
<kyak> larsc: thanks for your hints.. i will test it
<rafa> wpwrak: the packages are man-pages, *common*.. I would say that all/ repo dir has packages which you can install on any arch.. in this case our repo is just for mipsel, but OE put those there if these are packaeges wich dont depend of any arch.. (like manpages.. or stuff like *common*).
<rafa> wpwrak: but, I need to learn about why there are some of them with different version and how to manage them. I am not an oe expert anyway :).. Also, under all/ there are few packages..and them are not criticail I would say.. It just have stuff like documentation or maybe icons.. and these are not many packages there either (in comparison with mipsel/ repo dir). Now, the second category:
<xiangfu> kyak: I already fort the github of triggerhappy.
<xiangfu> *fork
<rafa> wpwrak: 2) the second category are packages you exactly found :) I created an extra-packages/ repo dir which has few packages which I built with toolchain. I put those packages there to not confuse them with packages built from OE. But then you found that I built rxvt with toolchain and OE already found another rxvt with another version (one live
<rafa> wpwrak: under mipsel/ repo dir and another under extra-packages/). The same happens xserver-kdriver for example. I built another xserver-kdriver version and put that under extra-packages because the version buit by OE had keyboard problems with nn.
<rafa> wpwrak: now.. how to manage them?.. the jlime-pkg is so simple, so it is not smart to choose or decide what to use.. it just find the name of package and whatever version it is it keeps that version to install
<rafa> wpwrak: but again.. these are few cases I would say.. and that will not break anything anyway.. I mean.. most of them are standalone and for the category 1) I would say that these do not have critical packages.. just documentation and stuff like that (and no many packages either)
<viric> what is that trigger happy?
<kyak> a daemon to produce events triggered by keys
<xiangfu> viric: A lightweight hotkey daemon
<kyak> xiangfu: btw, would be great to fork it as "triggersad" :)
<wpwrak> rafa: okay. i just wanted to check that jlime-pkg indeed doesn't do anything special about them (explicitly or implicitly). what i'm after is a faster version of jlime-pkg. but i need to understand exactly what it does first.
<wpwrak> rafa: so i guess it can't hurt to be able to also consider versions. not quite sure how to compare version strings, though.
<rafa> wpwrak: I found another bug or missing feature in jlime-pkg if you are doing some smarter thing :)
<kyak> xiangfu: awesome. id' leave it like that :) have you tested?
<xiangfu> kyak: tested in my laptop.
<viric> xiangfu: ah great. I can't find the url of it..
<wpwrak> rafa: what would that be ?
<larsc> xiangfu: '$<' should be removed from awks arguments
<xiangfu> larsc: thanks.
<rafa> wpwrak: the jlime-pkg does not use the "Provides:" field from Packages files.. For example. Package: alsa-utils-locale-ja .. it has an extra "Provides: alsa-utils-locale, ja-translation" field, so if another package to be installed needs "alsa-utils-locale" packages installed
<rafa> wpwrak: some of alsa-utils-locale-* shoulb be installed, or some of them shoulb be installed.
<rafa> wpwrak: no idea how to manage that.. because many packages provides the same.. If some package needs alsa-utils-locale installed and it is not then which version of alsa-utils-locale-* packages jlime-pkg should choose to install ?
<rafa> wpwrak: but, also.. I have not had that problem yet installing packages.. No sure how to test that to find the problem. I tried a couple of them which needs some package which just appears under Provides: but it happened that all my tries were already installed
<rafa> wpwrak: Do you follow me? :).. maybe I need to explain better :P .. I mean.. if you install (on the example above) alsa-utils-locale-ja.. you are installing that package and also the sytem registers that alsa-utils-locale is installed as well.
<kyak> xiangfu: builds fine here with and without $< arguments to awk (dunno what they mean)
<wpwrak> are "alsa-utils-locale" and "ja-translation" two separate "packages" in this case ? or is "ja-translation" a qualifier of "alsa-utils-locale" ?
<kyak> xiangfu: i think it's good to git poke the author :)
<rafa> wpwrak: no.. those packages dont exist as packages.. those are just virtual names For example.. if you need to be installed alsa-utils-locale you need to install some alsa-utils-locale-*. Any of them provides alsa-utils-locale, but alsa-utils-locale is not a real package on the repo
<rafa> wpwrak: ah no.. you are asking me the relation between  "alsa-utils-locale" and "ja-translation" .. Mmh.. no sure if there is a relation between them
<wpwrak> rafa: (virtual packages) yes, i understand that part
<xiangfu> kyak: send out to upstream author.
<wpwrak> do you know if there's any formal specification of this file format ?
<kyak> xiangfu: thanks!
<rafa> wpwrak: file format?.. you mean the package file?
<rafa> wpwrak: the files are debian format.. those are "ar" and inside you have two files.. a data.tar.gz and a control.tar.gz.. the data contains the files for / .. the control the metadata of the package.
<wpwrak> no, i mean files like packages-all
<xiangfu> kyak: let's wait until tomorrow. see if the triggerhappy author accept the patch.
<kyak> xiangfu: sure
<wpwrak> rafa: also, do you know the semantics of the stuff in the Status: lines of /usr/lib/opkg/status ?
<DocScrutinizer> moo
<kyak> xiangfu: i see the authoer has commented
<xiangfu> kyak: oh. really. he is fast
<kyak> i can't say if he' right or not
<rafa> wpwrak: no sorry, anything of those
<wpwrak> rafa: ah well, i'll use the "best guess" strategy then :)
<kyak> xiangfu: i think he's right.. evtable_*.h files are empty now..
<rafa> wpwrak: :)
<xiangfu> kyak: ok. yes. I tested it before I remove the "$<"
<kyak> what's "$<" doing? i tested it also after i removed "$<", those files are still empty
<xiangfu> kyak: the "$<" is "/usr/include/linux/input.h" in that makefile.
<xiangfu> kyak: we are not well test it. let's just create a triggerhappy-fixed for now. it's fast and well tested. :)
<kyak> i suggest the triggersad name :)
<kyak> echo "#include <linux/input.h>" | gcc -E -dD - | grep define
<kyak> xiangfu: works liek this
<kyak> -dD makes preprocessor leave the defines
<kyak> xiangfu: you might want to suggest this as an option to author
<kyak> xiangfu: tested, works fine
<kyak>         echo "#include <linux/input.h>" | $(CC) $(CPPFLAGS) -E -dD - | \
<kyak>         awk '/^#define $*_/ && $$2 !~ /_(MAX|CNT|VERSION)$$/ {print "EV_MAP("$$2"),"}' > $@
<kyak> seen it...
<kyak> he's in fact just grabbing the header file name from preprocessed output
<kyak> might work, too
<kyak> i just think -dD is better
<kyak> since we are interested in those defines
<kyak> not files name
<kyak> ah see his comment
<kyak> makes sense; though i doubt someone wants to define a custom input.h
<kyak> well, at least we've drawn his attention to this
<kyak> and now it will maybe work :)
<kyak> make[3]: *** No rule to make target `evtable_EV.h', needed by `eventnames.o'.  Stop.
<kyak> with the authors's commit -\
<xiangfu> kyak: have you edit the openwrt package Makefile??
<kyak> no, i just create the patch for TH makefile
<kristianpaul> unbelievable!!, GPIF designer a sofware from Cypress http://www.cypress.com/?rID=14448
<wpwrak> kristianpaul: *.zip ... looks windows-ish
<kristianpaul> now the posible usable code i may use is generated from a non-free tool :*
<kristianpaul> i wonder is this thing is used in usrp as well...
<kristianpaul> as i can read this code for the gn3s dongle is reused from usrp
<kristianpaul> argg
<wpwrak> perhaps the other way around ?
<kristianpaul> wpwrak: universal driver or ehat u mean?
<kristianpaul> s/ehat/what
<kyak> xiangfu: should work like this.. whatever :)
<kyak> xiangfu: thanks!
<kyak> though the authors fix is not complete.
<xiangfu> kyak: also sended this patch to Mirko.
<wpwrak> kristianpaul: that ursrp code got merged somewhere along the way (not quite sure what you're dealing with here, though)
<kyak> xiangfu: great!
<xiangfu> kyak: now I need working on the "netsurf" :)
<kristianpaul> wpwrak: wait a min i-ll paste some funy code i think
<kyak> xiangfu: good luck to you :) see you later
<xiangfu> kyak: see you.
<kristianpaul> firmware code is not so big, i was readina bit what i can read about sige chip ans is just initialziation and basic setup
<kristianpaul> wpwrak: http://paste.debian.net/100123/
<wpwrak> that's "not so big" indeed :)
<wpwrak> rafa: hehe, there are HomePage and Homepage tags :)
<wpwrak> rafa: are you sure the entry of gmu in packages-extra-packages is correctly formatted ? it's the only one what has lines that don't begin with  <tag>:
<kristianpaul> wpwrak: http://paste.debian.net/100125/  DO NOT EDIT ;)
<kristianpaul> wpwrak:  well the main code is more lines, if can pastebin if you want, but is just initilization and then jump to the loop
<wpwrak> kristianpaul: aaah ! now i have the connection.
<wpwrak> interesting
<wpwrak> yeah, got it. you're right. that stuff comes from the evil proprietary tool
<wpwrak> luckily, the USRP2 doens't have USB :)
<kristianpaul> argg
<kristianpaul> :D
<kristianpaul> good for you
<kristianpaul> now i'm warned in case i decide some day buy usrpv1
<wpwrak> mandatory seppuku narrowly avoided :)
<rafa> wpwrak: no.. all under extra-packages could not be well formatted.. It is just an extra packages which could not be present.. The main repos are the other dirs.. If we remove the whole extra-packages (rm -rf extra-packages/ :) ) all the repository is okey
<rafa> wpwrak: (okey=sane)
<wpwrak> rafa: so you say extra-packages shouldn't be there ?
<kristianpaul> ah
<kristianpaul> No. The formatting of the data is all handled in the FPGA. The FX2 firmware doesn't even see the bulk data going in and out. The data is transferred by DMA to/from the GPIF from/to the FPGA USB buffers.
<kristianpaul> Does FX2 reformat incoming/outgoing FPGA data?
<wpwrak> kristianpaul: i don't think that's its purpose
<wpwrak> kristianpaul: i mean, beyond making it fit into USB packets and such
<kristianpaul> wpwrak: what u think then?
<wpwrak> well it just passes the data stream between FPGA and USB, no ?
<kristianpaul> yes
<kristianpaul> bueno me avisa cuando para cambiar la config d cleinte
<kristianpaul> oops
<rafa> wpwrak: it could or not.. I just added that manually to upload packages built using toolchain. But if it is not there all the repo is sane. I would like to have extra-packages there to continue building more nice stuff which OE does not bring or not builds.. (like emacs for example).
<rafa> wpwrak: if it is a problem because you see that things do not work under extra packages then we can remove it
<rafa> wpwrak: I have my own local copy anyway :)
<wpwrak> naw, i'm just curious what it does
<wpwrak> ;-))
<wpwrak> i'm a bit surprised that OE wouldn't have emacs, though
<rafa> wpwrak: OE has
<rafa> wpwrak: do you remember the story I was telling you about what OE tried to do to build emacs?
<rafa> wpwrak: (I named it "if you know how OE tries to build emacs you would like to leave the it world"
<rafa> )
<wpwrak> yeah, dump/undump :) so it tries to build it but it takes very long ?
<rafa> wpwrak: it took long and it failed.. but the fun part was seeing OE trying to have a huge qemu rootfs to run a whole mips system to build emacs..
<wpwrak> i guess nobody thought of cross-compilation when they did that dump/undump things in emacs :)
<qi-bot> [commit] Xiangfu Liu: add libparserutils http://qi-hw.com/p/openwrt-packages/2b8e304
<qi-bot> [commit] Xiangfu Liu: add netsurf, direct fb web browser http://qi-hw.com/p/openwrt-packages/22bdc35
<qi-bot> [commit] Xiangfu Liu: add libhubbub, an HTML5 compliant parsing library http://qi-hw.com/p/openwrt-packages/5ab2226
<qi-bot> [commit] Xiangfu Liu: add libcss, a CSS parser and selection engine, written in C http://qi-hw.com/p/openwrt-packages/1d2f2bc
<qi-bot> [commit] Xiangfu Liu: mark libcss libhubbub libparserutils netsurf as BROKEN, not finish yet http://qi-hw.com/p/openwrt-packages/1f8d6bd
<aisa> I'm looking at the config.full_system file, and it contains this line:
<aisa> "CONFIG_PACKAGE_tune2fs is=y"
<aisa> is that space in there a bug?
<aisa> good morning everyone.
<aisa> or good evening ;-)
<kristianpaul> lunch hour
<kristianpaul> :O  The Milkymist GUI toolkit, because X11 sucks!
<LunaVorax> kristianpaul, Oh I didn't knew there already was alternative to X11
<mindw0rk> Hey guys, I've heard that it was announced here about the gamepad usb-hid support being added to the kernel
<mindw0rk> Who might be the person behind it?
<larsc> you
<mindw0rk> :[
<rafa> larsc: in current kernel, drivers/mfd/jz4740-adc.c.. there is a struct platform_driver jz4740_adc_driver = {..} which has .remove = __devexit_p(jz4740_adc_remove). Should not be it __exit_p(..) ?
<kristianpaul> ohh sie projects are in final week
<kristianpaul> :/
<kristianpaul> oh the paintbrush got interesting
<kristianpaul> ohh i founded an fft implementation in verilog.. good
<kristianpaul> ok time to get free of patent jlime :)
<kristianpaul> also the boostraping system
<kristianpaul> si es cierto !!
<kristianpaul> oops
<kristianpaul> oh nanoterm font is tooo small
<kristianpaul> wpwrak: can you tell me how are you using jlime boostraping thing..
<kristianpaul> rafa: como suena "hardware al reves" ?
<wpwrak> kristianpaul: i didn't use the bootstrap. i just installed the tar.gz on an uSD card: boot openwrt from nand, insert card, umount card, mke2fs /dev/mm..p1, mount /dev/mm..p1 /mnt; cd /mnt; bzcat ...bz2 | tar xf -; umount /mnt; sync; press M and reset
<wpwrak> (not quite sure if it was .bz2. or .gz)
<kristianpaul> wpwrak: ah you are using bootstraping image on uSD. right? :)
<kristianpaul> ahh
<kristianpaul> i still not undetstand that method
<wpwrak> i didn't use the bootstrap image. i used the other one, ~80 MB
<kristianpaul> ah ok
<kristianpaul> yeah i have that too
<kristianpaul> but i tought you'were crosscopiling apps fot jlime on your pc, right?
<wpwrak> sure, i do that too :)
<kristianpaul> how?
<kristianpaul> when i saw that 9~ Mb image for boostrap i tought, ok wait a min where is the toolchain..
<wpwrak> i untarred jlime-2010.1-2010.1-mipsel-linux-toolchain.tar.bz2 on my pc (from /)
<wpwrak> now .. the url ...
<kristianpaul> from / .. oh
<wpwrak> all the paths begin with ./usr/local/jlime-2010.1/mipsel/
<wpwrak> so it's safe
<wpwrak> then  . /usr/local/jlime-2010.1/mipsel/environment-setup
<wpwrak> note: ^-- the dot is important !
<kristianpaul> wait  a amin
<kristianpaul> 45Mb~ good
<kristianpaul> wpwrak: are you sure is not danegours, just descopmresed ona separte folder and i'm seeeing  (bin  boot  dev  etc  home  lib  linuxrc  media  mnt  proc  sbin  sys  tmp  usr  var)
<qi-bot> [commit] Xiangfu Liu: fix libhubbub, libparserutils compile and install http://qi-hw.com/p/openwrt-packages/59dacaa
<qi-bot> [commit] Xiangfu Liu: add libwapcaplet, a string internment library http://qi-hw.com/p/openwrt-packages/da7e7d1
<qi-bot> [commit] Xiangfu Liu: fix libcss compile and install http://qi-hw.com/p/openwrt-packages/72bfce5