qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Pavel Dovgalyuk" <dovgaluk@ispras.ru>
To: "'Michael Rolnik'" <mrolnik@gmail.com>, <qemu-devel@nongnu.org>
Cc: richard.henderson@linaro.org,
	'Sarah Harris' <S.E.Harris@kent.ac.uk>,
	philmd@redhat.com
Subject: Re: [Qemu-devel] [PATCH v27 5/8] target/avr: Add limited support for USART and 16 bit timer peripherals
Date: Thu, 25 Jul 2019 13:00:52 +0300	[thread overview]
Message-ID: <000c01d542cf$d8476a00$88d63e00$@ru> (raw)
In-Reply-To: <20190719082647.18113-6-mrolnik@gmail.com>

> From: Qemu-devel [mailto:qemu-devel-bounces+patchwork-qemu-
> devel=patchwork.kernel.org@nongnu.org] On Behalf Of Michael Rolnik
> From: Sarah Harris <S.E.Harris@kent.ac.uk>
> 
> These were designed to facilitate testing but should provide enough function to be useful in
> other contexts.

USART is very useful for testing, but to which model of AVR is belongs?
We also started implementation of USART and other devices in our internship program,
using prior version of your patches.
There were other register addresses for the registers and some of them even intersect
making read/write logic more complex (we looked at Atmega8).

You also mix the board and the SoC into one file, making hardware-on-chip harder to reuse.

I think that the structure can be revised in the following way:
Board -> SoC -> Devices

Board includes SoC, loads the firmware, and adds some external peripheral devices, if needed.

SoC includes embedded peripherals. It dispatches IO memory accesses and passes them
to the devices. In this case you can have different register addresses for different SoCs, but
the embedded device emulation code can be mostly the same for simple devices like USART.

> Only a subset of the functions of each peripheral is implemented, mainly due to the lack of a
> standard way to handle electrical connections (like GPIO pins).

We did not got too much results, you can check for our changes here: https://github.com/Dovgalyuk/qemu/tree/avr8

But we can help you in development of better version of the patches and split the work
for making this platform more usable.


Pavel Dovgalyuk



  reply	other threads:[~2019-07-25 10:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19  8:26 [Qemu-devel] [PATCH v27 0/8] QEMU AVR 8 bit cores Michael Rolnik
2019-07-19  8:26 ` [Qemu-devel] [PATCH v27 1/8] target/avr: Add outward facing interfaces and core CPU logic Michael Rolnik
2019-07-19  8:26 ` [Qemu-devel] [PATCH v27 2/8] target/avr: Add instruction helpers Michael Rolnik
2019-07-19  8:26 ` [Qemu-devel] [PATCH v27 3/8] target/avr: Add instruction decoding Michael Rolnik
2019-07-19  8:26 ` [Qemu-devel] [PATCH v27 4/8] target/avr: Add instruction translation Michael Rolnik
2019-07-19  8:26 ` [Qemu-devel] [PATCH v27 5/8] target/avr: Add limited support for USART and 16 bit timer peripherals Michael Rolnik
2019-07-25 10:00   ` Pavel Dovgalyuk [this message]
2019-07-25 17:52     ` Michael Rolnik
2019-07-26 14:53       ` Sarah Harris
2019-12-05 10:27     ` Aleksandar Markovic
2019-12-05 10:33       ` Aleksandar Markovic
2019-12-05 11:13         ` Aleksandar Markovic
2019-12-06 11:32       ` Pavel Dovgalyuk
2019-07-19  8:26 ` [Qemu-devel] [PATCH v27 6/8] target/avr: Add example board configuration Michael Rolnik
2019-07-19 14:02   ` Philippe Mathieu-Daudé
2019-07-19 15:04     ` Michael Rolnik
2019-07-19 15:14       ` Michael Rolnik
2019-07-19 15:29         ` Philippe Mathieu-Daudé
2019-07-19  8:26 ` [Qemu-devel] [PATCH v27 7/8] target/avr: Register AVR support with the rest of QEMU, the build system, and the MAINTAINERS file Michael Rolnik
2019-07-19 15:43   ` Eric Blake
2019-07-19 16:04     ` Michael Rolnik
2019-07-19  8:26 ` [Qemu-devel] [PATCH v27 8/8] target/avr: Add tests Michael Rolnik
2019-07-19 13:26   ` Philippe Mathieu-Daudé
2019-07-19 15:05     ` Michael Rolnik
2019-07-21  7:13     ` Thomas Huth
2019-07-22  9:16       ` Michael Rolnik
2019-07-22  9:41         ` Thomas Huth
2019-07-22 12:33           ` Michael Rolnik
2019-07-22 12:40             ` Peter Maydell
2019-07-22 13:45               ` Michael Rolnik

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='000c01d542cf$d8476a00$88d63e00$@ru' \
    --to=dovgaluk@ispras.ru \
    --cc=S.E.Harris@kent.ac.uk \
    --cc=mrolnik@gmail.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).