[10:27] <Kano> hi, do you intend to backport hawaii support or just use 3.17?
[10:28] <ohsix> google "graphics enablement stack"
[10:28] <ohsix> s/graphics/hardware
[10:47] <Kano> i mean for utopic
[15:31] <TJ-> If 12.04 has the tTusty HWE and devices supported by that HWE require firmware, shouldn't the HWE packages also Depends on the matching "linux-firmware" from Trusty, rather than the original 12.04 package, in order to provide the firmware? Otherwise, there's not much point to the HWE package if it is being installed to support a new device ?
[15:32] <rtg> TJ-, we generally just backport the necessary files to the existing package. Do you have some in particular ?
[15:33] <TJ-> rtg: Yes, a query from a user in #ubuntu for the rtl8188:
[15:33] <TJ-> modinfo $(awk '/10EC.*8179/{print $3}' /lib/modules/`uname -r`/modules.*) | grep ^firmware
[15:33] <TJ-> firmware:       rtlwifi/rtl8188efw.bin
[15:33] <TJ-> But that isn't in the linux-firmware of 12.04; it was first introduced for Saucy according to packages.u.c
[15:33] <rtg> TJ-, can you start a bug report. I'll follow up.
[15:34] <TJ-> rtg: Surely, thanks.
[15:34] <TJ-> rtg: Against linux-firmware?
[15:35] <rtg> TJ-, yup
[15:35] <TJ-> rtg: Or against the HWE package and it's depends?
[15:35] <TJ-> rtg OK
[15:39] <TJ-> rtg: japro bug 1368301
[15:39] <rtg> TJ-, ack
[15:40] <japro> TJ-, thanks
[15:59] <TJ-> rtg: Thanks for the rapid fix
[16:00] <japro> oh wow, thanks
[16:00] <rtg> TJ-, np. watch for the email requesting you to test it.
[16:00] <TJ-> rtg: That'll be japro - the user that reported this
[16:01] <rtg> ack
[16:11] <mandeep> Hey all , I want to take backup of all user config. Can anyone suggest me some way to take necessary config files. Just copied ~/.* files and just want to know which else files I must copy like in /etc folder.
[21:36] <infinity> zequence: Another ping about https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/1364293
[21:38] <ukiwi> Apologies in advance if this is the wrong forum for such questions but this is driving me nuts...
[21:38] <ukiwi> Greetings! I'm having a really hard time mapping the four colour buttons on my Logitech Harmony Smart Control Remote to scan-codes. I can see that the kernel is receiving these events when I 'cat /sys/kernel/debug/hid/events' (03 f5 01 00 00). I'm then editing my /lib/udev/hwdb.d/custom.hwdb with the right USB vendor/model (keyboard:usb:v046DpC150*) and my entries should be like other similar events - e.g.  'KEYBOARD_KEY_
[21:38] <ukiwi> c0069'. After running 'udevadm hwdb --update && udevadm trigger && udevasm control --reload' they're still not working. I suspect my raw events (03 f5 01 00 00 etc) aren't the same as 'c009a' etc. Can anyone help?
[21:41] <ukiwi> Greetings! I'm having a really hard time mapping the four colour buttons on my Logitech Harmony Smart Control Remote to scan-codes. I can see that the kernel is receiving these events when I 'cat /sys/kernel/debug/hid/events' (03 f5 01 00 00). I'm then editing my /lib/udev/hwdb.d/custom.hwdb with the right USB vendor/model (keyboard:usb:v046DpC150*) and adding entries which I assume should be like other similar entries - 
[21:41] <ukiwi> e.g. 'KEYBOARD_KEY_c0069'. After running 'udevadm hwdb --update && udevadm trigger && udevasm control --reload' they're still not working. I suspect my raw events (03 f5 01 00 00 etc) aren't the same as 'c009a' etc. Can anyone help?