Displaying 3 results from an estimated 3 matches for "l1229".
Did you mean:
1229
2016 Oct 19
2
NVAC "No Signal"
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 case 0xac ?
Care to create a patch?
I'll test it.
2016 Oct 19
0
NVAC "No Signal"
...gt; 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 case 0xac ?
>
> Care to create a patch?
> I'll test it.
>
>
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...
2016 Oct 18
2
NVAC "No Signal"
On 18.10.2016 09:35, Karol Herbst wrote:
> how sure are you, that this is needed for _every_ nvac?
>
Thank you for asking.
If you consider, as relevant,
referring to the original commit:
"drm/nouveau/disp/g94: implement workaround for dvi issue on fx380"
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2a4bd8a
<quote>
Fixes the second DVI output