ExternalVendorCode/genode
1
0
Fork 0
mirror of https://github.com/genodelabs/genode.git synced 2024-12-21 06:33:31 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

virt_qemu: Use VirtIO fb driver instead of ramfb.

Browse Source 
This driver should be better suited for VirtIO based board like
qemu_virt.
This commit is contained in:
Piotr Tworek 2021-11-16 18:40:29 +01:00 committed by Christian Helmuth
parent 7c1888644a
commit 30b3ad218f
3 changed files with 13 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
repos/base/board/virt_qemu/qemu_args
View File

@ -3,7 +3,7 @@
-device virtio-net-device,bus=virtio-mmio-bus.0,netdev=net0 -device virtio-net-device,bus=virtio-mmio-bus.0,netdev=net0
-device virtio-mouse-device -device virtio-mouse-device
-device virtio-keyboard-device -device virtio-keyboard-device
-device ramfb -device virtio-gpu-device
-netdev user,id=net0 -netdev user,id=net0
arm_v8a: -M virt,virtualization=true,gic-version=3 -cpu cortex-a53 -smp 4 arm_v8a: -M virt,virtualization=true,gic-version=3 -cpu cortex-a53 -smp 4
arm_v7a: -M virt,virtualization=true -cpu cortex-a15 -smp 2 arm_v7a: -M virt,virtualization=true -cpu cortex-a15 -smp 2

2
repos/os/recipes/pkg/drivers_interactive-virt_qemu/archives
View File

@ -1,4 +1,4 @@
_/src/virt_qemu_drivers _/src/virtio_fb_drv
_/src/virtio_input_drv _/src/virtio_input_drv
_/src/platform_drv _/src/platform_drv
_/src/event_filter _/src/event_filter

36
repos/os/recipes/raw/drivers_interactive-virt_qemu/drivers.config
View File

@ -18,15 +18,8 @@
<provides> <service name="ROM"/> </provides> <provides> <service name="ROM"/> </provides>
<route> <any-service> <parent/> </any-service> </route> <route> <any-service> <parent/> </any-service> </route>
<config> <config>
<policy label_prefix="virtio_fb_drv" info="yes">
<!-- device resource declarations --> <device name="gpu0"/>
<device name="fw-cfg" type="qemu,fw-cfg-mmio">
<io_mem address="0x9020000" size="0x1000"/>
</device>
<!-- policy part, who owns which devices -->
<policy label="fb_drv -> " info="yes">
<device name="fw-cfg"/>
</policy> </policy>
<policy label_prefix="virtio_keyboard_drv" info="yes"> <policy label_prefix="virtio_keyboard_drv" info="yes">
<device name="input0"/> <device name="input0"/>
@ -48,22 +41,6 @@
</route> </route>
</start> </start>
<start name="fb_drv">
<binary name="ram_fb_drv"/>
<resource name="RAM" quantum="8M"/>
<route>
<service name="Platform">
<child name="platform_drv"/>
</service>
<service name="ROM"> <parent/> </service>
<service name="PD"> <parent/> </service>
<service name="CPU"> <parent/> </service>
<service name="LOG"> <parent/> </service>
<service name="Timer"> <parent/> </service>
<service name="Capture"> <parent/> </service>
</route>
</start>
<start name="event_filter" caps="90"> <start name="event_filter" caps="90">
<resource name="RAM" quantum="1280K"/> <resource name="RAM" quantum="1280K"/>
<provides> <service name="Event"/> </provides> <provides> <service name="Event"/> </provides>
@ -108,4 +85,13 @@
</route> </route>
</start> </start>
<start name="virtio_fb_drv" caps="120">
<binary name="virtio_mmio_fb_drv"/>
<resource name="RAM" quantum="50M"/>
<route>
<service name="Platform"> <child name="platform_drv"/> </service>
<any-service> <parent/> </any-service>
</route>
</start>
</config> </config>