From: Anatol Pomozov <anatol.pomozov@gmail.com>
To: edk2-devel@lists.01.org
Subject: Extracting vendor blobs from edk2-coreboot payload
Date: Tue, 15 May 2018 15:36:58 -0700 [thread overview]
Message-ID: <CAOMFOmUJbMouNRNY8ebEXgi3dcvxDGR2CYhjtzfopPK1dML-2g@mail.gmail.com> (raw)
Hello
I am trying to modify/rebuild a Coreboot+EDK2 rom for my hardware. To
do that I need Intel vendor blobs that I cannot find in web
unfortunately. Intel seems does not share the blobs publicly.
Here is the build script used to build my UEFI payload
https://github.com/MattDevo/edk2/blob/master/build-cpp-hswbdw-box.sh
it needs vbt.bin and IntelGopDriver.efi for Haswell.
So I would like to get my device rom image and extract all the blobs.
BaseTools located at the sourcetree seems focusing around building the
image. But I do not see anything related to splitting the result.
googling does not give a clear answer neither.
Is there a simple tool that allows to extract these Intel blobs from
Build/CorebootPayloadPkgX64/RELEASE_GCC5/FV/UEFIPAYLOAD.fd ?
next reply other threads:[~2018-05-15 22:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 22:36 Anatol Pomozov [this message]
2018-05-17 19:30 ` Extracting vendor blobs from edk2-coreboot payload Blibbet
2018-05-17 19:34 ` Andrew Fish
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=CAOMFOmUJbMouNRNY8ebEXgi3dcvxDGR2CYhjtzfopPK1dML-2g@mail.gmail.com \
--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