All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <alex@antistatix.de>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: [Qemu-devel] hw/arm: add Lego NXT board
Date: Sun, 13 Jul 2014 16:20:56 +0200	[thread overview]
Message-ID: <53C295C8.5040309@antistatix.de> (raw)

Hi,

I developed a software in the loop simulator for the Lego Mindstorms NXT 
brick. It uses the Qemu ARM emulator to run the Robot's Firmware. I plan 
to release the simulator as an open source project. Now, I wonder if it 
makes sense to integrate the Qemu board implementation back into Qemu 
mainline or simply maintain it as an external set of patches.

The problem is that the qemu board I designed is not self-contained. It 
allows the firmware to read/write IO memory in order to read back sensor 
values from the simulated environment and to control actuators. The 
environment simulator is an external program which is connected to 
several qemu instances via posix named pipes using a simple 
communication protocol. Without pipe interaction the emulator can still 
be used to debug NXT firmware images without sensor/actuator interaction.

I'm happy to prepare a patch, but do you think it is of any value to 
integrate code that is not 100% self contained?

Best Regards
Alexander

             reply	other threads:[~2014-07-13 14:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-13 14:20 Alexander Graf [this message]
2014-07-14 11:23 ` [Qemu-devel] hw/arm: add Lego NXT board 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
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=53C295C8.5040309@antistatix.de \
    --to=alex@antistatix.de \
    --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.