-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Submit this to the kernel and get it in ASAP! #1
Comments
Hi. Nice issue) This version of patch is quite simple and clean, so I do expect it to be admitted. |
Unfortunately I'm not familiar with it, I'm just really hopeful it gets in. Cannot believe it hasn't happened sooner. |
Out of curiosity, which one should I be using? @JanmanX's or yours? |
Nice to hear it. I'm going to try within a week. The problem exists for years, so a week or two is a quite small time for waiting) BTW, have you tried the patched version? |
Well, I would recommend this version, because it has a bit cleaner code and is up to date (about kernel source). |
Also, Jan (@JanmanX) has also tested my patch and found it good and uses it now. If you install this patched version, please public your results, does it work for you and what device do you have. |
Any plans to support DKMS in the meantime? |
Well, it's a small patch for hid-apple. None of us is not an author of hid-apple module, so the question about DKMS is probably irrelevant. |
Yeah, I just figured it might be nice as it could be a while before the patch gets into any actually released kernels (Ubuntu). |
I think, I'll update a Ubuntu's wiki here |
Good idea to update the Ubuntu's wiki. This might prove as a good testing ground for the patch, and even a proof of the quality of the patch :) (The maintainers usually want tested code, or else they might reject it instantly) I figure that if the patch indeed proves to be bug-free, we can try contacting some of the previous authors or some maintainers of the HID modules and see if they are kind enough to help us push it through to the kernel. I am somewhat busy right now, but when I get the time, I am ready to try to make valid Linux kernel patch of the code and see if I can manage to get a hold of some Linux kernel hackers to help us out. /Jan |
Thanks everybody, I've added installation script, please take a look, it may have problems or simple typos as I've made it rather complicated and clever. |
I not only made installation script, but also made changes for passing kernel guidelines checker (scripts/checkpatch.pl in Linux kernel), and prepared a patch to fit this kernel checkpatch.pl requirements. |
Great news! Please keep us updated on the progress! |
Sorry guys for being away for two months. |
This patch was submitted to the kernel maintainers today!I hope it'll be accepted. Thanks to everybody how helped and especially to Jan. |
Amazing work! |
Congrats guys! If there's any advocacy/bumping you need done, feel free to link to the destinations here. |
Thanks, guys! I made it like in patching rules - sent it by email (using real name as it's required by rules) to maintainers. I was put to mail-lists, I've found it here today: |
What is the status of the kernel patch? |
1 of May 2015 - the patch was sent to the maintainers according to all kernel code rules. Since then the code was changed to fit newer kernels and new MacBooks, so in fact, not sure how it could get to the Linux upstream if patches are simply ignored there. |
I have no clue on how the kernel contribution process works. I'm a little surprised that this doesn't get more attention though, are there that few people running Linux on Macbook Pro? FYI: I tried this patch with 4.4.0-040400rc7-generic and it seems to be working fine. It seems like hid-apple.c didn't change between 4.2 and 4.4.0-040400rc7-generic. |
Status is something like - "Ignored by maintainer". Patched version was sent to kernel's maillists, so it's mentioned online at many places, like: http://www.kernelhub.org/?msg=739170&p=2 Anyway, since then the patched version moved forward and supports the new kernel with a few new features. |
any updates? |
Seems a shame this is being ignored - I was really pleased to find a solution and using DKMS it worked perfectly. Thanks! |
Should be in gentoo-sources from version 4.12 - one more reason to switch to Gentoo if someone is in doubt. https://gitweb.gentoo.org/proj/linux-patches.git/commit/?h=4.12&id=593358522f8e378eb4cc0e20efa2e57d6669adfd |
Works great with ubuntu 16, 4.4.0-83-generic on macbook late 2008 with french keyboard layout. This would've saved me some frustration 3 years ago! |
Thanks @benjeffery , @fancywriter , @vilian and everyone else. I'll try to make an updated patch for mainstream Linux kernel and try to push it there again. |
The patch is still working fine and in demand by people, so on holidays in January I'll try to make a version based on latest kernel code checking kernel code guidelines and will try to report it as a patch to mainstream one more time. I will keep you updated on this. |
Hi, are you still trying to get this into mainline? |
@peerchemist today I sent letters to the responsible maintainers (according to get_maintainer.pl script):
and I hope at least one of them will reply and I will be able to provide patches without being ignored. For start I plan to provide patch for only swapping fn and ctrl. And if everything goes smooth then other patches that are included in this repo. |
That is the most important patch indeed. Okay, good luck. |
Jiri Kosina replied. So the process started, maybe in a week it will be done. |
The patch was submitted to the kernel's developers (Jiri in particular). |
I see the patch was merged for Linux 5.8. Congrats! I've updated README in PR #75 Any plans to merge |
Yes, but I had no time or perseverance to prepare proper |
I've never done that. Can you tell me what's involved? Besides making and testing a minimal commit, of course. |
Working on creating a patch for |
After the |
It's the same source, with a few extra commits to add M1 support. I did a diff locally, and it was mostly just magic numbers for the M1/M2 keyboards. https://github.com/AsahiLinux/linux/commits/asahi/drivers/hid/hid-apple.c |
Hmm, I see. So is it preferable to push patches to upstream ASAP and take them to the M1/M2 fork or you prefer to support these patches separately? |
It's preferable to push them upstream, as Asahi runs close to upstream, and can easily adopt new patches. |
I tried to contact upstream maintainers that are responsible for |
What are you waiting for? :)
The text was updated successfully, but these errors were encountered: