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 1/2] chipsec: run CHIPSEC without the -i option
Date: Wed, 05 Jul 2017 17:52:56 -0700	[thread overview]
Message-ID: <1499302377-18722-2-git-send-email-ricardo.neri-calderon@linux.intel.com> (raw)
In-Reply-To: <1499302377-18722-1-git-send-email-ricardo.neri-calderon@linux.intel.com>

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

The CHIPSEC team has advised that running with the -i is not a good idea
as it may lead to invalid results. This option is used mainly for
debugging purposes when it is necessary to ignore the fact that CHIPSEC
does not recognize the platform on which it is running. In most cases
the platform will be known. Also, it is better to simply say that a
given platform is not supported rather than giving spurious results.

Signed-off-by: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
---
 meta-luv/recipes-core/chipsec/chipsec/chipsec | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-luv/recipes-core/chipsec/chipsec/chipsec b/meta-luv/recipes-core/chipsec/chipsec/chipsec
index fa72e45..57b5819 100644
--- a/meta-luv/recipes-core/chipsec/chipsec/chipsec
+++ b/meta-luv/recipes-core/chipsec/chipsec/chipsec
@@ -6,4 +6,4 @@
 
 # The below is replaced with the python site packages path during
 # do_patch().
-python PYTHONPATH/chipsec_main.py -i -v
+python PYTHONPATH/chipsec_main.py -v
-- 
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 [PATCH 0/2] Updates for CHIPSEC in LUV Ricardo Neri
2017-07-06  0:52 ` Ricardo Neri [this message]
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-2-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).