**** BEGIN LOGGING AT Wed Apr 09 02:59:57 2008 Apr 09 03:46:04 * * OE Bug 4172 has been created by  Apr 09 03:46:06 * * rox-filer-2.5-autobuild Apr 09 03:46:08 * * http://bugs.openembedded.net/show_bug.cgi?id=4172 Apr 09 06:36:27 morning Apr 09 06:58:13 morning Apr 09 08:13:05 yo Apr 09 08:24:43 re Apr 09 08:36:04 * * OE Bug 4173 has been created by  Apr 09 08:36:06 * * jikes-initial-1.0-autobuild Apr 09 08:36:08 * * http://bugs.openembedded.net/show_bug.cgi?id=4173 Apr 09 09:10:38 re Apr 09 09:11:04 how is your ucLinux compilation? It's working? Apr 09 09:11:59 methril: nope Apr 09 09:12:05 not much progress Apr 09 09:12:23 actually trying to convince the customer to stay away from it, since they anyway have an ARM9 ;> Apr 09 09:12:37 so now trying to tune performance and size of the mmu-linux system Apr 09 09:13:31 oh!! nice Apr 09 09:13:48 you think that was easier than it's :) Apr 09 09:13:59 well, uclinux is really a pain Apr 09 09:14:11 you didn't get a lot of support of me Apr 09 09:14:35 that's ok :) consider yourself lucky hehe Apr 09 09:14:45 hehe Apr 09 09:15:32 doh.. meta toolchain troubles - as always :( angstrom stable, uclibc, meta toolchain - gcc-cross-sdk-4.1.2 is failing - cross/bin/arm-angstrom-linux-uclibcgnueabi-ld: cannot find libc.so.6 Apr 09 09:15:45 why is it looking for glibc in a uclibc built distro? Apr 09 09:17:28 crazy Apr 09 09:17:40 dependencies sucks Apr 09 09:18:09 well, toolchain stuff is really a complicated nightmare :( Apr 09 09:19:11 maybe for that kind of projects it's easier to start in a cleaner way that angstrom Apr 09 09:19:45 well, I think that angstrom stable is a good basis Apr 09 09:20:21 but if it's so dependant to glib it's hard to change to uclibc Apr 09 09:20:22 but of course it has a lot of hidden quircks in it Apr 09 09:20:32 well, there is this ANGSTROM_MODE variable Apr 09 09:20:39 which you can use to set it to either glibc or uclibc Apr 09 09:20:41 and that works well Apr 09 09:21:35 i'm so new in that environment :) Apr 09 09:23:37 the thing that constantly makes troubles is the meta toolchain, other stuff usually works quite well Apr 09 09:40:05 * * OE Bug 4174 has been created by miska(AT)atrey.karlin.mff.cuni.cz Apr 09 09:40:06 * * lib-sdl-qpe cannot be build Apr 09 09:40:08 * * http://bugs.openembedded.net/show_bug.cgi?id=4174 Apr 09 09:46:56 hrw: ping Apr 09 09:51:13 ?ус? Apr 09 09:53:23 hrw: hi Apr 09 09:54:24 hrw: just to finish my TS issue... I'm using the altboot console image and boot from SD with a X11-image Apr 09 09:54:29 that's work fine Apr 09 09:55:00 in the dmesg --> input: Corgi Touchscreen as /class/input/input1 Apr 09 09:55:39 so I've set /etc/profile.d/tslib.sh --> TSLIB_TSDEVICE=/sys/class/input/input1 Apr 09 09:56:07 some people will never learn Apr 09 09:56:37 ok? Apr 09 09:56:59 cedric_: you have no idea what linux input system is? what for sysfs exists? what should be in tslib.sh? etc Apr 09 09:57:27 cedric_: and your (OE generated POODLE) image does not have /dev/input/touchscreen0? Apr 09 09:57:29 that's the previous value --> TSLIB_TSDEVICE=/dev/input/touchscreen0 Apr 09 09:58:03 but this path doesn't exist Apr 09 09:58:34 why you did not tell that at beginning? Apr 09 09:58:41 that's what I've though Apr 09 09:58:51 euhh sorry Apr 09 09:59:13 or not tried to get help from poodle maintainer? or even say that your device IS poodle? Apr 09 10:00:00 ok thanks for your help Apr 09 10:03:14 re Apr 09 10:08:04 * * OE Bug 4175 has been created by  Apr 09 10:08:06 * * openmoko-dialer2-0.1.0+svnr3689-autobuild Apr 09 10:08:08 * * http://bugs.openembedded.net/show_bug.cgi?id=4175 Apr 09 11:02:39 good morning Apr 09 11:03:18 gm Apr 09 11:18:38 hi florian Apr 09 11:26:10 hi florian Apr 09 11:43:11 zecke Apr 09 11:43:24 is this ur room dear Apr 09 11:45:24 hiiiiiiiiiii wrobbie Apr 09 11:57:07 Hi all ! Apr 09 11:57:20 Has anyone used OMA-DM in any of their projects ? Apr 09 11:59:56 OMA-DM? Apr 09 12:04:07 Crofton : Open Mobile Alliance (OMA) Device Management (DM) Apr 09 12:04:27 ah Apr 09 12:04:31 nope :) Apr 09 12:04:33 scary stuff Apr 09 12:04:42 Ive used it on a nokia phone, its a pain in the arse Apr 09 12:04:45 sounds like a MS doc :) Apr 09 12:04:59 although that might be because nokias tools are crap Apr 09 12:05:07 MS is using it on their pda-phones Apr 09 12:06:49 XorA : yes Nokia is using it also. But I don't even have a clue what it does ;) Apr 09 12:07:11 Isn't it DRM of some sort? Apr 09 12:08:39 it's supposed to manage/control/ and provision devices Apr 09 12:09:01 probably need to reed more about it Apr 09 12:10:47 steliosk: you basically make special format sms messages that can set parameters in the device Apr 09 12:11:00 steliosk: stuff like email gprs, mms can all be set remotely Apr 09 15:22:16 bye Apr 09 15:45:48 anyone tryin qemuarm here ? Apr 09 15:46:05 i'm trying qemux86 ;) Apr 09 15:46:16 but i can't start an XServer :( Apr 09 15:46:42 mrt2k7: Hmm is it on .dev Apr 09 15:46:56 Khem: i'm using .stable Apr 09 16:04:41 mrt2k7: hmmm for me Xservr is starting but no touchscreen response from xserver kernel is getting the touchscreen events though I checked with od Apr 09 16:14:44 is there a way to update a Packages.gz list for a feed without "bitbake package-index"? I'd like to do it from within a recipe so it doens't have to parse all n thousand files twice Apr 09 16:16:07 morning all Apr 09 16:16:32 thesing: morning Apr 09 18:06:26 re Apr 09 18:35:19 Does anyone know off-hand if any of the Zauruses implement resume from touch screen interaction? Apr 09 18:36:19 if they are capable of doing it,it hasn't been implemented in any model to my knowledge Apr 09 18:36:26 Good, good. Apr 09 18:41:46 maybe gpio required for resume action? Apr 09 18:44:04 If the WM97xx IRQ or PENDOWN lines is wired up they certainly *can* be used as wakeup sources. Apr 09 18:44:20 I was rather hoping nobody was doing that, though. Apr 09 18:50:50 re Apr 09 18:54:52 broonie: only wakeup from key AFAIK Apr 09 18:59:30 Yeah, unless your hardware is specially designed for it resume from pen down is a bit silly. Apr 09 19:57:33 hey flo_lap quim gil is asking about you on #maemo Apr 09 19:58:46 vivijim: oh, ok... Apr 09 19:58:51 vivijim: thanks Apr 09 20:02:37 broonie: only sl-6000l used wm97xx iirc Apr 09 20:02:53 broonie: others use wm8731 or wm8750 Apr 09 20:02:56 bye Apr 09 20:19:08 any news on the git-conversion ? Apr 09 20:28:49 hi, all! Apr 09 20:29:06 any news when wm97xx_ts will get vanilla? Apr 09 20:32:07 schurig_home: ah... good topic :) Apr 09 20:38:36 hm, what exactly is linuxtag OE booth personnell expected to be doing? do I qualify? Apr 09 20:39:32 yes Apr 09 20:39:33 :-) Apr 09 20:43:27 pH5: sure... Apr 09 20:43:36 pH5, breathing Apr 09 20:43:39 not smell bad Apr 09 20:43:44 look sort of presentable Apr 09 20:43:59 not gush over how great buildroot or T2 is :) Apr 09 20:44:14 pH5: looking intelligent ;) Apr 09 20:44:41 Rene will be there too... with T2 Apr 09 20:45:11 pH5: placing OE flyers at the T2 booth would be a good idea too ;) Apr 09 20:46:10 * pH5 wonders how placing T2 and OE booths facing each other would turn out Apr 09 20:47:19 pH5: I don't know how if they like humour ;) Apr 09 20:47:41 :) Apr 09 21:05:14 good night Apr 09 22:50:19 * flo_lap shoots Angstrom Apr 09 22:51:05 flo_lap: Why? Apr 09 22:51:06 What's wrong? Apr 09 22:51:58 Laibsch: not sure yet... built an image from .dev for my Netvista... looks like it starts all sorts of crap like gpsd but no getty Apr 09 22:52:17 Laibsch: what's the proress of Sonkei? Apr 09 22:54:10 Unfortunately, very stalled at this point in time Apr 09 22:54:18 too bad Apr 09 22:54:26 Neither CoreDump nor I can spend a lot of time on it ATM Apr 09 22:54:28 flo_lap, which image? Apr 09 22:54:41 But sonkei was never conveived as a technically superior solution Apr 09 22:54:52 a bit more polish? Apr 09 22:54:54 maybe Apr 09 22:55:16 But most and foremost a different approach to interaction among the participants Apr 09 22:55:37 Crofton: my own one Apr 09 22:55:55 ah :) Apr 09 22:56:04 flo_lap: I'd think your best bet is to start with a known good image first Apr 09 22:56:05 try a standard one first :) Apr 09 22:56:05 CoreDump: or the target I built? Apr 09 22:56:13 is there an echo in here :) Apr 09 22:56:26 Laibsch: Do you have a good one for IBM Netvista? ;) Apr 09 22:56:38 console-image Apr 09 22:56:53 Plus whatever you need in EXTRA_INSTALL or whatever the variable is called Apr 09 22:57:30 flo_lap: What is the problem with the image? Is it being created after all? Apr 09 22:57:40 Or does the process crap out before? Apr 09 22:58:25 Laibsch: the image is created, using the same kernel and config like with the stable tree I get a working one. Apr 09 22:58:58 The last sentence is weird Apr 09 22:59:02 Laibsch: even using the same kernel i suffer from effects like an unreliable usb keyboard Apr 09 22:59:02 You get an image Apr 09 22:59:04 but? Apr 09 23:01:46 Interesting effect: Some random keys do not work - if I unplug it an plug it in again some other random keyd do not work Apr 09 23:05:44 to clarify: you are compiling against .dev and have issues Apr 09 23:06:04 recompiling the kernel with the config from .stable gets you a working kernel? Apr 09 23:10:45 Laibsch: yes and no - the config is the same anyway. Apr 09 23:11:04 hm, that is strange indeed Apr 09 23:11:15 But I wouldn't be the right person to help with this Apr 09 23:11:26 And I am not sure this is angstrom's fault Apr 09 23:12:25 true... unstable is unstable. I wonder if the compiler might have a problem with this strange CPU **** ENDING LOGGING AT Thu Apr 10 02:59:56 2008