summaryrefslogtreecommitdiffstats
path: root/Documentation/m68k
diff options
context:
space:
mode:
authorHuacai Chen <chenhc@lemote.com>2020-03-31 08:18:08 +0200
committerGerd Hoffmann <kraxel@redhat.com>2020-03-31 16:48:00 +0200
commit80e5f89da3ab949fbbf1cae01dfaea29f5483a75 (patch)
tree7d7255645a629007455a3db68c979b0c3ff20f5d /Documentation/m68k
parentdrm/mm: revert "Break long searches in fragmented address spaces" (diff)
downloadlinux-80e5f89da3ab949fbbf1cae01dfaea29f5483a75.tar.xz
linux-80e5f89da3ab949fbbf1cae01dfaea29f5483a75.zip
drm/qxl: Use correct notify port address when creating cursor ring
The command ring and cursor ring use different notify port addresses definition: QXL_IO_NOTIFY_CMD and QXL_IO_NOTIFY_CURSOR. However, in qxl_device_init() we use QXL_IO_NOTIFY_CMD to create both command ring and cursor ring. This doesn't cause any problems now, because QEMU's behaviors on QXL_IO_NOTIFY_CMD and QXL_IO_NOTIFY_CURSOR are the same. However, QEMU's behavior may be change in future, so let's fix it. P.S.: In the X.org QXL driver, the notify port address of cursor ring is correct. Signed-off-by: Huacai Chen <chenhc@lemote.com> Cc: <stable@vger.kernel.org> Link: http://patchwork.freedesktop.org/patch/msgid/1585635488-17507-1-git-send-email-chenhc@lemote.com Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Diffstat (limited to 'Documentation/m68k')
0 files changed, 0 insertions, 0 deletions