From: Alexander Graf <graf@campus.tu-berlin.de>
To: Paolo Bonzini <pbonzini@redhat.com>,
Alexander Graf <alexander.graf@ilr.tu-berlin.de>,
Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] hw/arm: add Lego NXT board
Date: Wed, 16 Jul 2014 10:40:51 +0200 [thread overview]
Message-ID: <53C63A93.5000704@campus.tu-berlin.de> (raw)
In-Reply-To: <53C58A75.4000702@redhat.com>
On 07/15/2014 10:09 PM, Paolo Bonzini wrote:
> BTW, sorry for the confusion. There is another frequent contributor to
> QEMU with the same name as yours. I only noticed now that the email
> address is different.
Oh right I noticed that; should have said something.
>> 4. Now, thanks to the help on this list I know there is a the "-chardev"
>> functionality in qemu that basically archives what I did by hand using
>> pipes. Now my idea is to port my own "proprietary" implementation to
>> "the qemu way" - chardevs. You said you think it is a bad idea to build
>> a device that directly translates I/O memory access to a chardev. I
>> still don't understand why. Is this all about legal issues or is there a
>> technical reason?
> I think that there are two other ways to do it.
And what about the chardev way? Your silence in this regard is
misterious ;-)
>
> 1) [...]
> 2) [...]
Thanks a lot for your suggestions. I will play a bit and come back when
I have some code to show.
Alexander
next prev parent reply other threads:[~2014-07-16 8:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-13 14:20 [Qemu-devel] hw/arm: add Lego NXT board Alexander Graf
2014-07-14 11:23 ` Peter Crosthwaite
2014-07-14 11:46 ` Paolo Bonzini
2014-07-14 18:09 ` Alexander Graf
2014-07-14 20:37 ` Paolo Bonzini
2014-07-14 21:10 ` Alexander Graf
2014-07-14 22:48 ` Peter Maydell
2014-07-15 7:06 ` Paolo Bonzini
2014-07-15 10:26 ` Alexander Graf
2014-07-15 10:53 ` Paolo Bonzini
2014-07-15 18:55 ` Alexander Graf
2014-07-15 20:09 ` Paolo Bonzini
2014-07-16 8:40 ` Alexander Graf [this message]
2014-07-16 8:50 ` Paolo Bonzini
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=53C63A93.5000704@campus.tu-berlin.de \
--to=graf@campus.tu-berlin.de \
--cc=alexander.graf@ilr.tu-berlin.de \
--cc=pbonzini@redhat.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.