From: "Andreas Färber" <afaerber@suse.de>
To: Anthony Green <green@moxielogic.com>
Cc: Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
Antony Pavlov <antonynpavlov@gmail.com>,
liguang <lig.fnst@cn.fujitsu.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] target-moxie: Add moxie Marin SoC support
Date: Sun, 15 Dec 2013 20:31:50 +0100 [thread overview]
Message-ID: <52AE03A6.1000903@suse.de> (raw)
In-Reply-To: <87situl1ou.fsf@moxielogic.com>
Am 15.12.2013 13:48, schrieb Anthony Green:
> Peter Crosthwaite <peter.crosthwaite@xilinx.com> writes:
>> On Sun, Dec 15, 2013 at 1:59 PM, Anthony Green <green@moxielogic.com> wrote:
>>> diff --git a/hw/moxie/marin.c b/hw/moxie/marin.c
>>> new file mode 100644
>>> index 0000000..0a998e4
>>> --- /dev/null
>>> +++ b/hw/moxie/marin.c
[...]
>>> +static inline DeviceState *marin_uart_create(hwaddr base,
>>> + qemu_irq irq)
>>> +{
>>> + DeviceState *dev;
>>> +
>>> + dev = qdev_create(NULL, "marin-uart");
>>> + qdev_init_nofail(dev);
>>> + sysbus_mmio_map(SYS_BUS_DEVICE(dev), 0, base);
>>> + sysbus_connect_irq(SYS_BUS_DEVICE(dev), 0, irq);
>>> +
>>> + return dev;
>>> +}
>>
>> This is an old style qdev init function.
>
> Any good pointers for a new style init function?
What Peter C. probably meant here was it is a pre-qdev init function.
Unless there is a strong need for reuse, just inline it into the machine
init function to show that it is using pure QOM constructs.
As for new-style init functions, since you are not setting any
properties, chances are good that you can do in an instance_init
function (rather than realize function) what you did in a deprecated
SysBus init function IIRC.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-12-15 19:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-15 3:59 [Qemu-devel] [PATCH] target-moxie: Add moxie Marin SoC support Anthony Green
2013-12-15 5:17 ` Peter Crosthwaite
2013-12-15 5:27 ` Peter Crosthwaite
2013-12-15 12:48 ` Anthony Green
2013-12-15 19:31 ` Andreas Färber [this message]
2013-12-15 20:05 ` Andreas Färber
2013-12-15 21:02 ` Anthony Green
2013-12-16 0:33 ` Peter Crosthwaite
2013-12-16 3:35 ` Anthony Green
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=52AE03A6.1000903@suse.de \
--to=afaerber@suse.de \
--cc=antonynpavlov@gmail.com \
--cc=green@moxielogic.com \
--cc=lig.fnst@cn.fujitsu.com \
--cc=peter.crosthwaite@xilinx.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).