Thanks for all the insight.
My use case is for embedded programs interfacing with custom fpga
registers, and getting code coverage for these.
My device wouldn't have value for the community.
I'll play around with dlopen, and prototype some stuff on a fork.
Sam
On Thu, Mar 24, 2022 at 4:51 PM Al
On Thu, 24 Mar 2022 at 20:53, Alex Bennée wrote:
> 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 lik
Sam Price 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
Is there a shared library interface in the works for writing firmware
device models without recompiling all of qemu?
I was reading through
https://sebastienbourdelin.com/2021/06/16/writing-a-custom-device-for-qemu/
but was wondering if there was a shared library approach where I could
build my dev
