From: "Alex Bennée" <alex.bennee@linaro.org>
To: Sam Price <thesamprice@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: Device driver api
Date: Thu, 24 Mar 2022 20:44:13 +0000 [thread overview]
Message-ID: <87fsn72hx9.fsf@linaro.org> (raw)
In-Reply-To: <CAEekfLZ2iJKTZoqDCusrn+Hvcdxxe9TpyshkU9VvrLAVREBWdA@mail.gmail.com>
Sam Price <thesamprice@gmail.com> writes:
> Is there a shared library interface in the works for writing firmware
> device models without recompiling all of qemu?
No - but incremental builds should be fairly cheap especially if you
only build the target you care about, possibly with a reduced config.
> I was reading through
> https://sebastienbourdelin.com/2021/06/16/writing-a-custom-device-for-qemu/
That's a nice write-up.
> but was wondering if there was a shared library approach where I could build my device driver with some basic functions for getting
> memory ranges this library supports / etc and then
>
> https://elinux.org/images/9/95/Jw-ei-elc2010-final.pdf
> 10 years ago there was a presentation mentioning using dlopen to do
> thisd o this type of thing.
The upstream community isn't really motivated to maintain an API for
external device models because ultimately we believe they are best
placed in the QEMU code, if not upstream in a fork. There are some forks
of QEMU which support things like SystemC models but so far none of that
has been submitted for upstream.
--
Alex Bennée
next prev parent reply other threads:[~2022-03-24 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 15:45 Device driver api Sam Price
2022-03-24 20:44 ` Alex Bennée [this message]
2022-03-24 21:25 ` Peter Maydell
2022-03-24 23:04 ` Sam Price
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=87fsn72hx9.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thesamprice@gmail.com \
/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.