[07:16] <ppisati> moin
[08:10] <apw> moin
[10:21] <odinsbane> I tried out the 3.8 kernel, and I cannot build the compat-drivers package anymore. 
[10:21] <odinsbane> I'm not sure a good place to get help with that.
[11:45] <apw> smb, did i ask you about 'CONFIG_ARM_CHARLCD-yy------
[11:45] <apw> no not that thank you unity
[11:45] <smb> heh
[11:46] <smb> no
[11:46] <apw> smb, CONFIG_MULTICORE_RAID456 
[11:46] <smb> apw, that neither
[11:46]  * smb looks
[11:47] <smb> apw, OK, probably mostly performance and experimental... rather would tend to =n
[11:48] <apw> smb, ack thanks
[12:07] <zequence-s> I'm still a bit unsure of how much the mobile/ARM version of Ubuntu will be different from the desktop release, but I'm assuming the repo will be the same deal? A lot of people will be interested in the possibility of using the Ubuntu phone for multimedia, and some specifically for low latency audio, so I would be interested in adding a special kernel for that. 
[12:08] <zequence-s> Anything stopping making -lowlatency available for the phones and tablets?
[12:10] <amitk> zequence-s: only the fact that most such devices might be ARM-powered, so you'll need -lowlatency versions of specific SoC kernels
[12:11] <rtg> zequence-s, the kernels for mobile devices will almost certainly be different versions and in different repos then the desktop/server kernel.
[12:11] <rtg> much like the Nexus7
[12:11] <zequence-s> amitk, -lowlatency is currently based on -generic (really the same kernel, just differently configured). I actually don't know how the ARM kernel performs for audio, so it could be it's ok, but if not, I'd just tweak the config and create a -lowlatency flavor of it
[12:13] <zequence-s> rtg, There won't be any weird restrictions on those machines, so that anything is possible, like building your own kernel on the machine itself, or adding a PPA for it (maybe not exactly a kernel question)?
[12:14] <rtg> well, building the kernel on the device itself could be quite painfully slow
[12:14] <rtg> I've been using an armhf qemu chroot to build test kernels.
[12:26] <zequence-s> apw, both lowlatency's ready to be pulled
[12:30] <apw> zequence-s, ta
[13:25]  * ppisati loves strawberries
[13:38] <directhex> i have a user with a lenovo l420 laptop, running a -generic-pae kernel (the hardware wouldn't boot with a 64-bit kernel). i'm seeing a bizarre setup where the -36- kernel is fine, but the -38- kernel renders the laptop totally unresponsive - jerky mouse in X, keyboard keys being missed in VT1, and so on
[13:39] <directhex> are there any changes between -36- and -38- which could somehow be related? i'm stumped
[14:14] <RZAFC> anyone know how to get metaspoit on a ppc with lubuntu?
[14:46] <apw> directhex, not heard of it, the changes are tagged in git so you can look and see
[14:48] <apw> exactly what was changed
[15:09]  * rtg notes we have a chromebook kernel in raring
[15:09] <apw> we do ?
[15:10] <rtg> apw, just uploaded: linux-chromebook
[15:37]  * ogasawara back in 20
[17:07]  * ppisati goes for some sweating
[17:20] <rtg> apw, ogasawara: ok, rather then create a new repo I've opened a branch (unstable-3.9) in the raring repo that builds for amd64/i386.
[17:20] <apw> rtg, ack
[18:50]  * rtg -> lunch
[20:13] <infinity> ppisati: Are the ti-omap4 SRU rebases in progress?  This one's a bit more urgent than most.
[20:27] <ppisati> infinity: not really
[20:27] <ppisati> infinity: i'm a bit lost with SRU schedule these days
[20:31]  * rtg -> EOD
[20:32] <bjf> ppisati, this is a high priority CVE that is making it's way through
[20:32] <bjf> ppisati, this is outside the normal kernel SRU cadence
[20:32] <ppisati> bjf: yep, infinity told me that
[20:32] <ppisati> doing the rebases now
[21:21] <ppisati> herton: are you still there?
[21:22] <ppisati> herton: recall me, what do i need to change the "Upload to ppa" to... "confirmed"?
[21:40] <ppisati> infinity: bjf: P and Q are done, doing O now
[21:40] <bjf> ppisati, thanks
[21:41] <infinity> \o/
[21:48] <herton> ppisati, yes, but just the comment is enough too, I'll take a look
[22:16] <ppisati> and O done too.
[22:16] <ppisati> herton: ^
[22:17] <herton> ppisati, ack, I'm working on uploading them
[22:17] <ppisati> ok
[22:17]  * ppisati is here around...
[23:47] <apw> herton, i have uploaded lowlatency for P & Q
[23:47] <herton> apw, ack