From: Laszlo Ersek <lersek@redhat.com>
To: edk2-devel-01 <edk2-devel@lists.01.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Jiaxin Wu <jiaxin.wu@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Liming Gao <liming.gao@intel.com>
Subject: [PATCH 0/2] OvmfPkg: refresh -D E1000_ENABLE (Intel proprietary driver for e1000)
Date: Thu, 29 Jun 2017 00:06:43 +0200 [thread overview]
Message-ID: <20170628220645.26413-1-lersek@redhat.com> (raw)
The current instructions in the README, and the filenames in the FDF
files, are out of date. They are updated in the second patch.
Including the new driver in DXEFV requires a separate one-liner build
tweak for DXEFV, which however takes a wall of text to explain. This is
done in the first patch.
Repo: https://github.com/lersek/edk2.git
Branch: e1000_refresh
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Jiaxin Wu <jiaxin.wu@intel.com>
Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Liming Gao <liming.gao@intel.com>
Thanks,
Laszlo
Laszlo Ersek (2):
OvmfPkg: disable build-time relocation for DXEFV modules
OvmfPkg: update -D E1000_ENABLE from Intel PROEFI v.07 to BootUtil
v.22
OvmfPkg/OvmfPkgIa32.fdf | 6 +---
OvmfPkg/OvmfPkgIa32X64.fdf | 3 +-
OvmfPkg/OvmfPkgX64.fdf | 3 +-
OvmfPkg/README | 31 +++++++++++++-------
4 files changed, 26 insertions(+), 17 deletions(-)
--
2.13.1.3.g8be5a757fa67
next reply other threads:[~2017-06-28 22:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 22:06 Laszlo Ersek [this message]
2017-06-28 22:06 ` [PATCH 1/2] OvmfPkg: disable build-time relocation for DXEFV modules Laszlo Ersek
2017-06-29 3:32 ` Gao, Liming
2017-07-01 20:36 ` Laszlo Ersek
2017-07-03 15:08 ` Gao, Liming
2017-07-03 17:53 ` Laszlo Ersek
2017-07-05 17:48 ` Jordan Justen
2017-07-05 17:55 ` Laszlo Ersek
2017-06-28 22:06 ` [PATCH 2/2] OvmfPkg: update -D E1000_ENABLE from Intel PROEFI v.07 to BootUtil v.22 Laszlo Ersek
2017-06-30 1:20 ` Wu, Jiaxin
2017-07-01 20:22 ` Laszlo Ersek
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=20170628220645.26413-1-lersek@redhat.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