You have provided in your first email below that VarCheckUefiLib has been
linked to Variable driver.
MdeModulePkg/Universal/Variable/RuntimeDxe/VariableRuntimeDxe.inf {
<LibraryClasses>
NULL|MdeModulePkg/Library/VarCheckUefiLib/VarCheckUefiLib.inf
}
Thanks,
Star
-----Original Message-----
From: edk2-devel [mailto:[email protected]] On Behalf Of Michael
Zimmermann
Sent: Tuesday, November 3, 2015 9:42 PM
To: Zeng, Star; [email protected]
Subject: Re: [edk2] invalid_parameter when setting variable from application
This message seems to be from 'MdeModulePkg/Library/VarCheckUefiLib' but I'm
using 'MdeModulePkg/Universal/Variable/RuntimeDxe/VarCheck.c'.
Any hints on which lib should be used in which situation?
On Tue, Nov 3, 2015 at 2:30 PM, Zeng, Star <[email protected]> wrote:
> I don’t think return status can give all the meaningful information.
> For example, invalid parameter return status do not tell which
> parameter is invalid. I think it is normal.
>
>
>
> Sometimes, there may be some debug information (to serial) for the cases.
>
> For this case you met, as I know, there should be some debug
> information like “UEFI Variable Check fail %r - %s not in %g
> namespace” to indicate the invalid parameter return status.
>
>
>
> Thanks,
>
> Star
>
> *From:* Michael Zimmermann [mailto:[email protected]]
> *Sent:* Tuesday, November 3, 2015 9:12 PM
> *To:* Zeng, Star
> *Subject:* Re: [edk2] invalid_parameter when setting variable from
> application
>
>
>
> thx a lot for this hint :)
>
> Is it normal, that the description of the return values of the
> SetVariable function does not cover this case or is this a mistake?(or
> more general: do return value specs only cover the most common cases?)
>
>
>
>
>
> On Tue, Nov 3, 2015 at 1:56 AM, Zeng, Star <[email protected]> wrote:
>
> On 2015/11/2 18:31, Michael Zimmermann wrote:
>
> Hi,
>
> I tried to set a
>
> 'EFI_VARIABLE_NON_VOLATILE|EFI_VARIABLE_BOOTSERVICE_ACCESS|EFI_VARIABLE_RUNTIME_ACCESS'
> variable from an UEFI application but SetVariable just returns invalid
> parameter for some reason.(with the global GUID)
>
>
> UEFI spec 3.3 says
>
> "To prevent name collisions with possible future globally defined
> variables, other internal firmware data variables that are not defined
> here must be saved with a unique VendorGuid other than
> EFI_GLOBAL_VARIABLE or any other GUID defined by the UEFI Specification.
>
> Implementations must only permit the creation of variables with a UEFI
> Specification-defined VendorGuid when these variables are documented
> in the UEFI Specification."
>
> If the variable UEFI application set is not defined in UEFI with the
> global GUID, could you define a unique GUID for the special variable
> set in your UEFI application?
>
>
> Thanks,
> Star
>
>
>
>
> I'm setting the variable in the exact same way as other existing ones
> so the only difference really is that I'm using another name. Do I
> have to 'register' variables in the inf file before I can use it? The
> spec doesn't really say sth. about SetVariable returning
> invalid_parameter for sth. like that.
>
> I am using these packages:
> MdeModulePkg/Universal/Variable/RuntimeDxe/VariableRuntimeDxe.inf {
> <LibraryClasses>
> NULL|MdeModulePkg/Library/VarCheckUefiLib/VarCheckUefiLib.inf
> }
>
>
>
>
>
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.01.org/mailman/listinfo/edk2-devel
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.01.org/mailman/listinfo/edk2-devel
