public inbox for qemu-devel@nongnu.org
 help / color / mirror / Atom feed
From: BALATON Zoltan <balaton@eik.bme.hu>
To: qemu-devel@nongnu.org
Cc: "Gerd Hoffmann" <kraxel@redhat.com>,
	marcandre.lureau@redhat.com,
	"Chad Jablonski" <chad@jablonski.xyz>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [PATCH v5 0/8] ati-vga fixes
Date: Sat, 21 Mar 2026 02:04:18 +0100 (CET)	[thread overview]
Message-ID: <cover.1774054635.git.balaton@eik.bme.hu> (raw)

v5:
- fix typo on Patch 6
- add more patches to fix mouse pointer with big endian frame buffer

v4:
- compile fix in patch 5
- new patch 6 to work around fuloong2e issue:
https://lists.nongnu.org/archive/html/qemu-devel/2026-01/msg06308.html
v3:
- fix patch 1 to work with 8 and 16 bit modes too
- new patch 5 to fix display updates with 8 and 16 bit modes
v2:
- fix patch 4 to really avoid warnings

These are some fixes to ati-vga for 11.0.

Patch 1 fixes problem reported in
https://lists.nongnu.org/archive/html/qemu-ppc/2026-01/msg00105.html

Patch 2 fixes output from Solaris install iso
Rendering still not always correct as it uses some unimplemented
features but it's now readable. I did not test full install though.

Patch 3 fixes vram overrun errors seen with Solaris and MorphOS when
crtc offset is non-zero (this happens on MorphOS when additional
screen is opened)

Patch 4 tries to avoid Coverity warning matching what other places
already do

Patch 5 fixes dirty region tracking when guest display depth is not
the same as the host's

Patch 6 adds work around for fuloong2e to keep working with partial
machine model

BALATON Zoltan (8):
  ati-vga: Fix colors when frame buffer endianness does not match host
  ati-vga: Also switch mode on HW cursor enable bit change
  ati-vga: Do not add crtc offset to src and dst data address
  ati-vga: Avoid warnings about sign extension
  ati-vga: Fix display updates in non-32 bit modes
  ati-vga: Add work around for fuloong2e
  ati-vga: Fix mouse pointer on big endian frame buffer
  ati-vga: Make sure hardware cursor data is within vram

 hw/display/ati.c     | 95 +++++++++++++++++++++++++++-----------------
 hw/display/ati_2d.c  | 47 +++++++++++++++-------
 hw/display/ati_int.h |  1 +
 hw/mips/fuloong2e.c  |  1 +
 4 files changed, 93 insertions(+), 51 deletions(-)

-- 
2.41.3



             reply	other threads:[~2026-03-21  1:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-21  1:04 BALATON Zoltan [this message]
2026-03-21  1:04 ` [PATCH v5 1/8] ati-vga: Fix colors when frame buffer endianness does not match host BALATON Zoltan
2026-03-21  1:04 ` [PATCH v5 2/8] ati-vga: Also switch mode on HW cursor enable bit change BALATON Zoltan
2026-03-21  1:04 ` [PATCH v5 3/8] ati-vga: Do not add crtc offset to src and dst data address BALATON Zoltan
2026-03-21  1:04 ` [PATCH v5 4/8] ati-vga: Avoid warnings about sign extension BALATON Zoltan
2026-03-21  1:04 ` [PATCH v5 5/8] ati-vga: Fix display updates in non-32 bit modes BALATON Zoltan
2026-03-21  1:04 ` [PATCH v5 6/8] ati-vga: Add work around for fuloong2e BALATON Zoltan
2026-03-21  1:04 ` [PATCH v5 7/8] ati-vga: Fix mouse pointer on big endian frame buffer BALATON Zoltan
2026-03-21  1:04 ` [PATCH v5 8/8] ati-vga: Make sure hardware cursor data is within vram BALATON Zoltan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1774054635.git.balaton@eik.bme.hu \
    --to=balaton@eik.bme.hu \
    --cc=chad@jablonski.xyz \
    --cc=kraxel@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox