qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chad Jablonski <chad@jablonski.xyz>
To: qemu-devel@nongnu.org
Cc: balaton@eik.bme.hu, Chad Jablonski <chad@jablonski.xyz>
Subject: [PATCH v2 0/7] ati-vga: Implement HOST_DATA transfers to enable X.org text rendering
Date: Sun,  2 Nov 2025 22:36:01 -0500	[thread overview]
Message-ID: <20251103033608.120908-1-chad@jablonski.xyz> (raw)

This series implements HOST_DATA as a blit source enabling text rendering in
xterm under X.org with 2D acceleration.

The series builds up functionality incrementally:

* Patches 1-2: Scissor rectangle clipping registers and implementation
* Patches 3-4: Additional register support needed for HOST_DATA
* Patches 5-7: HOST_DATA register writes, color expansion, and final blit
               implementation

Tested with xterm on X.org using the r128 driver built with
--disable-dri (MMIO mode).

Changes from v1:

- Split monolithic patch into 7 logical patches as requested
- Integrate HOST_DATA blit into existing ati_2d_blt()
- Add fallback implementation for non-pixman builds
- Remove unnecessary initialization in realize (kept in reset only)
- Fixed DP_GUI_MASTER_CNTL mask to preserve GMC_SRC_SOURCE field
- Implement scissor clipping


Chad Jablonski (7):
  ati-vga: Add scissor clipping register support
  ati-vga: Implement scissor rectangle clipping for 2D operations
  ati-vga: Implement foreground and background color register writes
  ati-vga: Fix DP_GUI_MASTER_CNTL register mask
  ati-vga: Implement HOST_DATA register writes
  ati-vga: Add expand_colors() helper for monochrome color expansion
  ati-vga: Implement HOST_DATA blit source with color expansion

 hw/display/ati.c      |  77 ++++++++++++-
 hw/display/ati_2d.c   | 257 +++++++++++++++++++++++++++++++++---------
 hw/display/ati_dbg.c  |   9 ++
 hw/display/ati_int.h  |   6 +
 hw/display/ati_regs.h |  34 +++++-
 5 files changed, 320 insertions(+), 63 deletions(-)

-- 
2.51.0



             reply	other threads:[~2025-11-03  3:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03  3:36 Chad Jablonski [this message]
2025-11-03  3:36 ` [PATCH v2 1/7] ati-vga: Add scissor clipping register support Chad Jablonski
2025-11-03 13:16   ` BALATON Zoltan
2025-11-04 18:22     ` Chad Jablonski
2025-11-03  3:36 ` [PATCH v2 2/7] ati-vga: Implement scissor rectangle clipping for 2D operations Chad Jablonski
2025-11-03 13:29   ` BALATON Zoltan
2025-11-05 19:29     ` Chad Jablonski
2025-11-03  3:36 ` [PATCH v2 3/7] ati-vga: Implement foreground and background color register writes Chad Jablonski
2025-11-03 13:33   ` BALATON Zoltan
2025-11-03  3:36 ` [PATCH v2 4/7] ati-vga: Fix DP_GUI_MASTER_CNTL register mask Chad Jablonski
2025-11-03 13:46   ` BALATON Zoltan
2025-11-03  3:36 ` [PATCH v2 5/7] ati-vga: Implement HOST_DATA register writes Chad Jablonski
2025-11-03 13:58   ` BALATON Zoltan
2025-11-04 11:26     ` BALATON Zoltan
2025-11-10 19:53       ` Chad Jablonski
2025-11-03  3:36 ` [PATCH v2 6/7] ati-vga: Add expand_colors() helper for monochrome color expansion Chad Jablonski
2025-11-03 14:03   ` BALATON Zoltan
2025-11-10 20:20     ` Chad Jablonski
2025-11-03  3:36 ` [PATCH v2 7/7] ati-vga: Implement HOST_DATA blit source with " Chad Jablonski

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=20251103033608.120908-1-chad@jablonski.xyz \
    --to=chad@jablonski.xyz \
    --cc=balaton@eik.bme.hu \
    --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;
as well as URLs for NNTP newsgroup(s).