vasilito/RedBear-OS
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
ea1c855cdcde3b44ff9f2bfefde5726f64a3b658
RedBear-OS/virtiod/VIRTIO.md
T
Anhad Singh c176903905 virtio-blk: read and scheme 
* Minor code cleanup
* Able to read/write from the disk
* Recycle the descriptors (this is currently done inefficiently, will be
  fixed in a follow up commit)
* Add the disk scheme for virtio-blk with working functionality for seek(),
  read() and open()
* After all of this work, we are successfully able to boot redox from
  virtio-blk!! :)

Signed-off-by: Anhad Singh <andypython@protonmail.com>
2023-06-23 12:41:07 +10:00

1.2 KiB
Raw Blame History

Generic

  • Reset the device.
  • Set the ACKNOWLEDGE status bit: the guest OS has noticed the device.
  • Set the DRIVER status bit: the guest OS knows how to drive the device.
  • Setup Interrupts

Driver Specific

  • Read device feature bits, and write the subset of feature bits understood by the OS and driver to the device. During this step the driver MAY read (but MUST NOT write) the device-specific configuration fields to check that it can support the device before accepting it.
  • Set the FEATURES_OK status bit. The driver MUST NOT accept new feature bits after this step.
  • Re-read device status to ensure the FEATURES_OK bit is still set: otherwise, the device does not support our subset of features and the device is unusable.
  • Perform device-specific setup, including discovery of virtqueues for the device, optional per-bus setup, reading and possibly writing the device’s virtio configuration space, and population of virtqueues.
  • Set the DRIVER_OK status bit. At this point the device is “live”.

XXX

  • Mark the deamon as ready.

Drivers

  • virtio-blk (in-progress)
  • virtio-net
  • virtio-gpu
Reference in New Issue View Git Blame Copy Permalink