On 2014-12-29 04:25:28, Paulo Alcantara wrote:
> +typedef struct {
> + VENDOR_DEVICE_PATH DevicePath;
> + EFI_DEVICE_PATH_PROTOCOL End;
> +} UDF_DEVICE_PATH;
> +
> +//
> +// C5BD4D42-1A76-4996-8956-73CDA326CD0A
> +//
> +#define EFI_UDF_DEVICE_PATH_GUID \
> + { 0xC5BD4D42, 0x1A76, 0x4996, \
> + { 0x89, 0x56, 0x73, 0xCD, 0xA3, 0x26, 0xCD, 0x0A } \
> + }
> +
> +UDF_DEVICE_PATH gUdfDevicePath = {
> + { { MEDIA_DEVICE_PATH, MEDIA_VENDOR_DP,
> + { sizeof (VENDOR_DEVICE_PATH), 0 } },
> + EFI_UDF_DEVICE_PATH_GUID
> + },
> + { END_DEVICE_PATH_TYPE, END_ENTIRE_DEVICE_PATH_SUBTYPE,
> + { sizeof (EFI_DEVICE_PATH_PROTOCOL), 0 }
> + }
> +};
Mike,
We had some off-list discussions about the device path. There was some
discussion of trying to have UEFI standardize this device path, but I
think we decided to just stick with a GUID based 'Vendor' device path
for now.
Does Paulo's proposed device path look okay for now?
-Jordan
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
