User1: User4 hello?
User2: User1 he'll be right back...he is cooking dinner
User2: User1 it's his night...:)
User3: User2 he converted you to ubuntu the other day, right? i seem to remember reading about that on planet ubuntu
User2: User3 yep
User2: luvin' it
User1: User3 if you follow planet ubuntu women or ubuntu weblogs, you can see what she thinks about it
User2: User3 correction he didn't the t-shirt did....
User3: User2 good. took me a minute to figure out why you knew he was cooking dinner when i didn't see it in the chat logs. ;)
User1: seeing akgraner  and assuming #ubuntu-women was why i was all OT before
User2: User3 :)
User3: User2 matching last names was a bit of a giveaway, though. :)
User2: User3 he claims me once in a while...
User2: User1 he's almost finished...sorry
User1: haha thats fine. i'm both eating and trying to find kirkland to get him to ok a patch
User2: User1 ok
User4: User1 bug no?
User1: User4 bug 327949
User5: User1 Error: Could not parse data returned by Malone: The read operation timed out
User1: -_-
User1: https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/327949
 * pgraner looks
User1: this was marked as a dupe of the acpi_fakekey is broken bug, but then slangasek said fakekey's going away and the quirks should be in the kernel, stop relying on fakekey
User1: so i'd like to learn to fix these hotkey bugs. i believe mine belongs in drivers/misc/asus_laptop.c
User4: User1 your understanding is correct... we are quirking in the kernel now... apw is our hot key expert I need to check out the source and see if thats the right place (sounds like it tho)
User1: User4 i do see ASUS_HANDLE(ls_switch, ASUS_HOTK_PREFIX "ALSC"); in the area under the /* display */ comment, so i *think* that's what i should look at
User4: User1 so when you hit the hot key you don't see a scan code? ie. if you run xev in a term and it the hotkey you don't see anything?
User1: exactly
User1: User4 ^
User1: nothing from xev or input-events
User4: User1 what keys are borked?
User1: video output switch and www key
User4: User1 looks like those keys are not defined in the source
User4: #define ATKD_BR_UP       0x10
User4: #define ATKD_BR_DOWN     0x20
User4: #define ATKD_LCD_ON      0x33
User4: #define ATKD_LCD_OFF     0x34
User4: User1 it looks like the driver expects the DSDT table to provide those values, you'll have to disssasemble the DSDT to see what hex value its passing and then you can add it, and write the function to toggle it.
User1: ok...
User1: um, how do i find the dsdt?
User4: User1 instructions are here: https://wiki.ubuntu.com/BIOSandUbuntu
 * maco looks
User4: User1 I'll have apw or cking write a "hotkey" section to show you where to look in the dsdt for the hotkey info
 * pgraner has very little dsdt-fu
User1: O_O wow iasl rocks
User1: objdump is the only way i've ever tried disassembling anything, and that results in assembly
User1: er, that's obvious i guess...seeing as it's disassembling....but i'm surprised to see stuff i can read easily instead of intel asm
User1: (by which i mean, there are english words involved)
User4: User1 lol, enjoy, I'll have my guys edit that page so I would suggest you subscribe to it. Does that give you enough to go on?
User1: i'm attempting to see if, aside from reading this, i can actually understand any of what's going on :P
User1: though i think i'll have to stop soon and wait for tomorrow since i actually have to write some assembly tonight for school
User1: User4 thank you
User4: User1 no prob
User6: do you guys use any particular tags on bugs associated with the linux package - it strikes me you must get tons of stuff that could often be grouped into different things (e.g. USB, optical drives etc)
ubuntu-kernel
Ubuntu IRC