Page MenuHomeFreeBSD

riscv: include AHCI
ClosedPublic

Authored by br on Jun 5 2024, 12:39 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Nov 6, 3:20 AM
Unknown Object (File)
Wed, Nov 6, 3:20 AM
Unknown Object (File)
Sun, Oct 27, 6:33 AM
Unknown Object (File)
Fri, Oct 18, 9:46 AM
Unknown Object (File)
Oct 17 2024, 9:15 AM
Unknown Object (File)
Oct 16 2024, 2:33 PM
Unknown Object (File)
Oct 14 2024, 9:55 PM
Unknown Object (File)
Oct 13 2024, 10:14 AM
Subscribers

Details

Summary

Iinclude AHCI for PCI-e block device emulation.

(needed for Guest VM)

Test Plan

tested on bhyve

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

br requested review of this revision.Jun 5 2024, 12:39 PM
br updated this revision to Diff 139505.

place device directives before include

jrtc27 requested changes to this revision.Jun 5 2024, 3:44 PM

Please use conventional RISC-V IP. For the UART the platform standards want an 8250, and that’s what QEMU’s virt machine provides. For the RTC the goldfish RTC is simple to emulate and what its virt machine uses. If an OS boots on QEMU it should boot on bhyve.

This revision now requires changes to proceed.Jun 5 2024, 3:44 PM
br retitled this revision from riscv: include Arm IP to riscv: include AHCI.
br edited the summary of this revision. (Show Details)

Include AHCI only

Please use conventional RISC-V IP. For the UART the platform standards want an 8250, and that’s what QEMU’s virt machine provides. For the RTC the goldfish RTC is simple to emulate and what its virt machine uses. If an OS boots on QEMU it should boot on bhyve.

Ok I managed to switch to ns16550 uart, but for RTC it is not something I want to focus on currently, so we can do that later.
So lets include just ahci for now

This revision was not accepted when it landed; it landed in state Needs Review.Jun 12 2024, 12:42 PM
This revision was automatically updated to reflect the committed changes.