From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: "Andreas Färber" <afaerber@suse.de>
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 15:24:34 +0000 [thread overview]
Message-ID: <52F79DB2.1000401@ilande.co.uk> (raw)
In-Reply-To: <52F79A4B.5060404@suse.de>
On 09/02/14 15:10, Andreas Färber wrote:
Hi Andreas,
> Hi,
>
> Am 08.02.2014 17:38, schrieb Mark Cave-Ayland:
>> +static Property cg3_properties[] = {
>> + DEFINE_PROP_HEX32("vram_size", CG3State, vram_size, -1),
>
> Paolo is about to drop hex32 ...
Hmmmm okay...
>> + DEFINE_PROP_UINT16("width", CG3State, width, -1),
>> + DEFINE_PROP_UINT16("height", CG3State, height, -1),
>> + DEFINE_PROP_UINT16("depth", CG3State, depth, -1),
>> + DEFINE_PROP_HEX64("prom_addr", CG3State, prom_addr, -1),
>
> ...and hex64 types. Please use UINT32 and UINT64 instead.
Alright I can change those for the next version of the patch. Does that
mean the use of hex output is now a display option rather than a
separate property type?
>> + DEFINE_PROP_END_OF_LIST(),
>> +};
>
> And as far as QOM and style is concerned, please don't use TCX as excuse
> to do things the old way. If you feel you need consistency, feel free to
> clean up TCX, but we only require it for new patches. Otherwise no
> progress would be possible within the code base.
Okay, I understand this. I'm highly tempted to submit a clean-up patch
for TCX too when this is complete just to keep both drivers in a similar
state.
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? 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.
Many thanks,
Mark.
next prev parent reply other threads:[~2014-02-09 15:26 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 [this message]
2014-02-09 15:39 ` Andreas Färber
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=52F79DB2.1000401@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=atar4qemu@gmail.com \
--cc=blauwirbel@gmail.com \
--cc=breuerr@mc.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.