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