<wpwrak> mmh, about 180 USD fixed + 1.2 USD per board then, correct ?
<kristianpaul> wpwrak: seems
<kristianpaul> wpwrak: wow price go down..
<kristianpaul> a LOT
<wpwrak> :)
<wolfspraul> what did you do to bring the price down?
<kristianpaul> ask for 100 units not 10
<kristianpaul> well i just _ask_ i said, i'm curios no compromise
<wpwrak> s/compromise/promise/   :)
<kristianpaul> :p
<wpwrak> it's just the underlying calculation. real price = large_fixed_cost + units * small_unit_cost
<kristianpaul> jeje
<wpwrak> so the calculation unit_price = real_price / units  doesn't tell you what larger volumes will cost
<wolfspraul> ah ok, got it
<kristianpaul> argg this is male conector i dont have a adapter right now...
<kyak> suddenly breaks into the silence
<qi-bot> [commit] kyak: qstardict: fix build with 0.9.32 http://qi-hw.com/p/openwrt-packages/90818e8
<kyak> xiangfu_: ping
<xiangfu_> kyak: hi
<xiangfu_> (2 hours later)
<kyak> xiangfu_: he, not a problem :)
<kyak> xiangfu_: what do you think about ncursesw package in openwrt-packages git? it is necessary for backfire, but won't be necessary for trunk
<kyak> so we will have to remove it
<xiangfu_> hmm..
<xiangfu_> kyak: we can disable it in config.full_system for now. I was thinking: before we finish the openwrt-xburst.git rebase on 'trunk'. we better leave the openwrt-package.git full suppor the backfire.
<kyak> xiangfu_: there is not need to disable it, cause it causes no problems. It will just override the ncursesw from trunk. But i was wondering, what should we do after we finish the rebase?
<xiangfu_> oh. yes. after rebase we will just remove it
<kyak> so we will basically not support backfire anymore, and people would just checkout the last working git revision, as seen in VERSION, right?>
<kyak> (if they want to build backfire )
<xiangfu_> also like 'triggerhappy' stuff. we will try to remove all duplicate packages.
<xiangfu_> kyak: yes.
<kyak> i'm also asking it because for exmaple gcc-mips 4.3.3 would fail to build with trunk. But i made gcc-mips 4.5.2 build with trunk
<kyak> and i really don't want to make gcc-mips 4.5.2 work with backfire, too :)
<kyak> that's just double work
<kyak> probably not necessary
<kyak> therefore, after updated of gcc-mips 4.3.3.->4.5.2 in oprnwrt-packages it would not build anymore with backfire
<xiangfu_> (probably not necessary) agree with you
<xiangfu_> yes. if someone really want backfire. as you said using the VERSION files.
<kyak> there are other changes required in openwrt-packges. some patches dropped, some added
<kyak> it's really hard to look back to backfire all the time
<kyak> ok, good :)
<xiangfu_> sure. that is why 'trunk' packages sometimes not working in 'backfire' :-)
<xiangfu_> kyak: maybe we start a new branch in openwrt-package for trunk
<wpwrak> grmbl. the clearance thingy is highly mysterious. it picks the right value but then draws the wrong size. it gets even better - if i change the value manually in the .pro file, it shows the change in the dialog, yet it still picks the previous one when plotting. i wonder where it gets that from.
<kyak> xiangfu_: there are onyl few packages in openwrt-packages that have problems when building in trunk. So perhaps another branch is not necessary?
<wolfspraul> great, Ingenic removed all Programmer's Manuals from the FTP server again
<wolfspraul> "it was a mistake"
<xiangfu_> no another branch will be great. the less the better :). I am not look into the openwrt-package <--> trunk detail.
<wpwrak> wolfspraul: :-(
<wolfspraul> what a joke. but - makes Milkymist all the more fun :-)
<wolfspraul> next meeting with the CEO I will mostly demo him Milkymist One
<wolfspraul> I'm learning how to be a good Chinese.
<xiangfu_> kyak: so agree with you. no another branch :)
<xiangfu_> kyak: another little thing. what do you thing using all 'commandline apps' using same icon: utilities-terminal.png?
<qi-bot> [commit] Werner Almesberger: BOOKSHELF.ingenic: removed for Ingenic prefer to leave developers in the dark http://qi-hw.com/p/wernermisc/88e0f82
<kyak> xiangfu_: when you start examining the openwrt-package <--> trunk, let me know, i'll give you some patches :)
<xiangfu_> kyak: compare to add "[]" to name. or add "C" to icons. maybe change them all to 'utilities-terminal.png' is not a bad idea
<xiangfu_> kyak: very thanks.
<kyak> xiangfu_: we had this idea, but you told that emacs and vim won't have their nice icons in this case :)
<kyak> i like the icon of abook myself :)
<wolfspraul> wpwrak: that was quick :-)
<larsc> wolfspraul: and you told them!
<wolfspraul> you think my email made them realize they were up there?
<wolfspraul> it's possible, if so that would be bad and I will change my communication style with them.
<wolfspraul> but then files already started disappearing before I emailed them, although I am not exactly sure what was removed when.
<larsc> they would have realized it sooner or later
<wolfspraul> I'm looking forward to my Milkymist demo...
<wpwrak> wolfspraul: will you mention that one of the main motivations for doing this is insufficiently open documentation from chip vendors ? :)
<wolfspraul> they are not that rational, really
<xiangfu_> kyak: I think I change my mind. 1. 'utilities-terminal.png' indicate that is a command line app  2. 'utilities-terminal.png' almost half of those program is usually start in 'terminal' (in fact I never first open vim then open file inside vim)
<wolfspraul> I will try to get the _pms up again, well same as the last 1.5 years
<kyak> xiangfu_: i think it's OK using utilities-terminal.png for all terminal apps. Maybe we can make exception for some programs, i don't know. But overwall this would be eye catching and clear for users that this is the terminal app they are going to launch
<wolfspraul> they are most worried about documentation for the video accelerator, btw
<xiangfu_> 3. it's don't let user down. like beautiful ICON but command line interface.
<xiangfu_> kyak: yes. sure.
<wpwrak> the more video, the more patents. kinda makes sense.
<xiangfu_> sure. we can keeps some of them like 'abook' 'emacs' :)
<wpwrak> ah, the _ds are still there. okay, then i can bring back some of the bookshelf
<xiangfu_> kyak: definitely using  utilities-terminal.png in 'bc'
<kyak> xiangfu_: "tclsh" is a nice icon, too ;)
<kyak> sure
<wolfspraul> the _ds were always public
<xiangfu_> kyak: I will ask Yi to look into which one using 'utilities-terminal.png' is better. which one keep the beautiful icon.
<wpwrak> wolfspraul: ah, didn't know that
<kyak> xiangfu_: all right!
<xiangfu_> kyak: ok. we done with terminal icons. (probably we will only change two or three to 'terminal.png' after all :D)
<tuxbrain> !see wpwrak
<tuxbrain> wow channel without wpwrak for more than two hours.... the end is near... gonna pray some random goods just in case
<tuxbrain> btw wejp, thanks a lot for the non-black-if-not-on-frontend feature, It's really usefull to listen music while doing other things :)
<wejp> :)
<tuxbrain> wejp, do you have any other features in mind for next releases?
<wejp> yes, there are a few things. in the next version it will be possible to reduce Gmu`s verbosity on stdout (you can reduce its output in several steps from very verbose to quiet). also i`ve planned to add support for http streaming audio
<wejp> there are several other small thing on my todo list, those are just two that came to my mind right now ;)
<wejp> also i might add a text.only frontend, but i don
<wejp> t know if it will be ready with the next release
<tuxbrain> wow :), any improvemente on shorting/filtering the playlist?
<tuxbrain> wpwrak: hi, I have the quote for the PCBs and by the end of the week the smt ones
<tuxbrain> both 215¬ set up each model , x100 2.4046¬ each unit || 500x 0.6795¬ each unit
<tuxbrain> so 500x 1,1095¬ each
<tuxbrain> ENING
<tuxbrain> mm sorry atusb is slightly diferent on price
<tuxbrain> same setup price 215¬ but  x100 2.3667¬ each unit || 500x 0.6905¬ each unit
<tuxbrain> so this one 500x  1,1205 each
<tuxbrain> wpwrak: have you recived my last input about atben/atusb pcbs? I have experienced problems with inet conection
<tuxbrain> well seems is not my inet, it has been registered by the log
<wpwrak> tuxbrain: yes, thanks ! looks quite reasonable
<wpwrak> tuxbrain: for 100 units each, the total cost would be something like EUR 907, so going to +400% pieces is only +22% more expensive
<wpwrak> tuxbrain: how many units would you want to make ?
<tuxbrain> let's see how much smt will cost and will tell, but its clear I will go for the 500 pbc's
<wpwrak> tuxbrain: there's also the question whether one would want to make design changes after a first run, e.g., to improve RF characteristics or for any support possibly needed by a case
<wpwrak> tuxbrain: okay, great.
<tuxbrain> wpwrak: (modifications) well this is part of the game, isn't it?
<wpwrak> tuxbrain: yeah :) also, since you'll "leak" a few boards here and there, e.g., to kristianpaul, it's good to have a bit of a reserve
<wpwrak> tuxbrain: did they say anything about the protective cover ?
<tuxbrain> nop I will ask
<wpwrak> tuxbrain: and did you ask them about the stencil ? that would normally also come from the pcb fab
<tuxbrain> yes I have asked them but no answer, but I'm not too much worried due pcb and smt vendors are working quite close, the pcb vendor is the usual board provieder of the smt vendor
<tuxbrain> smt vendor was "surprised" I where talking with them directly :)
<wpwrak> good. it's always best if they're matched. saves you from nasty surprises :)
<wpwrak> hehe ;-)
<wpwrak> it'll take a bit longer until i have the final versions of the fab files. i found a bug in kicad that generates an incorrect solder mask and i haven't figured out yet why this happens
<wpwrak> i'll also have to shut my workstation for a while for maintenance. with the loss of mail.openmoko.org, i need to set up and test my own mail system
<wpwrak> and that only makes sense on a stable infrastructure. since i upgraded to ubuntu N by accident, i don't have that.
<wpwrak> i was hoping i could just sit it out, but now with the loss of mail added to the mess, that's no longer an option
<wpwrak> so i'll try to revert to a stable version and try to recover all data added since that checkpoint
<wpwrak> if i can't revert, i'll have to reinstall my workstation from scratch
<wpwrak> so it may take 1-2 days before i have things up again. let's hope nothing else goes wrong.
<tuxbrain> do you want a tuxbrain.org or tuxbrain.com email address?
<tuxbrain> I pay all my bills :P
<wpwrak> heh, thanks :) naw, i'll modernize almesberger.net
<wpwrak> a long time ago, i had almesberger.net set up with a vpn for in- and outbound mails, but that meant that everything was handled by my workstation. that was okay when i wasn't away from home for too long, but with the long trips to openmoko, it became increasingly problematic, because any power failure at home usually meant that my systems went down and stayed down
<wpwrak> that's why i switched to openmoko.org. now, i'll have to set up a more distributed approach, with a proper spam filter
<wpwrak> also, almesberger,net has suffered a disk failure just a few weeks ago and had to be set up from scratch, so things aren't entirely stable over there yet either
<wpwrak> the good thing that came with the disk failure was a bigger disk. so at least i now have some more room to experiment with things :)
<tuxbrain> In spain we have a said which "sui generis" translation should be : "In house of blacksmith, wood spoon" :P seems you case
<wpwrak> now .. first step ... push all data i don't mean to keep online to dvds ... then a full image backup to an external disk ...
<wpwrak> ;-)))
<tuxbrain> wpwrak: well whatever "outsourcing" you may need you can count on tuxbrain's servers
<wpwrak> tuxbrain: the last few months have indeed been rough on my infrastructure. lost my main work disk, then the pc controlling my mill, then the disk in almesberger.net died (a server hosted in the US), then the upgrade from hell, now mail.openmoko.org, ...
<tuxbrain> mmm it smell to sabotage!
<wpwrak> ah, two screens as well. at least these were easy to replace :)
<wpwrak> tuxbrain: (smt) did they indicate whether the data you sent them is enough for a quote ?