All of lore.kernel.org
 help / color / mirror / Atom feed
* chipsec as Buildroot's package
       [not found] <817343634.144463.1632305412989.ref@mail.yahoo.com>
@ 2021-09-22 10:10 ` Tal Lubko
  2021-09-23 21:08   ` Mitchell, Nathaniel P
  0 siblings, 1 reply; 3+ messages in thread
From: Tal Lubko @ 2021-09-22 10:10 UTC (permalink / raw)
  To: chipsec

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

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: 752 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: chipsec as Buildroot's package
  2021-09-22 10:10 ` chipsec as Buildroot's package Tal Lubko
@ 2021-09-23 21:08   ` Mitchell, Nathaniel P
  2021-09-29 15:20     ` Tal Lubko
  0 siblings, 1 reply; 3+ messages in thread
From: Mitchell, Nathaniel P @ 2021-09-23 21:08 UTC (permalink / raw)
  To: chipsec

[-- 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 --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: chipsec as Buildroot's package
  2021-09-23 21:08   ` Mitchell, Nathaniel P
@ 2021-09-29 15:20     ` Tal Lubko
  0 siblings, 0 replies; 3+ messages in thread
From: Tal Lubko @ 2021-09-29 15:20 UTC (permalink / raw)
  To: chipsec

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

 Hi Nathaniel
Thanks for replying.I've started integrating chipsec into buildroot.
Regards,Tal
    On Friday, September 24, 2021, 12:08:52 AM GMT+3, Mitchell, Nathaniel P <nathaniel.p.mitchell@intel.com> wrote:  
 
 
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 GitHubissues page or feel free to reach out to us directly atchipsec(a)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: 4709 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-09-29 15:20 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [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
2021-09-29 15:20     ` Tal Lubko

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.