From: David Abdurachmanov <david.abdurachmanov@gmail.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: Markus Armbruster <armbru@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 4/5] hw/display: Add basic ATI VGA emulation
Date: Tue, 12 Mar 2019 07:42:17 +0100 [thread overview]
Message-ID: <CAEn-LTrkA-7x=ZS2ufNWrJQev69oj63tFW+Vs4CGTBA0STR9KQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.1903112044360.69539@zero.eik.bme.hu>
On Mon, Mar 11, 2019 at 8:51 PM BALATON Zoltan <balaton@eik.bme.hu> wrote:
>
> On Mon, 11 Mar 2019, Markus Armbruster wrote:
> > Gerd Hoffmann <kraxel@redhat.com> writes:
> >> From: BALATON Zoltan <balaton@eik.bme.hu>
> >>
> >> At least two machines, the PPC mac99 and MIPS fulong2e, have an ATI
> >> gfx chip by default (Rage 128 Pro and M6/RV100 respectively) and
> >> guests running on these and the PMON2000 firmware of the fulong2e
> >> expect this to be available. Fortunately these are very similar chips
> >> so they can be mostly emulated in the same device model. This patch
> >> adds basic emulation of these ATI VGA chips.
> >>
> >> While this is incomplete and currently only enough to run the MIPS
> >> firmware and get framebuffer output with Linux, it allows the fulong2e
> >> board to work more like the real hardware and having it in QEMU in
> >> this state provides a way to experiment with it and allows others to
> >> contribute to improve it. It is compiled for all archs but only the
> >> fulong2e (which currently has no display output at all) is set to use
> >> it by default (in a separate patch).
> >>
> >> Signed-off-by: BALATON Zoltan <balaton@eik.bme.hu>
> >> Acked-by: Aleksandar Markovic <amarkovic@wavecomp.com>
> >> Tested-by: Andrew Randrianasulu <randrianasulu@gmail.com>
> >> Tested-by: Howard Spoelstra <hsp.cat7@gmail.com>
> >> Message-id: 0b1b7c22873a6e37627261b04fb687412b25ff4f.1552152100.git.balaton@eik.bme.hu
> >> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> > [...]
> >> diff --git a/hw/display/trace-events b/hw/display/trace-events
> >> index 37d3264bb2e6..80993cc4d913 100644
> >> --- a/hw/display/trace-events
> >> +++ b/hw/display/trace-events
> >> @@ -138,3 +138,7 @@ vga_cirrus_write_blt(uint32_t offset, uint32_t val) "offset 0x%x, val 0x%x"
> >> sii9022_read_reg(uint8_t addr, uint8_t val) "addr 0x%02x, val 0x%02x"
> >> sii9022_write_reg(uint8_t addr, uint8_t val) "addr 0x%02x, val 0x%02x"
> >> sii9022_switch_mode(const char *mode) "mode: %s"
> >> +
> >> +# hw/display/ati*.c
> >> +ati_mm_read(unsigned int size, uint64_t addr, const char *name, uint64_t val) "%u 0x%"HWADDR_PRIx " %s -> 0x%"PRIx64
> >> +ati_mm_write(unsigned int size, uint64_t addr, const char *name, uint64_t val) "%u 0x%"HWADDR_PRIx " %s <- 0x%"PRIx64
> >
> > Blows up for me:
> >
> > Traceback (most recent call last):
> > File "/work/armbru/qemu/scripts/tracetool.py", line 152, in <module>
> > main(sys.argv)
> > File "/work/armbru/qemu/scripts/tracetool.py", line 147, in main
> > binary=binary, probe_prefix=probe_prefix)
> > File "/work/armbru/qemu/scripts/tracetool/__init__.py", line 472, in generate
> > tracetool.format.generate(events, format, backend, group)
> > File "/work/armbru/qemu/scripts/tracetool/format/__init__.py", line 85, in generate
> > func(events, backend, group)
> > File "/work/armbru/qemu/scripts/tracetool/format/log_stap.py", line 121, in generate
> > fmt_str = "%d@%d " + e.name + " " + c_fmt_to_stap(e.fmt) + "\\n"
> > File "/work/armbru/qemu/scripts/tracetool/format/log_stap.py", line 64, in c_fmt_to_stap
> > bits.append(c_macro_to_format(macro))
> > File "/work/armbru/qemu/scripts/tracetool/format/log_stap.py", line 36, in c_macro_to_format
> > raise Exception("Unhandled macro '%s'" % macro)
> > Exception: Unhandled macro 'HWADDR_PRIx'
>
> No idea. Nobody else reported a problem with this yet and the above error
> makes no sense to me. Cc'd some tracetool related people who hopefully can
> hint what might be wrong. Do you get error during build? What trace
> backend do you use?
I hit the same issue on my daily QEMU builds for Fedora this morning:
https://copr-be.cloud.fedoraproject.org/results/davidlt/latest-qemu/fedora-29-x86_64/00867106-qemu/
build.log.gz contains all the details.
david
next prev parent reply other threads:[~2019-03-12 6:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 8:50 [Qemu-devel] [PULL 0/5] Vga 20190311 v2 patches Gerd Hoffmann
2019-03-11 8:50 ` [Qemu-devel] [PULL 1/5] virtio: add class_size to VirtioPCIDeviceTypeInfo Gerd Hoffmann
2019-03-11 8:50 ` [Qemu-devel] [PULL 2/5] virtio-vga: fix reset Gerd Hoffmann
2019-03-11 8:50 ` [Qemu-devel] [PULL 3/5] virtio-gpu: make virtio_gpu_reset static Gerd Hoffmann
2019-03-11 8:50 ` [Qemu-devel] [PULL 4/5] hw/display: Add basic ATI VGA emulation Gerd Hoffmann
2019-03-11 17:53 ` Markus Armbruster
2019-03-11 19:51 ` BALATON Zoltan
2019-03-11 19:55 ` Mark Cave-Ayland
2019-03-11 21:14 ` Markus Armbruster
2019-03-11 21:36 ` BALATON Zoltan
2019-03-12 6:42 ` David Abdurachmanov [this message]
2019-03-11 8:50 ` [Qemu-devel] [PULL 5/5] mips_fulong2e: Add on-board graphics chip Gerd Hoffmann
2019-03-11 16:27 ` [Qemu-devel] [PULL 0/5] Vga 20190311 v2 patches Peter Maydell
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='CAEn-LTrkA-7x=ZS2ufNWrJQev69oj63tFW+Vs4CGTBA0STR9KQ@mail.gmail.com' \
--to=david.abdurachmanov@gmail.com \
--cc=armbru@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).