=== bjf is now known as bjf-afk === asac_ is now known as asac === shenki_ is now known as shenki [06:09] hi i need some help with a OMAP3 board [06:29] hi i need some help with a OMAP3 board [06:29] neel_: what help? [07:07] oh hi [07:07] sorry you still there amitk? === persia` is now known as persia [14:00] ogra, asac: I'm writing an email summarizing my research and thoughts on the UDS session we had on debootstrap/qemu-arm; I was writing this as an email to you two, should I send it to some ML instead? [14:00] I'm not sure ubuntu-mobile@ is good for this, and people might lack context, but I would also like this to be archived so that I can point to it during discussions [14:04] ogra_: 15:00 < lool> ogra, asac: I'm writing an email summarizing my research and thoughts on the UDS session we had on debootstrap/qemu-arm; I was writing this as an email to you two, should I send it to some ML instead? [14:04] 15:00 < lool> I'm not sure ubuntu-mobile@ is good for this, and people might lack context, but I would also like this to be archived so that I can point to it during discussions [14:05] hmm, i was planning to put a TODO item for that into the spec [14:05] probably just add it to the wikipage ? [14:06] Ok [14:25] asac: wrt mobile-lucid-arm-lib-tests, the issues I'm running into are mainly poor/out of date documentation and the way the system is designed. Each test build requires the LSB build environment, which is a set of library stubs. This is generated partially from a database of functions. I just got the mysql database up and running (poor documentation) on my desktop, need to get my dove to connect to it. [14:26] After I get database connectivity, I need to figure out how to populate the database with info on arm. Right now it has none. Once I get that, there is a script in the build_env source tree to generate new code for arm. [14:26] GrueMaster: right. [14:27] sounds like a plan [14:27] remember to document what you do to setup etc. [14:27] Heh, yea. [14:27] in that way if you get blocked we can have someone else helping you ;) [14:27] without much communication [14:27] this is an important spec for us ... [14:28] I already have an email in to the linux foundation and key developers of LSB. I hope to hear from them this week. [14:29] GrueMaster: maybe add progress and things we are waiting for to the whiteboard too [14:29] thanks [14:30] I could, but it is mostly trial and error at this point. [14:30] GrueMaster: right. what i meant was: asked XXX for clarification; waiting for reply ... [14:30] so we know that we are waiting for something [14:30] but do it like you prefer [14:30] ;) [14:30] Part of the problem is that while I can get a daily snapshot of their database, they are using an old version of mysql. [14:30] we will review this spec at least weekly ;) [14:31] I'd rather not say I'm waiting for them. [14:31] I prefer to continue hacking at this while waiting for them. That way I'm still making some progress. [14:31] GrueMaster: have you found/documented the source trees by now? [14:31] Yes, I think I have. let me check. === ogra__ is now known as ogra [14:32] The only link I don't have is for the ABI tests, and any other tests we may add/replace. [14:33] lool: the idea was to document your qemu approach somewhere ... either mailing list or even in the spec [14:33] GrueMaster: add what you have for now. and maybe split those things in separate work items ;) [14:33] But the ABI test is a simple script that compares the old libs with the new ones. [14:33] Ok. [14:33] so we can document that there is progress ;) [14:33] thanks [14:33] ok have to do lunch and stuff [14:34] will be back in 1h or so [14:34] lunch is a good idea ! [14:34] I have a dental appoinment in 2.5 hours. [14:42] asac: Yeah that's why I was wondering where [14:43] asac: But I didn't think of the wiki and will copy that to the wiki now that I finished typing it === bjf-afk is now known as bjf === bjf is now known as bjf-afk === bjf-afk is now known as bjf