From: "wzab" <wzab01@gmail.com>
To: qemu-devel@nongnu.org
Cc: wzab@ise.pw.edu.pl
Subject: [Qemu-devel] QEMU API for modelling of user's hardware
Date: Mon, 28 Mar 2011 09:01:09 +0200 [thread overview]
Message-ID: <jrdXBnlsbgTg.QwcwVvWq@smtp.gmail.com> (raw)
Hi,
I wanted to prepare QEMU models of new hardware for my students, to let them to write and debug device drivers before the real hardware is available (or even to optimize the design of this hardware before it is really made).
I was able to establish the basic communication with memory mapped registers of my device, but when it comes to more advanced topics like DMA and interrupts, things start to be difficult.
Is there any reference or manual for people trying to write device models for QEMU? I know that the "hw" subdirectory is full of examples, but I'd prefere something more "formal", with info which solutions are optimal, which are deprecated...
Thank you very much in advance,
Wojciech Zabolotny
next reply other threads:[~2011-03-28 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 7:01 wzab [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-11 20:32 [Qemu-devel] QEMU API for modelling of user's hardware wzab
2011-06-14 8:44 ` Markus Armbruster
2011-06-17 18:26 wzab
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=jrdXBnlsbgTg.QwcwVvWq@smtp.gmail.com \
--to=wzab01@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=wzab@ise.pw.edu.pl \
/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).