<wolfspraul> xiangfu: hey there
<wolfspraul> I'm just testing the new image a little. I noticed that when I launch StarDict for the first time after flashing, it hangs for a long time, maybe > 60 seconds.
<wolfspraul> then it finally comes up
<wolfspraul> after this first time, even after reboots, startup time is much better
<xiangfu> wolfspraul: yes. it's try to index the dictionary.
<wolfspraul> so is it saving something into the rootfs?
<wolfspraul> can we include a prebuilt index in the image?
<xiangfu> wolfspraul: yes. one .idx file
<wolfspraul> we should find a way to prebuild this index and include it in the image (package)
<xiangfu> wolfspraul: yes. seems we just need copy the rootfs index to the package file.
<xiangfu> wolfspraul: I will working on that.
<wolfspraul> ah OK, great
<qi-bot> [commit] kyak: ben-cyrillic: add the required LC_ALL env variable http://qi-hw.com/p/openwrt-packages/5de66bd
<wolfspraul> xiangfu: when I launch NanoMap, I cannot return to gmenu2x (it will hang after exiting NanoMap)
<wolfspraul> do you have this too?
<xiangfu> same here.
<kyak> KDLC @C:C )
<kyak> same here :)
<kyak> in fact, this will happen to every Qt app
<kyak> (tryed with a Qt "hello world")
<xiangfu> kyak: it's uClibc 9.0.30 problem. make QT not exit correct.
<kyak> xiangfu: i'd say, it's the problem of Qt.. because it appeared after som qt update
<kyak> though you are right, it's working fine with newer uClibc
<kyak> so maybe it's both uClibc and Qt problem :)
<wolfspraul> what are the default uclibc and qt versions in the backfire release? is our image using those?
<kyak> uclibc is coming from base system, while qt is from feeds
<kyak> that's why qt got updated while uclibc basically remained the same
<kyak> now we have shiny new qt from latest feeds and uclibc 0.9.30.1 from backfire
<wolfspraul> well stability trumps (broken) features
<wolfspraul> I was wondering how the versions of the OpenWrt releases and the feeds are kept in sync anyway
<wolfspraul> how does this work?
<kyak> for example, at the time of backfire release, qt was 4.6.2 (http://downloads.openwrt.org/backfire/10.03/xburst/packages/)
<kyak> right now it's 4.7.0 in feeds
<kyak> wolfspraul: i'm not sure.. perhaps it's just the latest version of feeds at the time of release, and then feeds continue going forward
<wolfspraul> he
<wolfspraul> so no sync at all?
<wolfspraul> how can we 'pin' Qt to 4.6.2 (assuming that will fix the NanoMap bug)
<kyak> i've been always seening 'feeds' and 'base system' as pretty different parts.. but i could be wrong
<kyak> one should just be able to get the base system without feeds.. and feeds mechanism would just provide additional packages, if the user wishes so
<xiangfu> wolfspraul: it's hard.
<kyak> so it seems that this strategy may lead to discrepancy between "old" base system and "new" feeds
<xiangfu> if we back QT to 4.6.2. then we back all the package in svn://svn.openwrt.org/openwrt/packages to old version.
<xiangfu> wolfspraul: there is one method. add QT 4.6.2 to openwrt-package.git. disable the upstream QT. enable openwrt-xburst.git one.
<kyak> otherwiser, we can try and fix uClibc
<xiangfu> s/openwrt-xbursg.git/openwrt-package.git/
<wolfspraul> xiangfu: I don't understand what you mean with "all pacakges in ... to old version"
<wolfspraul> first I try to understand how the feeds and openwrt releases stay in sync, if at all
<wolfspraul> I think I remember seeing svn version numbers together with the feed urls somewhere
<wolfspraul> we haven't been able to make an image where gtk/sdl and qt all work since June :-)
<wolfspraul> with 'all work' I only mean that a simple app can be started and exit without a hang
<wolfspraul> can't go much lower than that :-)
<wolfspraul> so if older versions help, let's do that first to have a stable image, then we can try with newer versions again, but at least we have a stable base
<xiangfu> here is the feeds configure file:
<xiangfu> here is the release package svn versions :http://downloads.qi-hardware.com/software/images/NanoNote/Ben/testing/2010-11-07/VERSIONS
<kyak> wolfspraul: btw, sdl works just fine
<xiangfu> QT is included by "packages" , now the svn version is 23909.
<xiangfu> for example we back the "pakcage" to 21808. then all the packages in "package" will all goto old version.
<wolfspraul> kyak: yes, sdl works now :-) that's good
<wolfspraul> xiangfu: OK, what do you propose for the NanoMap bug?
<xiangfu> wolfspraul: I would like use setup one old version in openwrt-package.git.
<kyak> are there any problems with gtk and uClibc 0.9.30.1?
<kyak> i remember stardict won't start when uClibc is 0.9.30.1
<xiangfu> kyak: stardict works fine
<kyak> means that only Qt has problems, right?
<xiangfu> kyak: but when you startup "stardict" in terminal. it's will not exit. it's a directfb bug.
<xiangfu> or a stardict bug.
<kyak> xiangfu:  i see
<xiangfu> when stardict exit. there is no stardict thread anymore. but the screen just don't go back to terminal
<wolfspraul> first goal: an image where all apps that have an icon in gmenu2x after booting can at least be started and exited :-)
<wolfspraul> how about that?
<wolfspraul> I haven't seen that in many months...
<wolfspraul> I wouldn't know how to lower this more, unless we simply remove those apps.
<xiangfu> all apps? we need work on gmenu2x for make the gmenu2x can start a terminal apps.
<xiangfu> for now the gmenu2x can not start a terminal apps. like "joe" "mutt"
<xiangfu> most of package in openwrt is terminal apps,
<kyak> to start a terminal app, gmenu2x should exit, start this app, and then respawn again
<kyak> i think it's the same way it works now for dgclock
<mth> xiangfu: why can't it start them?
<mth> I have "read" as a menu item (idea from zear) to show the console and to allow the screen to go into power saving
<xiangfu> mth: I don't know the detail . I have add the icon of "joe" "lynx" "alsamixer" ... to gmenu2x. none of them started correct
<mth> is this with the latest version of gmenu2x? (from projects.qi-hardware.com git)
<xiangfu> mth: yes.
<kyak> mth: you should share your gmenu icon
<kyak> the menu item
<mth> /boot/local/gmenu2x/sections/applications # cat read
<mth> title=read
<mth> exec=/boot/read
<mth> the menu entry is only those two lines
<kyak> what does "wrapper" mean?
<kyak> exec=/usr/bin/dgclock
<kyak> wrapper=true
<kyak> like this
<kyak> xiangfu: maybe you need to remove that "wrapper" thing from terminal apps
<kyak> like mth suggests
<xiangfu> let me test
<mth> I don't know what the wrapper option does, but I don't have it here and here it works
<kyak> mth: do you know how to make "folders" in gmenu? to organize apps
<mth> this is how gmenu2x handles "wrapper" internally:
<mth> if (wrapper) command += "; sync & cd "+cmdclean(gmenu2x->getExePath())+"; exec ./gmenu2x";
<mth> I have no idea why those extra steps would ever be necessary
<kyak> maybe to save memory by not running gmenu2x while the app is running
<bartbes> gmenu2x is closed
<bartbes> with the wrapper it reopens
<bartbes> that's all
<kyak> the more i use gmenu2x (though i don't use it much), the more i want X and a decent window manager
<bartbes> since gtk and qt work, can't you like.. create a gtk/qt wm for the time being?
<bartbes> (you being general, not saying you have to do it)
<mth> kyak: gmenu2x is not running anyway when it starts something
<mth> at least on Dingux, it relies on init to respawn the menu when the started app exits
<mth> afaik the same approach is used on the NanoNote
<xiangfu> mth: can you test in your nanonote. http://pastebin.ca/1989851. it's not working here.
<mth> xiangfu: I only have a Dingoo though, not a NanoNote
<kyak> mth: yeah, i got it
<mth> I do have alsamixer though, so I can test it
<mth> xiangfu: it works fine here
<mth> I see the ncurses interface, can change volumes and leave with the button that's mapped to Esc
<xiangfu> mth: ok. it's not woking in Nanonote.
<mth> ah, I don't have the very latest version of gmenu2x installed
<mth> I'll retest with the latest
<xiangfu> mth: ok. there I can check the Dingoo rootfs ?
<kyak> i think Ben his it's own version of gmenu2x anyway
<mth> xiangfu: the one I'm using is slightly modified, but it's based on the rootfs built by booboo using buildroot
<mth> kyak: yes, but we're using the qi-hardware branch/fork as well
<mth> xiangfu: I had some problems with the "input.conf" in git not matching the Dingoo's keys, but now the latest version of gmenu2x is running
<mth> and it starts your alsamixer config without problems
<xiangfu> mth: thanks.
<xiangfu> for now I have no idea why it's not working in nanonote. :(
<mth> what happens on the nanonote then?
<xiangfu> mth: the system goto terminal. and there is 'alsamixer' thread running,  but the terminal display nothing.
<kyak> xiangfu: what if you started gmenu2x directly from terminal? would it display alsamixer?
<xiangfu> mth: the gmenu2x is autostart in nanonote.
<kyak> currently gmenu2x is not attached to any terminal, in runs in backgroudn via start-stop-daemon
<xiangfu> kyak: yes. when direct start from terminal . all works fine.
<kyak> i see..
<xiangfu> kyak: do you know how to make it attach to one terminal??
<mth> xiangfu: if you go to the /proc subdir corresponding to the pid of alsamixer, is there anything useful in the 'fd' directory there?
<qi-bot> [commit] Ayla: Added the input.conf file for the Dingoo A320/A330. http://qi-hw.com/p/gmenu2x/e3dffeb
<qi-bot> [commit] Ayla: Merge branch 'master' of projects.qi-hardware.com:gmenu2x http://qi-hw.com/p/gmenu2x/aebd031
<xiangfu> mth: wait I need restart my NanoNOte.
<mth> 0, 1 and 2 are /dev/tty1 here
<mth> start-stop-daemon maybe redirects output to /dev/null or to log file
<kyak> xiangfu: either start it without start-stop-daemon (thus creating additional unnecessary sh process - remember we discussed?) or rework the way gmenu2x executes apps...
<mth> I'm starting gmenu2x from inittab
<xiangfu> mth: http://pastebin.ca/1989890. here is the 'fd'
<mth> xiangfu: stdout (1) and stderr (2) redirected to /dev/null, that would explain why you don't see anything
<xiangfu> mth: yes. it's /dev/null
<xiangfu> mth:  very thanks.
<mth> you're welcome
<xiangfu> kyak: yes. now I am also try to start gmenu2x in inittab.
<xiangfu> mth: kyak very thanks. now the terminal apps works fine in nanonote.
<xiangfu> I will commit the change. :)
<xiangfu> mth: in Nanonote I must  export SDL_NOMOUSE=1 for make sure the gmenu2x correct start.
<xiangfu> mth: is that ok I add this line to gmenu2x.sh
<xiangfu> in gmenu2x.git
<mth> that's needed for Dingoo as well, I wonder why it's not in the script already
<mth> please add it
<qi-bot> [commit] Xiangfu Liu: add export SDL_NOMOUSE=1 to script file http://qi-hw.com/p/gmenu2x/aac04da
<kyak> xiangfu: you add it to inittab. I personally don't use it much and will replace with sh anyway
<kyak> *you can add it
<qi-bot> [commit] Xiangfu Liu: add ks7010 firmware http://qi-hw.com/p/openwrt-xburst/2e9ef26
<qi-bot> [commit] Xiangfu Liu: add gmenu2x to inittab, remove init.d/start http://qi-hw.com/p/openwrt-xburst/fce1850
<qi-bot> [commit] Xiangfu Liu: add a lot of apps entry in gmenu2x http://qi-hw.com/p/openwrt-xburst/ad70ede
<qi-bot> [commit] kyak: lynx: enable SSL and UTF-8 support http://qi-hw.com/p/openwrt-packages/47d1009
<kyak> it seems to me that keyboard layout switching can be done in DirectFB level with dfbinput. Alternatively, qt-embedded has kmap2qmap utility and QWSKEYBOARD env
<kyak> and it seems that gtk doesn't have anything for that, so perhaps dfbinput is the right thing to try..
<kyak> so few information about that.. people are mainly trying to fight with i18n input/output in console or X11
<kyak> nobody cares about qt or gtk running in fbdev :)
<lekernel_> kyak: +1
<lekernel_> everyone seems to prefer the X11 bloatware...
<lekernel_> and usermode applications that talk directly to I/O devices
<lekernel_> try google android maybe...
<lekernel_> btw, why didn't google use X11? :D
<rafa> lekernel_: well, google android does not use any application for linux, no just x11. .. it just uses linux kernel if I read correctly.. no shells, no initscrips, no linux fhs
<rafa> lekernel_: it is like android is not a linux distro, just uses the kernel
<rafa> maybe them hate GNU and dont want to be called gnu/linux :)
<qi-bot> [commit] Xiangfu Liu: [uboot-xburst] remove debug code http://qi-hw.com/p/openwrt-xburst/ce4de75
<kristianpaul> Dictionary+Wikpedia+Music http://en.qi-hardware.com/wiki/File:NN_stickers_drafts.png :D
<kristianpaul> and the first one
<wpwrak> lekernel_: you may enjoy reading this one: http://lwn.net/SubscriberLink/413335/2c202976e5743e89/
<kristianpaul> Wayland?..
<wpwrak> kristianpaul: yet another X without X, eh ? ;-)
<kristianpaul> xD
<kristianpaul> indeed
<wpwrak> kristianpaul: in fact, all these things remind me of the heydays of ATM. back then, they all recognized TCP as the "killer application of IPv4". so they tried to come up with alternatives. TCP without IP, TCP without TCP, and so on. it all led to nothing.
<kristianpaul> he
<kristianpaul> excuses just excuses
<wpwrak> kristianpaul: the arguments were of course complexity (both intrinsic and due to unnecessary features), efficiency, and so on. much like what X11 is getting accused of.
<lekernel_> yeah, nothing except google android, iOS and Mac OS X, all incenditally featuring a better and faster user experience than bloatware based on x-windows
<lekernel_> and more technically I think no one would argue that the fact that X talks directly to I/O devices instead of the kernel is a bad thing
<wpwrak> lekernel_: but they all live in parallel universes. you may as well list the text console :) i think can all agree that the text console works very well in its specific domain.
<lekernel_> mac os x, a parallel universe?
<wpwrak> lekernel_: if you and bleeding edge performance, you often need to cut out the man in the middle :)
<lekernel_> X is crap, period!
<wpwrak> let's talk about this again in ten years ;-)
<wpwrak> in that thread, a few good points are being made about legacy features that indeed don't make much sense anymore. of course, their main impact would be code size and porting effort, not so much real-life performance.
<lekernel_> isn't X all about those features?
<lekernel_> on top of crappy implementations...
<lekernel_> anectodally, which just crashed again on my machine this morning...
<rafa> lekernel_: is not mac os x propietary?
<lekernel_> sure it is, but at least it doesn't suck technically
<lekernel_> seems it takes a big software company to make bold technical decisions like Unix without X
<lekernel_> or, more exactly, successfully implement them :)
<kristianpaul> how you could know what the "successfull" really is if this is not open?
<kristianpaul> lekernel_: are you aware of a libre sofware or language for generating timing diagrams?
<kristianpaul> maybe latex?
<kristianpaul> well i could do the module in verilog and the view it on gtkwave but the idea is not simulte every time i need a timing graph
<wpwrak> gnuplot ?
<kristianpaul> dont know, but make sense
<kristianpaul> i'm not fan of gnuplot
<kristianpaul> i'll read a bit more about it
<wpwrak> data files for gnuplot are very very simple.  <x-coord> <y-coord>\n<x-coord> <y-coord>\n ...
<wpwrak> want a new line ? ... <x> <y>\n\n<x> <y>\n...
<wpwrak> don't have x coordinates but a constant "clock" ? just omit the x coordinate
<kristianpaul> wpwrak: ah gnuplot is what you use for the usrp signaling visualization isnt?
<wpwrak> gnuplot is what i use for probably 99% of all graphing tasks :)
<kristianpaul> well i'll follow you then
<wpwrak> kristianpaul: it's probably way too complex to express your graph algorithmically. better to make a file with the coordinates and plot the file
<kristianpaul> ok
<kristianpaul> script > file > plot
<wpwrak> yup
<viric> wejp, wpwrak: ah, this talks about batteries, MCUs, regulators... http://www.silabs.com/Marcom%20Documents/Resources/LowPowerSolutions.pdf
<mth> kristianpaul: I use matplotlib for Python to create graphs: http://matplotlib.sourceforge.net/
<viric> wpwrak: Do you think I could program this with free tools? http://www.silabs.com/products/mcu/lowpower/Pages/C8051F92x-93x.aspx
<wpwrak> viric: to a very large extent, yes. sdcc doesn't seem to support the C8051F9xx yet, but it supports 8051 in general many other C8051Fxxx MCUs.
<wpwrak> (maybe 9xx support is already there, too. didn't search very hard)
<wpwrak> C2 looks the same, so you can probably use my stuff from f32xbase
<wpwrak> note that there's no USB in these chips.
<qwebirc21411> Hello, has anyone where gotten the Ben NanoNote working with the micro-sdio wifi card (SDW-823)?
<viric> wpwrak: what about uploading the compiled code? easy?
<viric> wpwrak: a 3v3 serial port would do?
<viric> I'll check later the documentation
<viric> I only wondered, if they document how to program it, or instead they only say "click this on Our Program"
<wpwrak> viric: i'd use a ben for the upload :)
<wpwrak> the programming interface isn't completely documented. but you can find the information ... :)
<viric> I can find it? :)
<viric> I better start taking notes
<viric> I thought I could even use their temperature sensor!
<wpwrak> or just use f32xbase/f32x - it supports some of the functionality of C2, namely flash read/write and boundary scan :)
<wpwrak> didn't bother with breakpoints and the like, though
<viric> normal
<FrankBlues> waves
<mstevens> hello
<qi-bot> [commit] kyak: updated gmenu2x to latest git. http://qi-hw.com/p/openwrt-packages/afd6822
<qi-bot> [commit] Werner Almesberger: The eda-tools welcome the arrival of fpd2pdf http://qi-hw.com/p/eda-tools/4ae9a09
<qi-bot> [commit] Werner Almesberger: scripts/fpd2pdf (usage): don't call the input files .pdf - they're .fpd ! http://qi-hw.com/p/ben-wpan/bb54864
<qi-bot> [commit] Werner Almesberger: scripts/fpd2pdf: moved over to eda-tools http://qi-hw.com/p/ben-wpan/6f8665e
<kristianpaul> wolfspraul: Just telling you the debuging process is done now http://en.qi-hardware.com/wiki/GPS_Free_Stack#Debugging. and now i'm working on the implementation of gps data using SIE board, why not Ben?
<kristianpaul> well seems its hardware is not capable of getting data as faster as i spected (8mhz) and so far just 2mhz acording some tests made by wpwrak
<kristianpaul> anyway i'll dedicate later some time in the university lab  in order to do my benchmark, so SIE will be really usefull after all :)
<kristianpaul> i'm not sayinng i'm kicking out ben from my way, but for now SIE will help to develop then later optimize and fit gps stuff on the the nanonote
<wolfspraul> kristianpaul: sure, wpwrak already mentioned it to me
<wolfspraul> of course, this is the right approach
<wolfspraul> first we need to get it to work and learn, then we see what is the cheapest tech we can find to implement it
<wolfspraul> nice pictures!
<rafa> wolfspraul: hi.. I have uploaded :
<rafa> - a free of patents repository built from OE
<rafa> - 4 rootfs images : 2 bootstrap (one for NAND and another for SD) and 2 full jlime beta4 (one for nand and another for SD).
<rafa> wolfspraul: all this stuff is free of problematic packages. The repo is sane, so any package there is okey to install. Also, I removed from the full jlime beta4 image the packages with patented technologis. I replaced that stuff with a theora player.
<rafa> wolfspraul: maybe I should upload some screenshot and write a wiki page about?