Recent Features
| |||||||||||||
A long-term kernel support updateA long-term kernel support updatePosted Jan 10, 2012 16:38 UTC (Tue) by mpagano (subscriber, #46586)Parent article: A long-term kernel support update
I hope Ubuntu does upstream their patchset but from their history and current actions (see ALPS Dell patchset), I have doubts.
(Log in to post comments)
A long-term kernel support update Posted Jan 10, 2012 17:02 UTC (Tue) by iabervon (subscriber, #722) [Link]
I imagine they'd find it most straightforward to follow the usual long-term support procedure to generate a vanilla 2.6.32.x, and they add their own patches to that. If you don't follow the standard practice, there's no benefit to officially adopting the series.
A long-term kernel support update Posted Jan 10, 2012 20:42 UTC (Tue) by pkern (subscriber, #32883) [Link]
They should've tried harder to push Dell and ALPS to provide a sane driver. As far as I know the current patchset was rejected upstream because it's only doing magical undocumented initialization and then falling back to a dumber protocol (i.e. IMPS/2) than you'd normally talk with a touchpad. In the end, if customers actually had a choice, they'd avoid the Dell laptops for exactly that reason (and if you use the touchpad, it is dazed and confused even with the patch once in a while).
A long-term kernel support update Posted Jan 10, 2012 22:01 UTC (Tue) by jrn (subscriber, #64214) [Link]
linux-next seems to include support for recent ALPS touchpads (commit 25bded7cd60f, "Input: ALPS - add support for protocol versions 3 and 4"). Does it not work? Any links for people who missed the fuss?
A long-term kernel support update Posted Jan 10, 2012 23:09 UTC (Tue) by pkern (subscriber, #32883) [Link]
Then I have to take that back. Kudos to Seth! Any idea when this will land in
mainline, if it didn't already? I guess the author would need to send an explicit merge requests to take something from -next?
A long-term kernel support update Posted Jan 11, 2012 1:03 UTC (Wed) by jrn (subscriber, #64214) [Link]
$ git log 7cf801cfc077 ^origin/master
$
Merged today at 10:55 pacific time, apparently, if "git log --ancestry-path 7cf801cfc077..origin/master" is not tricking me.
|
|||||||||||||