Displaying 3 results from an estimated 3 matches for "l408".
Did you mean:
408
2017 Nov 17
1
Blank console but X11 works on MCP79 - old regression since 3.8
.../drm/nouveau/nv50_display.c#L1808
and surrounding items. Looks like lut_clr sets 0x40000000 which was
previously not used. Not sure what the difference between that and
0x00000000 is. This is what we have in rnndb for it:
https://github.com/envytools/envytools/blob/master/rnndb/display/nv_evo.xml#L408
So bit 30 is mode, set is "high res", unset is "low res". So really
what we want is 0x80000000 which leaves the LUT enabled but uses the
low-res mode?
All this could use some playing-around with.
-ilia
2017 Nov 17
3
Blank console but X11 works on MCP79 - old regression since 3.8
On Friday 17 November 2017 18:41:17 Ilia Mirkin wrote:
> On Fri, Nov 17, 2017 at 12:33 PM, Ondrej Zary
>
> <linux at rainbow-software.org> wrote:
> > @@ -483,8 +483,8 @@
> > nouveau 0000:02:00.0: disp: 0860: 00000000 -> 00000500
> > nouveau 0000:02:00.0: disp: 0864: 00000000
> > nouveau 0000:02:00.0: disp: 0868: 00000000 -> 04000500
>
2018 Dec 02
10
[PATCH nbdkit 0/4] Multiple valgrind improvements and possible security fix.
I worked out why valgrind wasn't being applied to nbdkit when run by
many of the tests (patches 1-2). Unfortunately I'm not able to make
it actually fail tests when valgrind fails. Although the situation is
marginally improved in that you can now manually examine the *.log
files and find valgrind failures that way. Also adds valgrinding of
the Python plugin (patch 3).
Along the way I