oe-chipsec.lists.linux.dev archive mirror
 help / color / mirror / Atom feed

From: Mitchell, Nathaniel P <nathaniel.p.mitchell@intel.com>
To: chipsec@lists.01.org
Subject: Re: chipsec as Buildroot's package
Date: Thu, 23 Sep 2021 21:08:47 +0000	[thread overview]
Message-ID: <CO1PR11MB486607B4E4991BDE8406D194DDA39@CO1PR11MB4866.namprd11.prod.outlook.com> (raw)
In-Reply-To: <817343634.144463.1632305412989@mail.yahoo.com>

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

Hi Tal,

I am not familiar with Buildroot, so I’m not sure if there are limitations around that. For the Makefile, it should work just fine without modifications. You’ll just have to set the KSRC variable to point to the kernel source/header directory you are compiling for.

If you have any questions feel free to post them on the GitHub issues<https://github.com/chipsec/chipsec/issues> page or feel free to reach out to us directly at chipsec(a)intel.com<mailto:chipsec@intel.com>.

Thanks,
Nathaniel


From: Tal Lubko <tallubko@yahoo.com>
Sent: Wednesday, September 22, 2021 03:10 AM
To: chipsec(a)lists.01.org
Subject: [chipsec] chipsec as Buildroot's package

Hi

I'm thinking of adding chipsec to Buildroot.
Are there any limitations for that?

Can the kernel module be built against a kernel that is not the one of the build machine without Makefile modifications?

Thanks,
Tal

[-- Attachment #2: attachment.htm --]
[-- Type: text/html, Size: 42138 bytes --]

next prev parent reply	other threads:[~2021-09-23 21:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <817343634.144463.1632305412989.ref@mail.yahoo.com>
2021-09-22 10:10 ` chipsec as Buildroot's package Tal Lubko
2021-09-23 21:08   ` Mitchell, Nathaniel P [this message]
2021-09-29 15:20     ` Tal Lubko

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=CO1PR11MB486607B4E4991BDE8406D194DDA39@CO1PR11MB4866.namprd11.prod.outlook.com \
    --to=nathaniel.p.mitchell@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

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).