qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: aaron.zakhrov@gmail.com
To: qemu-devel@nongnu.org
Cc: kraxel@redhat.com, Aaron Dominick <aaron.zakhrov@gmail.com>
Subject: [RFC 0/1] ATI R300 emulated grpahics card V2
Date: Thu, 28 Nov 2019 12:13:49 +0530	[thread overview]
Message-ID: <20191128064350.20727-1-aaron.zakhrov@gmail.com> (raw)

From: Aaron Dominick <aaron.zakhrov@gmail.com>

This is the cleaned up patchset to my previous RFC patch set.
I could not reliably clean up my previous commits so I deleted my fork and started from scratch.
The patch looks like a lot of changes but most of it is just register definitions copied from the kernel radeon DRM tree.
What I have implemented so far seems to get a Linux guest to load the DRM and KMS drivers but it cannot find any CRTCs.
dmesg also says that while the GART is allocated, it cannot bind any pages to it.


Aaron Dominick (1):
  Cleaned up Work tree. The radeon_reg.h r300_reg.h and r500_reg.h files
    are from the kernel drm tree. They contain the register definitions
    for the R300 GPU

 hw/display/Kconfig       |    9 +-
 hw/display/Makefile.objs |    2 +
 hw/display/r100d.h       |  869 +++++++++
 hw/display/r300.c        | 1087 +++++++++++
 hw/display/r300.h        |  269 +++
 hw/display/r300_2d.c     |  190 ++
 hw/display/r300_debug.c  |  272 +++
 hw/display/r300_reg.h    | 1789 ++++++++++++++++++
 hw/display/r300d.h       |  343 ++++
 hw/display/r500_reg.h    |  801 ++++++++
 hw/display/radeon_reg.h  | 3725 ++++++++++++++++++++++++++++++++++++++
 11 files changed, 9355 insertions(+), 1 deletion(-)
 create mode 100644 hw/display/r100d.h
 create mode 100644 hw/display/r300.c
 create mode 100644 hw/display/r300.h
 create mode 100644 hw/display/r300_2d.c
 create mode 100644 hw/display/r300_debug.c
 create mode 100644 hw/display/r300_reg.h
 create mode 100644 hw/display/r300d.h
 create mode 100644 hw/display/r500_reg.h
 create mode 100644 hw/display/radeon_reg.h

--
2.24.0


             reply	other threads:[~2019-11-28  6:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28  6:43 aaron.zakhrov [this message]
2019-11-28  6:43 ` [RFC 1/1] Cleaned up Work tree. The radeon_reg.h r300_reg.h and r500_reg.h files are from the kernel drm tree. They contain the register definitions for the R300 GPU aaron.zakhrov
2019-11-28 11:30 ` [RFC 0/1] ATI R300 emulated grpahics card V2 Gerd Hoffmann
2019-11-29 18:41   ` BALATON Zoltan
2019-11-30 12:11     ` BALATON Zoltan
2020-02-11  0:36       ` BALATON Zoltan
2019-11-28 17:33 ` no-reply
2019-11-28 17:39 ` no-reply

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=20191128064350.20727-1-aaron.zakhrov@gmail.com \
    --to=aaron.zakhrov@gmail.com \
    --cc=kraxel@redhat.com \
    --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).