oe-chipsec.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
To: chipsec@lists.01.org
Subject: [PATCH 0/2] Updates for CHIPSEC in LUV
Date: Wed, 05 Jul 2017 17:52:55 -0700	[thread overview]
Message-ID: <1499302377-18722-1-git-send-email-ricardo.neri-calderon@linux.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]

Now that CHIPSEC v1.3.1 is out. It might be good to update LUV to use it.
These two patches deal with this.

While bumping to v1.3.1, one our patches to not include CHIPSEC
documentation needed a trivial update. Also, now CHIPSEC determines which
version of the Linux module it needs to build (32-bit or 64-bit) based on
the kernel running in the host machine. This makes cross-compiling
difficult. Thus, this change was reverted. Instead, we allow setup.py
determine the correct version.

Lastly, the CHIPSEC team has recommended to not run the tool with the -i
option as it may lead to spurious results. This is fixed.

Thanks and BR,
Ricardo

Ricardo Neri (2):
  chipsec: run CHIPSEC without the -i option
  chipsec: bump to v1.3.1

 ...issue-with-building-driver-on-32bit-syste.patch | 43 ++++++++++++++++++++++
 .../chipsec/0001-chipsec-do-not-ship-manual.patch  |  4 +-
 meta-luv/recipes-core/chipsec/chipsec/chipsec      |  2 +-
 meta-luv/recipes-core/chipsec/chipsec_git.bb       |  5 ++-
 4 files changed, 49 insertions(+), 5 deletions(-)
 create mode 100644 meta-luv/recipes-core/chipsec/chipsec/0001-Revert-fix-issue-with-building-driver-on-32bit-syste.patch

-- 
2.7.4


             reply	other threads:[~2017-07-06  0:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06  0:52 Ricardo Neri [this message]
2017-07-06  0:52 ` [PATCH 1/2] chipsec: run CHIPSEC without the -i option Ricardo Neri
2017-07-06  0:52 ` [PATCH 2/2] chipsec: bump to v1.3.1 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=1499302377-18722-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 NNTP newsgroup(s).