[Kernel-packages] [Bug 1196730] Re: Fn key doesn't work in raring on MacBook Air 6, 2

2013-09-03 Thread Linus G Thiel
Actually, it's not quite fixed. The patch that went in for this had the device ids wrong, I think. I am in touch with Henrik Rydberg about this. It kind of works for me now, but the and the §° buttons are switched, which is because I don't get the ISO flag set. I think it will get sorted

[Kernel-packages] [Bug 1196730] Re: Fn key doesn't work in raring on MacBook Air 6, 2

2013-09-01 Thread Julian Wiedmann
** Changed in: linux (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1196730 Title: Fn key doesn't work in raring on MacBook Air 6,2

[Kernel-packages] [Bug 1196730] Re: Fn key doesn't work in raring on MacBook Air 6, 2

2013-08-31 Thread Linus G Thiel
Yes, I can confirm it's fixed in kernel 3.8.0-29.42. Sorry for the delay. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1196730 Title: Fn key doesn't work in raring on MacBook Air 6,2

[Kernel-packages] [Bug 1196730] Re: Fn key doesn't work in raring on MacBook Air 6, 2

2013-08-30 Thread Julian Wiedmann
Miek, Let's please use the bug you already filed (bug 1213770) to track the 0x0290. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1196730 Title: Fn key doesn't work in raring on

[Kernel-packages] [Bug 1196730] Re: Fn key doesn't work in raring on MacBook Air 6, 2

2013-08-30 Thread Miek Gieben
Note this is about to be fixed, see https://bugzilla.kernel.org/show_bug.cgi?id=60181, 0x0290 should be added too to that patch ** Bug watch added: Linux Kernel Bug Tracker #60181 http://bugzilla.kernel.org/show_bug.cgi?id=60181 -- You received this bug notification because you are a member

[Kernel-packages] [Bug 1196730] Re: Fn key doesn't work in raring on MacBook Air 6, 2

2013-08-23 Thread Miek Gieben
Note: this is on a Macbook Air 2013 6,1 Model, lsusb lists: % lsusb Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 001 Device 003: ID 05ac:0290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001:

[Kernel-packages] [Bug 1196730] Re: Fn key doesn't work in raring on MacBook Air 6, 2

2013-08-20 Thread Julian Wiedmann
Linus G Thiel, could you please test the latest kernel in -updates (3.8.0-29.42) and see if this bug is fixed? Thanks. ** Changed in: linux (Ubuntu) Status: Fix Committed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed

[Kernel-packages] [Bug 1196730] Re: Fn key doesn't work in raring on MacBook Air 6, 2

2013-07-30 Thread Julian Wiedmann
Should be fixed in current -proposed (3.8.0-28.41) with HID: apple: Add support for the 2013 Macbook Air Input: bcm5974 - add support for the 2013 MacBook Air ** Changed in: linux (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member

[Kernel-packages] [Bug 1196730] Re: Fn key doesn't work in raring on MacBook Air 6, 2

2013-07-23 Thread Joseph Salisbury
I built a Raring test kernel with commit 9d9a04ee applied. The kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1196730/ Can you test this kernel and post back if it resolves this bug? Please note, you will need to install both the linux-image and linux-image- extra .deb

[Kernel-packages] [Bug 1196730] Re: Fn key doesn't work in raring on MacBook Air 6, 2

2013-07-22 Thread Joseph Salisbury
Thanks for the pointer, Linus. Commit 9d9a04ee is in mainline as of v3.11-rc1. It was also cc'd to upstream stable, so it will make it's way into all the stable kernel versions, including Raring. I'll build a test kernel for you with this patch and post a link shortly. If it fixes this bug, I