Displaying 3 results from an estimated 3 matches for "a27e56996".
2016 Jan 17
5
Recommendation for cherry-pick between 3.12 and 4.2: 0a363e85cdaf
...h a quirk, but it isn't extremely necessary for these devices, and
disabling (or, rather, not enabling) MSI is a pretty safe thing to do.
The patch went upstream in 4.3-rc1, however I believe that there are
still a number of kernels between 3.12 (where MSI was first enabled by
default - commit a27e56996) and 4.2 (inclusive) which are still being
maintained. To those maintainers, please consider including this in
your trees.
Cheers,
-ilia
2016 Jan 19
0
Recommendation for cherry-pick between 3.12 and 4.2: 0a363e85cdaf
...ary for these devices, and
>> disabling (or, rather, not enabling) MSI is a pretty safe thing to do.
>>
>> The patch went upstream in 4.3-rc1, however I believe that there are
>> still a number of kernels between 3.12 (where MSI was first enabled by
>> default - commit a27e56996) and 4.2 (inclusive) which are still being
>> maintained. To those maintainers, please consider including this in
>> your trees.
>
> But it needs
> commit fa8c9ac72fe0bcdf5bc7cc84e85cc2a1af53f9fd
> Author: Ilia Mirkin <imirkin at alum.mit.edu>
> Date: Wed Feb 5 14...
2016 Jan 19
2
Recommendation for cherry-pick between 3.12 and 4.2: 0a363e85cdaf
...;t extremely necessary for these devices, and
> disabling (or, rather, not enabling) MSI is a pretty safe thing to do.
>
> The patch went upstream in 4.3-rc1, however I believe that there are
> still a number of kernels between 3.12 (where MSI was first enabled by
> default - commit a27e56996) and 4.2 (inclusive) which are still being
> maintained. To those maintainers, please consider including this in
> your trees.
But it needs
commit fa8c9ac72fe0bcdf5bc7cc84e85cc2a1af53f9fd
Author: Ilia Mirkin <imirkin at alum.mit.edu>
Date: Wed Feb 5 14:33:02 2014 -0500
drm/nv4c/...