similar to: [PATCH 1/3] drm/nv50: Implement ctxprog/state generation.

Signed-off-by: Marcin Ko?cielnicki <koriakin at 0x04.net> --- drivers/gpu/drm/nouveau/nv50_grctx.c | 13 ++++++++++++- 1 files changed, 12 insertions(+), 1 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nv50_grctx.c b/drivers/gpu/drm/nouveau/nv50_grctx.c index 3c3cc46..42a8fb2 100644 --- a/drivers/gpu/drm/nouveau/nv50_grctx.c +++ b/drivers/gpu/drm/nouveau/nv50_grctx.c @@ -177,6 +177,7

This will fix races between generated ctxprogs and interrupt handler. Signed-off-by: Marcin Ko?cielnicki <koriakin at 0x04.net> --- drivers/gpu/drm/nouveau/nv50_grctx.c | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nv50_grctx.c b/drivers/gpu/drm/nouveau/nv50_grctx.c index d105fcd..9f909ab 100644 ---

Avoids conditional definition of grctx build functions, which is hard for IDE's to handle properly. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> --- drivers/gpu/drm/nouveau/nouveau_grctx.h | 21 ++------------------- drivers/gpu/drm/nouveau/nouveau_grctx_def.h | 21 +++++++++++++++++++++ drivers/gpu/drm/nouveau/nv40_graph.c | 2 +-

Avoids conditional definition of grctx build functions, which is hard for IDE's to handle properly. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> --- drivers/gpu/drm/nouveau/nouveau_grctx.h | 21 ++------------------- drivers/gpu/drm/nouveau/nouveau_grctx_def.h | 21 +++++++++++++++++++++ drivers/gpu/drm/nouveau/nv40_graph.c | 2 +-

This makes nouveau recognise and report more kinds of PGRAPH errors, as well as prevent GPU lockups resulting from some of them. Lots of guesswork was involved and some part of this is probably incorrect. Some potential-lockuop situations are handled by just resetting a whole PGRAPH subunit, which doesn't sound like a "proper" solution, but seems to work just fine... for now.

Firmware files in firmware/ directory are not expected to be in binary format. The nouveau files are in binary format, and are therefore removed when running e.g. make clean. Fix that by converting them to ihex format instead. The patch is really big as it contains the ctxprogs stuff, so I'll provide a link instead:

http://bugs.freedesktop.org/show_bug.cgi?id=25952 Summary: GeForce 9800 GTX - nouveau_init takes ~ 1 minute to complete Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: major Priority: high Component: Driver/nouveau AssignedTo: nouveau at

Some archs defconfigs have CONFIG_FRAME_WARN set to 1024, which lead to this warning: drivers/gpu/drm/nouveau/core/engine/graph/ctxnv40.c: warning: the frame size of 1184 bytes is larger than 1024 bytes Reported-by: Geert Uytterhoeven <geert at linux-m68k.org> Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> --- drivers/gpu/drm/nouveau/core/engine/graph/ctxnv40.c | 12

Hi, Here is my patch queue I accumulated over quite a long time. Patches 1-6 are bugfixes, and rest is mostly RFC. Comments are welcome. Best regards, Maxim Levitsky

So, I wrote a generator for ctxprogs on NV50, NV84, NV86, NV92, NV94, NV96, NV98. Atm it's only tested with NV86 and I'd like to see if it works for all the other cards, especially NV50. NVAx support is still missing due to some differences, but should be coming soon. Address is http://0x04.net/~mwk/gen.diff , please test it with all mentioned cards, and involve as much gallium as

11c/004 offset corresponds to PGRAPH reg 0x400828, and is initialised earlier anyway by both our ctxprog generator and blob ctxvals. It's actually incorrect with the generator, since we use different layout on pre-NVA0. Signed-off-by: Marcin Ko?cielnicki <koriakin at 0x04.net> --- drivers/gpu/drm/nouveau/nv50_graph.c | 4 ---- 1 files changed, 0 insertions(+), 4 deletions(-) diff

http://0x04.net/~mwk/0001-drm-nv50-Implement-ctxprog-state-generation.patch This patch makes nouveau generate its own ctxprogs out of thin air on NV50 family cards and allows us to get rid of nvidia's firmware. It differs quite a bit from nvidia progs and needs thorough testing on as many chipsets and applications as possible, including gallium3d. Anything that works with nvidia firmware,

http://bugs.freedesktop.org/show_bug.cgi?id=18286 Summary: GeForce 8300 not supported (10de:0848/C77/MCP77) Product: xorg Version: 7.4 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

Hi, this is from mmio-traces. After startx I see mouse cursor which moves, background split into black and garbage areas. First area consists of repeated pattern of something. Surrealistic picture, and after several seconds box locks up hard, monitor turns off. However much improvement against non-starting X. :-) Card is 10de:0191 (GeForce 8800 GTX) diff --git a/shared-core/nv50_graph.c

Good day. I am Carlo - living in the Netherlands. Today I came in possession of a MSI-produced barebone laptop - a MS-1656-ID1 (which is equivalent in hardware to the GT640 "gaming" laptop). This laptop comes wih a video card that is identified as follows: 01:00.0 VGA compatible controller: nVidia Corporation GT215 [GeForce GTS 250M] (rev a2) (pci ID 10de:0ca9). For your info, the

https://bugzilla.mindrot.org/show_bug.cgi?id=2177 Bug ID: 2177 Summary: wrong sizeof() parameter following chacha20 commit Product: Portable OpenSSH Version: -current Hardware: All OS: All Status: NEW Severity: minor Priority: P5 Component: sshd Assignee: unassigned-bugs at

http://bugs.freedesktop.org/show_bug.cgi?id=23198 Summary: nv50/NVS135M: video hangs/flickers when fullscreen Product: xorg Version: 7.3 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

On Sat, 4 Nov 2017 18:42:36 -0600 Jeff Sadowski <jeff.sadowski at gmail.com> wrote: > I decided to continue trying the ldap route as well > > littlehex2int() > { > hex=$1 > hex_chunk=$(echo ${hex}|cut -c$2-$3) > little=$(echo ${hex_chunk}|awk '{print > substr($0,7,2)substr($0,5,2)substr($0,3,2)substr($0,1,2)}') > echo "ibase=16; ${little}" |

- In the current situation the padding that is added is dangerous to write to, userspace could potentially overwrite parts of another bo. - Depth and stencil buffers are supposed to be large enough in general so the waste of memory should be acceptable. - Alternatives are hiding the padding from users or splitting vram into 2 zones. Signed-off-by: Maarten Maathuis <madman2003 at gmail.com>

http://bugs.freedesktop.org/show_bug.cgi?id=19744 Summary: 9600M GT support Product: xorg Version: unspecified Platform: All OS/Version: All Status: NEW Severity: major Priority: high Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: d.okias at gmail.com