On 18/10/16 12:19, Alexandre Courbot wrote:
On Mon, Oct 17, 2016 at 6:47 PM, Samuel Pitoiset
wrote:
This requires at least a quick test. :-)
Acked-by: Samuel Pitoiset
On 10/16/2016 09:14 PM, Ilia Mirkin wrote:
Signed-off-by: Ilia Mirkin
---
Untested. I don't have the hardware.
Tested on
On 18.10.2016 16:02, Karol Herbst wrote:
> well, I just don't want that this fix breaks the same thing for other
> users, that's why I am asking.
>
Affected device ID:
https://github.com/skeggsb/nouveau/blob/master/drm/nouveau/nvkm/engine/device/pci.c#L1229
can it be excluded from device->chipset
2016-10-19 16:47 GMT+02:00 poma :
> On 18.10.2016 16:02, Karol Herbst wrote:
>> well, I just don't want that this fix breaks the same thing for other
>> users, that's why I am asking.
>>
>
> Affected device ID:
> https://github.com/skeggsb/nouveau/blob/master/drm/nouveau/nvkm/engine/device/pci.c#L1
On 19.10.2016 17:03, Karol Herbst wrote:
> You don't get why I try to say. We have to actually find out when to
> apply this workaround, not to create some silly whitelist/blacklist.
> It's the last option, we never want to actually use.
>
Well if you do not say, who can understand!? :)
Besides,
Hello,
On 07:37 pm - Oct 19 2016, poma wrote:
> On 19.10.2016 17:03, Karol Herbst wrote:
>
> > You don't get why I try to say. We have to actually find out when to
> > apply this workaround, not to create some silly whitelist/blacklist.
> > It's the last option, we never want to actually use.
> >
On 10/20/2016 03:58 AM, Pierre Moreau wrote:
> Hello,
>
> On 07:37 pm - Oct 19 2016, poma wrote:
>> On 19.10.2016 17:03, Karol Herbst wrote:
>>
>>> You don't get why I try to say. We have to actually find out when to
>>> apply this workaround, not to create some silly whitelist/blacklist.
>>> It
