[01:43] if I bought a pandaboard what would I be able to expect? [01:44] is it going to be like beagle where I buy one now and then 4 revisions later it actually works and I am stuck with a dud? :D [02:31] JakeJBailey: gave up of Maverick? [02:31] Neko: well, the current one works quite ok, and it seems most of the issues are software related [02:32] it'll probably be better than what we had for beagle, but I believe it could happen in some sort [02:33] rsalveti, you should be getting a smartbook tomorrow :) [02:35] Neko: yeah, looking for it :-) [13:56] where's the unity irc channel [13:56] or can I ask here, what on earth is this "eglx" backend for clutter? === hrw is now known as hrw|afk [13:57] embedded glx? [13:57] bb soon [13:57] does that just mean that libegl1-x11 is the backend (i.e. an EGL that runs on X?) [14:09] Neko_: yep [14:09] it's basically gles but compatible with x [14:10] so basically, EGL that takes XDisplay as EGLDisplay or whatever [14:10] Neko_: #ubuntu-uds-Bonaire4 [14:10] yup [14:10] rather than EGL which has some crazy GLX support [14:10] in case you want to check the current unity->compiz transition [14:10] we're just having this session now [14:10] (we noticed Cairo OpenGLES backend etc. and some others create context using GLX then render GLES with it) [14:11] nah I am fine with whatever result [14:11] as long as some standard GL library stuff will work and it doesn't depend on Mesa [14:12] Neko_: yeah, it shouldn't depend it on mesa, should work just fine with gles [14:13] but as now they are changing mutter to compiz, the gles compatibility still needs to be developed [14:13] ARGH [14:13] tell them it's a dumb idea. mutter is going to be fine in the future [14:14] why keep using compiz just so that you can support some amd64 PC? mutter will do that. and you will update to GNOME 3 and be discarding their default window manager :D [14:14] but they want to change it to the next cycle already, seems they had too many problems with mutter [14:16] Neko_: do you know the current state of the gles drivers for i.MX51? [14:19] rsalveti, we have the technology :D [14:20] could ship something for smartbook by the end of the week but I wouldn't be proud of it [14:21] Neko_: haha :-) [14:21] do you have the proper xdriver and etc? [14:21] well [14:21] let's explain the situation [14:21] ok [14:21] there is a EGL, GLES1.1 GLES2.0 and OpenVG [14:22] they communicate through this kernel layer (cross platform) which is in the kernel we ship, called GSL [14:22] it is like DRM but it works on WindowsCE too :D [14:22] Qualcomm also use it [14:22] what there is, is basically EGL for X11 and EGL for framebuffer [14:22] OpenGL doesn't care [14:22] got it [14:22] the Xorg 2D driver uses the OpenVG unit to accelerate EXA [14:23] Freescale use UIO because they thought it was faster [14:23] Neko_: what is the chip that handles the gles? [14:23] but the original AMD interface works just as well [14:23] (through GSL) [14:23] interesting, never saw people using openvg to accelerate exa [14:23] problem: with AMD GSL for the X11 driver, everything is red [14:23] they don't they're poking the hardware to do things like blits and render lines and stuff [14:23] 2D is 2D [14:24] now thats a statement [14:24] problem: with FSL UIO for the X11 driver, everything is fine, a bit faster, but it disables any ability to use OpenVG [14:24] we hate that idea and FSL are dropping it next BSP anyway [14:24] (and that has 2.6.35 in it as well, yay!) [14:25] what we might do is package 3D on the basis that you can use it how you like without any X11 support for EXA or so. pixman is used in fbdev and works nice. OpenGL will render on top of it at decent speed. So will OpenVG. [14:25] and then we will work out the stupid red tint bug and ship an accelerated X11 driver later [14:27] hehe we just dropped pixman 0.20.0 on the smartbook and it screams along [14:27] hooray [14:30] hehe === ogra_ac_ is now known as ogra_ac === hrw|afk is now known as hrw|uds === XorA is now known as XorA|gone [16:39] font question! [16:40] guys, when jaunty was around it had this nice sort of curvy console font [16:40] anyone remember what it was? [16:40] stuck with terminus here and missing the curvy jaunty one === ogra is now known as Guest32127 === Guest32127 is now known as ogra_g [19:33] ogra_ac: (working on the emmc installer) what is triggering the ubuntu image installer (asking for locale, create a user, ...) on the 1st image boot? (I have all the pieces ok, except that on the 1st boot from emmc I get a logging screen) [19:33] ogra_ac: note that we bypass jasper and try to reproduce some parts of it in another initramfs (so I may be missing something made by jasper?) === Neko_ is now known as NekoOptometry [20:08] sebjan_, yes you likely miss the whole of jasper_setup, and you shouldnt do the partitioning and copying by a script, debian-installer has all we need, i will work on a proper solution for natty [20:10] ogra_ac: yes, as a short term work-around we bypass jasper and try to do most of it on our side. I was missing /root/var/lib/oem-config/run. Now the installer runs. I still have to fix the default session. [20:11] thats also in jasper (will be fixed elsewhere in natty) [20:11] yes, I saw that :). I miss the call to gdm-set-default-session [20:12] in natty we will just set it at image buildtime so there wont be a need for the jasper hack [20:12] ogra_ac: where does the /usr/share/xsessions/une-efl.desktop comes from? [20:14] N900 has gained U-Boot support. Does that mean that I could dd a flashcard, insert it and boot Ubuntu ARM on it? :) === NekoOptometry is now known as Neko [20:50] jo-erlend: I'm also waiting to have it on my n900 so we can try to spin an image for it [20:50] I'm building a maverick compatible kernel that should work at the n900 [20:50] nice :) [20:50] but still needs more testing [20:51] I'm just trying out MeeGo as we speak :) [20:51] that is to say: I'm preparing to do so. [20:51] jo-erlend: cool, will ping you when I get something :-) [20:51] grand. :) [20:51] but in our best case, we should have a working kernel, working initrd, and working xserver, accelerated by sgx [20:52] all working fine, that's the goal :-) [20:52] and with ofono you can even use the modem, and call someone :-) [20:52] but unfortunally I don't have much time this week to search for the u-boot support [20:52] wow! I can _call someone_ with my phone?! Awesome. :) [20:53] doesn't seems to be public, but I can be wrong [20:53] on ubuntu, that's the awesome part ;-) [20:53] yes, I know. :) [20:54] out again, another ude session :-) [20:55] :) [20:57] rsalveti: did you look at meego 1.1 kernel yet? [21:14] suihkulokki: that's where I'm getting the kernel patches [21:15] and the good thing is that it's also 2.6.35 [21:47] Hi all, I have a beaglebord C series and was trying to install the OMAP3 preinstalled Maverick (10.10) image, after typing in the console the setenv bootcmd 'mmc init;fatload mmc ... I got ** Unable to use mmc 0:1 for fatload ** Unknown command 'source' - try 'help'. Any Idea how to solve this? [22:01] jcastellanos: Maverick doesn't work on BB RevC [22:05] lag: Thanks! [22:07] jcastellanos: np [22:56] lag: jcastellanos: it should work [22:56] the C4 was quite well tested [22:56] and it's officially supported by us [22:57] it's not the recommended board from a user experience point of view [22:57] but you can for sure run ubuntu quite well on it, if you switch to a lighter wm and etc [22:57] hi [22:59] hey [23:00] * rsalveti out, just finished last session [23:01] anyone interested at joining the arm team? http://webapps.ubuntu.com/employment/canonical_UOASE/ [23:21] rsalveti: Thanks for the board info === hrw is now known as hrw|gone === JaMa is now known as JaMa|Off