Hi,
On Wed, August 20, 2014 11:31 pm, Tian, Feng wrote:
> Thanks for the great job!
Thank you! It was a lot of fun, though.
> My personal thought likes the idea to add a new package to place your UDF
> driver, but let's see if there is different opinion.
>
> And I am not sure if we can split it to two layers, one is in PartitionDxe
> driver to parse UDF volume descriptor, another layer is like FatDxe to
> parse UDF file system format. Formalizing UDF device path may be another
> concern.
When I started writing the driver, I initially thought it could be part of
PartitionDxe like you said, but the PartitionDxe is just a driver that
follows _exactly_ the path defined by UEFI specification. UDF filesystems
aren't supposed to be recognised or even parsed by firmware as per UEFI
specification.
If there's no problem at all regarding to put UDF code into PartitionDxe,
that would be definitely better. The current code that checks if the block
device has an UDF volume (e.g. IsSupportedUdfVolume()) would be moved to
PartitionDxe and then an EFI_BLOCK_IO_PROTOCOL be provided to each
partition found.
Thanks for the suggestions.
-pcacjr
--
Paulo Alcantara, C.E.S.A.R
Speaking for myself only.
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
