Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

duplicate FVName GUIDs #323

Open
orangecms opened this issue Nov 4, 2020 · 1 comment
Open

duplicate FVName GUIDs #323

orangecms opened this issue Nov 4, 2020 · 1 comment

Comments

@orangecms
Copy link
Collaborator

orangecms commented Nov 4, 2020

Check if it's a bug in utk or in the vendor firmware - neither is desirable, but our side is fixable.

See fiedka/fiedka#12 where the issue was spotted.

Addendum: UEFITool also lists those duplicates. The question is whether utk should ever handle/support such scenarios: The image file stems from an upgrade, so it could be that it is actually not meant to be a complete nor single image. Cumulative updates, two images in one file for different board variants etc may be the case here.
2020-11-04-181019628317506

@NikolajSchlej
Copy link

Because FVName GUID is optional, and there are no requirements on the container that has volumes for those GUIDs to be unique (there are almost no requirements on that container at all, but very obvious ones like "volumes should not overlap", that's why I'm calling it "raw area" in UEFITool), it's not an issue that those GUIDs are duplicated, at least from parser/editor tool standpoint. Can make a warning about it, but it doesn't break the spec (at least in the "word, not spirit" sense).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants