From: Laurent Vivier <Laurent@Vivier.EU>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Peter Crosthwaite" <peter.crosthwaite@xilinx.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Hervé Poussineau" <hpoussin@reactos.org>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
"Leon Alrae" <leon.alrae@imgtec.com>,
"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH 0/3] dp8393x update
Date: Fri, 02 Jan 2015 12:33:00 +0100 [thread overview]
Message-ID: <54A681EC.9010903@Vivier.EU> (raw)
In-Reply-To: <CAFEAcA9J6kejbB-ohOeCb=ZWL=TcbtuHzkPoFcgOstJ6XmUj_g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
Le 02/01/2015 11:19, Peter Maydell a écrit :
> On 2 January 2015 at 09:25, Laurent Vivier <Laurent@vivier.eu> wrote:
>> Using AddressSpace is really a very good idea, in fact, but I don't like
>> the way you pass it to the device (a qdev_set_prop()).
>>
>> I think we should do as it is done in PCI. This must be managed at
>> sysbus level, not at the device level.
>
> Actually I think using properties is the direction we're
> headed for this currently. (Consider the case of a sysbus
> device which has two DMA master ports, like an ARM trustzone
Does it means that these two DMA master ports can access different
address spaces ?
> aware device.) However I have a feeling the plan was to use
> MemoryRegion properties rather than AddressSpaces.
Is it possible to use something like dma_memory_rw() with MemoryRegion ?
Regards,
Laurent
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2015-01-02 11:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 0:39 [Qemu-devel] [PATCH 0/3] dp8393x update Laurent Vivier
2014-12-29 0:39 ` [Qemu-devel] [PATCH 1/3] dp8393x: add registers offset Laurent Vivier
2014-12-29 0:39 ` [Qemu-devel] [PATCH 2/3] dp8393x: add PROM to store MAC address Laurent Vivier
2014-12-29 0:39 ` [Qemu-devel] [PATCH 3/3] qdev'ify dp8393x Laurent Vivier
2015-01-01 16:15 ` Andreas Färber
2015-01-01 17:32 ` Laurent Vivier
2015-01-01 21:01 ` [Qemu-devel] [PATCH 0/3] dp8393x update Hervé Poussineau
2015-01-02 1:34 ` Laurent Vivier
2015-01-02 9:25 ` Laurent Vivier
2015-01-02 10:19 ` Peter Maydell
2015-01-02 11:33 ` Laurent Vivier [this message]
2015-01-02 12:31 ` Peter Maydell
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=54A681EC.9010903@Vivier.EU \
--to=laurent@vivier.eu \
--cc=aurelien@aurel32.net \
--cc=edgar.iglesias@gmail.com \
--cc=hpoussin@reactos.org \
--cc=leon.alrae@imgtec.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 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).