From: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
To: chipsec@lists.01.org
Subject: [PATCH 0/9] chipsec: bump to v1.2.5+
Date: Fri, 10 Mar 2017 15:36:12 -0800 [thread overview]
Message-ID: <1489188981-23886-1-git-send-email-ricardo.neri-calderon@linux.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2559 bytes --]
This patches aims to update to CHIPSEC v1.2.5 plus the latest contents
of the CHIPSEC repository. The intention is to pave the way to update
to v1.2.6 once it is out; provided it does not vary significantly wrt
the current code base.
Many things have changed in CHIPSEC since the last time we updated it:
* CHIPSEC now relies more on various python modules and less on custom
solutions.
* CHIPSEC now handles the build and insertion of the chipsec.ko
kernel module.
* The structure of the repository has changed significantly
All these changes need to be reflected in our recipe. In order to not
break builds, these changes would need to be done in a single gigantic
patch. Instead, I disabled CHIPSEC temporarily to be able to split
all the needed changes in a more logical and simpler manner. CHIPSEC
is re-enabled towards the end of the series.
Thanks and BR,
Ricardo
Ricardo Neri (9):
core-image-efi-initramfs: Temporarily disable chipsec
chipsec: update support for 32-bit
chipsec: do not custom-build the chipsec kernel module
chipsec: remove _prepend's that change directories
chipsec: correct location of installation
chipsec: update build time and runtime dependencies
chipsec: bump to v1.2.5+
chipsec: do not ship manual
core-image-efi-initramfs: Re-enable chipsec
.../0001-chipsec-building-for-32-bit-systems.patch | 49 ++++----------
.../chipsec/0001-chipsec-do-not-ship-manual.patch | 38 +++++++++++
...ux-Do-not-host-system-s-kernel-source-dir.patch | 29 +++++++++
...utilize-inode_lock-unlock-wrappers-for-ne.patch | 44 -------------
...ux-Don-t-build-userland-app-automatically.patch | 37 -----------
meta-luv/recipes-core/chipsec/chipsec/chipsec | 5 --
...up-install-cores-library-under-helper-lin.patch | 31 ---------
meta-luv/recipes-core/chipsec/chipsec_git.bb | 75 +++++++++-------------
8 files changed, 110 insertions(+), 198 deletions(-)
create mode 100644 meta-luv/recipes-core/chipsec/chipsec/0001-chipsec-do-not-ship-manual.patch
create mode 100644 meta-luv/recipes-core/chipsec/chipsec/0001-drivers-linux-Do-not-host-system-s-kernel-source-dir.patch
delete mode 100644 meta-luv/recipes-core/chipsec/chipsec/0002-chipsec_km-utilize-inode_lock-unlock-wrappers-for-ne.patch
delete mode 100644 meta-luv/recipes-core/chipsec/chipsec/0006-drivers-linux-Don-t-build-userland-app-automatically.patch
delete mode 100644 meta-luv/recipes-core/chipsec/chipsec/chipsec-setup-install-cores-library-under-helper-lin.patch
--
2.7.4
next reply other threads:[~2017-03-10 23:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 23:36 Ricardo Neri [this message]
2017-03-10 23:36 ` [PATCH 1/9] core-image-efi-initramfs: Temporarily disable chipsec Ricardo Neri
2017-03-10 23:36 ` [PATCH 2/9] chipsec: update support for 32-bit Ricardo Neri
2017-03-10 23:36 ` [PATCH 3/9] chipsec: do not custom-build the chipsec kernel module Ricardo Neri
2017-03-10 23:36 ` [PATCH 4/9] chipsec: remove _prepend's that change directories Ricardo Neri
2017-03-10 23:36 ` [PATCH 5/9] chipsec: correct location of installation Ricardo Neri
2017-03-10 23:36 ` [PATCH 6/9] chipsec: update build time and runtime dependencies Ricardo Neri
2017-03-10 23:36 ` [PATCH 7/9] chipsec: bump to v1.2.5+ Ricardo Neri
2017-03-10 23:36 ` [PATCH 8/9] chipsec: do not ship manual Ricardo Neri
2017-03-10 23:36 ` [PATCH 9/9] core-image-efi-initramfs: Re-enable chipsec Ricardo Neri
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-all 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=1489188981-23886-1-git-send-email-ricardo.neri-calderon@linux.intel.com \
--to=ricardo.neri-calderon@linux.intel.com \
--cc=chipsec@lists.01.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).