Re: [edk2] SCT 2.3.1 v1.3

2017-01-21 Thread Jin, Eric
idambara GR <chidambara...@broadcom.com> Subject: Re: [edk2] SCT 2.3.1 v1.3 Laszlo: I agree this is gap between SCT and UEFI spec. I think UEFI spec can be updated to describe these error conditions. Thanks Liming >-Original Message- >From: edk2-devel [mailto:edk2-d

Re: [edk2] SCT 2.3.1 v1.3

2017-01-20 Thread Gao, Liming
8, 2017 4:57 PM >To: Daniel Samuelraj <daniel.samuel...@broadcom.com> >Cc: Jianning Wang <jianning.w...@broadcom.com>; edk2-devel@lists.01.org; >Sathya Prakash <sathya.prak...@broadcom.com>; Chidambara GR ><chidambara...@broadcom.com> >Subject: Re: [edk2] SCT

Re: [edk2] SCT 2.3.1 v1.3

2017-01-18 Thread Laszlo Ersek
(Dropping the and email addresses; please never cross-post the public edk2-devel list with the confidential spec development / working group lists on UEFI.org!) On 01/17/17 22:22, Daniel Samuelraj wrote: > Hi, > > What SCT v1.3 states for HII Config Access Protocol

Re: [edk2] SCT 2.3.1 v1.3

2017-01-17 Thread Daniel Samuelraj
Hi, What SCT v1.3 states for HII Config Access Protocol seems not in align with UEFI spec? For example, for extract config, when Progress or Result or Request is NULL, SCT is expecting EFI Invalid Parameter; similarly for Route Config, when progress is NULL, SCT expects EFI_INVALID_PARAMETER.