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 7/8] ati-vga: Fix mouse pointer on big endian frame buffer
Date: Sat, 21 Mar 2026 02:04:25 +0100 (CET) [thread overview]
Message-ID: <306212035766ca9459c6c8e890135d361bb5d491.1774054635.git.balaton@eik.bme.hu> (raw)
In-Reply-To: <cover.1774054635.git.balaton@eik.bme.hu>
Rewrite reading of mouse pointer image to fix broken mouse cursor with
big endian frame buffer. I am not sure this is entirely correct but
appears to work at least on little endian host with PPC guests using
little or big endian frame buffer.
Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
---
hw/display/ati.c | 63 +++++++++++++++++++++++++++---------------------
1 file changed, 35 insertions(+), 28 deletions(-)
diff --git a/hw/display/ati.c b/hw/display/ati.c
index fba73a9956..c278d11d34 100644
--- a/hw/display/ati.c
+++ b/hw/display/ati.c
@@ -142,27 +142,29 @@ static void ati_vga_switch_mode(ATIVGAState *s)
/* Used by host side hardware cursor */
static void ati_cursor_define(ATIVGAState *s)
{
- uint8_t data[1024];
+ uint64_t data[128];
uint32_t srcoff;
- int i, j, idx = 0;
if ((s->regs.cur_offset & BIT(31)) || s->cursor_guest_mode) {
return; /* Do not update cursor if locked or rendered by guest */
}
/* FIXME handle cur_hv_offs correctly */
- srcoff = s->regs.cur_offset -
- (s->regs.cur_hv_offs >> 16) - (s->regs.cur_hv_offs & 0xffff) * 16;
- for (i = 0; i < 64; i++) {
- for (j = 0; j < 8; j++, idx++) {
- data[idx] = vga_read_byte(&s->vga, srcoff + i * 16 + j);
- data[512 + idx] = vga_read_byte(&s->vga, srcoff + i * 16 + j + 8);
+ srcoff = s->regs.cur_offset - (s->regs.cur_hv_offs >> 16) -
+ (s->regs.cur_hv_offs & 0xffff) * 16;
+ for (int i = 0; i < 64; i++, srcoff += 16) {
+ if (s->vga.big_endian_fb) {
+ data[i] = wswap64(ldq_be_p(&s->vga.vram_ptr[srcoff]));
+ data[i + 64] = wswap64(ldq_be_p(&s->vga.vram_ptr[srcoff + 8]));
+ } else {
+ data[i] = ldq_le_p(&s->vga.vram_ptr[srcoff]);
+ data[i + 64] = ldq_le_p(&s->vga.vram_ptr[srcoff + 8]);
}
}
if (!s->cursor) {
s->cursor = cursor_alloc(64, 64);
}
cursor_set_mono(s->cursor, s->regs.cur_color1, s->regs.cur_color0,
- &data[512], 1, &data[0]);
+ (uint8_t *)&data[64], 1, (uint8_t *)&data[0]);
dpy_cursor_define(s->vga.con, s->cursor);
}
@@ -197,9 +199,9 @@ static void ati_cursor_invalidate(VGACommonState *vga)
static void ati_cursor_draw_line(VGACommonState *vga, uint8_t *d, int scr_y)
{
ATIVGAState *s = container_of(vga, ATIVGAState, vga);
- uint32_t srcoff;
+ uint32_t h, srcoff, color;
+ uint64_t abits, xbits, mask;
uint32_t *dp = (uint32_t *)d;
- int i, j, h, idx = 0;
if (!(s->regs.crtc_gen_cntl & CRTC2_CUR_EN) ||
scr_y < vga->hw_cursor_y || scr_y >= vga->hw_cursor_y + 64 ||
@@ -210,26 +212,31 @@ static void ati_cursor_draw_line(VGACommonState *vga, uint8_t *d, int scr_y)
srcoff = s->cursor_offset + (scr_y - vga->hw_cursor_y) * 16;
dp = &dp[vga->hw_cursor_x];
h = ((s->regs.crtc_h_total_disp >> 16) + 1) * 8;
- for (i = 0; i < 8; i++) {
- uint32_t color;
- uint8_t abits = vga_read_byte(vga, srcoff + i);
- uint8_t xbits = vga_read_byte(vga, srcoff + i + 8);
- for (j = 0; j < 8; j++, abits <<= 1, xbits <<= 1, idx++) {
- if (vga->hw_cursor_x + idx >= h) {
- return; /* end of screen, don't span to next line */
- }
- if (abits & BIT(7)) {
- if (xbits & BIT(7)) {
- color = dp[idx] ^ 0xffffffff; /* complement */
- } else {
- continue; /* transparent, no change */
- }
+ abits = ldq_le_p(&vga->vram_ptr[srcoff]);
+ xbits = ldq_le_p(&vga->vram_ptr[srcoff + 8]);
+ if (vga->big_endian_fb) {
+ abits = wswap64(abits);
+ xbits = wswap64(xbits);
+ } else {
+ bswap64s(&abits);
+ bswap64s(&xbits);
+ }
+ mask = BIT(63);
+ for (int i = 0; i < 64; i++, mask >>= 1) {
+ if (vga->hw_cursor_x + i >= h) {
+ return; /* end of screen, don't span to next line */
+ }
+ if (abits & mask) {
+ if (xbits & mask) {
+ color = dp[i] ^ 0xffffffff; /* complement */
} else {
- color = (xbits & BIT(7) ? s->regs.cur_color1 :
- s->regs.cur_color0) | 0xff000000;
+ continue; /* transparent, no change */
}
- dp[idx] = color;
+ } else {
+ color = (xbits & mask ? s->regs.cur_color1 :
+ s->regs.cur_color0) | 0xff000000;
}
+ dp[i] = color;
}
}
--
2.41.3
next prev parent 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 [PATCH v5 0/8] ati-vga fixes BALATON Zoltan
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 ` BALATON Zoltan [this message]
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=306212035766ca9459c6c8e890135d361bb5d491.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