qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel@nongnu.org, Blue Swirl <blauwirbel@gmail.com>,
	Bob Breuer <breuerr@mc.net>,
	Anthony Liguori <aliguori@amazon.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Artyom Tarasenko <atar4qemu@gmail.com>
Subject: Re: [Qemu-devel] [PATCHv2 1/2] sun4m: Add Sun CG3 framebuffer and corresponding OpenBIOS FCode ROM
Date: Sun, 09 Feb 2014 16:39:59 +0100	[thread overview]
Message-ID: <52F7A14F.3050906@suse.de> (raw)
In-Reply-To: <52F79DB2.1000401@ilande.co.uk>

Am 09.02.2014 16:24, schrieb Mark Cave-Ayland:
> One thing I'm not sure about is how the QOM stuff interacts with sysbus
> - can you quickly point me towards an existing device that does this so
> I can understand how this works?

The ARM MPCore devices come to mind. But really all you've been asked to
do in that aspect is replace dc->init with dc->realize and adapt the
signature to make it compile. :) A bonus would be to separate between
.instance_init and dc->realize, with MemoryRegion initialization and
anything that does not rely on properties going into the initfn, and
everything relying on properties being specified or affecting global
state (such as RAM registration, VMState registration, ...) going into
the realizefn.

> These patches have been around for
> months and I really want to get them in for QEMU 2.0 if freeze is coming
> up soon.

Apart from Blue's absence I see no major blocker to that. :)

I initially wondered if -vga wasn't considered a legacy option, but I
figured we can't create SysBus/SBus devices through -device, so no
alternative. SBus QOM base class refactorings as discussed for an
earlier device can be applied on top and are not strictly needed for 2.0
unless you have more such devices coming up.

Cheers,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2014-02-09 15:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-08 16:38 [Qemu-devel] [PATCHv2 0/2] sun4m: Implement Sun CG3 framebuffer for QEMU Mark Cave-Ayland
2014-02-08 16:38 ` [Qemu-devel] [PATCHv2 1/2] sun4m: Add Sun CG3 framebuffer and corresponding OpenBIOS FCode ROM Mark Cave-Ayland
2014-02-09  4:14   ` Peter Crosthwaite
2014-02-09 13:35     ` Mark Cave-Ayland
2014-02-14 14:54       ` Peter Crosthwaite
2014-02-17 12:50         ` Mark Cave-Ayland
2014-02-17 16:18           ` Bob Breuer
2014-02-09 14:41   ` Peter Maydell
2014-02-09 15:19     ` Mark Cave-Ayland
2014-02-09 15:33       ` Peter Maydell
2014-02-17 12:33         ` Mark Cave-Ayland
2014-02-09 15:10   ` Andreas Färber
2014-02-09 15:24     ` Mark Cave-Ayland
2014-02-09 15:39       ` Andreas Färber [this message]
2014-02-10  8:20       ` Paolo Bonzini
2014-02-17 12:43         ` Mark Cave-Ayland
2014-02-17 12:54           ` Paolo Bonzini
2014-02-08 16:38 ` [Qemu-devel] [PATCHv2 2/2] sun4m: Add Sun CG3 framebuffer initialisation function Mark Cave-Ayland
2014-02-09 15:32   ` Andreas Färber
2014-02-17 12:30     ` Mark Cave-Ayland
2014-02-19 21:23       ` Mark Cave-Ayland

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=52F7A14F.3050906@suse.de \
    --to=afaerber@suse.de \
    --cc=aliguori@amazon.com \
    --cc=atar4qemu@gmail.com \
    --cc=blauwirbel@gmail.com \
    --cc=breuerr@mc.net \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@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;
as well as URLs for NNTP newsgroup(s).