mirror of
https://github.com/RGBCube/serenity
synced 2025-05-31 11:38:11 +00:00
Kernel/Storage+Base: Fix boot_device_addressing document for NVMe
The LUN.target_id parameter points to a NVMe Namespace which starts from 1 and not 0. Fix the document to reflect the same while addressing a nvme device in the boot parameters
This commit is contained in:
parent
84e17fcbcc
commit
f8b67e1596
2 changed files with 2 additions and 2 deletions
|
@ -46,7 +46,7 @@ public:
|
|||
// For example, on a legacy ATA instance, one might connect an harddrive to the second IDE controller,
|
||||
// to the Primary channel as a slave device, which translates to LUN 1:0:1.
|
||||
// On NVMe, for example, connecting a second PCIe NVMe storage device as a sole NVMe namespace translates
|
||||
// to LUN 1:0:0.
|
||||
// to LUN 1:1:0.
|
||||
struct LUNAddress {
|
||||
u32 controller_id;
|
||||
u32 target_id;
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue