From: "Andreas Färber" <afaerber@suse.de>
To: Anthony Green <green@moxielogic.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
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 21:05:25 +0100 [thread overview]
Message-ID: <52AE0B85.5080200@suse.de> (raw)
In-Reply-To: <87situl1ou.fsf@moxielogic.com>
Hi,
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
>>> @@ -0,0 +1,167 @@
>>> +/*
>>> + * QEMU/marin SoC emulation
>>> + *
>>> + * Emulates the FPGA-hosted Marin SoC
[...]
>>> +static QEMUMachine marin_machine = {
>>> + .name = "marin",
>>> + .desc = "Marin SoC",
>>
>> So SoCs should generally be implemented on two levels. There is the
>> SoC device, which contains the devices that are on the SoC chip, then
>> the board level instantiates the SoC. This looks like a flat
>> board-and-SoC in one (on board level). Your deisgn is trivial so far
>> (and good for a first series), but long term what is the organsation?
>> Is this going towards a particular board emulation? Have a look at
>> Liguangs Allwinner series (and some of the early review comments) for
>> a discussion on this topic:
>>
>> http://lists.gnu.org/archive/html/qemu-devel/2013-11/msg03940.html
>>
>> As a starting point, can you tell us what is and isn't hosted on the
>> FPGA in this board model? That might be the best way to split this.
>
> The Marin SoC currently runs on two boards: the Nexys3 (Xilinx) and DE-2
> (Altera). They are pretty much identical from the software side of
> things. Marin currently provides the UART, PIC, 7 segment display and
> timer devices, as well as various memory controllers. There's no useful
> distinction between SoC and board at this time. I'd like to keep it
> simple as per my patch rather than try to factor them out prematurely.
I thought I've seen a number of odd embedded systems already, but I'm
having trouble understanding your combination of SoC and FPGA: Xilinx
and Altera both have SoCs combining a Cortex-A9 with an FPGA. But your
reference to Xilinx and Altera boards rather sounds as if Moxie is used
as a soft-core processor on the FPGA? In that case the term "SoC" would
be really confusing to me... Can you clarify or aid with some links?
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 20:05 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
2013-12-15 20:05 ` Andreas Färber [this message]
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=52AE0B85.5080200@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=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.