RFC: add initial support virtio mmio net, rng and serial frontend drivers #529
Conversation
|
@uLipe please add Dan to the commit header. For now it can be in the form of " We can fix it up when Dan signs off |
rng, net and serial device frontend. Authored-by: Dan Milea [email protected] Signed-off-by: Felipe Neves <[email protected]>
uLipe
force-pushed
the
feature/virtio_mmio_drivers_native
branch
from
5ec99e2 to
1a94260
Compare
Done! |
|
@arnopo I don't think the purpose of this PR was to get merged in open-amp main, but to replace the virtio-exp branch. In order to do that, a tag should be created on the current HEAD of virtio-exp, then virtio-exp should be replaced/recreated based on the main branch. Once that is done (I assume by you?), we can reintroduce the native virtio functionality using PRs. |
|
As we discussed in the development channel, @danmilea already have the additions of virtio-mmio drivers in place, but in another branch that will be upstreamed to the main branch once it gets done, so I'm closing this one. Please feel free to reopen if something changes. |
This PR brings the work already done in the open-amp/virtio-exp branch and targets them to the upstream, it is composed by the implementations of the front end drivers of Serial, Networking and RNG kind of devices under the native virtio-mmio transport, for example using the device side implemented into QEMU. It is on top of the work did by @danmilea with some changes to reflect the recent updates on the open-amp functions.
Although the implementations of the devices above are complete, there are some decisions regarding the placement of the VRINGS and how to expose them for both sides needs to be taken, and until that this PR can be reviewed but it should not merged.
The current drivers were tested against following Zephyr RTOS branch,
which provided some samples to evaluate each of the devices: