similar to: [PATCH] drm/nv04/disp: restore console accel after the modeset

cpp[BytePerPlane] can't describe the 10bit data format correctly, So we use bpp[BitPerPlane] to instead cpp. Signed-off-by: Sandy Huang <hjc at rock-chips.com> --- drivers/gpu/drm/nouveau/dispnv04/crtc.c | 7 ++++--- drivers/gpu/drm/nouveau/dispnv50/base507c.c | 4 ++-- drivers/gpu/drm/nouveau/dispnv50/ovly507e.c | 2 +- 3 files changed, 7 insertions(+), 6 deletions(-) diff --git

On Mon, Sep 23, 2019 at 8:56 AM Sandy Huang <hjc at rock-chips.com> wrote: > > cpp[BytePerPlane] can't describe the 10bit data format correctly, > So we use bpp[BitPerPlane] to instead cpp. > > Signed-off-by: Sandy Huang <hjc at rock-chips.com> > --- > drivers/gpu/drm/nouveau/dispnv04/crtc.c | 7 ++++--- > drivers/gpu/drm/nouveau/dispnv50/base507c.c | 4

The buffer object stored in nvbo is also available GEM object in obj[0] of struct drm_framebuffer. Therefore remove nvbo in favor obj[0] and replace all references accordingly. This may require an additional cast. With this change we can already replace nouveau_user_framebuffer_destroy() and nouveau_user_framebuffer_create_handle() with generic GEM helpers. Calls to nouveau_framebuffer_new()

Signed-off-by: Marcin Ko?cielnicki <koriakin at 0x04.net> --- drivers/gpu/drm/nouveau/nv04_graph.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nv04_graph.c b/drivers/gpu/drm/nouveau/nv04_graph.c index 396ee92..d561d77 100644 --- a/drivers/gpu/drm/nouveau/nv04_graph.c +++ b/drivers/gpu/drm/nouveau/nv04_graph.c @@ -543,7 +543,7 @@

Turns out we used a misaligned long instruction near the end, and the shader was getting killed after writing R, A components. This has gone unnoticed since the remaining G, B outputs aren't actually used. --- src/nv50_accel.c | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/src/nv50_accel.c b/src/nv50_accel.c index 5fa539c..1218e18 100644 --- a/src/nv50_accel.c

Hello, After bisection I found the first bad commit : 5e120f6e4b3f35b741c5445dfc755f50128c3c44 is the first bad commit commit 5e120f6e4b3f35b741c5445dfc755f50128c3c44 Author: Ben Skeggs <bskeggs at redhat.com> Date: Mon Apr 30 13:55:29 2012 +1000 drm/nouveau/fence: convert to exec engine, and improve channel sync Now have a somewhat simpler semaphore sync implementation for

On 11/13/2013 02:53 PM, Christian Gagneraud wrote: > Hi there, > > I have used qemu to install FreeBSD 9.2 release, and i can boot it fine > with: > $ qemu-system-x86_64 -hda images/FreeBSD-9.2-RELEASE-amd64.img > > I then made virsh aware of my brand new VM (see attached XML), but when > i run it via virsh, It hangs after the bootloader whith this message: >

On Thu, Dec 14, 2017 at 10:40 AM, ????????? ????????????? ??????? via Syslinux <syslinux at zytor.com> wrote: > Hello friends! > > HAXM is a hardware-assisted virtualization engine (hypervisor) that uses > Intel Virtualization Technology to speed up IA (x86/ x86_64) emulation on a > host machine running Windows or macOS. > > Latest Isolinux 6.03 hangs under VM after

On 14/11/13 10:53, Christian Gagneraud wrote: > Hi there, > > I have used qemu to install FreeBSD 9.2 release, and i can boot it fine > with: > $ qemu-system-x86_64 -hda images/FreeBSD-9.2-RELEASE-amd64.img > > I then made virsh aware of my brand new VM (see attached XML), but when > i run it via virsh, It hangs after the bootloader whith this message: > Booting... >

