=== zz_chihchun is now known as chihchun === chihchun is now known as zz_chihchun === zz_chihchun is now known as chihchun === chihchun is now known as zz_chihchun === zz_chihchun is now known as chihchun [06:25] anyone tried compiling raspberry pi kernel using ubuntu10.10? === doko_ is now known as doko === chihchun is now known as zz_chihchun === zz_chihchun is now known as chihchun === jkridner_ is now known as jkridner === chihchun is now known as zz_chihchun === zz_chihchun is now known as chihchun === chihchun is now known as zz_chihchun [20:20] ogra_: do you have a bug # handy of the "can't type in the fields in oem-config but works elsewhere" [20:25] quick q: i'm considering getting a samsung chromebook and installing raring on it. do the chromeOS suspend/resume bugs affect ubuntu as well? [20:28] xnox, heh, funny coincidence ... [20:29] xnox, watch your bugmail. i just duplicated one to the master bug [20:29] bug 1093050 [20:29] Launchpad bug 1093050 in ubuntu-nexus7 "compiz dies during oem-config and steals the focus so that input fields are unusable" [High,Confirmed] https://launchpad.net/bugs/1093050 [20:30] i thought i made the description clear enough, but just searched my butt off to find it again ... [20:30] ogra_: thanks, i was pinged about the one you marked as duplicate on #ubuntu-quality ;-) [20:31] heh [20:32] is the omap u-boot device tree the same as the kernel one? [20:32] I wonder how to pass the device tree to u-boot on tegra [20:33] ppisati, ^^^ [20:33] btw, it's maybe not a clever choice to put device tree outside of /boot if you want to load it [20:33] marvin24: you mean the DTB file? it's build from kernel source so yes [20:33] *built [20:34] ppisati: you mean it is build into the kernel? [20:34] marvin24: nope [20:34] marvin24: it's in... [20:34] marvin24: wait [20:34] I know it is inside the kernel source [20:34] but you need to pass it to the kernel on boot [20:34] marvin24: right [20:35] either you compile it in (bad) [20:35] or you load it with uboot [20:35] marvin24: it's not compiled in [20:35] ppisati: so how is it loaded? [20:35] marvin24: we are switching to a multiplatform kernel (omap3/4, freescale imx6 and vexpress) [20:35] yes, even with single platform (multi-soc) you need to load it [20:36] marvin24: you manually modify uboot.scr or uenv.txt (or the other don't remember) [20:36] marvin24: wait [20:36] marvin24: and add [20:36] I haven't found this in flash-kernel [20:36] marvin24: "fatload mmc 0:1 0x82600000 board.dtb" [20:36] that's why I asked [20:36] marvin24: "bootm ... ... 0x82600000" [20:36] marvin24: our flash-kernel doesn't support DTB [20:37] marvin24: you need to do the modification manually [20:38] oh [20:38] so hard coded in u-boot ... [20:39] marvin24: you can modify the loader script and rebuild (boot.scr) or just modify/update it (uenv.txt&c) [20:39] boot script is in /usr/share/... and should not be modified [20:40] and uenv.txt is kinda non standard, but ok [20:40] if that's that way to go [20:41] ppisati: still, dtb in /lib/firmware/device-tree is not so nice [20:41] marvin24: there was something in /etc/... [20:41] if you have a /boot partition [20:41] marvin24: uh? [20:41] yu copy it to the fat partition and you load it from there [20:41] marvin24: that's what flash-kernel should do [20:41] there is /etc/defaults/flash-kernel or so which can be enhanced [20:42] marvin24: but (unfortunately) doesn't [20:42] ah, copy [20:42] I did it by hand [20:42] yes, also missing in flash-kernel [20:44] marvin24: watch out that if you are running an old version of u-boot it doesn't support dtb [20:46] ppisati: it's already booting (2013.01) [20:46] just need to fix up the last things (e.g. flash-kernel) [20:51] topi`: I have a Chromebook that's a few months old. Has Precise, which does not suspend. I don't know about Raring. [20:54] qengho, apparently hrw's kernel in raring is supposed to suspend [20:54] i havent found the time to try it yet [20:54] Nice. I have a reason to upgrade, then. [20:55] * ogra_ runs raring userspace but still the original kernel [21:07] qengho: have you tested if suspend works in chromeOS? [21:08] I just read that there are problems suspending in chromeOS [21:08] doesn't ubuntu use the same kernel? [21:08] worked in the original chromeos install for me [21:09] ogra_: sounds better than the suspend reliability in AC100, then ;) [21:09] well, in ubuntu it reliably doesnt suspend with that kernel [21:09] wife wants an absolutely quiet netbook, so I'm probably shelling out some $$$ for chromebook [21:09] and if i upgrade i'll likely lose dualboot [21:10] how does dualboot work then? [21:10] and while flash from chromeone works flawless in ubuntu chromium, the hangout plugin doesnt [21:10] I know nothing of samsung bootloader [21:10] painful [21:10] topi`: not the same kernel, exept in the narrowest sense as in "your television uses the same kernel as your Android phone". [21:10] you need to switch back from developer mode to boot back int chrOS [21:11] interesting [21:11] qengho, i currently use the exact same kernel here [21:12] I knew ogra would ;) [21:12] ogra_: I bet you must already be playing with some nice Aarch64 boards already ;) [21:13] nah, #ubuntu-touch toptally sucked me in [21:13] you guys get all those fancy devices a year earlier than us mortals [21:13] ouch... [21:13] and the boards nowadays go rather to linaro [21:13] I was (slightly) involved in the touchscreen driver for the Nokia N( [21:13] N9 [21:15] well, ubuntu touch bases on CWM 10.1 ... [21:15] so there are no drivers to touch, they just work [21:15] ok [21:19] 23 ports to other devices underway after 5 days ... https://wiki.ubuntu.com/Touch/Devices [21:21] ogra_: are they merged? are they legal to be merged? [21:21] not yet merged, not sure what the plan is on merging, but there are images that you can just use with our userspace image [21:22] awesome! [21:22] i think its absolutely legal [21:23] if the userspace image is detached than I can see how we don't have to merge anything, apart from possibly make pointers to android repo git forests URL (either straight from android.com or with some patches applied in forked github repos) [21:23] s/detached/independ of base-hw image/ [21:24] yeah [21:24] porting is largely just copy paste work and a successfull compile run [21:25] oh, so we could automate it =) e.g. by hosting a repository with android-repo manifests URLs pointing to the right places. [21:26] well, until you run into build issues [21:26] but yeah, you could just rip the snippets out of CWM [21:27] ogra_: s/CWM/CM/ I assume? [21:27] err, yes [21:28] * infinity was trying to sort out how ClockWork factored into this. [21:28] heh, i'm just learning all the android l33tspeak and names, bear with me :) [21:31] ogra_: hehe, learning to optimize by changing the wallpaper then? [21:31] lol [21:32] my Android devices seem to get stuck on stock roms, Optimize too often means break ;-) [21:34] well, we only use the kernel and driver layers (HAL, surfaceflinger etc) ... the rest is a plain ubuntu rootfs [21:34] so as long as androind HW layer doesnt suck performance wise .... [21:35] would need one of these funky modern devices I guess to try ubuntu-touch [21:43] well, yeah, dualcore and 1G is currently a requirement ... [21:44] i doubt you would have aany fun below that [21:48] ppisati: I guess I will just change the kernel package to copy the relevant device tree to /boot/device-tree.dtb based on /proc/device-tree/model instead of poking around with flash-kernel [21:49] ++ [21:49] its not like they change or anything [21:50] ogra_: my phone is an Xperia Play :-D so just a little old :-D