=== chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === zequence_ is now known as zequence === ojn_ is now known as ojn === bzyx_ is now known as bzyx === chihchun is now known as chihchun_afk [12:36] infinity, ogra: I will send UCM profiles from Ubuntu to ALSA. Who from Ubuntu I should add to Cc: for discussion? [12:36] either diwic or TheMuso [12:37] both do alsa maintenance [12:37] ok [13:25] Hullo. My boss's boss wanted me to put Ubuntu on her kid's netbook, just got the thing and discovered it's INTEL Atom, which iirc means ARM. === doko_ is now known as doko [13:25] Is there a recommended (or any) disk image for this kind of situation? The main point of the install is to get her kid playing on laby. [13:27] jeek: atom !== arm [13:28] http://en.wikipedia.org/wiki/Intel_Atom [13:30] Whoops. From the wiki page, looks like the regular image should work. [13:30] Thanks, gildean. Looks like I had a fundamental misunderstanding of what Atom was. [13:31] np === Snark_ is now known as Snark === suihkulo1ki is now known as suihkulokki [16:24] hrw: diwic is alsa upstream, you might save yourself some trouble by proxying through him. [17:55] infinity: I got new UCM profiles which should work on all omap4 devices [17:57] hrw: I thought we needed multiple profiles because of silly naming convention differences? [17:57] hrw: Or is that all fixed in newer upstream kernels? [17:57] infinity: still silly naming iirc [17:57] hrw: (If so, we still need the old profiles because we still "support" old kernels... Ugh) [17:57] just scanned though email on a phone [18:04] btw - which omap4 device was named Tuna? [18:04] sdp4430? [18:05] tuna sounds like an android platform name. [18:06] all occurences point to [18:06] Google suggests it was the Galaxy Nexus. [18:07] I didn't even know that was an OMAP device. :P [18:08] it was [18:08] but I though that GNexus was maguro/toro/toroplus ;D [18:09] infinity: who does panda(es) support? [18:11] The board on my desk. [18:11] PandaBoard (4430) and PandaBoardES (4460) [18:11] ;) [18:11] can you test UCM profiles? [18:14] I can possibly test on my ES, though not today. I'm headless chickening all over right now. [18:16] no problem [18:18] http://tygrysek.juszkiewicz.com.pl/~hrw/ubuntu/ucm/20130510-ucm-panda-test.tar.xz [18:18] hrw: Remind me next week, I'm going to forget otherwise. :) [18:18] ok [18:19] I will open a bug for it even [18:26] bug 1178772 [18:26] Launchpad bug 1178772 in alsa-lib (Ubuntu) "Please test new UCM profiles for PandaBoard(ES)" [Wishlist,New] https://launchpad.net/bugs/1178772 [19:04] hrw@krolik:~$ uname -a;cat /proc/device-tree/model ;echo [19:04] Linux krolik 3.8.0 #6 SMP Fri May 10 18:58:38 UTC 2013 armv7l armv7l armv7l GNU/Linux [19:04] Google Snow [19:04] ;) === lool- is now known as lool [19:08] What's Snow? Is that the Chromebook? [19:09] yes [19:09] 3.8.0 from chromeos-next [19:10] need to ubuntuify kernel config first [19:10] and check will it boot compiled with saucy [19:15] Bug #1164484 [19:15] Launchpad bug 1164484 in flash-kernel (Ubuntu) "Add support for checking Device Tree model name" [Low,Confirmed] https://launchpad.net/bugs/1164484 [19:58] ok. ubuntified kernel booted [19:58] next step: saucy build [20:31] ok. something is fishy with gcc-4.8 and older kernels [21:00] hrw: Which gcc-4.8 are you using? [21:00] 4.8.0-6ubuntu1 [21:00] Oh, building natively with that? [21:00] yes [21:01] Then it's not the bug that just got fixed. [21:01] kernel builds, boots and panics [21:02] http://pastebin.com/jxsq08rX [21:02] that was wit older gcc [21:02] for current I do not have dmesg [21:17] apw: ^-- Was that the same thing you were seeing on manta/mako? [21:17] apw: Did doko's new GCC fix it, or no?