generated from riscv/docs-spec-template
-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #6 from vlsunil/reorg
Reorganize individual chapters as separate files
- Loading branch information
Showing
7 changed files
with
338 additions
and
371 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,8 @@ | ||
[bibliography] | ||
== Bibliography | ||
== References | ||
|
||
bibliography::[] | ||
* link:https://github.com/riscv-non-isa/riscv-iommu/releases/download/v1.0.0/riscv-iommu.pdf[RISC-V IOMMU Specification], v1.0.0 | ||
* link:https://uefi.org/specs/ACPI/6.5/[ACPI Specification], Version: v6.5 | ||
|
||
// REVISIT | ||
//bibliography::[] |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
== Introduction | ||
|
||
The RISC-V IO Mapping Table (RIMT) provides information about the RISC-V IOMMU and the relationship | ||
between the IO topology and the IOMMU in ACPI based RISC-V platforms. The RIMT identifies which | ||
components are behind IOMMU and how they are connected together. RISC-V IOMMU can be implemented as | ||
either a PCI device or a platform device. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
[[Mapping-Examples]] | ||
== ID Mapping Examples | ||
|
||
.PCIe device ID mapping example | ||
[[pci_rc_id_mapping_2]] | ||
[cols="2,2,2,4,1", width=95%, options="header"] | ||
|=== | ||
| *Source ID Base* | *Number of IDs* | *Destination Device ID Base* | *Destination IOMMU Offset* | *Flags* | ||
| 0x0000 | 0x10 | 0x0 | IOMMU0_OFFSET_IN_RIMT | 0 | ||
| 0x0100 | 0x10 | 0x10 | IOMMU0_OFFSET_IN_RIMT | 0 | ||
|=== | ||
|
||
.Platform device ID mapping example | ||
[[platform_id_mapping]] | ||
[cols="2,2,2,4,1", width=95%, options="header"] | ||
|=== | ||
| *Source ID Base* | *Number of IDs* | *Destination Device ID Base* | *Destination IOMMU Offset* | *Flags* | ||
| 0x0000 | 0x1 | 0x20 | IOMMU0_OFFSET_IN_RIMT | 0 | ||
|=== |
Oops, something went wrong.