You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the time of writing, we now have a virtio example that shows of libvmm's support for the virtIO console and block devices. We also have a virtio-snd example that shows off the support for virtIO sound.
Originally, we had planned for these two to be merged into one example when we merge all the work regarding sound.
However, to support block we need a driver VM and we also need a driver VM for audio. This presents a problem as for these driver VMs to initialise and talk to their respective pass-through devices, they need access to certain busses (I believe for things like pinmux/clock).
Giving both of these VMs access to these busses does not work. This is a general issue when having multiple driver VMs and not specific to virtIO but this is the first instance where it is a problem for us.
We are working on native drivers for clock/pinmux and once those are done hopefully we can resolve this issue.
The text was updated successfully, but these errors were encountered:
At the time of writing, we now have a
virtio
example that shows of libvmm's support for the virtIO console and block devices. We also have avirtio-snd
example that shows off the support for virtIO sound.Originally, we had planned for these two to be merged into one example when we merge all the work regarding sound.
However, to support block we need a driver VM and we also need a driver VM for audio. This presents a problem as for these driver VMs to initialise and talk to their respective pass-through devices, they need access to certain busses (I believe for things like pinmux/clock).
Giving both of these VMs access to these busses does not work. This is a general issue when having multiple driver VMs and not specific to virtIO but this is the first instance where it is a problem for us.
We are working on native drivers for clock/pinmux and once those are done hopefully we can resolve this issue.
The text was updated successfully, but these errors were encountered: