Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#53037 - [linux]Enable Multitouch Support for Surface Pro 3

Attached to Project: Arch Linux
Opened by Andrew Slane (slaneaw) - Tuesday, 21 February 2017, 10:10 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 27 February 2022, 10:45 GMT
Task Type Feature Request
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

I was directed here from the Manjaro forums, as the request relates to an upstream kernel patch.

The way it stands, Arch/Manjaro are now the most Surface Pro 3 friendly distributions available. I've been running Manjaro 17.01 Gnome for about two weeks now without any issues aside from missing the multitouch functionality of the type cover's touchpad. A patch for this has been availble since kernel 4.3 was the stable kernel, but it seems that pretty much everyone ignores it... I manually patched and installed the 4.9.11 kernel yesterday using this patch from Fedora (https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org/thread/XID7IKP46VRVRROZP72MCYKLW5WNELCT/1) and the source from kernel.org, and it brings full functionality to the Surface Pro 3 (perhaps other Surface devices as well, although I don't personally own one to test this.)

Any chance this could get applied to the Arch/Manjaro 4.9 and 4.10 kernels? With such a small change, I think you'd be surprised at how much attention it would bring to these distros, being the only distros that supports the Surface Pro (and possibly other Surface devices) out-of-the-box.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Sunday, 27 February 2022, 10:45 GMT
Reason for closing:  None
Additional comments about closing:  No response in years. Let's assume fixed upstream.
Comment by Doug Newgard (Scimmia) - Tuesday, 21 February 2017, 15:36 GMT
A non-upstream feature patch? Chances of this getting included in Arch this way are extremely low.
Comment by mattia (nTia89) - Tuesday, 03 October 2017, 20:21 GMT
is this issue still valid?

have this patch been included in the newer kernel?

Loading...