13:57 < soko> hello. i am getting an error on launch when i set-hv to an arm system. the error appears to be caused by no default machine. here is a log https://pastebin.com/CUBcnG44 13:59 < soko> the default hv works (launch, mount, etc) but fails to emulate (sh, command, etc) the binaries on the fs 14:17 < soko> if i upload qemu-arm-static and then command it

Previously we used (on arm): -M virt -machine accel=... After this change, we use: -machine virt,accel=... On x86 there is no change. The -M option is an abbreviation for -machine, and we can combine the two options together. (Qemu combines the two options internally, but it's more predictable if we do it ourselves). Upstream qemu has supported the -machine option for over 5 years, and in

there's a regression in the xf86-video-nouveau driver that came up in 1.0.3 that causes the desktop to bounce around in virtualbox whenever using HW acceleration in cinnamon and gnome 3, but not in fallback or cinnamon 2d, only happens in virtualbox and not the host, I've confirmed it was the graphics driver on the host because it happened with the 1.0.3 driver but not the 1.0.2.

Hello friends! HAXM is a hardware-assisted virtualization engine (hypervisor) that uses Intel Virtualization Technology to speed up IA (x86/ x86_64) emulation on a host machine running Windows or macOS. Latest Isolinux 6.03 hangs under VM after "Main image LBA =...". Please, help us investigate the root of the problem. Bug on github: https://github.com/intel/haxm/issues/15 Thank you!

ThibG from irc reported an issue with transparent cursors, i noticed the ddx had a workaround, which wasn't in the kms code. ThibG (whoever you are), please test. The patch is untested. Maarten. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-nv04-import-hw-workaround-for-partially-transparent-.patch Type: text/x-patch Size: 4908 bytes Desc: not

The NV4A (aka NV44A) is an oddity in the family. It only comes in AGP and PCI varieties, rather than a core PCIE chip with a bridge for AGP/PCI as necessary. As a result, it appears that the MMU is also non-functional. For AGP cards, the vast majority of the NV4A lineup, this worked out since we force AGP cards to use the nv04 mmu. However for PCI variants, this did not work. Switching to the

In preparation to enabling -Wimplicit-fallthrough, mark switch cases where we are expecting to fall through. Addresses-Coverity-ID: 143119 Addresses-Coverity-ID: 143120 Addresses-Coverity-ID: 143121 Addresses-Coverity-ID: 143122 Addresses-Coverity-ID: 143123 Addresses-Coverity-ID: 143124 Signed-off-by: Gustavo A. R. Silva <garsilva at embeddedor.com> ---

match_string() returns the array index of a matching string. Use it instead of the open-coded implementation. Signed-off-by: YueHaibing <yuehaibing at huawei.com> --- drivers/gpu/drm/nouveau/dispnv04/tvnv17.c | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/drivers/gpu/drm/nouveau/dispnv04/tvnv17.c b/drivers/gpu/drm/nouveau/dispnv04/tvnv17.c index

drivers/gpu/drm/nouveau/dispnv04/arb.c: In function nv04_calc_arb: drivers/gpu/drm/nouveau/dispnv04/arb.c:56:21: warning: variable width set but not used [-Wunused-but-set-variable] 'width' is never used, so remove it. Reported-by: Hulk Robot <hulkci at huawei.com> Signed-off-by: YueHaibing <yuehaibing at huawei.com> --- drivers/gpu/drm/nouveau/dispnv04/arb.c | 3 +-- 1

This fixes a somewhat indeterministic corruption problem on nv17 when there is stuff going on the other fifos (e.g. gallium but I've also reproduced it with an app just SIFM-ing memory around): in some cases it made the blits the X server had scheduled use the wrong pitch. Signed-off-by: Francisco Jerez <currojerez at riseup.net> --- src/nv04_exa.c | 22 ++++++++++++---------- 1

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> Cc: stable at vger.kernel.org --- Ian Romanick reported a kernel crash that implicated this path in a null pointer jump, which means that one of the function pointers had been nulled out. Not sure if a race there would explain it, but maybe. There is also questionable ramht usage in channv50 and various disp code. If you think this is a