From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [edk2-devel] Interpretation of specification To: Paulo Henrique Lacerda de Amorim ,devel@edk2.groups.io From: "Eugene Khoruzhenko" X-Originating-Location: Redmond, Washington, US (50.35.77.204) X-Originating-Platform: Windows Chrome 79 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Fri, 03 Jan 2020 11:52:56 -0800 References: <0daf62c6-f746-9e3c-bc01-e32b11161b6f@riseup.net> In-Reply-To: <0daf62c6-f746-9e3c-bc01-e32b11161b6f@riseup.net> Message-ID: <9658.1578081176951253055@groups.io> Content-Type: multipart/alternative; boundary="GRm0b3hasBf1XTdgiNWc" --GRm0b3hasBf1XTdgiNWc Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Paulo, I finally got to looking into this and I was able to replicate yo= ur experiment. I created the payloads with your scripts and tried to write = the "file_name" one with my firmware code and I get the error. So the probl= em may be not with the TestPkg.c but the way payloads are generated. I'll t= ry to dig deeper and compare with my code that works OK, and figure it out = if you want. --GRm0b3hasBf1XTdgiNWc Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Paulo, I finally got to looking into this and I was able to replicate yo= ur experiment. I created the payloads with your scripts and tried to write = the "file_name" one with my firmware code and I get the error. So the probl= em may be not with the TestPkg.c but the way payloads are generated. I'll t= ry to dig deeper and compare with my code that works OK, and figure it out = if you want. --GRm0b3hasBf1XTdgiNWc--