Device Path Protocols

[rogurr]

What's the end goal for device paths in Patina?

There is a /patina/core/patina_internal_device_path module that handles parsing paths, but it does not implement a lot of the things Tiano supports as defined in:

/edk2/MdePkg/Include/Protocol/DevicePath.h
/edk2/MdePkg/Include/Protocol/DevicePathFromText.h
/edk2/MdePkg/Include/Protocol/DevicePathToText.h
/edk2/MdePkg/Include/Protocol/DevicePathUtilities.h

If we have a PR that needs to parse a device path, should we put the parsing function in patina_internal_device_path for now so that later it can be found and updated to match all other handlers? Or should we keep it local to where it is needed and not expect a central crate to perform those actions?

[makubacki]

I believe the more generic device path code that you should use is in patina_sdk/src/uefi_protocol/device_path

@joschock & @magravel who have worked on device path related changes in the past.

[makubacki]

@rogurr, can we close this discussion or is there more you'd like to discuss?