From: "Christopher Friedt" <chrisfriedt@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] example pci code ? stubs ?
Date: Fri, 19 Dec 2008 21:22:59 -0500 [thread overview]
Message-ID: <3ea34a000812191822r6a44762fwbe3800a30185e558@mail.gmail.com> (raw)
Hi everyone,
I've been using qemu for a long time, and now I'm hoping to use it for
a project at work - an arm coprocessor over the pci bus. I'm hoping to
design all of the software that I will need, including a kernel module
and userspace libraries, before creating a pcb to have shipped out. I
already have all of the main chips in my BOM determined. Actually, I'm
using the BeagleBoard as a reference design, which has a TI OMAP 3530
ARMv7 chip.
I've been hacking at the qemu code for quite some time now - a few
months actually. I've included my .h in pci.h, and called the init()
in pc.c. My card's init() prints 'Hello, World!\n' to stdout when qemu
starts, but I have yet to see my card with 'lspci'.
Is it possible for one of the qemu developers with a bit more
experience with Qemu to write code for basic PCI card, as well as code
for a kernel module, so that 'lspci' will actually show the card?
This is a bit of a 'jump-start' for would-be Qemu developers, and
could easily be included in the sources for distribution.
Cheers,
Chris
reply other threads:[~2008-12-20 2:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3ea34a000812191822r6a44762fwbe3800a30185e558@mail.gmail.com \
--to=chrisfriedt@gmail.com \
--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).