Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork175
doc: streamline device path documentation between uefi-raw and uefi#1641
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
24709c7 to5522012Compare| //! ├─── DevicePathInstance ────╨────── DevicePathInstance ─────┤ | ||
| //! │ │ | ||
| //! └─────────────────── Entire DevicePath ─────────────────────┘ | ||
| //! ``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I'd like to keep this more detailed documentation inuefi, even if it's also duplicated inuefi-raw. I think users shouldn't normally have to look atuefi-raw unless they're doing something advanced.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I don't have a strong opinion, but I like consistency. In#1612 I also put the main documentation intouefi-raw and just forward to it fromuefi.
When in doubt, I think I prefer some overlap , as long asuefi-raw holds the majority of the low-level documentation details
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Updated. Do you like the new version better?
The idea is that people should not always read the uefi-raw docin any case. Therefore, a briefly simplified version of the uefi-rawdoc is now also in uefi.See#1641 (comment)for a discussion.
The idea is that people should not always read the uefi-raw docin any case. Therefore, a briefly simplified version of the uefi-rawdoc is now also in uefi.See#1641 (comment)for a discussion.
The idea is that people should not always read the uefi-raw docin any case. Therefore, a briefly simplified version of the uefi-rawdoc is now also in uefi.See#1641 (comment)for a discussion.
The idea is that people should not always read the uefi-raw docin any case. Therefore, a briefly simplified version of the uefi-rawdoc is now also in uefi.See#1641 (comment)for a discussion.
The idea is that people should not always read the uefi-raw docin any case. Therefore, a briefly simplified version of the uefi-rawdoc is now also in uefi.See#1641 (comment)for a discussion.
9b9e621Uh oh!
There was an error while loading.Please reload this page.
We don't deduplicate everything and keep a few important thingsin uefi as well. See#1641 (comment) for a discussion.
We don't deduplicate everything and keep a few important thingsin uefi as well. See#1641 (comment) for a discussion.
We don't deduplicate everything and keep a few important thingsin uefi as well. See#1641 (comment) for a discussion.
We don't deduplicate everything and keep a few important thingsin uefi as well. Seerust-osdev#1641 (comment) for a discussion.
Uh oh!
There was an error while loading.Please reload this page.
Closes#1639. I personally prefer to move all generic low-level UEFI documentation to
uefi-rawand refer to it fromuefi.Together with#1612, I think this is a major step forward in our documentation, when it comes to Protocols and Device Paths.
Checklist