From: "Paulo Henrique Lacerda de Amorim" <phlamorim@riseup.net>
To: devel@edk2.groups.io, ekhoruzhenko@absolute.com
Subject: Re: [edk2-devel] Interpretation of specification
Date: Sat, 4 Jan 2020 14:17:43 -0300 [thread overview]
Message-ID: <e2ba6906-1d8c-8c18-f027-420ada87a50b@riseup.net> (raw)
In-Reply-To: <9658.1578081176951253055@groups.io>
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
I Appreciate you replicated my experiment, and for sure it will be
helpful if you can figure out where the payload is wrong.
Let me know if i should provide more info.
Em 03/01/2020 16:52, Eugene Khoruzhenko escreveu:
> Hi Paulo, I finally got to looking into this and I was able to
> replicate your 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 problem may be not with the TestPkg.c but the way
> payloads are generated. I'll try to dig deeper and compare with my
> code that works OK, and figure it out if you want.
>
[-- Attachment #2: Type: text/html, Size: 1054 bytes --]
next prev parent reply other threads:[~2020-01-04 17:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 17:12 Interpretation of specification phlamorim
2019-10-24 12:33 ` [edk2-devel] " Laszlo Ersek
2019-11-15 18:51 ` phlamorim
2019-11-15 21:32 ` Laszlo Ersek
2019-11-23 4:59 ` Eugene Khoruzhenko
2019-11-23 13:08 ` Paulo Henrique Lacerda de Amorim
2019-11-26 6:08 ` Eugene Khoruzhenko
2019-11-26 15:22 ` Paulo Henrique Lacerda de Amorim
2020-01-03 19:52 ` Eugene Khoruzhenko
2020-01-04 17:17 ` Paulo Henrique Lacerda de Amorim [this message]
2020-01-07 18:13 ` Eugene Khoruzhenko
2020-01-08 11:24 ` Laszlo Ersek
2020-01-08 19:13 ` James Bottomley
2020-01-09 17:17 ` Laszlo Ersek
2020-01-09 17:20 ` James Bottomley
2020-01-10 10:55 ` Laszlo Ersek
2020-01-10 16:04 ` James Bottomley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e2ba6906-1d8c-8c18-f027-420ada87a50b@riseup.net \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox