|
From: | Sam Price |
Subject: | Re: Device driver api |
Date: | Thu, 24 Mar 2022 19:04:34 -0400 |
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
[Prev in Thread] | Current Thread | [Next in Thread] |