qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Filip Navara <filip.navara@gmail.com>
To: Evgeniy Dushistov <dushistov@mail.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] [RFC] add emulation of at91sam9263 cpu
Date: Wed, 18 Nov 2009 00:43:15 +0100	[thread overview]
Message-ID: <5b31733c0911171543m6616b3d4nbdadc914f89315f1@mail.gmail.com> (raw)
In-Reply-To: <20091117192315.GB13844@rain>

On Tue, Nov 17, 2009 at 8:23 PM, Evgeniy Dushistov <dushistov@mail.ru> wrote:
> On Tue, Nov 17, 2009 at 10:39:27AM +0100, Filip Navara wrote:
>> I'd say it is preferable to split the individual devices and model
>> them using the QDEV infrastructure instead of putting it all together
>> into one "system controller" device.
>>
>> I've QDEV-based implementation of these devices already: PMC, DBGU,
>> PIO, PITC, AIC. That leaves the "bus matrix", SDRAM controller and
>> USART (which is very similar to DBGU) to be split up.
>>
>
> I also see ethernet IP block (emac),
> I have plans to implement it,
> what about USB slave and CAN controller, you plan/have implementations
> of them?

The EMAC emulation is fully functional and good enough to run a
FreeRTOS/uIP web server and all Atmel examples. I do not plan to
implement USB slave or CAN controller, but I would certainly welcome
if you (or someone else) implemented it. If anything then I will
implement I2C.

Best regards,
Filip Navara

      reply	other threads:[~2009-11-17 23:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-15 20:49 [Qemu-devel] [PATCH 2/2] [RFC] add emulation of at91sam9263 cpu Evgeniy Dushistov
2009-11-17  9:39 ` Filip Navara
2009-11-17 19:23   ` Evgeniy Dushistov
2009-11-17 23:43     ` Filip Navara [this message]

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=5b31733c0911171543m6616b3d4nbdadc914f89315f1@mail.gmail.com \
    --to=filip.navara@gmail.com \
    --cc=dushistov@mail.ru \
    --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).