From stappers at stappers.nl  Mon Jun  1 06:10:57 2020
From: stappers at stappers.nl (Geert Stappers)
Date: Mon, 1 Jun 2020 08:10:57 +0200
Subject: [ipxe-devel] ipxe on hyperv windows 2019
In-Reply-To: <CAHhAHvh=-GJrRs+5oqrXRW8yLMM8QwtBjrUF-0=9repMW3yvkQ@mail.gmail.com>
References: <035b01d63784$fd2e9eb0$f78bdc10$@inver.sk>
 <CAHhAHvh=-GJrRs+5oqrXRW8yLMM8QwtBjrUF-0=9repMW3yvkQ@mail.gmail.com>
Message-ID: <20200601061057.ikv3wf6znse2wmrm@gpm.stappers.nl>

On Mon, Jun 01, 2020 at 08:02:56AM +0900, Christian Nilsson wrote:
> On Mon, 1 Jun 2020, 04:52 Kamil Ondrus, <kondrus at inver.sk> wrote:
> > Hello,
> >
> > I?m unable to boot ipxe.iso in hyperv windows 2019 environment.
> >
> > I had no problem to use it in windows 2016, but current version is not
> > working.

What says the changelog?   What says the software vendor?


> > I also tried different host hw, but it seems that problem is not lying
> > here, because it does not work on x3650M3/X5675 CPU (westmere) and also on
> > x3650m4/E5-2680v2 CPU (IvyBridge).
> >
> > I can only confirm that ipxe boot works flawlesly in hypervV 2016.
> >
> >
> > For configuration & test I tried to use steps from here:
> >
> >
> >   https://techdirectarchive.com/2020/01/19/how-to-setup-a-vm-via-pxe-boot-on-a-generation-2-vm-hyper-v/
> >
> >
> >
> > After boot, there?s only only screen:
     
That became https://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200531/78c17ef2/attachment.png


> > I tried to play with VM config (tune different options, like ram, cpu,
> > advanced features etc), but no success after all.
> 
> 
> Test using a valid .usb image instead, especially, try using ipxe.efi
> 

How to get those images?



Regards
Geert Stappers
-- 
Silence is hard to parse

From voltagex at voltagex.org  Sun Jun  7 07:30:30 2020
From: voltagex at voltagex.org (Adam Baxter)
Date: Sun, 07 Jun 2020 17:30:30 +1000
Subject: [ipxe-devel] Sectigo/UserTrust certificates not supported
Message-ID: <1cc16dd4-33c6-41d2-9812-b091db7a82cc@www.fastmail.com>

Hi all,
I'm trying to boot a kernel image from https://ewr.edge.kernel.org/fedora-buffet/fedora/linux/releases/32/Server/x86_64/os/images/pxeboot/vmlinuz via packet.net's iPXE. I can replicate the issue I'm getting with a local build of iPXE from Git.

X509 chain 0xf3fe4 added X509 0xf5da4 "*.edge.kernel.org"
X509 chain 0xf3fe4 added X509 0xfb614 "Sectigo RSA Domain Validation Secure Server CA"
X509 chain 0xf3fe4 added X509 0xfbce4 "USERTrust RSA Certification Authority"
.X509 0xf5da4 "*.edge.kernel.org" is valid (at time 1591514259)
X509 0xf5da4 "*.edge.kernel.org" is not a root certificate
X509 0xf5da4 "*.edge.kernel.org" has no issuer
X509 0xfb614 "Sectigo RSA Domain Validation Secure Server CA" is valid (at time 1591514259)
X509 0xfb614 "Sectigo RSA Domain Validation Secure Server CA" is not a root certificate
X509 0xfb614 "Sectigo RSA Domain Validation Secure Server CA" has no issuer
X509 0xfbce4 "USERTrust RSA Certification Authority" is valid (at time 1591514259)
X509 0xfbce4 "USERTrust RSA Certification Authority" is not a root certificate
X509 0xfbce4 "USERTrust RSA Certification Authority" has no issuer

curl on the box that I built my debug copy of iPXE verifies it OK - I thought they both used the same set of certificates?

* Server certificate:
*  subject: CN=*.edge.kernel.org
*  start date: Mar 16 00:00:00 2020 GMT
*  expire date: Mar 16 23:59:59 2021 GMT
*  subjectAltName: host "ewr.edge.kernel.org" matched cert's "*.edge.kernel.org"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.

My next step will be trying to chain from packet.net's iPXE to my own with these specific certificates in them.

Thanks,
Adam

From stappers at stappers.nl  Sun Jun  7 07:37:05 2020
From: stappers at stappers.nl (Geert Stappers)
Date: Sun, 7 Jun 2020 09:37:05 +0200
Subject: [ipxe-devel] Sectigo/UserTrust certificates not supported
In-Reply-To: <1cc16dd4-33c6-41d2-9812-b091db7a82cc@www.fastmail.com>
References: <1cc16dd4-33c6-41d2-9812-b091db7a82cc@www.fastmail.com>
Message-ID: <20200607073705.odn24yazjpa6grv4@gpm.stappers.nl>

On Sun, Jun 07, 2020 at 05:30:30PM +1000, Adam Baxter wrote:
> Hi all,
> I'm trying to boot a kernel image from https://ewr.edge.kernel.org/fedora-buffet/fedora/linux/releases/32/Server/x86_64/os/images/pxeboot/vmlinuz via packet.net's iPXE. I can replicate the issue I'm getting with a local build of iPXE from Git.
> 
> X509 chain 0xf3fe4 added X509 0xf5da4 "*.edge.kernel.org"
> X509 chain 0xf3fe4 added X509 0xfb614 "Sectigo RSA Domain Validation Secure Server CA"
> X509 chain 0xf3fe4 added X509 0xfbce4 "USERTrust RSA Certification Authority"
> .X509 0xf5da4 "*.edge.kernel.org" is valid (at time 1591514259)
> X509 0xf5da4 "*.edge.kernel.org" is not a root certificate
> X509 0xf5da4 "*.edge.kernel.org" has no issuer
> X509 0xfb614 "Sectigo RSA Domain Validation Secure Server CA" is valid (at time 1591514259)
> X509 0xfb614 "Sectigo RSA Domain Validation Secure Server CA" is not a root certificate
> X509 0xfb614 "Sectigo RSA Domain Validation Secure Server CA" has no issuer
> X509 0xfbce4 "USERTrust RSA Certification Authority" is valid (at time 1591514259)
> X509 0xfbce4 "USERTrust RSA Certification Authority" is not a root certificate
> X509 0xfbce4 "USERTrust RSA Certification Authority" has no issuer
> 
> curl on the box that I built my debug copy of iPXE verifies it OK - I thought they both used the same set of certificates?
> 
> * Server certificate:
> *  subject: CN=*.edge.kernel.org
> *  start date: Mar 16 00:00:00 2020 GMT
> *  expire date: Mar 16 23:59:59 2021 GMT
> *  subjectAltName: host "ewr.edge.kernel.org" matched cert's "*.edge.kernel.org"
> *  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
> *  SSL certificate verify ok.
> 
> My next step will be trying to chain from packet.net's iPXE to my own with these specific certificates in them.

LOL


Regards
Geert Stappers
-- 
Silence is hard to parse

From voltagex at voltagex.org  Sun Jun  7 07:36:56 2020
From: voltagex at voltagex.org (Adam Baxter)
Date: Sun, 07 Jun 2020 17:36:56 +1000
Subject: [ipxe-devel] ECDHE ciphers becoming more of an issue
Message-ID: <b28233cc-58f5-4c37-aed1-1822b9a94942@www.fastmail.com>

While messing around trying to boot Fedora Server via iPXE, I ran into the issue mentioned at https://forum.ipxe.org/showthread.php?tid=11985&highlight=ECDHE on several different hosts. It seems like more and more servers will be deprecating the ciphers that iPXE supports.

Unfortunately, the one person who mentioned adding support to iPXE seems to have disappeared off the face of the earth. 

For completeness I've attached the log from when I ran into this.

I'll add my +1 I guess - can you please add support for more ciphers to iPXE's TLS implementation?

Thanks,
Adam
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: tls-fedora.txt
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200607/7ba37978/attachment.txt>

From voltagex at voltagex.org  Sun Jun  7 07:44:22 2020
From: voltagex at voltagex.org (Adam Baxter)
Date: Sun, 07 Jun 2020 17:44:22 +1000
Subject: [ipxe-devel] Sectigo/UserTrust certificates not supported
In-Reply-To: <20200607073705.odn24yazjpa6grv4@gpm.stappers.nl>
References: <1cc16dd4-33c6-41d2-9812-b091db7a82cc@www.fastmail.com>
 <20200607073705.odn24yazjpa6grv4@gpm.stappers.nl>
Message-ID: <da82811a-d4aa-41e6-afd2-52d2e9b959a5@www.fastmail.com>

On Sun, 7 Jun 2020, at 17:37, Geert Stappers wrote:
> LOL

If I've missed something or done something stupid, I'd like to know what it is. What's funny here?

--Adam

From sebaroth at gmx.de  Sun Jun  7 07:44:09 2020
From: sebaroth at gmx.de (Sebastian Roth)
Date: Sun, 7 Jun 2020 09:44:09 +0200
Subject: [ipxe-devel] Sectigo/UserTrust certificates not supported
In-Reply-To: <da82811a-d4aa-41e6-afd2-52d2e9b959a5@www.fastmail.com>
References: <1cc16dd4-33c6-41d2-9812-b091db7a82cc@www.fastmail.com>
 <20200607073705.odn24yazjpa6grv4@gpm.stappers.nl>
 <da82811a-d4aa-41e6-afd2-52d2e9b959a5@www.fastmail.com>
Message-ID: <945e70dd-7a31-d97d-0688-95d22e0eae97@gmx.de>

On 6/7/20 9:44 AM, Adam Baxter wrote:
> On Sun, 7 Jun 2020, at 17:37, Geert Stappers wrote:
>> LOL
>
> If I've missed something or done something stupid, I'd like to know what it is. What's funny here?
>

You wanna read this:
https://support.sectigo.com/articles/Knowledge/Sectigo-AddTrust-External-CA-Root-Expiring-May-30-2020



From voltagex at voltagex.org  Sun Jun  7 07:49:39 2020
From: voltagex at voltagex.org (Adam Baxter)
Date: Sun, 07 Jun 2020 17:49:39 +1000
Subject: [ipxe-devel] Sectigo/UserTrust certificates not supported
In-Reply-To: <945e70dd-7a31-d97d-0688-95d22e0eae97@gmx.de>
References: <1cc16dd4-33c6-41d2-9812-b091db7a82cc@www.fastmail.com>
 <20200607073705.odn24yazjpa6grv4@gpm.stappers.nl>
 <da82811a-d4aa-41e6-afd2-52d2e9b959a5@www.fastmail.com>
 <945e70dd-7a31-d97d-0688-95d22e0eae97@gmx.de>
Message-ID: <0c65f7c8-0b16-4d6e-9ef1-6c90933fcc97@www.fastmail.com>


On Sun, 7 Jun 2020, at 17:44, Sebastian Roth wrote:
> On 6/7/20 9:44 AM, Adam Baxter wrote:
> > On Sun, 7 Jun 2020, at 17:37, Geert Stappers wrote:
> >> LOL
> >
> > If I've missed something or done something stupid, I'd like to know what it is. What's funny here?
> >
> 
> You wanna read this:
> https://support.sectigo.com/articles/Knowledge/Sectigo-AddTrust-External-CA-Root-Expiring-May-30-2020

No wonder it sounded familiar. Thanks. I did make an attempt to search the list archive before posting this, but I should have Googled the certificate itself.

--Adam

From voltagex at voltagex.org  Sun Jun  7 07:56:17 2020
From: voltagex at voltagex.org (Adam Baxter)
Date: Sun, 07 Jun 2020 17:56:17 +1000
Subject: [ipxe-devel] Sectigo/UserTrust certificates not supported
In-Reply-To: <0c65f7c8-0b16-4d6e-9ef1-6c90933fcc97@www.fastmail.com>
References: <1cc16dd4-33c6-41d2-9812-b091db7a82cc@www.fastmail.com>
 <20200607073705.odn24yazjpa6grv4@gpm.stappers.nl>
 <da82811a-d4aa-41e6-afd2-52d2e9b959a5@www.fastmail.com>
 <945e70dd-7a31-d97d-0688-95d22e0eae97@gmx.de>
 <0c65f7c8-0b16-4d6e-9ef1-6c90933fcc97@www.fastmail.com>
Message-ID: <9ca33d4c-4a34-4a48-9ffe-f973b0978697@www.fastmail.com>

For the benefit of anyone Googling this, I was able to manually trust this chain by doing the following:

ex +'g/BEGIN CERTIFICATE/,/END CERTIFICATE/p' <(echo | openssl s_client -showcerts -connect ewr.edge.kernel.org:443) -scq > ewr.edge.kernel.org.crt

make -j4 bin/ipxe.lkrn CERT=ewr.edge.kernel.org.crt TRUST=ewr.edge.kernel.org.crt DEBUG=x509

--Adam

From stappers at stappers.nl  Sun Jun  7 08:30:26 2020
From: stappers at stappers.nl (Geert Stappers)
Date: Sun, 7 Jun 2020 10:30:26 +0200
Subject: [ipxe-devel] Add certificate Was: X_Y_Z certificates not supported
In-Reply-To: <9ca33d4c-4a34-4a48-9ffe-f973b0978697@www.fastmail.com>
References: <1cc16dd4-33c6-41d2-9812-b091db7a82cc@www.fastmail.com>
 <20200607073705.odn24yazjpa6grv4@gpm.stappers.nl>
 <da82811a-d4aa-41e6-afd2-52d2e9b959a5@www.fastmail.com>
 <945e70dd-7a31-d97d-0688-95d22e0eae97@gmx.de>
 <0c65f7c8-0b16-4d6e-9ef1-6c90933fcc97@www.fastmail.com>
 <9ca33d4c-4a34-4a48-9ffe-f973b0978697@www.fastmail.com>
Message-ID: <20200607083026.rbmhhsrqz2tihy76@gpm.stappers.nl>

On Sun, Jun 07, 2020 at 05:56:17PM +1000, Adam Baxter wrote:
> For the benefit of anyone Googling this,
} For the benefit of anyone websearching this,

> > How to add SSL certificate to the iPXE executable?


> I was able to manually trust this chain by doing the following:
> 
> ex +'g/BEGIN CERTIFICATE/,/END CERTIFICATE/p' <(echo | openssl s_client -showcerts -connect ewr.edge.kernel.org:443) -scq > ewr.edge.kernel.org.crt

Hey, that is a cool way to create  a  .crt  file.


 
> make -j4 bin/ipxe.lkrn CERT=ewr.edge.kernel.org.crt TRUST=ewr.edge.kernel.org.crt DEBUG=x509

make -j$(nproc) bin/ipxe.lkrn CERT=ewr.edge.kernel.org.crt TRUST=ewr.edge.kernel.org.crt

For as much parallel jobs as you have number of processor cores,
without x509 debug output.


> --Adam
> ipxe-devel at lists.ipxe.org

Thanks
 

Regards
Geert Stappers

P.S.
My 'LOL' was planned to get a follow-up by me where I would explain
what is funny.  I'll do a more serious follow-up on
  ECDHE ciphers becoming more of an issue
-- 
Silence is hard to parse

From stappers at stappers.nl  Sun Jun  7 08:47:19 2020
From: stappers at stappers.nl (Geert Stappers)
Date: Sun, 7 Jun 2020 10:47:19 +0200
Subject: [ipxe-devel] ECDHE ciphers becoming more of an issue
In-Reply-To: <b28233cc-58f5-4c37-aed1-1822b9a94942@www.fastmail.com>
References: <b28233cc-58f5-4c37-aed1-1822b9a94942@www.fastmail.com>
Message-ID: <20200607084719.ahr4rizkmcthekim@gpm.stappers.nl>

On Sun, Jun 07, 2020 at 05:36:56PM +1000, Adam Baxter wrote:
> While messing around trying to boot Fedora
> Server via iPXE, I ran into the issue mentioned at
> https://forum.ipxe.org/showthread.php?tid=11985&highlight=ECDHE on
> several different hosts. It seems like more and more servers will be
> deprecating the ciphers that iPXE supports.
> 
> Unfortunately, the one person who mentioned adding support to iPXE
> seems to have disappeared off the face of the earth.

We, O.P. and I, don't known.  I think that skilled people solve
their problem and than move on.
 
> I'll add my +1 I guess - can you please add support for more ciphers
> to iPXE's TLS implementation?

In https://lists.ipxe.org/pipermail/ipxe-devel/2020-June/007077.html is
hinted that "packet.net's iPXE"  has implemented what Original Poster
and many others want. Those who really want it, will explore that.

And the better explorers report back  8^)
 
> Thanks,
> Adam

Regards
Geert Stappers
-- 
Silence is hard to parse

From stappers at stappers.nl  Sun Jun  7 09:10:29 2020
From: stappers at stappers.nl (Geert Stappers)
Date: Sun, 7 Jun 2020 11:10:29 +0200
Subject: [ipxe-devel] Voluntering for updating https://ipxe.org/err/410de1
Message-ID: <20200607091029.d6fyzfbsg52k4zwv@gpm.stappers.nl>

Summary: password reset for wiki user stappers

On Sun, Jun 07, 2020 at 05:36:56PM +1000, Adam Baxter wrote:
      ...
> iPXE 1.20.1+ (g6a6de) -- Open Source Network Boot Firmware -- http://ipxe.org
> Features: DNS HTTP HTTPS iSCSI SRP AoE ELF MBOOT PXE bzImage Menu PXEXT
> Configuring (net0 52:54:00:12:34:56)...... ok
> TLS 0xf02d4 created session
    .... DEBUG=x509  output ....
> Received plaintext data:
> 000f0722 : 02 28                                           : .(              
> TLS 0xf02d4 received fatal alert 40
>  Operation not permitted (http://ipxe.org/410de13c)
> 

I would like to make two changes.

1.
  was unable to negotiate <a>compatible cipher</a> suite
to
  was <a>unable to negotiate compatible cipher</a> suite
the effect is that _unable to negotiate_ also gets link color.

2.
  Enable something on the server side what is supported
to
  Enable something on the server side to show what is supported


I would already have done, if knew my iPXE wiki password.

What should be done to get a wiki password reset?


Regards
Geert Stappers
wiki account name:  stappers
-- 
Silence is hard to parse

From robin at smidsrod.no  Sun Jun  7 20:48:06 2020
From: robin at smidsrod.no (=?UTF-8?Q?Robin_Smidsr=c3=b8d?=)
Date: Sun, 7 Jun 2020 22:48:06 +0200
Subject: [ipxe-devel] Voluntering for updating
 https://ipxe.org/err/410de1
In-Reply-To: <20200607091029.d6fyzfbsg52k4zwv@gpm.stappers.nl>
References: <20200607091029.d6fyzfbsg52k4zwv@gpm.stappers.nl>
Message-ID: <5cfd4551-af6a-172b-d0a6-a830c92aa22b@smidsrod.no>



On 2020-06-07 11:10, Geert Stappers wrote:
> On Sun, Jun 07, 2020 at 05:36:56PM +1000, Adam Baxter wrote:
>>
>> TLS 0xf02d4 created session
>     .... DEBUG=x509  output ....
>> Received plaintext data:
>> 000f0722 : 02 28                                           : .(              
>> TLS 0xf02d4 received fatal alert 40
>>  Operation not permitted (http://ipxe.org/410de13c)
> 
> I would like to make two changes.
> 
> 1.
>   was unable to negotiate <a>compatible cipher</a> suite
> to
>   was <a>unable to negotiate compatible cipher</a> suite
> the effect is that _unable to negotiate_ also gets link color.
> 
> 2.
>   Enable something on the server side what is supported
> to
>   Enable something on the server side to show what is supported

I've made those two changes on https://ipxe.org/err/410de1

-- Robin

From pothana.golla at broadcom.com  Thu Jun 11 17:00:15 2020
From: pothana.golla at broadcom.com (Pothana Golla)
Date: Thu, 11 Jun 2020 22:30:15 +0530
Subject: [ipxe-devel] New Boot files undionly.kpxe and ipxe.efi
Message-ID: <79a1242fe67fdceb8edcafec11777d71@mail.gmail.com>

Hi



I had replaced with latest version of IPXe boot files in TFTPBOOT directory
from https://boot.ipxe.org/  it pick up  the new files but will not pick my
menu.ipxe files . it just loops .

OLD version is IPXE 1.0.0+ (827dd) and new Version IPXE 1.20.1+ (g9ee70)



When we replace the old files it works complete fine .



The new servers Dell R740is not Picking the IPXe may be because of OLD
version  so thought of upgrading IPXE  Please advice all new version of
servers are not installing the IPXE boot it picks file but never loads the
boot menu   OLD version servers are working fine.



Need your kind help



*--------------------------------------------------- *

*Pothana Golla*

[image: cid:image001.png at 01D2464D.E1F79150][image: Description:
Description: diwas's Avatar]

O: 080-46116317 M: 9900214516 H: 08042158021

S1, Wipro Electronic City SEZ,  Doddathogur Village,

Begur Hobli, Bengaluru- 560100, Karnataka , INDIA

P Please consider the environment before printing this email
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200611/db313cb3/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 1610 bytes
Desc: not available
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200611/db313cb3/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.gif
Type: image/gif
Size: 6311 bytes
Desc: not available
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200611/db313cb3/attachment.gif>

From geert.stappers at hendrikx-itc.nl  Thu Jun 11 17:14:15 2020
From: geert.stappers at hendrikx-itc.nl (Geert Stappers)
Date: Thu, 11 Jun 2020 19:14:15 +0200
Subject: [ipxe-devel] New Boot files undionly.kpxe and ipxe.efi
In-Reply-To: <79a1242fe67fdceb8edcafec11777d71@mail.gmail.com>
References: <79a1242fe67fdceb8edcafec11777d71@mail.gmail.com>
Message-ID: <4fc7808e-e834-9d76-51a7-9788ab259390@hendrikx-itc.nl>


On 11-06-2020 19:00, Pothana Golla wrote:
> Hi
> 
> ?
> 
> I had replaced with latest version of IPXe boot files in TFTPBOOT
> directory from https://boot.ipxe.org/ ?it pick up? the new files but
> will not pick my menu.ipxe files . it just loops .

The "it just loops" reminds me
on https://ipxe.org/howto/chainloading#breaking_the_infinite_loop

And while writing this mail
on https://forum.ipxe.org/showthread.php?tid=21808&pid=41982#pid41982
(kudos to Alkis)

> OLD version is IPXE 1.0.0+ (827dd) and new Version IPXE 1.20.1+ (g9ee70)
> 
> ?
> 
> When we replace the old files it works complete fine .
> 
> ?
> 
> The new servers Dell R740is not Picking the IPXe may be because of OLD
> version? so thought of upgrading IPXE? Please advice all new version of
> servers are not installing the IPXE boot it picks file but never loads
> the boot menu ??OLD version servers are working fine.
> 
> ?
> 
> Need your kind help
> 

I'm looking forward to your further contribution to the iPXE project.


> 
> *Pothana Golla*
> 


Regards
Geert Stappers
-- 
Silence is hard to parse

From pothana.golla at broadcom.com  Fri Jun 12 05:50:04 2020
From: pothana.golla at broadcom.com (Pothana Golla)
Date: Fri, 12 Jun 2020 11:20:04 +0530
Subject: [ipxe-devel] New Boot files undionly.kpxe and ipxe.efi
In-Reply-To: <4fc7808e-e834-9d76-51a7-9788ab259390@hendrikx-itc.nl>
References: <79a1242fe67fdceb8edcafec11777d71@mail.gmail.com>
 <4fc7808e-e834-9d76-51a7-9788ab259390@hendrikx-itc.nl>
Message-ID: <de37832d5c9d2887d437926de2190710@mail.gmail.com>

Geert



When I compile  I got this below error and I had download the source thru
git and compiled and ran the below command



ecd.ipxe  file

#!ipxe



  dhcp

  chain http://10.123.56.11/menu.ipxe



[root at localhost src]# make bin/undionly.kpxe EMBED=ecd.ipxe

make: *** No rule to make target 'ecd.ipxe', needed by 'bin/embedded.o'.
Stop.

[root at localhost src]# ls -l bin/undionly.kpxe

-rw-r--r--. 1 root root 67001 Jun 12 01:30 bin/undionly.kpxe

[root at localhost bin]# ls -l ecd.ipxe

-rwxr-xr-x. 1 root root 55 Jun 12 01:35 ecd.ipxe



Please let me know if missing something.



-----Original Message-----
From: ipxe-devel [mailto:ipxe-devel-bounces at lists.ipxe.org] On Behalf Of
Geert Stappers
Sent: Thursday, June 11, 2020 10:44 PM
To: ipxe-devel at lists.ipxe.org
Subject: Re: [ipxe-devel] New Boot files undionly.kpxe and ipxe.efi





On 11-06-2020 19:00, Pothana Golla wrote:

> Hi

>

>

>

> I had replaced with latest version of IPXe boot files in TFTPBOOT

> directory from https://boot.ipxe.org/  it pick up  the new files but

> will not pick my menu.ipxe files . it just loops .



The "it just loops" reminds me

on https://ipxe.org/howto/chainloading#breaking_the_infinite_loop



And while writing this mail

on https://forum.ipxe.org/showthread.php?tid=21808&pid=41982#pid41982

(kudos to Alkis)



> OLD version is IPXE 1.0.0+ (827dd) and new Version IPXE 1.20.1+ (g9ee70)

>

>

>

> When we replace the old files it works complete fine .

>

>

>

> The new servers Dell R740is not Picking the IPXe may be because of OLD

> version  so thought of upgrading IPXE  Please advice all new version of

> servers are not installing the IPXE boot it picks file but never loads

> the boot menu   OLD version servers are working fine.

>

>

>

> Need your kind help

>



I'm looking forward to your further contribution to the iPXE project.





>

> *Pothana Golla*

>





Regards

Geert Stappers

-- 

Silence is hard to parse

_______________________________________________

ipxe-devel mailing list

ipxe-devel at lists.ipxe.org

https://lists.ipxe.org/mailman/listinfo/ipxe-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200612/29bb159a/attachment-0001.htm>

From notifications at github.com  Fri Jun 12 11:30:19 2020
From: notifications at github.com (Jarrod Johnson)
Date: Fri, 12 Jun 2020 04:30:19 -0700
Subject: [ipxe-devel] [ipxe/ipxe] [efi] Restore the TPL to the original
 one (#113)
In-Reply-To: <ipxe/ipxe/pull/113@github.com>
References: <ipxe/ipxe/pull/113@github.com>
Message-ID: <ipxe/ipxe/pull/113/c643222007@github.com>

I'll second this as a problem. Have been testing 'snponly.efi' and I'm not sure the circumstances, but occasionally linux will error about trying to exit boot services, and esxi pretty much always hangs trying to exit boot services (also some 'keyboard errors' are printed early on) when booted from snponly.efi.

This change does seem to sidestep it. I don't know enough to gauge the cleaner approach (to my inexperienced eyes, it would be equivalent to just deleting the TPL lines from the timer function) nor do I have familiarity with the problem that required those lines in the first place.

-- 
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/113#issuecomment-643222007
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200612/b5b39cfc/attachment.htm>

From stuart.tener at bh90210.net  Fri Jun 12 14:48:45 2020
From: stuart.tener at bh90210.net (IT1 Stuart Blake Tener, USNR)
Date: Fri, 12 Jun 2020 10:48:45 -0400
Subject: [ipxe-devel] iPXE and booting ISOs over the network
Message-ID: <20200612104845.Horde.CLKVOsRm6f7YMhdInqNw-6y@mgtmail.com>

List members,

I have done a number of web searches and am interested in gaining some  
insights into what choices I have in implementing iPXE to boot ISO  
files directly (I have read several postings that were 6 to 10 years  
old in this area but no code was really given just oh I did this, I  
did that). I had asked in an IRC channel a while ago (they are so  
useless, people ignoring your question and trying to find a different  
question you should be asking because that is what they can answer),  
and got a bunch of discouraging replies. A huge discussion ensued  
having nothing to do with what I had originally asked, and I abandoned  
obtaining any help there.

I'd like to setup a server (as a virtual machine for portability, but  
would be fine starting as a physical server to decrease complication)  
with a singular purpose of providing iPXE/PXE booting services on my  
home lab network. I'd like to be able to have a directory or that into  
which I can plop an ISO file and then have some sort of menu generated  
on the fly that notices all ISOs in that directory and offers a menu  
that is presented whence someone boots iPXE/PXE via the network. I'd  
also like to have a sub-menu of permanent ISO choices with  
descriptions that can be selected from as well. It is my understanding  
that iPXE/PXE can do this quite easily, but then I was given a ton of  
reasons on the IRC why it would not work so I gave up in frustration  
trying to sort "IRC wheat from IRC chaff".

My thought is to create a private 192.168.100.0/24 network in this  
environment I propose, and for the server to have TFTP, DNS, and  
whatever else is requisite installed there within. I think I'd like to  
use Debian to do it, but am open to whatever distribution people think  
will make this most easiest.

Thanks in advance and I hope everyone stays safe from looting thugs  
and healthy from the pandemic.

Very Respectfully,

Stuart

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200612/f589880c/attachment.htm>

From voltagex at voltagex.org  Fri Jun 12 15:11:47 2020
From: voltagex at voltagex.org (Adam Baxter)
Date: Sat, 13 Jun 2020 01:11:47 +1000
Subject: [ipxe-devel] iPXE and booting ISOs over the network
In-Reply-To: <20200612104845.Horde.CLKVOsRm6f7YMhdInqNw-6y@mgtmail.com>
References: <20200612104845.Horde.CLKVOsRm6f7YMhdInqNw-6y@mgtmail.com>
Message-ID: <c31c67b4-9ac4-4666-b444-0778001f7a43@www.fastmail.com>

On Sat, 13 Jun 2020, at 00:48, IT1 Stuart Blake Tener, USNR wrote:
> 

> List members,
> 
> I have done a number of web searches and am interested in gaining some insights into what choices I have in implementing iPXE to boot ISO files directly (I have read several postings that were 6 to 10 years old in this area but no code was really given just oh I did this, I did that). I had asked in an IRC channel a while ago (they are so useless, people ignoring your question and trying to find a different question you should be asking because that is what they can answer), and got a bunch of discouraging replies. 
> 

Careful there, a few of the people you're calling useless are on this list.

> 

> It is my understanding that iPXE/PXE can do this quite easily, but then I was given a ton of reasons on the IRC why it would not work so I gave up in frustration trying to sort "IRC wheat from IRC chaff".
> 

PXE has nothing to do with your ISOs, PXE is just a standard way of booting a machine from DHCP/TFTP. iPXE adds some nice stuff like HTTP on top of that (so does UEFI sometimes, but now we're really offtopic)

One of the reasons you might have had pushback from IRC is that it's not clear if you really need to boot ISOs (which can be done in a not-quite-reliable way through sanboot/memdisk) or whether you're just needing a whole lot of boot options - which can be done in a supported way by grabbing the distro netboot/pxeboot files and putting them in a directory. Have a look at https://netboot.xyz for this idea taken to an extreme.
> 

> 
> My thought is to create a private 192.168.100.0/24 network in this environment I propose, and for the server to have TFTP, DNS, and whatever else is requisite installed there within. I think I'd like to use Debian to do it, but am open to whatever distribution people think will make this most easiest.
> 

Yes Debian will work - I recommend dnsmasq for this.

So to recap:

* Have a think about whether you really want to boot ISOs through sanboot or memdisk. I mean, it's worth trying just to see what does and doesn't work and the different ways it can break

* Download the pxeboot files for whatever distro and put them in a folder where a tftpd or webserver can get to them. You'll still need a tftp server for the initial loading of iPXE (unless you use iPXE as your virtual NIC firmware or via an iPXE ISO, but I'd stick with tftp for now)


--Adam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200613/54eaea9d/attachment.htm>

From stuart.tener at bh90210.net  Fri Jun 12 16:16:42 2020
From: stuart.tener at bh90210.net (IT1 Stuart Blake Tener, USNR)
Date: Fri, 12 Jun 2020 12:16:42 -0400
Subject: [ipxe-devel] iPXE and booting ISOs over the network
In-Reply-To: <e6be0c8f-556b-4053-80b6-32370348ed7d@www.fastmail.com>
References: <20200612104845.Horde.CLKVOsRm6f7YMhdInqNw-6y@mgtmail.com>
 <e6be0c8f-556b-4053-80b6-32370348ed7d@www.fastmail.com>
Message-ID: <20200612121642.Horde.0IbSiCjpeo7A4mhJG5KAXXw@mgtmail.com>

  Adam,

Perhaps I was a bit inarticulate there, when I said "they are so  
useless", I meant the answers not the people. However, having read  
over what I said I surely can see how the inference you drew was taken  
from that. An email list in my view is far better given each answer is  
individual and replied to in order and must be read and thought about.

Your reply does raise a few good points that I did not speak to in my  
question, so I will clarify and amplify my concerns in pursuance of  
everyone understanding my goals.

1. In general I think whatever solution that I craft should be  
functional for BIOS booting for now, UEFI I will address later once I  
have a BIOS based solution working. Granted, perhaps knowing I would  
do that would be useful to assure I do not go down any rabbit holes  
that will cause a future UEFI solution to mean major redesigns of what  
I do now.

2. I do understand the difference between PXE (a standard) and iPXE  
(software). I realize that PXE has no ability to boot ISOs directly  
(please do correct me if I am wrong). Initially I was thinking to boot  
iPXE via a USB stick, but I like the idea of starting out being able  
to PXE boot iPXE, that is far better. In fact, several servers I have  
(IBM x3650s) have difficulty booting certain types of USB sticks  
(depending as best I understand it on if the USB stick's internal  
firmware presents the USB stick as?a hard drive, floppy or CD-ROM).  
Thus, to PXE boot iPXE I think is really the best choice for me.

If may also ask, what are the differences, advantages and  
disadvantages of booting via memdisk vs sanboot?

Any recommended reading on each that you can offer I will surely go  
and read up on.

3. So, I am interested in being able to boot ISOs, though I do realize  
copying them into directories and such is what many people do.  
However, for me, I prefer to be able to just pull updated ISOs, toss  
them in a directory and have a manner for a menu to be generated  
offering the option of booting any one of say 5 or whatever ISOs in  
that directory.

4. I do like Debian and dnsmasq, but I had a lot of trouble finding  
any really good documents (other than the man pages, which I believe  
are not all that clear as to how to use dnsmasq). Granted, that said,  
I am happy to learn and make use of dnsmasq.

So, let me see if I get what I should be looking to build so far:

Phase 1 testing

5. A virtual machine running debian that has dnsmasq and tftp  
installed. In order to PXE boot iPXE from this system, I would need to  
use the directory method to copy all the files off of the iPXE ISO to  
achieve this?

6. A second virtual machine that will be the system to be booted via  
PXE/iPXE. I could also just feed this VM the iPXE ISO also I realize,  
though PXE booting iPXE is the more clever and interesting solution to  
me.
?
  Thank you to everyone on the list and stay safe from looting thugs  
and healthy from the pandemic.

Very Respectfully,

Stuart
?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200612/960ba08d/attachment.htm>

From nikize at gmail.com  Fri Jun 12 17:06:16 2020
From: nikize at gmail.com (Christian Nilsson)
Date: Fri, 12 Jun 2020 19:06:16 +0200
Subject: [ipxe-devel] iPXE and booting ISOs over the network
In-Reply-To: <20200612104845.Horde.CLKVOsRm6f7YMhdInqNw-6y@mgtmail.com>
References: <20200612104845.Horde.CLKVOsRm6f7YMhdInqNw-6y@mgtmail.com>
Message-ID: <CAHhAHvj0=6dD87jmnY350C8s=qRXOogHneddPXGAYDK5Uvitow@mail.gmail.com>

On Fri, 12 Jun 2020 at 16:49, IT1 Stuart Blake Tener, USNR <
stuart.tener at bh90210.net> wrote:

> List members,
>
> I have done a number of web searches and am interested in gaining some
> insights into what choices I have in implementing iPXE to boot ISO files
> directly (I have read several postings that were 6 to 10 years old in this
> area but no code was really given just oh I did this, I did that). I had
> asked in an IRC channel a while ago (they are so useless, people ignoring
> your question and trying to find a different question you should be asking
> because that is what they can answer), and got a bunch of discouraging
> replies. A huge discussion ensued having nothing to do with what I had
> originally asked, and I abandoned obtaining any help there.
>
> I'd like to setup a server (as a virtual machine for portability, but
> would be fine starting as a physical server to decrease complication) with
> a singular purpose of providing iPXE/PXE booting services on my home lab
> network. I'd like to be able to have a directory or that into which I can
> plop an ISO file and then have some sort of menu generated on the fly that
> notices all ISOs in that directory and offers a menu that is presented
> whence someone boots iPXE/PXE via the network. I'd also like to have a
> sub-menu of permanent ISO choices with descriptions that can be selected
> from as well. It is my understanding that iPXE/PXE can do this quite
> easily, but then I was given a ton of reasons on the IRC why it would not
> work so I gave up in frustration trying to sort "IRC wheat from IRC chaff".
>
> My thought is to create a private 192.168.100.0/24 network in this
> environment I propose, and for the server to have TFTP, DNS, and whatever
> else is requisite installed there within. I think I'd like to use Debian to
> do it, but am open to whatever distribution people think will make this
> most easiest.
>
> Thanks in advance and I hope everyone stays safe from looting thugs and
> healthy from the pandemic.
>
>
> Very Respectfully,
>
> Stuart
>
In the iPXE forum FAQ you have the "answer" to ISO - it is still a valid
answer! (the way PCBIOS INT calls work won't be changed, and EFI has
similar issues in this regards, so there is no reason to think that a 10
year old answer is invalid)
https://forum.ipxe.org/showthread.php?tid=5948&pid=19101#pid19101
See the part about: I'm using memdisk or sanboot to boot an ISO and bootup
fails

It boils down to: booting ISO might work if what is on the ISO does not
start it's own OS (that is keep using the BIOS for all access and iPXE
stays active)
But as soon as you have some other driver that takes control of the NIC
(actually before that but it's an easy way to understand when things happen)
There is no longer any way to access the disk (ISO) and it usually fails.
(There is a few exceptions where this does work, but not many)
So due to the fact that the "boot a ISO over PXE" will fail in most cases,
it is better to pursue an approach that is known to work.

Just to be clear, first start with getting the iPXE demo boot to work the
way you want, people will be happy to help you with that!
Then feel free to try out booting ISOs, you might be lucky that it works,
but please remember that those are special cases.
(it is more likely that you will see isolinux or grub work fine, but when
Linux kernel boots it will fail to find the live system, since "there won't
be" any ISO that it can be found from)

Kind regards
Christian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200612/bc125029/attachment-0001.htm>

From bobgus at rcn.com  Fri Jun 12 17:23:14 2020
From: bobgus at rcn.com (Bob Gustafson)
Date: Fri, 12 Jun 2020 12:23:14 -0500
Subject: [ipxe-devel] iPXE and booting ISOs over the network
In-Reply-To: <20200612104845.Horde.CLKVOsRm6f7YMhdInqNw-6y@mgtmail.com>
References: <20200612104845.Horde.CLKVOsRm6f7YMhdInqNw-6y@mgtmail.com>
Message-ID: <bb11b46f-4936-68f8-7563-89315c6fd349@chidig.com>

Here are a few fragments of an ansible playbook file (simple.yml) which 
does part of what you want to do:

If the command lines are puzzling, you can get more information from 
ansible-doc as in:

$ ansible-doc shell???? or??? $ ansible-doc register??? or? $ 
ansible-doc debug

Ansible commands generally are written by different developers and they 
have individualistic naming conventions.

However, Ansible is a decent tool among a collection of fair to middling 
configuration tools.


# ===== http.server

 ? - name: test running of http.server
 ??? command: pgrep -f http.server
 ??? ignore_errors: yes
 ??? changed_when: false
 ??? register: http_pid # used to restart server if necessary

 ? - name: start simple http server in background w port 8000
 ??? become: no?? # If you do port 80, then need to run as root
#?? shell: cd {{ des_path }}; nohup python -m http.server 80 \
 ??? shell: cd {{ des_path }}; nohup python -m http.server \
 ???????????? --bind 192.168.50.60? &
#??????????? --directory /home/user1/Downloads/Atomic
#???? The cd in front of nohup python sets the home directory
 ??? when: http_pid.stdout == ""

 ? - name: get pid of http.server
 ??? shell: pgrep -f http.server
 ??? ignore_errors: yes
 ??? changed_when: false
 ??? register: http_pid

 ? - debug:
 ????? var: http_pid.stdout

On 6/12/20 9:48 AM, IT1 Stuart Blake Tener, USNR wrote:
>
> List members,
>
> I have done a number of web searches and am interested in gaining some 
> insights into what choices I have in implementing iPXE to boot ISO 
> files directly (I have read several postings that were 6 to 10 years 
> old in this area but no code was really given just oh I did this, I 
> did that). I had asked in an IRC channel a while ago (they are so 
> useless, people ignoring your question and trying to find a different 
> question you should be asking because that is what they can answer), 
> and got a bunch of discouraging replies. A huge discussion ensued 
> having nothing to do with what I had originally asked, and I abandoned 
> obtaining any help there.
>
> I'd like to setup a server (as a virtual machine for portability, but 
> would be fine starting as a physical server to decrease complication) 
> with a singular purpose of providing iPXE/PXE booting services on my 
> home lab network. I'd like to be able to have a directory or that into 
> which I can plop an ISO file and then have some sort of menu generated 
> on the fly that notices all ISOs in that directory and offers a menu 
> that is presented whence someone boots iPXE/PXE via the network. I'd 
> also like to have a sub-menu of permanent ISO choices with 
> descriptions that can be selected from as well. It is my understanding 
> that iPXE/PXE can do this quite easily, but then I was given a ton of 
> reasons on the IRC why it would not work so I gave up in frustration 
> trying to sort "IRC wheat from IRC chaff".
>
> My thought is to create a private 192.168.100.0/24 network in this 
> environment I propose, and for the server to have TFTP, DNS, and 
> whatever else is requisite installed there within. I think I'd like to 
> use Debian to do it, but am open to whatever distribution people think 
> will make this most easiest.
>
> Thanks in advance and I hope everyone stays safe from looting thugs 
> and healthy from the pandemic.
>
>
> Very Respectfully,
>
> Stuart
>
>
>
> _______________________________________________
> ipxe-devel mailing list
> ipxe-devel at lists.ipxe.org
> https://lists.ipxe.org/mailman/listinfo/ipxe-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200612/99b79090/attachment.htm>

From stappers at stappers.nl  Fri Jun 12 19:09:37 2020
From: stappers at stappers.nl (Geert Stappers)
Date: Fri, 12 Jun 2020 21:09:37 +0200
Subject: [ipxe-devel] iPXE and booting ISOs over the network
In-Reply-To: <CAHhAHvj0=6dD87jmnY350C8s=qRXOogHneddPXGAYDK5Uvitow@mail.gmail.com>
References: <20200612104845.Horde.CLKVOsRm6f7YMhdInqNw-6y@mgtmail.com>
 <CAHhAHvj0=6dD87jmnY350C8s=qRXOogHneddPXGAYDK5Uvitow@mail.gmail.com>
Message-ID: <20200612190937.4gfvvnyhsrm4rxuq@gpm.stappers.nl>

On Fri, Jun 12, 2020 at 07:06:16PM +0200, Christian Nilsson wrote:
> On Fri, 12 Jun 2020 at 16:49, IT1 Stuart Blake Tener, USNR wrote:
> 
> > List members,
> >
> > I have done a number of web searches and am interested in gaining some
> > insights into what choices I have in implementing iPXE to boot ISO files
> > directly (I have read several postings that were 6 to 10 years old in this
> > area but no code was really given just oh I did this, I did that). I had
> > asked in an IRC channel a while ago (they are so useless, people ignoring
> > your question and trying to find a different question you should be asking
> > because that is what they can answer), and got a bunch of discouraging
> > replies. A huge discussion ensued having nothing to do with what I had
> > originally asked, and I abandoned obtaining any help there.
> >
> > I'd like to setup a server (as a virtual machine for portability, but
> > would be fine starting as a physical server to decrease complication) with
> > a singular purpose of providing iPXE/PXE booting services on my home lab
> > network. I'd like to be able to have a directory or that into which I can
> > plop an ISO file and then have some sort of menu generated on the fly that
> > notices all ISOs in that directory and offers a menu that is presented
> > whence someone boots iPXE/PXE via the network. I'd also like to have a
> > sub-menu of permanent ISO choices with descriptions that can be selected
> > from as well. It is my understanding that iPXE/PXE can do this quite
> > easily, but then I was given a ton of reasons on the IRC why it would not
> > work so I gave up in frustration trying to sort "IRC wheat from IRC chaff".
> >
> > My thought is to create a private 192.168.100.0/24 network in this
> > environment I propose, and for the server to have TFTP, DNS, and whatever
> > else is requisite installed there within. I think I'd like to use Debian to
> > do it, but am open to whatever distribution people think will make this
> > most easiest.
> >
> > Thanks in advance and I hope everyone stays safe from looting thugs and
> > healthy from the pandemic.
> >
> >
> > Very Respectfully,
> >
> > Stuart
> >
> In the iPXE forum FAQ you have the "answer" to ISO - it is still a valid
> answer! (the way PCBIOS INT calls work won't be changed, and EFI has
> similar issues in this regards, so there is no reason to think that a 10
> year old answer is invalid)
> https://forum.ipxe.org/showthread.php?tid=5948&pid=19101#pid19101
> See the part about: I'm using memdisk or sanboot to boot an ISO and bootup
> fails
> 
> It boils down to: booting ISO might work if what is on the ISO does not
> start it's own OS (that is keep using the BIOS for all access and iPXE
> stays active)
> But as soon as you have some other driver that takes control of the NIC
> (actually before that but it's an easy way to understand when things happen)
> There is no longer any way to access the disk (ISO) and it usually fails.
> (There is a few exceptions where this does work, but not many)
> So due to the fact that the "boot a ISO over PXE" will fail in most cases,
> it is better to pursue an approach that is known to work.
> 
> Just to be clear, first start with getting the iPXE demo boot to work the
> way you want, people will be happy to help you with that!
> Then feel free to try out booting ISOs, you might be lucky that it works,
> but please remember that those are special cases.
> (it is more likely that you will see isolinux or grub work fine, but when
> Linux kernel boots it will fail to find the live system, since "there won't
> be" any ISO that it can be found from)

In https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510
do I read something that I'm now sharing here.  What I understand from it:
* Have a "special" .iso    [0]
* Netboot
* Linux boot parameters for  ramdisk and url=http://server/path/the.iso

The interresting line
 APPEND root=/dev/ram0 ramdisk_size=1500000 ip=dhcp \
 url=http://cdimage.ubuntu.com/ubuntu-server/daily-live/current/focal-live-server-amd64.iso 


I hope it will bring "network booters" and "ISO booters" closer ...

 
> Kind regards
> Christian

Regards
Geert Stappers

Footnote
[0] How special "special" is, is indeed the question
-- 
Silence is hard to parse

From champetier.etienne at gmail.com  Fri Jun 12 19:28:56 2020
From: champetier.etienne at gmail.com (Etienne Champetier)
Date: Fri, 12 Jun 2020 15:28:56 -0400
Subject: [ipxe-devel] appnote/debian_preseed instructions are wrong
Message-ID: <CAOdf3grptyeoiE76_1y7d5D1BDKKH3-4a-zyLkhQsRP3p5y2Hw@mail.gmail.com>

Hello iPXE devs,

The text at https://ipxe.org/appnote/debian_preseed suggests that you
can load a non cpio file,
put it as initrd= param, and that even for EFI mode iPXE will make a
cpio for you.
In my testing (and as discussed here
https://forum.ipxe.org/showthread.php?tid=7830&pid=11948#pid11948 by
others)
this is only working with cpio files when in EFI mode, so 2 questions:
- is this appnote/debian_preseed page just a design document that was
never implemented ?
- can someone update it to mention it's not working, or what options
are needed ?

Thanks a lot
Etienne

PS: I initially subscribed with '+ipxe' in my address so there is 2
time this same email in the moderation queue, please drop them

From stappers at stappers.nl  Fri Jun 12 20:54:58 2020
From: stappers at stappers.nl (Geert Stappers)
Date: Fri, 12 Jun 2020 22:54:58 +0200
Subject: [ipxe-devel] appnote/debian_preseed instructions are wrong
In-Reply-To: <CAOdf3grptyeoiE76_1y7d5D1BDKKH3-4a-zyLkhQsRP3p5y2Hw@mail.gmail.com>
References: <CAOdf3grptyeoiE76_1y7d5D1BDKKH3-4a-zyLkhQsRP3p5y2Hw@mail.gmail.com>
Message-ID: <20200612205458.hzdl6debrd5kd3a4@gpm.stappers.nl>

On Fri, Jun 12, 2020 at 03:28:56PM -0400, Etienne Champetier wrote:
> Hello iPXE devs,
> 
> The text at https://ipxe.org/appnote/debian_preseed suggests that you
> can load a non cpio file,
> put it as initrd= param, and that even for EFI mode iPXE will make a
> cpio for you.
> In my testing (and as discussed here
> https://forum.ipxe.org/showthread.php?tid=7830&pid=11948#pid11948 by
> others)
> this is only working with cpio files when in EFI mode, so 2 questions:
> - is this appnote/debian_preseed page just a design document that was
> never implemented ?

Or something that worked five years ago ...


} - can someone update it

Posting is recieved as reminder on a pending  password request


> - can someone update it to mention it's not working,

That is a recipe / request for getting out-dated information
even more outdated   :-/


> or what options are needed ?

Few days  (few weeks?) ago I saw some  "iPXE initrd advice"
But it is not anymore in IRC scroll buffer

Things I remember
 *  BIOS and  EFI  have different idea how initrd should be provided
 *  "only switch once  initrd  type" 

 
> Thanks a lot

Thank you for poking us


> Etienne

Groeten
Geert Stappers
-- 
Silence is hard to parse

From champetier.etienne at gmail.com  Fri Jun 12 21:42:49 2020
From: champetier.etienne at gmail.com (Etienne Champetier)
Date: Fri, 12 Jun 2020 17:42:49 -0400
Subject: [ipxe-devel] appnote/debian_preseed instructions are wrong
In-Reply-To: <20200612205458.hzdl6debrd5kd3a4@gpm.stappers.nl>
References: <CAOdf3grptyeoiE76_1y7d5D1BDKKH3-4a-zyLkhQsRP3p5y2Hw@mail.gmail.com>
 <20200612205458.hzdl6debrd5kd3a4@gpm.stappers.nl>
Message-ID: <CAOdf3grSxnf51GWbKQsJkCK85Z764aV=481p=A1h=AXSz-WY3g@mail.gmail.com>

Le ven. 12 juin 2020 ? 16:55, Geert Stappers <stappers at stappers.nl> a ?crit :
>
> On Fri, Jun 12, 2020 at 03:28:56PM -0400, Etienne Champetier wrote:
> > Hello iPXE devs,
> >
> > The text at https://ipxe.org/appnote/debian_preseed suggests that you
> > can load a non cpio file,
> > put it as initrd= param, and that even for EFI mode iPXE will make a
> > cpio for you.
> > In my testing (and as discussed here
> > https://forum.ipxe.org/showthread.php?tid=7830&pid=11948#pid11948 by
> > others)
> > this is only working with cpio files when in EFI mode, so 2 questions:
> > - is this appnote/debian_preseed page just a design document that was
> > never implemented ?
>
> Or something that worked five years ago ...

So I lied a bit, my use case is for kickstart file, so maybe it
changes something,
But here is what works for for me, for bios and uefi:
~~~~
kernel ../kernel/vmlinuz initrd=initrd.img initrd=ks.cfg.cpio
inst.ks=file:/ks.cfg ... (more cmdline options here)
initrd ../kernel/initrd.img
initrd ../ks/ks.cfg.cpio
boot
~~~~
Where ks.cfg.cpio is build using "echo ks.cfg | cpio -c -o > ks.cfg.cpio"

Thanks
Etienne

> } - can someone update it
>
> Posting is recieved as reminder on a pending  password request
>
> > - can someone update it to mention it's not working,
>
> That is a recipe / request for getting out-dated information
> even more outdated   :-/
>
> > or what options are needed ?
>
> Few days  (few weeks?) ago I saw some  "iPXE initrd advice"
> But it is not anymore in IRC scroll buffer
>
> Things I remember
>  *  BIOS and  EFI  have different idea how initrd should be provided
>  *  "only switch once  initrd  type"
>
> > Thanks a lot
>
> Thank you for poking us
>
> > Etienne
>
> Groeten
> Geert Stappers
> --
> Silence is hard to parse

From notifications at github.com  Fri Jun 12 22:32:59 2020
From: notifications at github.com (Etienne Champetier)
Date: Fri, 12 Jun 2020 15:32:59 -0700
Subject: [ipxe-devel] [ipxe/ipxe] allow to build ISO image with EFI
 support (ipxe.eiso) (#50)
In-Reply-To: <ipxe/ipxe/pull/50@github.com>
References: <ipxe/ipxe/pull/50@github.com>
Message-ID: <ipxe/ipxe/pull/50/c643508480@github.com>

I have no Makefile skills to help finish this PR, but thanks @eworm-de, it's working perfectly with your example command
(I've tested BIOS/UEFI cdrom/disk under QEMU/KVM)

-- 
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/50#issuecomment-643508480
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200612/b95ac562/attachment.htm>

From stappers at stappers.nl  Sun Jun 14 10:21:29 2020
From: stappers at stappers.nl (Geert Stappers)
Date: Sun, 14 Jun 2020 12:21:29 +0200
Subject: [ipxe-devel] Robustness principle
In-Reply-To: <c31c67b4-9ac4-4666-b444-0778001f7a43@www.fastmail.com>
Message-ID: <20200614102129.w5mmnwkxpdv4jf6z@gpm.stappers.nl>

On Sat, Jun 13, 2020 at 01:11:47AM +1000:
> On Sat, 13 Jun 2020, at 00:48:
> > 
> > List members,
> > 
> > I have done a number of web searches and am interested in gaining
> > some insights into what choices I have in implementing iPXE to boot
> > ISO files directly (I have read several postings that were 6 to 10
> > years old in this area but no code was really given just oh I did
> > this, I did that). I had asked in an IRC channel a while ago (they
> > are so useless, people ignoring your question and trying to find a
> > different question you should be asking because that is what they
> > can answer), and got a bunch of discouraging replies.
> > 
> 
> Careful there,
> a few of the people you're calling useless are on this list.
> 

Qouting https://en.wikipedia.org/wiki/Robustness_principle

} the robustness principle is a design guideline for software:
}
}    Be conservative in what you do,
}    be liberal in what you accept from others


So please keep reporting what could be improved.



Regards
Geert Stappers
-- 
Silence is hard to parse

From stappers at stappers.nl  Sun Jun 14 11:25:13 2020
From: stappers at stappers.nl (Geert Stappers)
Date: Sun, 14 Jun 2020 13:25:13 +0200
Subject: [ipxe-devel] iPXE and booting ISOs over the network
In-Reply-To: <20200612190937.4gfvvnyhsrm4rxuq@gpm.stappers.nl>
References: <20200612104845.Horde.CLKVOsRm6f7YMhdInqNw-6y@mgtmail.com>
 <CAHhAHvj0=6dD87jmnY350C8s=qRXOogHneddPXGAYDK5Uvitow@mail.gmail.com>
 <20200612190937.4gfvvnyhsrm4rxuq@gpm.stappers.nl>
Message-ID: <20200614112513.bxsy2ous26zltbtq@gpm.stappers.nl>

On Fri, Jun 12, 2020 at 09:09:37PM +0200, Geert Stappers wrote:
> On Fri, Jun 12, 2020 at 07:06:16PM +0200, Christian Nilsson wrote:
> > On Fri, 12 Jun 2020 at 16:49, IT1 Stuart Blake Tener, USNR wrote:
> > >  ... what choices I have in implementing iPXE to boot ISO files
> > > directly (I have read several postings that were 6 to 10 years old in this
> > > area but no code was really given just oh I did this, I did that).
> > > ...
> > >
> > > I'd like to setup a server (as a virtual machine for portability, but
> > > would be fine starting as a physical server to decrease complication) with
> > > a singular purpose of providing iPXE/PXE booting services on my home lab
> > > network. I'd like to be able to have a directory or that into which I can
> > > plop an ISO file and then have some sort of menu generated on the fly that
> > > notices all ISOs in that directory and offers a menu that is presented
> > > whence someone boots iPXE/PXE via the network. I'd also like to have a
> > > sub-menu of permanent ISO choices with descriptions that can be selected
> > > from as well. It is my understanding that iPXE/PXE can do this quite
> > > easily, but then I was given a ton of reasons on the IRC why it would not
> > > work so I gave up in frustration trying to sort "IRC wheat from IRC chaff".
> > >
> > > My thought is to create a private 192.168.100.0/24 network in this
> > > environment I propose, and for the server to have TFTP, DNS, and whatever
> > > else is requisite installed there within. I think I'd like to use Debian to
> > > do it, but am open to whatever distribution people think will make this
> > > most easiest.
> > >
> > >
> > In the iPXE forum FAQ you have the "answer" to ISO - it is still a valid
> > answer! (the way PCBIOS INT calls work won't be changed, and EFI has
> > similar issues in this regards, so there is no reason to think that a 10
> > year old answer is invalid)
> > https://forum.ipxe.org/showthread.php?tid=5948&pid=19101#pid19101
> > See the part about: I'm using memdisk or sanboot to boot an ISO and bootup
> > fails
> > 
> > It boils down to: booting ISO might work if what is on the ISO does not
> > start it's own OS (that is keep using the BIOS for all access and iPXE
> > stays active)
> > But as soon as you have some other driver that takes control of the NIC
> > (actually before that but it's an easy way to understand when things happen)
> > There is no longer any way to access the disk (ISO) and it usually fails.
> > (There is a few exceptions where this does work, but not many)
> > So due to the fact that the "boot a ISO over PXE" will fail in most cases,
> > it is better to pursue an approach that is known to work.
> > 
> > Just to be clear,
> > first start with getting the iPXE demo boot to work the way you want,

Please do read that as a strong advice.


> > people will be happy to help you with that!

Please do read that as an offer from a community[2].


> > Then feel free to try out booting ISOs, you might be lucky that it works,
> > but please remember that those are special cases.
> > (it is more likely that you will see isolinux or grub work fine, but when
> > Linux kernel boots it will fail to find the live system, since "there won't
> > be" any ISO that it can be found from)
> 
> In https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510
> do I read something that I'm now sharing here.  What I understand from it:
> * Have a "special" .iso    [0]
> * Netboot
> * Linux boot parameters for  ramdisk and url=http://server/path/the.iso
> 
> The interresting line
>  APPEND root=/dev/ram0 ramdisk_size=1500000 ip=dhcp \
>  url=http://cdimage.ubuntu.com/ubuntu-server/daily-live/current/focal-live-server-amd64.iso 
> 
> 
> I hope it will bring "network booters" and "ISO booters" closer ...
> 
> 
> Regards
> Geert Stappers
> 
> Footnote
> [0] How special "special" is, is indeed the question

The "special" part is in additional content in the initrd.
Those extras are provided by "casper". And "casper" is
a "Initramfs-tools hook".

So far my research for now. Parking here[1] these links

 https://git.launchpad.net/casper/tree/scripts/casper
 http://manpages.ubuntu.com/manpages/focal/man7/casper.7.html

for later ...


Regards
Geert Stappers

Footnote
[1] Here this mailinglist which includes my mailarchive,
    your local mailarchive and our mailarchive
    at https://lists.ipxe.org/pipermail/ipxe-devel/
[2] We all benefit from a healthy community
-- 
Silence is hard to parse

From notifications at github.com  Sun Jun 14 14:35:37 2020
From: notifications at github.com (blitmap)
Date: Sun, 14 Jun 2020 07:35:37 -0700
Subject: [ipxe-devel] [ipxe/pipxe] Raspberry Pi 4? (#2)
In-Reply-To: <ipxe/pipxe/issues/2@github.com>
References: <ipxe/pipxe/issues/2@github.com>
Message-ID: <ipxe/pipxe/issues/2/643775114@github.com>

So this looks promising:

https://rpi4-uefi.dev/v1-13-release-for-pi-4/


-- 
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/pipxe/issues/2#issuecomment-643775114
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200614/ee7d79d2/attachment.htm>

From notifications at github.com  Sun Jun 14 15:03:53 2020
From: notifications at github.com (Rui Lopes)
Date: Sun, 14 Jun 2020 08:03:53 -0700
Subject: [ipxe-devel] [ipxe/pipxe] Raspberry Pi 4? (#2)
In-Reply-To: <ipxe/pipxe/issues/2@github.com>
References: <ipxe/pipxe/issues/2@github.com>
Message-ID: <ipxe/pipxe/issue/2/issue_event/3441766011@github.com>

Closed #2.

-- 
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/pipxe/issues/2#event-3441766011
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200614/5db26fc5/attachment.htm>

From notifications at github.com  Sun Jun 14 15:03:53 2020
From: notifications at github.com (Rui Lopes)
Date: Sun, 14 Jun 2020 08:03:53 -0700
Subject: [ipxe-devel] [ipxe/pipxe] Raspberry Pi 4? (#2)
In-Reply-To: <ipxe/pipxe/issues/2@github.com>
References: <ipxe/pipxe/issues/2@github.com>
Message-ID: <ipxe/pipxe/issues/2/643778848@github.com>

Forgot to update this issue... but I have to report that upstream ipxe (1.20.1) works fine with rpi4-uefi (you need v1.15 for rpi4+8gb support).

FYI, I have a vagrant environment for building ipxe and uefi at https://github.com/rgl/raspberrypi-uefi-edk2-vagrant.

-- 
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/pipxe/issues/2#issuecomment-643778848
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200614/dd18fd8c/attachment.htm>

From notifications at github.com  Wed Jun 17 22:11:33 2020
From: notifications at github.com (realtime-neil)
Date: Wed, 17 Jun 2020 15:11:33 -0700
Subject: [ipxe-devel] [ipxe/ipxe] fix EMBED: don't eagerly assign over
 non-empty value (#115)
Message-ID: <ipxe/ipxe/pull/115@github.com>


You can view, comment on, or merge this pull request online at:

  https://github.com/ipxe/ipxe/pull/115

-- Commit Summary --

  * fix EMBED: don&#39;t eagerly assign over non-empty value

-- File Changes --

    M src/Makefile.housekeeping (2)

-- Patch Links --

https://github.com/ipxe/ipxe/pull/115.patch
https://github.com/ipxe/ipxe/pull/115.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/115
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200617/e9558ab5/attachment.htm>

From notifications at github.com  Wed Jun 17 22:26:41 2020
From: notifications at github.com (Dave Anderson)
Date: Wed, 17 Jun 2020 15:26:41 -0700
Subject: [ipxe-devel] [ipxe/ipxe] fix EMBED: don't eagerly assign over
 non-empty value (#115)
In-Reply-To: <ipxe/ipxe/pull/115@github.com>
References: <ipxe/ipxe/pull/115@github.com>
Message-ID: <ipxe/ipxe/pull/115/review/432819509@github.com>

@danderson approved this pull request.





-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/115#pullrequestreview-432819509
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200617/a52348c5/attachment.htm>

From notifications at github.com  Wed Jun 17 23:44:22 2020
From: notifications at github.com (Michael Brown)
Date: Wed, 17 Jun 2020 16:44:22 -0700
Subject: [ipxe-devel] [ipxe/ipxe] fix EMBED: don't eagerly assign over
 non-empty value (#115)
In-Reply-To: <ipxe/ipxe/pull/115@github.com>
References: <ipxe/ipxe/pull/115@github.com>
Message-ID: <ipxe/ipxe/pull/115/c645683219@github.com>

What problem is this actually solving?  Any variables specified in the `make` command line will override assignments within the Makefile.  Building with `make EMBED=...` works with no problems already.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/115#issuecomment-645683219
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200617/3633f10b/attachment.htm>

From notifications at github.com  Thu Jun 18 01:05:56 2020
From: notifications at github.com (realtime-neil)
Date: Wed, 17 Jun 2020 18:05:56 -0700
Subject: [ipxe-devel] [ipxe/ipxe] fix EMBED: don't eagerly assign over
 non-empty value (#115)
In-Reply-To: <ipxe/ipxe/pull/115@github.com>
References: <ipxe/ipxe/pull/115@github.com>
Message-ID: <ipxe/ipxe/pull/115/c645707277@github.com>

> What problem is this actually solving?

Allow me to demonstrate:

```
$ echo && cat Makefile.bad && echo && EMBED=foobar make -f Makefile.bad && echo && cat Makefile.good && EMBED=foobar make -f Makefile.good 

EMBED := $(EMBEDDED_IMAGE)

.PHONY: all
all:
	echo "EMBEDDED_IMAGE: $(EMBEDDED_IMAGE)"
	echo "EMBED: $(EMBED)"


echo "EMBEDDED_IMAGE: "
EMBEDDED_IMAGE: 
echo "EMBED: "
EMBED: 

EMBED ?= $(EMBEDDED_IMAGE)

.PHONY: all
all:
	echo "EMBEDDED_IMAGE: $(EMBEDDED_IMAGE)"
	echo "EMBED: $(EMBED)"

echo "EMBEDDED_IMAGE: "
EMBEDDED_IMAGE: 
echo "EMBED: foobar"
EMBED: foobar
```

When the definition of the shell variable `EMBED` precedes `make`, `Makefile.good` shows the effect and `Makefile.bad` does not.

> Any variables specified in the `make` command line will override assignments within the Makefile. Building with `make EMBED=...` works with no problems already.

You're not wrong: `make EMBED=...` works. What doesn't work is `EMBED=... make` or any combination of exporting a shell variable for later consumption by a `make` invocation. For reasons that I have yet to dig out of the GNU Make manual, consuming that variable definition only works when it appears as a argument to the `make` command.

Strictly speaking, it's not incorrect to accept only variable assignments that happen to follow the command, but it will confuse others (like me) that assume the `EMBED` should behave like a shell variable when the immediate assignment prevents exactly that.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/115#issuecomment-645707277
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200617/cc0133e1/attachment.htm>

From notifications at github.com  Thu Jun 18 01:24:03 2020
From: notifications at github.com (realtime-neil)
Date: Wed, 17 Jun 2020 18:24:03 -0700
Subject: [ipxe-devel] [ipxe/ipxe] fix EMBED: don't eagerly assign over
 non-empty value (#115)
In-Reply-To: <ipxe/ipxe/pull/115@github.com>
References: <ipxe/ipxe/pull/115@github.com>
Message-ID: <ipxe/ipxe/pull/115/c645712584@github.com>

Found it:

> Any target in the makefile may be specified as a goal (unless it starts with ?-? or contains an ?=?, in which case it will be parsed as a switch or variable definition, respectively).
-- https://www.gnu.org/software/make/manual/make.html#Goals

I make my living on exactly this kind of minutia, but IMHO, one parenthetical clause in the `make` manual is too little reason to flout the principle of least surprise.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/115#issuecomment-645712584
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200617/0973908c/attachment.htm>

From Jeroen.Zwetsloot at nl.thalesgroup.com  Fri Jun 19 10:35:19 2020
From: Jeroen.Zwetsloot at nl.thalesgroup.com (ZWETSLOOT Jeroen)
Date: Fri, 19 Jun 2020 10:35:19 +0000
Subject: [ipxe-devel] ECCN request for iPXE (770a7bd) and wimboot (91be50c)
Message-ID: <2fa46b85cd844e1ea09a57f2df398f47@nl.thalesgroup.com>

Hello,

Thales Nederland BV is considering to use iPXE and wimboot in its own products. In order to do so we have to make sure that they comply with export regulations that apply to our products.

According to our information your software could be subject to the Export Administration Regulations (EAR) when it is either hosted in the United States of America or if any contributor is a resident of the United States of America (for more information on this subject, please consult https://www.bis.doc.gov/).

We therefore kindly ask you if your iPXE (the latest version, as of this writing commit 770a7bd43aa236fe415e0643e2f452e1ad191596) and wimboot (also the latest version, as of this writing commit 91be50c17d4d9f463109d5baafd70f9fdadd86db) software is subject to the EAR and, if so, to provide us with the ECCN that applies to these iPXE and wimboot versions.

Thank you for your time,

Kind regards, on behalf of Thales Nederland BV,

Jeroen Zwetsloot
Software Engineer


------------------------------------------------------------------------------------------------------------
Disclaimer:

If you are not the intended recipient of this email, please notify the sender and
delete it.
Any unauthorized copying, disclosure or distribution of this email or its
attachment(s) is forbidden.
Thales Nederland BV will not accept liability for any damage caused by this email or
its attachment(s).
Thales Nederland BV is seated in Hengelo and is registered at the Chamber of
Commerce under number 06061578.
------------------------------------------------------------------------------------------------------------


From nikize at gmail.com  Fri Jun 19 11:29:37 2020
From: nikize at gmail.com (Christian Nilsson)
Date: Fri, 19 Jun 2020 13:29:37 +0200
Subject: [ipxe-devel] ECCN request for iPXE (770a7bd) and wimboot
 (91be50c)
In-Reply-To: <2fa46b85cd844e1ea09a57f2df398f47@nl.thalesgroup.com>
References: <2fa46b85cd844e1ea09a57f2df398f47@nl.thalesgroup.com>
Message-ID: <CAHhAHvi3-kFJPw4n+V92PVy9uZ40sgLobhVbJDr-JznmR+fQ+A@mail.gmail.com>

On Fri, 19 Jun 2020 at 12:35, ZWETSLOOT Jeroen <
Jeroen.Zwetsloot at nl.thalesgroup.com> wrote:

> Hello,
>
> Thales Nederland BV is considering to use iPXE and wimboot in its own
> products. In order to do so we have to make sure that they comply with
> export regulations that apply to our products.
>
> According to our information your software could be subject to the Export
> Administration Regulations (EAR) when it is either hosted in the United
> States of America or if any contributor is a resident of the United States
> of America (for more information on this subject, please consult
> https://www.bis.doc.gov/).
>
> We therefore kindly ask you if your iPXE (the latest version, as of this
> writing commit 770a7bd43aa236fe415e0643e2f452e1ad191596) and wimboot (also
> the latest version, as of this writing commit
> 91be50c17d4d9f463109d5baafd70f9fdadd86db) software is subject to the EAR
> and, if so, to provide us with the ECCN that applies to these iPXE and
> wimboot versions.
>
> Thank you for your time,
>
> Kind regards, on behalf of Thales Nederland BV,
>
> Jeroen Zwetsloot
> Software Engineer
>
>
>
> ------------------------------------------------------------------------------------------------------------
> Disclaimer:
>
> If you are not the intended recipient of this email, please notify the
> sender and
> delete it.
> Any unauthorized copying, disclosure or distribution of this email or its
> attachment(s) is forbidden.
> Thales Nederland BV will not accept liability for any damage caused by
> this email or
> its attachment(s).
> Thales Nederland BV is seated in Hengelo and is registered at the Chamber
> of
> Commerce under number 06061578.
>
> ------------------------------------------------------------------------------------------------------------
>
> _______________________________________________
> ipxe-devel mailing list
> ipxe-devel at lists.ipxe.org
> https://lists.ipxe.org/mailman/listinfo/ipxe-devel


Hi,

Some information from a long time user of iPXE. Do note that the usual
IANAL applies.
You might be interested in reading https://ipxe.org/licensing
Also: https://github.com/ipxe/ipxe/blob/master/COPYING.UBDL

Since this is an open source project it is unlikely that you will get help
with ECCN (but not impossible, see the support page on ipxe.org)

Even if all development have been made in/from the U.K. and the source was
primarily hosted in the U.K.
The sources are now mainly hosted on GitHub. - this seem to make U.S. think
that they have the right to control this (IMHO that is ludicrous)
But it seems that you should be able to just "fire of an email" yourself to
get this, see
https://www.bis.doc.gov/index.php/policy-guidance/encryption/1-encryption-items-not-subject-to-the-ear


"EAR Open Source" might be a helpful searchterm here.

Kind regards
Christian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200619/98dd221b/attachment.htm>

From aj.shirvani at gmail.com  Mon Jun 22 07:09:29 2020
From: aj.shirvani at gmail.com (Ali Shirvani)
Date: Mon, 22 Jun 2020 11:39:29 +0430
Subject: [ipxe-devel] Couldn't find attached devices with sandev_find
Message-ID: <CAFQ97XGoX72a0ACne_VRLG6q4oZgb2zqto_gxNY5oc+U_OXnaw@mail.gmail.com>

Hi all,
I tried to list the number of attached hard disks in sanboot command. I
modified sanboot_cmd.c file and I can get the number of attached drives
with:

get_real ( num_drives, BDA_SEG, BDA_NUM_DRIVES );

But when I try to get the san_device structure of each drive with
`sandev_find` I couldn't get any san_device, and the `sandev_find`
always returns NULL.

I also should note that, `iPXE> sanboot -n -d 0x82` boots the system
successfully from the third hard device.

Would you please help me how should I proceed?

Regards,
Ali
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200622/288dd8b1/attachment.htm>

From notifications at github.com  Tue Jun 23 16:17:48 2020
From: notifications at github.com (Christopher)
Date: Tue, 23 Jun 2020 09:17:48 -0700
Subject: [ipxe-devel] [ipxe/ipxe] [tls] Add support for fragmented tls
 handshake packets (#116)
Message-ID: <ipxe/ipxe/pull/116@github.com>

iPXE currently does not support TLS connections with large certificate chains because it can not handle TLS handshake record fragmentation. So i implemented the detection and reassembling of fragmented packets. Please let me know if there is any problem with the code or the way i handled the reassembling.

I appreciate your comments and feedback.
You can view, comment on, or merge this pull request online at:

  https://github.com/ipxe/ipxe/pull/116

-- Commit Summary --

  * [tls] Add support for fragmented tls handshake packets

-- File Changes --

    M src/include/ipxe/tls.h (5)
    M src/net/tls.c (55)

-- Patch Links --

https://github.com/ipxe/ipxe/pull/116.patch
https://github.com/ipxe/ipxe/pull/116.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/116
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200623/6206ae8e/attachment.htm>

From mcb30 at ipxe.org  Sat Jun 27 20:42:57 2020
From: mcb30 at ipxe.org (Michael Brown)
Date: Sat, 27 Jun 2020 21:42:57 +0100
Subject: [ipxe-devel] [PATCH] [build] Be explicit about -fcommon
 compiler directive
In-Reply-To: <20200506210302.277343-1-brogers@suse.com>
References: <20200506210302.277343-1-brogers@suse.com>
Message-ID: <6c9ccc8f-fb61-9195-4757-0952d6b7bcb1@ipxe.org>

On 06/05/2020 22:03, Bruce Rogers wrote:
> gcc10 switched default behavior from -fcommon to -fno-common. Since
> "__shared" relies on the legacy behavior, explicitly specify it.
> 
> Signed-off-by: Bruce Rogers <brogers at suse.com>

Applied, with modification to just specify -fcommon unconditionally 
(since even older gcc versions will accept it):

   http://github.com/ipxe/ipxe/commit/f982a7129

Thanks,

Michael

From aj.shirvani at gmail.com  Sun Jun 28 04:35:12 2020
From: aj.shirvani at gmail.com (Ali Shirvani)
Date: Sun, 28 Jun 2020 09:05:12 +0430
Subject: [ipxe-devel] Could not find hard disk in EFI mode
Message-ID: <CAFQ97XEBT7bx2XWDXEOWmAQ1OHNMoQUp=VarPLw0aJFLnyQ6CA@mail.gmail.com>

Hi all,
I created a bootable USB with ipxe.efi. I can boot my system in UEFI mode
and that USB stick, but when I try to sanboot from hard drive I got
following error:

`Boot from SAN device 0x80 failed, no such device`

Also I added some print statements to the `efi_block.c` and I found that in
`efi_block_boot` sandev_find could not find the device.

But I can boot my system with `sanboot` when I use BIOS instead of UEFI.
Would you please help me to fix this?

Regards,
Ali
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200628/bbb41efd/attachment.htm>

From aj.shirvani at gmail.com  Sun Jun 28 04:50:09 2020
From: aj.shirvani at gmail.com (Ali Shirvani)
Date: Sun, 28 Jun 2020 09:20:09 +0430
Subject: [ipxe-devel] Could not find hard disk in EFI mode
In-Reply-To: <CAFQ97XEBT7bx2XWDXEOWmAQ1OHNMoQUp=VarPLw0aJFLnyQ6CA@mail.gmail.com>
References: <CAFQ97XEBT7bx2XWDXEOWmAQ1OHNMoQUp=VarPLw0aJFLnyQ6CA@mail.gmail.com>
Message-ID: <CAFQ97XFeBrG24Pd8CFCh=gbTVD-=pLKFwcmso3zrF6a6GisD+g@mail.gmail.com>

I found this thread with similar problem:
https://forum.ipxe.org/showthread.php?tid=10915




On Sun, Jun 28, 2020 at 9:05 AM Ali Shirvani <aj.shirvani at gmail.com> wrote:

> Hi all,
> I created a bootable USB with ipxe.efi. I can boot my system in UEFI mode
> and that USB stick, but when I try to sanboot from hard drive I got
> following error:
>
> `Boot from SAN device 0x80 failed, no such device`
>
> Also I added some print statements to the `efi_block.c` and I found that
> in `efi_block_boot` sandev_find could not find the device.
>
> But I can boot my system with `sanboot` when I use BIOS instead of UEFI.
> Would you please help me to fix this?
>
> Regards,
> Ali
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200628/8c2d6df4/attachment.htm>

From nikize at gmail.com  Sun Jun 28 04:51:30 2020
From: nikize at gmail.com (Christian Nilsson)
Date: Sun, 28 Jun 2020 13:51:30 +0900
Subject: [ipxe-devel] Could not find hard disk in EFI mode
In-Reply-To: <CAFQ97XEBT7bx2XWDXEOWmAQ1OHNMoQUp=VarPLw0aJFLnyQ6CA@mail.gmail.com>
References: <CAFQ97XEBT7bx2XWDXEOWmAQ1OHNMoQUp=VarPLw0aJFLnyQ6CA@mail.gmail.com>
Message-ID: <CAHhAHviSCDT7osEd+Ojn7UgfVj5x8mtk222h7rBHH=Nv4iHDgQ@mail.gmail.com>

On Sun, 28 Jun 2020, 13:35 Ali Shirvani, <aj.shirvani at gmail.com> wrote:

> Hi all,
> I created a bootable USB with ipxe.efi. I can boot my system in UEFI mode
> and that USB stick, but when I try to sanboot from hard drive I got
> following error:
>
> `Boot from SAN device 0x80 failed, no such device`
>
> Also I added some print statements to the `efi_block.c` and I found that
> in `efi_block_boot` sandev_find could not find the device.
>
> But I can boot my system with `sanboot` when I use BIOS instead of UEFI.
> Would you please help me to fix this?
>
> Regards,
> Ali
> _______________________________________________
> ipxe-devel mailing list
> ipxe-devel at lists.ipxe.org
> https://lists.ipxe.org/mailman/listinfo/ipxe-devel



Hi
iPXE is made for booting over network, the hack to use sanboot to boot from
disk is not something that you should take as "supported".
Use exit instead, see the FAQ in the forum as well.



>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200628/b2275a59/attachment.htm>

From aj.shirvani at gmail.com  Sun Jun 28 04:55:56 2020
From: aj.shirvani at gmail.com (Ali Shirvani)
Date: Sun, 28 Jun 2020 09:25:56 +0430
Subject: [ipxe-devel] Could not find hard disk in EFI mode
In-Reply-To: <CAHhAHviSCDT7osEd+Ojn7UgfVj5x8mtk222h7rBHH=Nv4iHDgQ@mail.gmail.com>
References: <CAFQ97XEBT7bx2XWDXEOWmAQ1OHNMoQUp=VarPLw0aJFLnyQ6CA@mail.gmail.com>
 <CAHhAHviSCDT7osEd+Ojn7UgfVj5x8mtk222h7rBHH=Nv4iHDgQ@mail.gmail.com>
Message-ID: <CAFQ97XGU1UBDp-DUEEQ0xB60tHq=VLDBnSVWewcmpUB0+k+bbQ@mail.gmail.com>

Thanks Christian, I tried `exit` and `exit 1` both return to the UEFI menu
of my system.

On Sun, Jun 28, 2020 at 9:21 AM Christian Nilsson <nikize at gmail.com> wrote:

>
>
> On Sun, 28 Jun 2020, 13:35 Ali Shirvani, <aj.shirvani at gmail.com> wrote:
>
>> Hi all,
>> I created a bootable USB with ipxe.efi. I can boot my system in UEFI mode
>> and that USB stick, but when I try to sanboot from hard drive I got
>> following error:
>>
>> `Boot from SAN device 0x80 failed, no such device`
>>
>> Also I added some print statements to the `efi_block.c` and I found that
>> in `efi_block_boot` sandev_find could not find the device.
>>
>> But I can boot my system with `sanboot` when I use BIOS instead of UEFI.
>> Would you please help me to fix this?
>>
>> Regards,
>> Ali
>> _______________________________________________
>> ipxe-devel mailing list
>> ipxe-devel at lists.ipxe.org
>> https://lists.ipxe.org/mailman/listinfo/ipxe-devel
>
>
>
> Hi
> iPXE is made for booting over network, the hack to use sanboot to boot
> from disk is not something that you should take as "supported".
> Use exit instead, see the FAQ in the forum as well.
>
>
>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200628/ffaedc9f/attachment.htm>

From stappers at stappers.nl  Sun Jun 28 05:26:10 2020
From: stappers at stappers.nl (Geert Stappers)
Date: Sun, 28 Jun 2020 07:26:10 +0200
Subject: [ipxe-devel] Could not find hard disk in EFI mode
In-Reply-To: <CAFQ97XGU1UBDp-DUEEQ0xB60tHq=VLDBnSVWewcmpUB0+k+bbQ@mail.gmail.com>
References: <CAFQ97XEBT7bx2XWDXEOWmAQ1OHNMoQUp=VarPLw0aJFLnyQ6CA@mail.gmail.com>
 <CAHhAHviSCDT7osEd+Ojn7UgfVj5x8mtk222h7rBHH=Nv4iHDgQ@mail.gmail.com>
 <CAFQ97XGU1UBDp-DUEEQ0xB60tHq=VLDBnSVWewcmpUB0+k+bbQ@mail.gmail.com>
Message-ID: <20200628052610.jb6wg6yot3hbgtje@gpm.stappers.nl>


[0]

On Sun, Jun 28, 2020 at 09:25:56AM +0430, Ali Shirvani wrote:
> On Sun, Jun 28, 2020 at 9:21 AM Christian Nilsson <nikize at gmail.com> wrote:
> > On Sun, 28 Jun 2020, 13:35 Ali Shirvani, <aj.shirvani at gmail.com> wrote:
> >
> >> Hi all,
> >> I created a bootable USB with ipxe.efi. I can boot my system in UEFI mode
> >> and that USB stick, but when I try to sanboot from hard drive I got
> >> following error:
> >>
> >> `Boot from SAN device 0x80 failed, no such device`
> >>
> >> Also I added some print statements to the `efi_block.c` and I found that
> >> in `efi_block_boot` sandev_find could not find the device.
> >>
> >> But I can boot my system with `sanboot` when I use BIOS instead of UEFI.
> >> Would you please help me to fix this?
> >>
> >> Regards,
> >> Ali
> >
> > Hi
> > iPXE is made for booting over network, the hack to use sanboot to boot
> > from disk is not something that you should take as "supported".
> > Use exit instead, see the FAQ in the forum as well.
> >
> 
> Thanks Christian, I tried `exit` and `exit 1` both return to the UEFI menu
> of my system.
 
And that is good?  In case it isn't,  tell more about your situation.
And karma bonuspoints for explicite reporting "I got a SANboot"


Regards
Geert Stappers


Footnote
[0] It is a good thing that you show that you understand
    concepts as "timezones" and "mailinglists" by replying
    below the previous text.
-- 
Silence is hard to parse

From nikize at gmail.com  Sun Jun 28 06:02:00 2020
From: nikize at gmail.com (Christian Nilsson)
Date: Sun, 28 Jun 2020 15:02:00 +0900
Subject: [ipxe-devel] Could not find hard disk in EFI mode
In-Reply-To: <CAFQ97XGU1UBDp-DUEEQ0xB60tHq=VLDBnSVWewcmpUB0+k+bbQ@mail.gmail.com>
References: <CAFQ97XEBT7bx2XWDXEOWmAQ1OHNMoQUp=VarPLw0aJFLnyQ6CA@mail.gmail.com>
 <CAHhAHviSCDT7osEd+Ojn7UgfVj5x8mtk222h7rBHH=Nv4iHDgQ@mail.gmail.com>
 <CAFQ97XGU1UBDp-DUEEQ0xB60tHq=VLDBnSVWewcmpUB0+k+bbQ@mail.gmail.com>
Message-ID: <CAHhAHvg6nbrXZpa_tgq76+QbZx9SLSvuR=-7X+crGjUZx_RhLQ@mail.gmail.com>

To bad your firmware don't handle that case well.

As workaround you could start grub or other bootloader that supports hard
drives.
You can even load and start grub from disk via file:// in efi mode, it does
require some more hacks tho. But you will figure those out along the way :)

On Sun, 28 Jun 2020, 13:56 Ali Shirvani, <aj.shirvani at gmail.com> wrote:

> Thanks Christian, I tried `exit` and `exit 1` both return to the UEFI menu
> of my system.
>
> On Sun, Jun 28, 2020 at 9:21 AM Christian Nilsson <nikize at gmail.com>
> wrote:
>
>>
>>
>> On Sun, 28 Jun 2020, 13:35 Ali Shirvani, <aj.shirvani at gmail.com> wrote:
>>
>>> Hi all,
>>> I created a bootable USB with ipxe.efi. I can boot my system in UEFI
>>> mode and that USB stick, but when I try to sanboot from hard drive I got
>>> following error:
>>>
>>> `Boot from SAN device 0x80 failed, no such device`
>>>
>>> Also I added some print statements to the `efi_block.c` and I found that
>>> in `efi_block_boot` sandev_find could not find the device.
>>>
>>> But I can boot my system with `sanboot` when I use BIOS instead of UEFI.
>>> Would you please help me to fix this?
>>>
>>> Regards,
>>> Ali
>>> _______________________________________________
>>> ipxe-devel mailing list
>>> ipxe-devel at lists.ipxe.org
>>> https://lists.ipxe.org/mailman/listinfo/ipxe-devel
>>
>>
>>
>> Hi
>> iPXE is made for booting over network, the hack to use sanboot to boot
>> from disk is not something that you should take as "supported".
>> Use exit instead, see the FAQ in the forum as well.
>>
>>
>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200628/72b06b93/attachment-0001.htm>

From miesi at mail.com  Mon Jun 29 05:56:28 2020
From: miesi at mail.com (Thomas Mieslinger)
Date: Mon, 29 Jun 2020 07:56:28 +0200
Subject: [ipxe-devel] Could not find hard disk in EFI mode
In-Reply-To: <CAFQ97XFeBrG24Pd8CFCh=gbTVD-=pLKFwcmso3zrF6a6GisD+g@mail.gmail.com>
References: <CAFQ97XEBT7bx2XWDXEOWmAQ1OHNMoQUp=VarPLw0aJFLnyQ6CA@mail.gmail.com>
 <CAFQ97XFeBrG24Pd8CFCh=gbTVD-=pLKFwcmso3zrF6a6GisD+g@mail.gmail.com>
Message-ID: <694be59c-0ee5-e67e-83c1-73915ad40b82@mail.com>

On 6/28/20 6:50 AM, Ali Shirvani wrote:
> I found this thread with similar problem:
> https://forum.ipxe.org/showthread.php?tid=10915

When I first tested ipxe/EFI on Dell 13G/14G Servers I had similar
looking issues.

It turned out that I did not correctly ended all layers of running ipxe
scripts. As soon as I fixed the logic bug it started working.

I noticed that it takes long for Dell EFI to move on to the next boot
target after Network Boot exited.

Cheers

Thomas

From notifications at github.com  Mon Jun 29 11:17:35 2020
From: notifications at github.com (Michael Brown)
Date: Mon, 29 Jun 2020 04:17:35 -0700
Subject: [ipxe-devel] [ipxe/ipxe] [efi] Restore the TPL to the original
 one (#113)
In-Reply-To: <ipxe/ipxe/pull/113@github.com>
References: <ipxe/ipxe/pull/113@github.com>
Message-ID: <ipxe/ipxe/pull/113/c651045296@github.com>

Neither the code change nor the commit message make any sense to me, sorry.

Instead of the commit, could you please provide a way to reproduce your observed problem?

Thanks.

-- 
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/113#issuecomment-651045296
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200629/c9e90e81/attachment.htm>

From notifications at github.com  Tue Jun 30 02:23:35 2020
From: notifications at github.com (He Huang)
Date: Mon, 29 Jun 2020 19:23:35 -0700
Subject: [ipxe-devel] [ipxe/ipxe] [efi] Restore the TPL to the original
 one (#113)
In-Reply-To: <ipxe/ipxe/pull/113@github.com>
References: <ipxe/ipxe/pull/113@github.com>
Message-ID: <ipxe/ipxe/pull/113/c651480996@github.com>

You need an AMI based UEFI BIOS, and then power on and boot ESXi 6.5U3 through UEFI iPXE and without norts =1 as the parameter of boot loader.

-- 
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/113#issuecomment-651480996
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200629/37db7179/attachment.htm>

From notifications at github.com  Tue Jun 30 02:42:45 2020
From: notifications at github.com (He Huang)
Date: Mon, 29 Jun 2020 19:42:45 -0700
Subject: [ipxe-devel] [ipxe/ipxe] [efi] Restore the TPL to the original
 one (#113)
In-Reply-To: <ipxe/ipxe/pull/113@github.com>
References: <ipxe/ipxe/pull/113@github.com>
Message-ID: <ipxe/ipxe/pull/113/c651487810@github.com>

And it also does not make sense to me that iPXE always restore to TPL_CALLBACK, even the original TPL is TPL_APPLICATION.
If you do not have env to reproduct this issue, would you print log to monitor the original/old TPL? Then you will see, it is not always the TPL_CALLBACK.
Please read UEFI spec about the "TPL Restriction".

-- 
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/113#issuecomment-651487810
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200629/4908c0a2/attachment.htm>

From notifications at github.com  Tue Jun 30 03:47:06 2020
From: notifications at github.com (JamesWangAmiTw)
Date: Mon, 29 Jun 2020 20:47:06 -0700
Subject: [ipxe-devel] [ipxe/ipxe] [efi] Restore the TPL to the original
 one (#113)
In-Reply-To: <ipxe/ipxe/pull/113@github.com>
References: <ipxe/ipxe/pull/113@github.com>
Message-ID: <ipxe/ipxe/pull/113/c651511355@github.com>

@mcb30,

It raised TPL to TPL_CALLBACK and never restored it.  NotifyFunction of EVT_SIGNAL_EXIT_BOOT_SERVICES will not be called because of that while booting.

The change of efi_currticks() causing this problem was from [[efi] Run at TPL_CALLBACK to protect against UEFI timers](https://github.com/ipxe/ipxe/commit/c89a446cf09f30a121ae21d91f4a1aa071044084#diff-8abaf825db412e28b0c57b0f8947ed23).

I am wondering if you can find another way to work around the [problem](https://github.com/ipxe/ipxe/commit/c89a446cf09f30a121ae21d91f4a1aa071044084#diff-8abaf825db412e28b0c57b0f8947ed23) or restore TPL before ExitBootService?


-- 
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/113#issuecomment-651511355
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200629/82d6ca5a/attachment.htm>

From notifications at github.com  Tue Jun 30 11:00:27 2020
From: notifications at github.com (Michael Brown)
Date: Tue, 30 Jun 2020 04:00:27 -0700
Subject: [ipxe-devel] [ipxe/ipxe] [efi] Restore the TPL to the original
 one (#113)
In-Reply-To: <ipxe/ipxe/pull/113@github.com>
References: <ipxe/ipxe/pull/113@github.com>
Message-ID: <ipxe/ipxe/pull/113/c651721586@github.com>

@huanghe4 The expected mechanism (as documented in [[efi] Run at TPL_CALLBACK to protect against UEFI timers](https://github.com/ipxe/ipxe/commit/c89a446cf09f30a121ae21d91f4a1aa071044084#diff-8abaf825db412e28b0c57b0f8947ed23) is that iPXE code runs at TPL_CALLBACK almost all of the time, in order to overcome fundamental design flaws in the UEFI specification.

iPXE will record the TPL at which it was entered and will restore this TPL before exiting.  This applies to all externally callable entry points, such as the SNP API (see e.g. the matched RaiseTPL/RestoreTPL calls in `efi_snp_get_status()`).

This also applies to the overall code path from initial invocation through to ExitBootServices, although this is less immediately obvious due to the exchange of responsibilities between different UEFI components.  The expected sequence of events is:
* An application-level entry point such as `_efi_start()` or `efi_snp_load_file()` (as opposed to an API-level entry point such as `efi_snp_get_status()`) will call `efi_snp_claim()` to claim exclusive ownership of the network devices for iPXE (and so to prevent packet loss due to other UEFI code attempting to poll the network).
* This call to `efi_snp_claim()` will record the original TPL in `efi_snp_old_tpl` and will raise to TPL_CALLBACK.
* Before executing an image (such as an OS kernel), iPXE will call `efi_snp_release()`
* This call to `efi_snp_release()` will restore the original TPL as recorded in `efi_snp_old_tpl`
* iPXE then invokes the OS kernel via `StartImage()`.  At this point, the TPL is whatever TPL was recorded when iPXE was started, which should be TPL_APPLICATION.
* The OS kernel is responsible for calling `ExitBootServices()`

I have added debug code to iPXE to dump the TPL prior to calling `StartImage()` and (via the `efi_wrap` mechanism) to dump the TPL at the point that the OS kernel invokes `ExitBootServices()`.  I have tested with both an iPXE EFI ROM and with a chainloaded `snponly.efi`.  In both cases and at both debug points the TPL was TPL_APPLICATION, as expected.

Is it possible that the AMI BIOS is erroneously starting iPXE at TPL_CALLBACK, thereby causing `efi_snp_old_tpl` to end up containing TPL_CALLBACK rather than TPL_APPLICATION?

Michael


-- 
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/113#issuecomment-651721586
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200630/2bdb5447/attachment.htm>

From notifications at github.com  Tue Jun 30 12:13:03 2020
From: notifications at github.com (Jarrod Johnson)
Date: Tue, 30 Jun 2020 05:13:03 -0700
Subject: [ipxe-devel] [ipxe/ipxe] [efi] Restore the TPL to the original
 one (#113)
In-Reply-To: <ipxe/ipxe/pull/113@github.com>
References: <ipxe/ipxe/pull/113@github.com>
Message-ID: <ipxe/ipxe/pull/113/c651752678@github.com>

I can confirm same behavior, using bootx64.efi from esxi 7, the following produces the same behavior he reported:
#!ipxe
chain boot/efi/boot/bootx64.efi -c /path/to/boot.cfg also call efi_snp_release() of course.

> iPXE then invokes the OS kernel via StartImage(). At this point, the TPL is whatever TPL was recorded when iPXE was started, which should be TPL_APPLICATION.

Well, iPXE code may still run at this point. In fact it explicitly does for iPXE booted ESXi boot loader. efi_download.c has three functions that may be called by the loaded efi executable. At the very least they call efi_download_start. I don't know the full flow of the code, but I am wondering if efi_download_start use of intf_init or xfer_open before calling efi_snp_claim causes a RaiseTPL before efi_snp_claim stores the old TPL causing it to erroneously 'save' iPXE induced TPL_CALLBACK as the 'old' TPL? I am a bit preoccupied today, but I'd be tempted to modify efi_download_start() to call claim earlier and call efi_snp_release() on error. I'm a bit rusty and I botched even a simple change so I'm not sure.

If my naive guess happens to be in the ballpark, it doesn't explain a *seeming* improvement in our Linux boot testing, where iPXE DL protocol is not used and we also were seeing errors on kernel trying to exit boot servicing that happened *sometimes*. However this was a little fuzzier so it may not be completely accurate.



-- 
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/113#issuecomment-651752678
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200630/68d29623/attachment.htm>

From notifications at github.com  Tue Jun 30 13:58:09 2020
From: notifications at github.com (Jarrod Johnson)
Date: Tue, 30 Jun 2020 06:58:09 -0700
Subject: [ipxe-devel] [ipxe/ipxe] [efi] Restore the TPL to the original
 one (#113)
In-Reply-To: <ipxe/ipxe/pull/113@github.com>
References: <ipxe/ipxe/pull/113@github.com>
Message-ID: <ipxe/ipxe/pull/113/c651808383@github.com>

Alternatively, if efi_snp_old_tpl seems to have been previously assigned, perhaps don't save a new 'old' value?

-- 
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/113#issuecomment-651808383
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200630/6af2918c/attachment.htm>

From notifications at github.com  Tue Jun 30 15:53:35 2020
From: notifications at github.com (Michael Brown)
Date: Tue, 30 Jun 2020 08:53:35 -0700
Subject: [ipxe-devel] [ipxe/ipxe] [efi] Don't use timers to gather
 entropy, if EFI_RNG_PROTOCOL is available (#101)
In-Reply-To: <ipxe/ipxe/pull/101@github.com>
References: <ipxe/ipxe/pull/101@github.com>
Message-ID: <ipxe/ipxe/pull/101/issue_event/3498470480@github.com>

Closed #101.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/101#event-3498470480
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200630/c0589150/attachment.htm>

From notifications at github.com  Tue Jun 30 15:53:35 2020
From: notifications at github.com (Michael Brown)
Date: Tue, 30 Jun 2020 08:53:35 -0700
Subject: [ipxe-devel] [ipxe/ipxe] [efi] Don't use timers to gather
 entropy, if EFI_RNG_PROTOCOL is available (#101)
In-Reply-To: <ipxe/ipxe/pull/101@github.com>
References: <ipxe/ipxe/pull/101@github.com>
Message-ID: <ipxe/ipxe/pull/101/c651884103@github.com>

Thank you for the detailed report.  Have fixed the underlying root cause in commit 2ae5d4338

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/101#issuecomment-651884103
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200630/48d96741/attachment.htm>

From notifications at github.com  Tue Jun 30 16:33:57 2020
From: notifications at github.com (Pankaj Bansal)
Date: Tue, 30 Jun 2020 09:33:57 -0700
Subject: [ipxe-devel] [ipxe/ipxe] implement api to convert pci address to
 host address (#117)
Message-ID: <ipxe/ipxe/pull/117@github.com>

The PCI device address may not be same as host address (CPU view address)
To read/write directly to PCI device&#39;s BARs (without using
EFI_PCI_ROOT_BRIDGE_IO_PROTOCOL.Mem.Read() and
EFI_PCI_ROOT_BRIDGE_IO_PROTOCOL.Mem.Write()) we need to convert PCI
device address to host address.

The UEFI specifications 2.7 provide a method to translate the PCI device
address to host address and vice versa.

device address = host address + translation offset

EFI_PCI_ROOT_BRIDGE_IO_PROTOCOL.Configuration() method can provide us with
the translation offset and host address range.

Using this we can convert the PCI device address to host address.

Signed-off-by: Pankaj Bansal &lt;pankaj.bansal at nxp.com&gt;
You can view, comment on, or merge this pull request online at:

  https://github.com/ipxe/ipxe/pull/117

-- Commit Summary --

  * implement api to convert pci address to host address

-- File Changes --

    M src/include/ipxe/pci_io.h (10)
    M src/interface/efi/efi_pci.c (60)

-- Patch Links --

https://github.com/ipxe/ipxe/pull/117.patch
https://github.com/ipxe/ipxe/pull/117.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/117
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200630/dc6690be/attachment.htm>

From notifications at github.com  Tue Jun 30 20:28:18 2020
From: notifications at github.com (jw14812)
Date: Tue, 30 Jun 2020 13:28:18 -0700
Subject: [ipxe-devel] [ipxe/ipxe] Bnxt (#118)
Message-ID: <ipxe/ipxe/pull/118@github.com>


You can view, comment on, or merge this pull request online at:

  https://github.com/ipxe/ipxe/pull/118

-- Commit Summary --

  * [bnxt] Add driver support for Broadcom NetXtreme-E Adapters
  * [bnxt] Add PCI_ROM entries for 5881x family device IDs
  * [bnxt] Update VLAN insertion logic
  * [bnxt] Use short command format where required
  * [bnxt] Update chip initialization sequence
  * [bnxt] Update device ID values
  * [bnxt] Restrict issuing HWRM_BACKING_STORE command for VF devices
  * [bnxt] Fix loopback test with VLAN
  * [bnxt] Use hexadecimal values in PCI_ROM entries

-- File Changes --

    M src/Makefile (1)
    A src/drivers/net/bnxt/bnxt.c (2285)
    A src/drivers/net/bnxt/bnxt.h (979)
    A src/drivers/net/bnxt/bnxt_dbg.h (677)
    A src/drivers/net/bnxt/bnxt_hsi.h (10337)

-- Patch Links --

https://github.com/ipxe/ipxe/pull/118.patch
https://github.com/ipxe/ipxe/pull/118.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/ipxe/pull/118
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200630/50a50db1/attachment-0001.htm>

From champetier.etienne at gmail.com  Thu Jun  4 02:24:35 2020
From: champetier.etienne at gmail.com (Etienne Champetier)
Date: Thu, 04 Jun 2020 02:24:35 -0000
Subject: [ipxe-devel] appnote/debian_preseed instructions are wrong
Message-ID: <CAOdf3gpmX99RMO6=c=D+FsXXvP9XfkLt14M14XwLywfaRTy+RQ@mail.gmail.com>

Hello iPXE devs,

The text at https://ipxe.org/appnote/debian_preseed suggests that you
can load a non cpio file,
put it as initrd= param, and that even for EFI mode iPXE will make a
cpio for you.
In my testing (and as discussed here
https://forum.ipxe.org/showthread.php?tid=7830&pid=11948#pid11948 by
others)
this is only working with cpio files when in EFI mode, so 2 questions:
- is this appnote/debian_preseed page just a design document that was
never implemented ?
- can someone update it to mention it's not working, or what options
are needed ?

Thanks a lot
Etienne

From shawn_ward at byu.edu  Thu Jun  4 22:33:21 2020
From: shawn_ward at byu.edu (Shawn Ward)
Date: Thu, 04 Jun 2020 22:33:21 -0000
Subject: [ipxe-devel] Network driver issues
Message-ID: <CY4PR08MB3559289252481BD438A0F3D8F2890@CY4PR08MB3559.namprd08.prod.outlook.com>

Hello!

I am attempting to pxeboot a Proliant m710x Server cartridge in our HP Moonshot 1500 chassis. However, when it runs dhcp I get a 'waiting for link up on net0 and net1 timeout with an unknown (http://ipxe.org/err/1a086194).'

Then when I try to manually assign ip settings and then call boot.php and pass my mac with it I get 'Network unreachable (http://ipxe.org/err/280a60)'

My guess is that it doesn't support our network cards.

Our network cards are the Mellanox Connect-X3 Pro adapters.

My question is, do you know of any documentation available on how to add network adapter drivers into ipxe so that we can pxeboot our cartridges?

We are using ipxe in correlation with Fog. If you happen to know how to create a bootable thumb drive so I can get into the Fog OS that would also be helpful. I was unable to get it to work with their documentation. I tried to contact someone with FOG but I had to create an account first and their account creation portion is broken right now.

Thanks.

Shawn Ward
Windows Systems Admin
CAEDM - College of Engineering
801-422-8120

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200604/255dca23/attachment-0001.htm>

From notifications at github.com  Mon Jun  8 17:05:32 2020
From: notifications at github.com (mek)
Date: Mon, 08 Jun 2020 17:05:32 -0000
Subject: [ipxe-devel] [ipxe/pipxe] iSCSI (#5)
Message-ID: <ipxe/pipxe/issues/5@github.com>

Hi!

I tried it on a Rpi3b, but I did not manage to boot from iSCSI.

What are the pre requirements to be configured to get this to work?

I configured the iqn but the next menu "add attempt" just returns
a page which only shows "MAC Selection" on the top and "Esx=Exit" 
on the bottom but nothings to select.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/ipxe/pipxe/issues/5
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200608/b394e4c8/attachment-0001.htm>

From ksitzes at amperecomputing.com  Wed Jun 10 20:36:20 2020
From: ksitzes at amperecomputing.com (Kevin Sitzes)
Date: Wed, 10 Jun 2020 20:36:20 -0000
Subject: [ipxe-devel] Compiling Wimboot for ARM64
Message-ID: <MWHPR01MB3312464F5D56B3E33BBC5E7AA2830@MWHPR01MB3312.prod.exchangelabs.com>

Greetings!

Thanks for your contributions to iPXE! Curious if you have any documentation or details on compiling wimboot for arm64 ?   The iPXE portion worked perfectly I'm just attempting to chainload winPE on Arm64. Any assistance is much appreciated.

Cheers,
Kevin Sitzes


CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and contains information that is confidential and proprietary to Ampere Computing or its subsidiaries. It is to be used solely for the purpose of furthering the parties' business relationship. Any review, copying, or distribution of this email (or any attachments thereto) is strictly prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete the original and any copies of this email and any attachments thereto.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200610/28cde83a/attachment-0001.htm>

From vladislav.valtchev at gmail.com  Thu Jun 11 10:54:52 2020
From: vladislav.valtchev at gmail.com (Vladislav K. Valtchev)
Date: Thu, 11 Jun 2020 10:54:52 -0000
Subject: [ipxe-devel] [bug] Unbalanced UEFI TPL manipulations in iPXE with
 DOWNLOAD_PROTO_HTTPS=1
References: <159183106698.6395.17435419830579655737.malone@chaenomeles.canonical.com>
Message-ID: <5edcb9de59026ca39be6055be4fcbd222a806356.camel@gmail.com>

Hello,
I'd like to forward here a bug-report that's currently on
launchpad.net: https://bugs.launchpad.net/ipxe/+bug/1882671

Originally it seemed a QEMU bug, but later the investigation done by
Laszlo Ersek (Red Hat) plus some tests of mine confirmed that the
bug is in the 82540em.efi iPXE driver for QEMU.

He was even able to
bisect the problem and get d8c500b7945e
("[efi] Drop to TPL_APPLICATION when gathering entropy",
2018-03-12) as first bad commit.

I hope this is the right mailing list for reporting this bug
and that the information provided so far will be helpful.

Thanks,
Vladislav K. Valtchev

P.S.
I'm not sure whether to add 1882671 at bugs.launchpad.net
in CC or not. In doubt, I omitted it. Please, add it to CC
if you believe its the right thing to do.

-------- Forwarded Message --------
From: Laszlo Ersek (Red Hat) <1882671 at bugs.launchpad.net>
Reply-To: Bug 1882671 <1882671 at bugs.launchpad.net>
To: vladislav.valtchev at gmail.com
Subject: [Bug 1882671] Re: qemu-system-x86_64 (ver 4.2) stuck at boot 
with OVMF bios
Date: Wed, 10 Jun 2020 23:17:46 -0000

Hi Vlad,

the ipxe-qemu package in Ubuntu (1.0.0+git-20190109.133f4c4-0ubuntu3) is
built with DOWNLOAD_PROTO_HTTPS enabled (in "src/config/general.h").
According to the Ubuntu changelog, this is a new feature added in
"1.0.0+git-20190109.133f4c4-0ubuntu1".

With DOWNLOAD_PROTO_HTTPS enabled, I can reproduce the issue locally,
with iPXE built from source at git commit 133f4c4 (which you report the
issue for), and also at current iPXE master (9ee70fb95bc2).

The issue does not reproduce (with DOWNLOAD_PROTO_HTTPS enabled) at
commit fbe8c52d. This suggests the problem should be bisectable.

If I disable DOWNLOAD_PROTO_HTTPS, then the problem goes away even at
133f4c4 (i.e., the issue is masked).

I've used current edk2 master to test with (14c7ed8b51f6).

Viewed at 133f4c4:

The DOWNLOAD_PROTO_HTTPS feature test macro seems to result in iPXE
attempting to gather entropy. (Likely for setting up TLS connections.)
For entropy gathering, iPXE seems to use an EFI timer, and to measure
jitter across one timer tick. In this, iPXE plays some tricks with the
UEFI TPL (Task Priority Level).

In general, iPXE seems to want to run at TPL_CALLBACK most of the time,
to mask the timer interrupt in most code locations, and drops down to
TPL_APPLICATION only when it actively wants a timer callback (for the
jitter collection, see above).

When the iPXE driver is launched, the StartImage() UEFI boot service
takes a note of the current TPL. It is TPL_APPLICATION (value 4). Then
iPXE seems to perform the above trickery with TPL_CALLBACK & entropy
collection. Finally, after installing EfiDriverBindingProtocol and
EfiComponentName2Protocol, the iPXE driver exits (as expected from a
UEFI driver model driver -- the entry point function is only supposed to
perform some setup steps & install some protocol interfaces). At this
point, StartImage() verifies whether the TPL has been restored to the
same as it was before launching the driver.

Unfortunately, something about the TPL manipulations in iPXE is
unbalanced, because I see the following TPL changes:

- raise: APPLICATION (4) -> CALLBACK (8)
- raise: CALLBACK (8) -> NOTIFY (16)
- raise: NOTIFY (16) -> NOTIFY (16)
- restore: NOTIFY (16) -> NOTIFY (16)
- restore: NOTIFY (16) -> CALLBACK (8)

Note that the final "restore: CALLBACK (8) -> APPLICATION (4)"
transition is missing, before iPXE exits. This is what StartImage()
catches and reports with the failed ASSERT().

So, as I mentioned, the problem is bisectable. Here's the bisection log:

> git bisect start
> # bad: [9ee70fb95bc266885ff88be228b044a2bb226eeb] [efi] Attempt to
> # connect our driver directly if ConnectController fails
> git bisect bad 9ee70fb95bc266885ff88be228b044a2bb226eeb
> # bad: [133f4c47baef6002b2ccb4904a035cda2303c6e5] [build] Handle
> # R_X86_64_PLT32 from binutils 2.31
> git bisect bad 133f4c47baef6002b2ccb4904a035cda2303c6e5
> # good: [fbe8c52d0d9cdb3d6f5fe8be8edab54618becc1f] [ena] Fix spurious
> # uninitialised variable warning on older versions of gcc
> git bisect good fbe8c52d0d9cdb3d6f5fe8be8edab54618becc1f
> # bad: [bc85368cdd311fe68ffcf251e7e8e90c14f8a9dc] [librm] Ensure that
> # inline code symbols are unique
> git bisect bad bc85368cdd311fe68ffcf251e7e8e90c14f8a9dc
> # bad: [0778418e29ea16fc897fc5b6e497054f5ba86ebd] [golan] Do not
> # assume all devices are identical
> git bisect bad 0778418e29ea16fc897fc5b6e497054f5ba86ebd
> # good: [f672a27b34220865b403df519593f382859559e0] [efi] Raise TPL
> # within EFI_USB_IO_PROTOCOL entry points
> git bisect good f672a27b34220865b403df519593f382859559e0
> # bad: [d8c500b7945e57023dde5bd0be2b0e40963315d9] [efi] Drop to
> # TPL_APPLICATION when gathering entropy
> git bisect bad d8c500b7945e57023dde5bd0be2b0e40963315d9
> # good: [c84f9d67272beaed98f98bf308471df16340a3be] [iscsi] Parse IPv6
> # address in root path
> git bisect good c84f9d67272beaed98f98bf308471df16340a3be
> # first bad commit: [d8c500b7945e57023dde5bd0be2b0e40963315d9] [efi]
> # Drop to TPL_APPLICATION when gathering entropy

The bisection fingers d8c500b7945e ("[efi] Drop to TPL_APPLICATION when
 gathering entropy", 2018-03-12) as first bad commit.

Feel free to report this problem on the upstream iPXE mailing list.

Regarding Ubuntu downstream, you should be able to work around this
issue by #undef-ing DOWNLOAD_PROTO_HTTPS again, in
"src/config/general.h" -- *minimally* in the CONFIG=qemu build(s). That
is, in the ipxe-qemu subpackage.

That's because in a CONFIG=qemu build, you totally don't need (or even
*use*) the iPXE HTTPS infrastructure (the entropy gathering that trips
the ASSERT seems spurious to me, with CONFIG=qemu). With CONFIG=qemu,
iPXE provides the UEFI SNP (Simple Network Protocol) interface on top of
the e1000 NIC, and the crypto stuff (if any) is done by the platform
firmware (edk2 / OVMF).



** Project changed: qemu => ipxe

** Package changed: qemu (Ubuntu) => ipxe (Ubuntu)

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1882671

Title:
  qemu-system-x86_64 (ver 4.2) stuck at boot with OVMF bios

Status in iPXE:
  New
Status in ipxe package in Ubuntu:
  Confirmed

Bug description:
  The version of QEMU (4.2.0) packaged for Ubuntu 20.04 hangs
  indefinitely at boot if an OVMF bios is used. This happens ONLY with
  qemu-system-x86_64. qemu-system-i386 works fine with the latest ia32
  OVMF bios.

  NOTE[1]: the same identical OVMF bios works fine on QEMU 2.x packaged with Ubuntu 18.04.
  NOTE[2]: reproducing the fatal bug requires *no* operating system:

     qemu-system-x86_64 -bios OVMF-pure-efi.fd

  On its window QEMU gets stuck at the very first stage:
     "Guest has not initialized the display (yet)."

  NOTE[3]: QEMU gets stuck no matter if KVM is used or not.

  NOTE[4]: By adding the `-d int` option it is possible to observe that
  QEMU is, apparently, stuck in an endless loop of interrupts. For the
  first few seconds, registers' values vary quickly, but at some point
  they reach a final value, while the interrupt counter increments:

    2568: v=68 e=0000 i=0 cpl=0 IP=0038:0000000007f1d225 pc=0000000007f1d225 SP=0030:0000000007f0c8d0 env->regs[R_EAX]=0000000000000000
  RAX=0000000000000000 RBX=0000000007f0c920 RCX=0000000000000000 RDX=0000000000000001
  RSI=0000000006d18798 RDI=0000000000008664 RBP=0000000000000000 RSP=0000000007f0c8d0
  R8 =0000000000000001 R9 =0000000000000089 R10=0000000000000000 R11=0000000007f2c987
  R12=0000000000000000 R13=0000000000000000 R14=0000000007087901 R15=0000000000000000
  RIP=0000000007f1d225 RFL=00000246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
  ES =0030 0000000000000000 ffffffff 00cf9300 DPL=0 DS   [-WA]
  CS =0038 0000000000000000 ffffffff 00af9a00 DPL=0 CS64 [-R-]
  SS =0030 0000000000000000 ffffffff 00cf9300 DPL=0 DS   [-WA]
  DS =0030 0000000000000000 ffffffff 00cf9300 DPL=0 DS   [-WA]
  FS =0030 0000000000000000 ffffffff 00cf9300 DPL=0 DS   [-WA]
  GS =0030 0000000000000000 ffffffff 00cf9300 DPL=0 DS   [-WA]
  LDT=0000 0000000000000000 0000ffff 00008200 DPL=0 LDT
  TR =0000 0000000000000000 0000ffff 00008b00 DPL=0 TSS64-busy
  GDT=     00000000079eea98 00000047
  IDT=     000000000758f018 00000fff
  CR0=80010033 CR2=0000000000000000 CR3=0000000007c01000 CR4=00000668
  DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 
  DR6=00000000ffff0ff0 DR7=0000000000000400
  CCS=0000000000000044 CCD=0000000000000000 CCO=EFLAGS  
  EFER=0000000000000d00

  
  NOTE[5]: Just to better help the investigation of the bug, I'd like to remark that the issue is NOT caused by an endless loop of triple-faults. I tried with -d cpu_reset and there is NO such loop. No triple fault whatsoever.

  NOTE[6]: The OVMF version used for the test has been downloaded from:
  https://www.kraxel.org/repos/jenkins/edk2/edk2.git-ovmf-x64-0-20200515.1398.g6ff7c838d0.noarch.rpm

  but the issue is the same with older OVMF versions as well.

  
  Please take a look at it, as the bug is NOT a corner case. QEMU 4.2.0 cannot boot with an UEFI firmware (OVMF) while virtualizing a x86_64 machine AT ALL.

  Thank you very much,
  Vladislav K. Valtchev

To manage notifications about this bug go to:
https://bugs.launchpad.net/ipxe/+bug/1882671/+subscriptions


From JamesWang at ami.com.tw  Fri Jun 12 06:16:06 2020
From: JamesWang at ami.com.tw (=?big5?B?SmFtZXNXYW5nIFuk/a5hqfpd?=)
Date: Fri, 12 Jun 2020 06:16:06 -0000
Subject: [ipxe-devel] UEFI's TPL is not restored caused EXSi 6.5U3 boot
 failed with iPXE
Message-ID: <CC2D91CF91568A4998E8DB825C949D944E39C130@TW-MBX2.tw.megatrends.com>

Hi,

We encountered a CPU exception problem while booting EXSi 6.5U3 with iPXE.  It is caused by system is running on TPL_CALLBACK level.

In Efi_timer.c: efi_currticks()
    if ( efi_shutdown_in_progress ) {
        efi_jiffies++;
    } else {
        bs->RestoreTPL ( TPL_APPLICATION );
        bs->RaiseTPL ( TPL_CALLBACK );
    }


It raised TPL to TPL_CALLBACK and never restored it.  NotifyFunction of EVT_SIGNAL_EXIT_BOOT_SERVICES will not be called because of that while booting.

The change of efi_currticks() causing this problem was from [efi] Run at TPL_CALLBACK to protect against UEFI timers<https://github.com/ipxe/ipxe/commit/c89a446cf09f30a121ae21d91f4a1aa071044084#diff-8abaf825db412e28b0c57b0f8947ed23>.

Can you find another way to work around the problem or restore TPL before ExitBootService?
CONFIDENTIAL INFORMATION : The information contained in this message may be confidential and proprietary to American Megatrends, Inc. This communication is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. Please promptly notify the sender by reply e-mail or by telephone at 886-2-2516-8887, and then delete or destroy all copies of the transmission.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200612/b71bc12b/attachment-0001.htm>

From marc.hillesheim at theflexible.de  Thu Jun 18 07:19:38 2020
From: marc.hillesheim at theflexible.de (marc.hillesheim at theflexible.de)
Date: Thu, 18 Jun 2020 07:19:38 -0000
Subject: [ipxe-devel] iPXE fails to configure interface with intel i211
 gigabit lan in uefi mode
Message-ID: <b2519f0d6fd24a0ba7074faf59be9d7b@EXDAG34-1.EXCHANGE.INT>

Hi guys,

i implemented ipxe and it is perfectly working (latest git version). With legacy mode (bios) all is working like a charm.
In uefi mode the config of interface fails. Also extending timouts for dhcp doesn't change anything - i can't reach a ipxe shell to check manually.
A test with a vm in vmware workstation in uefi mode is working fine and booting correctly.

Lan chip is intel i211 (onboard) and it's vendor and device are 8086:1539

As i noticed some fixes for intel chips in the past i think this chip has a similar bug.

Thx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200618/ee79c549/attachment-0001.htm>

From scott-xu at msn.com  Fri Jun 19 17:22:51 2020
From: scott-xu at msn.com (Xu Scott)
Date: Fri, 19 Jun 2020 17:22:51 -0000
Subject: [ipxe-devel] UEFI ExitBootServices
Message-ID: <CH2PR06MB6535339667C6E8A9127263BA9A980@CH2PR06MB6535.namprd06.prod.outlook.com>

Is it able to call UEFI ExitBootServices in ipxe.efi? I ask because I want to turn on UEFI Secure Boot while not want to verify the Linux kernel by firmware . I want to verify the Linux kernel by iPXE?s imgtrust.

Regards,
Scott
???? iPhone

From gongjq2 at lenovo.com  Sun Jun 21 07:03:59 2020
From: gongjq2 at lenovo.com (Gavin JQ2 Gong)
Date: Sun, 21 Jun 2020 07:03:59 -0000
Subject: [ipxe-devel] Install centos 7.5 by broadcom 57416 OCP-NIC issue
Message-ID: <SG2PR03MB30035C244E5653DA30B27F978C960@SG2PR03MB3003.apcprd03.prod.outlook.com>

Hi

I want to install centos 7.5 by ipxe, don?t succeed,  have set PXE boot in 57416 NIC.  my server with nic?broadcom 57416?venderid : deviceid=14e4:16ee?,  maybe because nic driver. Can you help add 57416 driver into ipxe tg3.c?  thanks

When intall os by ipxe? get error details:

[cid:image002.jpg at 01D647DD.25E1D530]

At ipxe commandl ine  net0 status is close

[cid:image007.jpg at 01D647DD.25E1D530]

I can open net0?but when I undrug net cable?the staus is still open?At the same time?when I run dhcp?net0 status will close?

[cid:image009.jpg at 01D647DD.25E1D530]

Gavin,gong  gongjiaq

T?18611184662
E?gongjq2 at lenovo.com<mailto:gongjq2 at lenovo.com>
Lenovo HQ West, Building 1, No.10 Courtyard Xibeiwang East Rd, Haidian District, Beijing, China 100094
???????????10??1??

[cid:image010.png at 01D647DD.25E1D530]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200621/eb856b8e/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 51550 bytes
Desc: image002.jpg
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200621/eb856b8e/attachment-0003.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.jpg
Type: image/jpeg
Size: 71175 bytes
Desc: image007.jpg
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200621/eb856b8e/attachment-0004.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.jpg
Type: image/jpeg
Size: 100319 bytes
Desc: image009.jpg
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200621/eb856b8e/attachment-0005.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.png
Type: image/png
Size: 8892 bytes
Desc: image010.png
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200621/eb856b8e/attachment-0001.png>

From sadhanalankalapalli at gmail.com  Tue Jun 23 04:59:35 2020
From: sadhanalankalapalli at gmail.com (Sadhana)
Date: Tue, 23 Jun 2020 04:59:35 -0000
Subject: [ipxe-devel] iPXE boot failing with the below error
Message-ID: <CAErcrO9PprE63ufOn_5s3ipLWNi_d8qHafbDBPdNOuzsrKttPA@mail.gmail.com>

Hi iPXE team

we are seeing the below error while doing iPXE.
Is there any way to clear the memory from pxe mode.

PXE> boot t*ftp://<address>/<image_path>/
<ftp://223.255.254.253/auto/smu-automation/fretta/cafy/SMU-NCS5500/r1><image_to_load>*
. Not enough space (http://ipxe.org/310f2089)

-- 
Regards
Sadhana
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200623/907f33ea/attachment-0001.htm>

From bts at square-r00t.net  Wed Jun 24 08:02:14 2020
From: bts at square-r00t.net (brent s.)
Date: Wed, 24 Jun 2020 08:02:14 -0000
Subject: [ipxe-devel] "make everything" fails on GCC 9
Message-ID: <e50b0f8f-e953-814e-aa5f-b93c2d488171@square-r00t.net>

Hello, all!


Currently, on Arch Linux using the following:

GCC: 9.3.0
make: 4.3

and building from the latest master branch HEAD
(8830f2f3514751e702199600fa6d0c42522a709a),

it serves what I think are PIE-related errors (gcc6+ enables PIE by
default) (see pie.err.txt) via:

make CC="gcc-9" everything

Example of error:


  [DEPS] arch/x86/drivers/net/undiisr.S
cc1: error: code model kernel does not support PIC mode


So then I try disabling PIE (make CC="gcc-9 -no-pie" everything), and
get far fewer errors (nopie.err.txt), but it also eventually fails. I
suspect it's because of this?[0]


Error:

  [BUILD] bin-x86_64-pcbios/__divdi3.o
cc1: error: code model kernel does not support PIC mode
make[2]: *** [Makefile.housekeeping:946: bin-x86_64-pcbios/__divdi3.o]
Error 1
make[1]: *** [Makefile.housekeeping:276:
bin-x86_64-pcbios/8086100e.mrom] Error 2
make: *** [Makefile:168: everything] Error 2



Is there a way to build the "everything" target on systems with
PIE-enabled gcc? (Or wherever the attached error is coming from.)



[0] https://lists.ipxe.org/pipermail/ipxe-devel/2018-January/006009.html

-- 
brent saner
https://square-r00t.net/
GPG info: https://square-r00t.net/gpg-info
-------------- next part --------------
rm -f bin{,-*}/*.* bin{,-*}/.certificate.* bin{,-*}/.certificates.* bin{,-*}/.private_key.* bin{,-*}/errors bin{,-*}/NIC ./util/zbin ./util/elf2efi32 ./util/elf2efi64 ./util/efirom ./util/efifatbin ./util/iccfix ./util/einfo TAGS bin{,-*}/symtab
  [PARSEROM]
  [DEPS] arch/x86/drivers/net/undiisr.S
  [DEPS] arch/x86/transitions/librm.S
  [DEPS] arch/x86/transitions/libpm.S
  [DEPS] arch/x86/transitions/libkir.S
  [DEPS] arch/x86/transitions/liba20.S
  [DEPS] arch/x86/prefix/usbdisk.S
  [DEPS] arch/x86/prefix/unlzma.S
  [DEPS] arch/x86/prefix/unlzma16.S
  [DEPS] arch/x86/prefix/undiloader.S
  [DEPS] arch/x86/prefix/romprefix.S
  [DEPS] arch/x86/prefix/pxeprefix.S
  [DEPS] arch/x86/prefix/pciromprefix.S
  [DEPS] arch/x86/prefix/nullprefix.S
  [DEPS] arch/x86/prefix/nbiprefix.S
  [DEPS] arch/x86/prefix/mromprefix.S
  [DEPS] arch/x86/prefix/mbr.S
  [DEPS] arch/x86/prefix/lkrnprefix.S
  [DEPS] arch/x86/prefix/libprefix.S
  [DEPS] arch/x86/prefix/kpxeprefix.S
  [DEPS] arch/x86/prefix/kkpxeprefix.S
  [DEPS] arch/x86/prefix/kkkpxeprefix.S
  [DEPS] arch/x86/prefix/isaromprefix.S
  [DEPS] arch/x86/prefix/hdprefix.S
  [DEPS] arch/x86/prefix/exeprefix.S
  [DEPS] arch/x86/prefix/dskprefix.S
  [DEPS] arch/x86/prefix/bootpart.S
  [DEPS] arch/x86/interface/syslinux/com32_wrapper.S
  [DEPS] arch/x86/interface/pxe/pxe_entry.S
  [DEPS] arch/x86/interface/pcbios/e820mangler.S
  [DEPS] arch/x86/core/stack.S
  [DEPS] arch/x86/core/stack16.S
  [DEPS] arch/x86/core/patch_cf.S
  [DEPS] arch/i386/tests/gdbstub_test.S
  [DEPS] arch/i386/core/setjmp.S
  [DEPS] arch/i386/core/gdbidt.S
  [DEPS] drivers/net/ath/ath9k/ath9k_xmit.c
  [DEPS] drivers/net/ath/ath9k/ath9k_recv.c
  [DEPS] drivers/net/ath/ath9k/ath9k_main.c
  [DEPS] drivers/net/ath/ath9k/ath9k_mac.c
  [DEPS] drivers/net/ath/ath9k/ath9k_init.c
  [DEPS] drivers/net/ath/ath9k/ath9k_hw.c
  [DEPS] drivers/net/ath/ath9k/ath9k_eeprom_def.c
  [DEPS] drivers/net/ath/ath9k/ath9k_eeprom.c
  [DEPS] drivers/net/ath/ath9k/ath9k_eeprom_9287.c
  [DEPS] drivers/net/ath/ath9k/ath9k_eeprom_4k.c
  [DEPS] drivers/net/ath/ath9k/ath9k_common.c
  [DEPS] drivers/net/ath/ath9k/ath9k_calib.c
  [DEPS] drivers/net/ath/ath9k/ath9k.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9003_phy.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9003_mac.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9003_hw.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9003_eeprom.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9003_calib.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9002_phy.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9002_mac.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9002_hw.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9002_calib.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ar5008_phy.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ani.c
  [DEPS] drivers/net/ath/ath5k/ath5k_rfkill.c
  [DEPS] drivers/net/ath/ath5k/ath5k_reset.c
  [DEPS] drivers/net/ath/ath5k/ath5k_qcu.c
  [DEPS] drivers/net/ath/ath5k/ath5k_phy.c
  [DEPS] drivers/net/ath/ath5k/ath5k_pcu.c
  [DEPS] drivers/net/ath/ath5k/ath5k_initvals.c
  [DEPS] drivers/net/ath/ath5k/ath5k_gpio.c
  [DEPS] drivers/net/ath/ath5k/ath5k_eeprom.c
  [DEPS] drivers/net/ath/ath5k/ath5k_dma.c
  [DEPS] drivers/net/ath/ath5k/ath5k_desc.c
  [DEPS] drivers/net/ath/ath5k/ath5k_caps.c
  [DEPS] drivers/net/ath/ath5k/ath5k.c
  [DEPS] drivers/net/ath/ath5k/ath5k_attach.c
  [DEPS] drivers/net/ath/ath_regd.c
  [DEPS] drivers/net/ath/ath_key.c
  [DEPS] drivers/net/ath/ath_hw.c
  [DEPS] drivers/net/rtl818x/rtl818x.c
  [DEPS] drivers/net/rtl818x/rtl8185_rtl8225.c
  [DEPS] drivers/net/rtl818x/rtl8185.c
  [DEPS] drivers/net/rtl818x/rtl8180_sa2400.c
  [DEPS] drivers/net/rtl818x/rtl8180_max2820.c
  [DEPS] drivers/net/rtl818x/rtl8180_grf5101.c
  [DEPS] drivers/net/rtl818x/rtl8180.c
  [DEPS] net/80211/wpa_tkip.c
  [DEPS] net/80211/wpa_psk.c
  [DEPS] net/80211/wpa_ccmp.c
  [DEPS] net/80211/wpa.c
  [DEPS] net/80211/wep.c
  [DEPS] net/80211/sec80211.c
  [DEPS] net/80211/rc80211.c
  [DEPS] net/80211/net80211.c
  [DEPS] net/oncrpc/portmap.c
  [DEPS] net/oncrpc/oncrpc_iob.c
  [DEPS] net/oncrpc/nfs_uri.c
  [DEPS] net/oncrpc/nfs_open.c
  [DEPS] net/oncrpc/nfs.c
  [DEPS] net/oncrpc/mount.c
  [DEPS] arch/x86/drivers/net/undirom.c
  [DEPS] arch/x86/drivers/net/undipreload.c
  [DEPS] arch/x86/drivers/net/undionly.c
  [DEPS] arch/x86/drivers/net/undinet.c
  [DEPS] arch/x86/drivers/net/undiload.c
  [DEPS] arch/x86/drivers/net/undi.c
  [DEPS] arch/x86/transitions/librm_test.c
  [DEPS] arch/x86/transitions/librm_mgmt.c
  [DEPS] arch/x86/drivers/hyperv/hyperv.c
  [DEPS] arch/x86/drivers/xen/hvm.c
  [DEPS] arch/x86/hci/commands/pxe_cmd.c
  [DEPS] arch/x86/hci/commands/cpuid_cmd.c
  [DEPS] arch/x86/interface/syslinux/comboot_resolv.c
  [DEPS] arch/x86/interface/syslinux/comboot_call.c
  [DEPS] arch/x86/interface/syslinux/com32_call.c
  [DEPS] arch/x86/interface/vmware/vmware.c
  [DEPS] arch/x86/interface/vmware/vmconsole.c
  [DEPS] arch/x86/interface/vmware/guestrpc.c
  [DEPS] arch/x86/interface/vmware/guestinfo.c
  [DEPS] arch/x86/interface/efi/efix86_nap.c
  [DEPS] arch/x86/interface/pxe/pxe_undi.c
  [DEPS] arch/x86/interface/pxe/pxe_udp.c
  [DEPS] arch/x86/interface/pxe/pxe_tftp.c
  [DEPS] arch/x86/interface/pxe/pxe_preboot.c
  [DEPS] arch/x86/interface/pxe/pxe_loader.c
  [DEPS] arch/x86/interface/pxe/pxe_file.c
  [DEPS] arch/x86/interface/pxe/pxe_exit_hook.c
  [DEPS] arch/x86/interface/pxe/pxe_call.c
  [DEPS] arch/x86/interface/pcbios/vesafb.c
  [DEPS] arch/x86/interface/pcbios/rtc_time.c
  [DEPS] arch/x86/interface/pcbios/rtc_entropy.c
  [DEPS] arch/x86/interface/pcbios/rsdp.c
  [DEPS] arch/x86/interface/pcbios/pnpbios.c
  [DEPS] arch/x86/interface/pcbios/pcibios.c
  [DEPS] arch/x86/interface/pcbios/memtop_umalloc.c
  [DEPS] arch/x86/interface/pcbios/memmap.c
  [DEPS] arch/x86/interface/pcbios/int13con.c
  [DEPS] arch/x86/interface/pcbios/int13.c
  [DEPS] arch/x86/interface/pcbios/hidemem.c
  [DEPS] arch/x86/interface/pcbios/fakee820.c
  [DEPS] arch/x86/interface/pcbios/bios_timer.c
  [DEPS] arch/x86/interface/pcbios/bios_smbios.c
  [DEPS] arch/x86/interface/pcbios/bios_reboot.c
  [DEPS] arch/x86/interface/pcbios/bios_nap.c
  [DEPS] arch/x86/interface/pcbios/biosint.c
  [DEPS] arch/x86/interface/pcbios/bios_console.c
  [DEPS] arch/x86/interface/pcbios/basemem.c
  [DEPS] arch/x86/interface/pcbios/apm.c
  [DEPS] arch/x86/interface/pcbios/acpi_timer.c
  [DEPS] arch/x86/interface/pcbios/acpipwr.c
  [DEPS] arch/x86/image/sdi.c
  [DEPS] arch/x86/image/pxe_image.c
  [DEPS] arch/x86/image/nbi.c
  [DEPS] arch/x86/image/multiboot.c
  [DEPS] arch/x86/image/initrd.c
  [DEPS] arch/x86/image/elfboot.c
  [DEPS] arch/x86/image/comboot.c
  [DEPS] arch/x86/image/com32.c
  [DEPS] arch/x86/image/bzimage.c
  [DEPS] arch/x86/image/bootsector.c
  [DEPS] arch/x86/core/x86_uart.c
  [DEPS] arch/x86/core/x86_tcpip.c
  [DEPS] arch/x86/core/x86_string.c
  [DEPS] arch/x86/core/x86_io.c
  [DEPS] arch/x86/core/x86_bigint.c
  [DEPS] arch/x86/core/vram_settings.c
  [DEPS] arch/x86/core/video_subr.c
  [DEPS] arch/x86/core/runtime.c
  [DEPS] arch/x86/core/relocate.c
  [DEPS] arch/x86/core/rdtsc_timer.c
  [DEPS] arch/x86/core/pit8254.c
  [DEPS] arch/x86/core/pic8259.c
  [DEPS] arch/x86/core/pcidirect.c
  [DEPS] arch/x86/core/pci_autoboot.c
  [DEPS] arch/x86/core/gdbmach.c
  [DEPS] arch/x86/core/dumpregs.c
  [DEPS] arch/x86/core/debugcon.c
  [DEPS] arch/x86/core/cpuid_settings.c
  [DEPS] arch/x86/core/cpuid.c
  [DEPS] arch/x86/core/cachedhcp.c
  [DEPS] arch/x86/core/basemem_packet.c
  [DEPS] arch/i386/core/nulltrap.c
  [DEPS] config/config_usb.c
  [DEPS] config/config_timer.c
  [DEPS] config/config_route.c
  [DEPS] config/config_romprefix.c
  [DEPS] config/config_pixbuf.c
  [DEPS] config/config_pcbios.c
  [DEPS] config/config_net80211.c
  [DEPS] config/config_linux.c
  [DEPS] config/config_infiniband.c
  [DEPS] config/config_http.c
  [DEPS] config/config_fdt.c
  [DEPS] config/config_fc.c
  [DEPS] config/config_ethernet.c
  [DEPS] config/config_efi.c
  [DEPS] config/config_crypto.c
  [DEPS] config/config.c
  [DEPS] config/config_asn1.c
  [DEPS] usr/sync.c
  [DEPS] usr/route_ipv6.c
  [DEPS] usr/route_ipv4.c
  [DEPS] usr/route.c
  [DEPS] usr/pxemenu.c
  [DEPS] usr/prompt.c
  [DEPS] usr/profstat.c
  [DEPS] usr/pingmgmt.c
  [DEPS] usr/ntpmgmt.c
  [DEPS] usr/nslookup.c
  [DEPS] usr/neighmgmt.c
  [DEPS] usr/lotest.c
  [DEPS] usr/iwmgmt.c
  [DEPS] usr/ipstat.c
  [DEPS] usr/imgtrust.c
  [DEPS] usr/imgmgmt.c
  [DEPS] usr/ifmgmt.c
  [DEPS] usr/ibmgmt.c
  [DEPS] usr/fcmgmt.c
  [DEPS] usr/dhcpmgmt.c
  [DEPS] usr/certmgmt.c
  [DEPS] usr/autoboot.c
  [DEPS] hci/keymap/keymap_wo.c
  [DEPS] hci/keymap/keymap_us.c
  [DEPS] hci/keymap/keymap_uk.c
  [DEPS] hci/keymap/keymap_ua.c
  [DEPS] hci/keymap/keymap_th.c
  [DEPS] hci/keymap/keymap_sr.c
  [DEPS] hci/keymap/keymap_sg.c
  [DEPS] hci/keymap/keymap_ru.c
  [DEPS] hci/keymap/keymap_ro.c
  [DEPS] hci/keymap/keymap_pt.c
  [DEPS] hci/keymap/keymap_pl.c
  [DEPS] hci/keymap/keymap_no-latin1.c
  [DEPS] hci/keymap/keymap_no.c
  [DEPS] hci/keymap/keymap_nl.c
  [DEPS] hci/keymap/keymap_mt.c
  [DEPS] hci/keymap/keymap_mk.c
  [DEPS] hci/keymap/keymap_lt.c
  [DEPS] hci/keymap/keymap_it.c
  [DEPS] hci/keymap/keymap_il.c
  [DEPS] hci/keymap/keymap_hu.c
  [DEPS] hci/keymap/keymap_gr.c
  [DEPS] hci/keymap/keymap_fr.c
  [DEPS] hci/keymap/keymap_fi.c
  [DEPS] hci/keymap/keymap_et.c
  [DEPS] hci/keymap/keymap_es.c
  [DEPS] hci/keymap/keymap_dk.c
  [DEPS] hci/keymap/keymap_de.c
  [DEPS] hci/keymap/keymap_cz.c
  [DEPS] hci/keymap/keymap_cf.c
  [DEPS] hci/keymap/keymap_by.c
  [DEPS] hci/keymap/keymap_bg.c
  [DEPS] hci/keymap/keymap_az.c
  [DEPS] hci/keymap/keymap_al.c
  [DEPS] hci/mucurses/widgets/editbox.c
  [DEPS] hci/mucurses/wininit.c
  [DEPS] hci/mucurses/windows.c
  [DEPS] hci/mucurses/winattrs.c
  [DEPS] hci/mucurses/slk.c
  [DEPS] hci/mucurses/print_nadv.c
  [DEPS] hci/mucurses/print.c
  [DEPS] hci/mucurses/mucurses.c
  [DEPS] hci/mucurses/kb.c
  [DEPS] hci/mucurses/edging.c
  [DEPS] hci/mucurses/colour.c
  [DEPS] hci/mucurses/clear.c
  [DEPS] hci/mucurses/ansi_screen.c
  [DEPS] hci/mucurses/alert.c
  [DEPS] hci/tui/settings_ui.c
  [DEPS] hci/tui/menu_ui.c
  [DEPS] hci/tui/login_ui.c
  [DEPS] hci/commands/vlan_cmd.c
  [DEPS] hci/commands/time_cmd.c
  [DEPS] hci/commands/sync_cmd.c
  [DEPS] hci/commands/sanboot_cmd.c
  [DEPS] hci/commands/route_cmd.c
  [DEPS] hci/commands/reboot_cmd.c
  [DEPS] hci/commands/profstat_cmd.c
  [DEPS] hci/commands/poweroff_cmd.c
  [DEPS] hci/commands/ping_cmd.c
  [DEPS] hci/commands/pci_cmd.c
  [DEPS] hci/commands/param_cmd.c
  [DEPS] hci/commands/nvo_cmd.c
  [DEPS] hci/commands/ntp_cmd.c
  [DEPS] hci/commands/nslookup_cmd.c
  [DEPS] hci/commands/neighbour_cmd.c
  [DEPS] hci/commands/menu_cmd.c
  [DEPS] hci/commands/lotest_cmd.c
  [DEPS] hci/commands/login_cmd.c
  [DEPS] hci/commands/iwmgmt_cmd.c
  [DEPS] hci/commands/ipstat_cmd.c
  [DEPS] hci/commands/image_trust_cmd.c
  [DEPS] hci/commands/image_cmd.c
  [DEPS] hci/commands/ifmgmt_cmd.c
  [DEPS] hci/commands/ibmgmt_cmd.c
  [DEPS] hci/commands/gdbstub_cmd.c
  [DEPS] hci/commands/fcmgmt_cmd.c
  [DEPS] hci/commands/digest_cmd.c
  [DEPS] hci/commands/dhcp_cmd.c
  [DEPS] hci/commands/console_cmd.c
  [DEPS] hci/commands/config_cmd.c
  [DEPS] hci/commands/cert_cmd.c
  [DEPS] hci/commands/autoboot_cmd.c
  [DEPS] hci/wireless_errors.c
  [DEPS] hci/strerror.c
  [DEPS] hci/shell.c
  [DEPS] hci/readline.c
  [DEPS] hci/linux_args.c
  [DEPS] hci/jumpscroll.c
  [DEPS] hci/editstring.c
  [DEPS] crypto/mishmash/rsa_sha512.c
  [DEPS] crypto/mishmash/rsa_sha384.c
  [DEPS] crypto/mishmash/rsa_sha256.c
  [DEPS] crypto/mishmash/rsa_sha224.c
  [DEPS] crypto/mishmash/rsa_sha1.c
  [DEPS] crypto/mishmash/rsa_md5.c
  [DEPS] crypto/mishmash/rsa_aes_cbc_sha256.c
  [DEPS] crypto/mishmash/rsa_aes_cbc_sha1.c
  [DEPS] crypto/mishmash/oid_sha512.c
  [DEPS] crypto/mishmash/oid_sha512_256.c
  [DEPS] crypto/mishmash/oid_sha512_224.c
  [DEPS] crypto/mishmash/oid_sha384.c
  [DEPS] crypto/mishmash/oid_sha256.c
  [DEPS] crypto/mishmash/oid_sha224.c
  [DEPS] crypto/mishmash/oid_sha1.c
  [DEPS] crypto/mishmash/oid_rsa.c
  [DEPS] crypto/mishmash/oid_md5.c
  [DEPS] crypto/mishmash/oid_md4.c
  [DEPS] crypto/x509.c
  [DEPS] crypto/sha512.c
  [DEPS] crypto/sha512_256.c
  [DEPS] crypto/sha512_224.c
  [DEPS] crypto/sha384.c
  [DEPS] crypto/sha256.c
  [DEPS] crypto/sha224.c
  [DEPS] crypto/sha1extra.c
  [DEPS] crypto/sha1.c
  [DEPS] crypto/rsa.c
  [DEPS] crypto/rootcert.c
  [DEPS] crypto/rbg.c
  [DEPS] crypto/random_nz.c
  [DEPS] crypto/privkey.c
  [DEPS] crypto/ocsp.c
  [DEPS] crypto/null_entropy.c
  [DEPS] crypto/ntlm.c
  [DEPS] crypto/md5.c
  [DEPS] crypto/md4.c
  [DEPS] crypto/hmac_drbg.c
  [DEPS] crypto/hmac.c
  [DEPS] crypto/hash_df.c
  [DEPS] crypto/entropy.c
  [DEPS] crypto/ecb.c
  [DEPS] crypto/drbg.c
  [DEPS] crypto/deflate.c
  [DEPS] crypto/crypto_null.c
  [DEPS] crypto/crc32.c
  [DEPS] crypto/cms.c
  [DEPS] crypto/chap.c
  [DEPS] crypto/certstore.c
  [DEPS] crypto/cbc.c
  [DEPS] crypto/bigint.c
  [DEPS] crypto/asn1.c
  [DEPS] crypto/arc4.c
  [DEPS] crypto/aes_wrap.c
  [DEPS] crypto/aes.c
  [DEPS] tests/x509_test.c
  [DEPS] tests/vsprintf_test.c
  [DEPS] tests/uri_test.c
  [DEPS] tests/umalloc_test.c
  [DEPS] tests/time_test.c
  [DEPS] tests/tests.c
  [DEPS] tests/test.c
  [DEPS] tests/tcpip_test.c
  [DEPS] tests/string_test.c
  [DEPS] tests/sha512_test.c
  [DEPS] tests/sha256_test.c
  [DEPS] tests/sha1_test.c
  [DEPS] tests/settings_test.c
  [DEPS] tests/setjmp_test.c
  [DEPS] tests/rsa_test.c
  [DEPS] tests/profile_test.c
  [DEPS] tests/pnm_test.c
  [DEPS] tests/png_test.c
  [DEPS] tests/pixbuf_test.c
  [DEPS] tests/pem_test.c
  [DEPS] tests/pccrc_test.c
  [DEPS] tests/ocsp_test.c
  [DEPS] tests/ntlm_test.c
  [DEPS] tests/memset_test.c
  [DEPS] tests/memcpy_test.c
  [DEPS] tests/md5_test.c
  [DEPS] tests/md4_test.c
  [DEPS] tests/math_test.c
  [DEPS] tests/list_test.c
  [DEPS] tests/linebuf_test.c
  [DEPS] tests/ipv6_test.c
  [DEPS] tests/ipv4_test.c
  [DEPS] tests/iobuf_test.c
  [DEPS] tests/hmac_drbg_test.c
  [DEPS] tests/hash_df_test.c
  [DEPS] tests/entropy_sample.c
  [DEPS] tests/dns_test.c
  [DEPS] tests/digest_test.c
  [DEPS] tests/der_test.c
  [DEPS] tests/deflate_test.c
  [DEPS] tests/crc32_test.c
  [DEPS] tests/cms_test.c
  [DEPS] tests/cipher_test.c
  [DEPS] tests/byteswap_test.c
  [DEPS] tests/bofm_test.c
  [DEPS] tests/bitops_test.c
  [DEPS] tests/bigint_test.c
  [DEPS] tests/base64_test.c
  [DEPS] tests/base16_test.c
  [DEPS] tests/asn1_test.c
  [DEPS] tests/aes_test.c
  [DEPS] interface/hyperv/vmbus.c
  [DEPS] interface/xen/xenstore.c
  [DEPS] interface/xen/xengrant.c
  [DEPS] interface/xen/xenbus.c
  [DEPS] interface/bofm/bofm.c
  [DEPS] interface/smbios/smbios_settings.c
  [DEPS] interface/smbios/smbios.c
  [DEPS] interface/efi/efi_wrap.c
  [DEPS] interface/efi/efi_watchdog.c
  [DEPS] interface/efi/efi_utils.c
  [DEPS] interface/efi/efi_usb.c
  [DEPS] interface/efi/efi_umalloc.c
  [DEPS] interface/efi/efi_uaccess.c
  [DEPS] interface/efi/efi_timer.c
  [DEPS] interface/efi/efi_time.c
  [DEPS] interface/efi/efi_strings.c
  [DEPS] interface/efi/efi_snp_hii.c
  [DEPS] interface/efi/efi_snp.c
  [DEPS] interface/efi/efi_smbios.c
  [DEPS] interface/efi/efi_reboot.c
  [DEPS] interface/efi/efi_pxe.c
  [DEPS] interface/efi/efiprefix.c
  [DEPS] interface/efi/efi_pci.c
  [DEPS] interface/efi/efi_local.c
  [DEPS] interface/efi/efi_init.c
  [DEPS] interface/efi/efi_hii.c
  [DEPS] interface/efi/efi_guid.c
  [DEPS] interface/efi/efi_file.c
  [DEPS] interface/efi/efi_fdt.c
  [DEPS] interface/efi/efi_fbcon.c
  [DEPS] interface/efi/efi_entropy.c
  [DEPS] interface/efi/efidrvprefix.c
  [DEPS] interface/efi/efi_driver.c
  [DEPS] interface/efi/efi_download.c
  [DEPS] interface/efi/efi_debug.c
  [DEPS] interface/efi/efi_console.c
  [DEPS] interface/efi/efi_bofm.c
  [DEPS] interface/efi/efi_block.c
  [DEPS] interface/efi/efi_blacklist.c
  [DEPS] interface/efi/efi_autoboot.c
  [DEPS] interface/efi/efi_acpi.c
  [DEPS] drivers/usb/xhci.c
  [DEPS] drivers/usb/usbnet.c
  [DEPS] drivers/usb/usbkbd.c
  [DEPS] drivers/usb/usbio.c
  [DEPS] drivers/usb/usbhub.c
  [DEPS] drivers/usb/usbhid.c
  [DEPS] drivers/usb/uhci.c
  [DEPS] drivers/usb/ehci.c
  [DEPS] drivers/infiniband/mlx_nodnic/src/mlx_port.c
  [DEPS] drivers/infiniband/mlx_nodnic/src/mlx_device.c
  [DEPS] drivers/infiniband/mlx_nodnic/src/mlx_cmd.c
  [DEPS] drivers/infiniband/mlx_utils/mlx_lib/mlx_mtu/mlx_mtu.c
  [DEPS] drivers/infiniband/mlx_utils/mlx_lib/mlx_link_speed/mlx_link_speed.c
  [DEPS] drivers/infiniband/mlx_utils/mlx_lib/mlx_blink_leds/mlx_blink_leds.c
  [DEPS] drivers/infiniband/mlx_utils/mlx_lib/mlx_vmac/mlx_vmac.c
  [DEPS] drivers/infiniband/mlx_utils/mlx_lib/mlx_nvconfig/mlx_nvconfig_defaults.c
  [DEPS] drivers/infiniband/mlx_utils/mlx_lib/mlx_nvconfig/mlx_nvconfig.c
  [DEPS] drivers/infiniband/mlx_utils/mlx_lib/mlx_reg_access/mlx_reg_access.c
  [DEPS] drivers/infiniband/mlx_utils/src/public/mlx_utils.c
  [DEPS] drivers/infiniband/mlx_utils/src/public/mlx_pci_gw.c
  [DEPS] drivers/infiniband/mlx_utils/src/public/mlx_pci.c
  [DEPS] drivers/infiniband/mlx_utils/src/public/mlx_memory.c
  [DEPS] drivers/infiniband/mlx_utils/src/public/mlx_icmd.c
  [DEPS] drivers/infiniband/mlx_utils_flexboot/src/mlx_utils_priv.c
  [DEPS] drivers/infiniband/mlx_utils_flexboot/src/mlx_pci_priv.c
  [DEPS] drivers/infiniband/mlx_utils_flexboot/src/mlx_memory_priv.c
  [DEPS] drivers/infiniband/qib7322.c
  [DEPS] drivers/infiniband/linda_fw.c
  [DEPS] drivers/infiniband/linda.c
  [DEPS] drivers/infiniband/hermon.c
  [DEPS] drivers/infiniband/golan.c
  [DEPS] drivers/infiniband/flexboot_nodnic.c
  [DEPS] drivers/infiniband/arbel.c
  [DEPS] drivers/bitbash/spi_bit.c
  [DEPS] drivers/bitbash/mii_bit.c
  [DEPS] drivers/bitbash/i2c_bit.c
  [DEPS] drivers/bitbash/bitbash.c
  [DEPS] drivers/nvs/threewire.c
  [DEPS] drivers/nvs/spi.c
  [DEPS] drivers/nvs/nvsvpd.c
  [DEPS] drivers/nvs/nvs.c
  [DEPS] drivers/block/srp.c
  [DEPS] drivers/block/scsi.c
  [DEPS] drivers/block/ibft.c
  [DEPS] drivers/block/ata.c
  [DEPS] drivers/net/sfc/sfc_hunt.c
  [DEPS] drivers/net/sfc/efx_hunt.c
  [DEPS] drivers/net/sfc/efx_common.c
  [DEPS] drivers/net/bnxt/bnxt.c
  [DEPS] drivers/net/tg3/tg3_phy.c
  [DEPS] drivers/net/tg3/tg3_hw.c
  [DEPS] drivers/net/tg3/tg3.c
  [DEPS] drivers/net/efi/snponly.c
  [DEPS] drivers/net/efi/snpnet.c
  [DEPS] drivers/net/efi/snp.c
  [DEPS] drivers/net/efi/nii.c
  [DEPS] drivers/net/vxge/vxge_traffic.c
  [DEPS] drivers/net/vxge/vxge_main.c
  [DEPS] drivers/net/vxge/vxge_config.c
  [DEPS] drivers/net/vxge/vxge.c
  [DEPS] drivers/net/phantom/phantom.c
  [DEPS] drivers/net/igbvf/igbvf_vf.c
  [DEPS] drivers/net/igbvf/igbvf_mbx.c
  [DEPS] drivers/net/igbvf/igbvf_main.c
  [DEPS] drivers/net/wd.c
  [DEPS] drivers/net/w89c840.c
  [DEPS] drivers/net/vmxnet3.c
  [DEPS] drivers/net/virtio-net.c
  [DEPS] drivers/net/velocity.c
  [DEPS] drivers/net/tulip.c
  [DEPS] drivers/net/tlan.c
  [DEPS] drivers/net/thunderx.c
  [DEPS] drivers/net/sundance.c
  [DEPS] drivers/net/smscusb.c
  [DEPS] drivers/net/smsc95xx.c
  [DEPS] drivers/net/smsc75xx.c
  [DEPS] drivers/net/smc9000.c
  [DEPS] drivers/net/sky2.c
  [DEPS] drivers/net/skge.c
  [DEPS] drivers/net/skeleton.c
  [DEPS] drivers/net/sis900.c
  [DEPS] drivers/net/sis190.c
  [DEPS] drivers/net/rhine.c
  [DEPS] drivers/net/realtek.c
  [DEPS] drivers/net/prism2_plx.c
  [DEPS] drivers/net/prism2_pci.c
  [DEPS] drivers/net/pnic.c
  [DEPS] drivers/net/pcnet32.c
  [DEPS] drivers/net/ns8390.c
  [DEPS] drivers/net/netvsc.c
  [DEPS] drivers/net/netfront.c
  [DEPS] drivers/net/ne.c
  [DEPS] drivers/net/ne2k_isa.c
  [DEPS] drivers/net/ncm.c
  [DEPS] drivers/net/natsemi.c
  [DEPS] drivers/net/myson.c
  [DEPS] drivers/net/myri10ge.c
  [DEPS] drivers/net/mii.c
  [DEPS] drivers/net/legacy.c
  [DEPS] drivers/net/lan78xx.c
  [DEPS] drivers/net/jme.c
  [DEPS] drivers/net/ipoib.c
  [DEPS] drivers/net/intelxvf.c
  [DEPS] drivers/net/intelxlvf.c
  [DEPS] drivers/net/intelxl.c
  [DEPS] drivers/net/intelx.c
  [DEPS] drivers/net/intelvf.c
  [DEPS] drivers/net/intel.c
  [DEPS] drivers/net/icplus.c
  [DEPS] drivers/net/forcedeth.c
  [DEPS] drivers/net/exanic.c
  [DEPS] drivers/net/etherfabric.c
  [DEPS] drivers/net/epic100.c
  [DEPS] drivers/net/eoib.c
  [DEPS] drivers/net/ena.c
  [DEPS] drivers/net/eepro.c
  [DEPS] drivers/net/eepro100.c
  [DEPS] drivers/net/ecm.c
  [DEPS] drivers/net/dmfe.c
  [DEPS] drivers/net/dm96xx.c
  [DEPS] drivers/net/depca.c
  [DEPS] drivers/net/davicom.c
  [DEPS] drivers/net/cs89x0.c
  [DEPS] drivers/net/bnx2.c
  [DEPS] drivers/net/b44.c
  [DEPS] drivers/net/axge.c
  [DEPS] drivers/net/atl1e.c
  [DEPS] drivers/net/amd8111e.c
  [DEPS] drivers/net/acm.c
  [DEPS] drivers/net/3c90x.c
  [DEPS] drivers/net/3c5x9.c
  [DEPS] drivers/net/3c595.c
  [DEPS] drivers/net/3c529.c
  [DEPS] drivers/net/3c515.c
  [DEPS] drivers/net/3c509-eisa.c
  [DEPS] drivers/net/3c509.c
  [DEPS] drivers/net/3c503.c
  [DEPS] drivers/bus/virtio-ring.c
  [DEPS] drivers/bus/virtio-pci.c
  [DEPS] drivers/bus/usb.c
  [DEPS] drivers/bus/pcivpd.c
  [DEPS] drivers/bus/pci_settings.c
  [DEPS] drivers/bus/pcimsix.c
  [DEPS] drivers/bus/pciextra.c
  [DEPS] drivers/bus/pciea.c
  [DEPS] drivers/bus/pci.c
  [DEPS] drivers/bus/pcibackup.c
  [DEPS] drivers/bus/mca.c
  [DEPS] drivers/bus/isapnp.c
  [DEPS] drivers/bus/isa_ids.c
  [DEPS] drivers/bus/isa.c
  [DEPS] drivers/bus/eisa.c
  [DEPS] drivers/bus/cdc.c
  [DEPS] image/segment.c
  [DEPS] image/script.c
  [DEPS] image/pnm.c
  [DEPS] image/png.c
  [DEPS] image/pem.c
  [DEPS] image/embedded.c
  [DEPS] image/elf.c
  [DEPS] image/efi_image.c
  [DEPS] image/der.c
  [DEPS] net/infiniband/xsigo.c
  [DEPS] net/infiniband/ib_srp.c
  [DEPS] net/infiniband/ib_smc.c
  [DEPS] net/infiniband/ib_sma.c
  [DEPS] net/infiniband/ib_service.c
  [DEPS] net/infiniband/ib_pathrec.c
  [DEPS] net/infiniband/ib_packet.c
  [DEPS] net/infiniband/ib_mi.c
  [DEPS] net/infiniband/ib_mcast.c
  [DEPS] net/infiniband/ib_cmrc.c
  [DEPS] net/infiniband/ib_cm.c
  [DEPS] net/udp/tftp.c
  [DEPS] net/udp/syslog.c
  [DEPS] net/udp/slam.c
  [DEPS] net/udp/ntp.c
  [DEPS] net/udp/dns.c
  [DEPS] net/udp/dhcpv6.c
  [DEPS] net/udp/dhcp.c
  [DEPS] net/tcp/syslogs.c
  [DEPS] net/tcp/oncrpc.c
  [DEPS] net/tcp/iscsi.c
  [DEPS] net/tcp/https.c
  [DEPS] net/tcp/httpntlm.c
  [DEPS] net/tcp/httpgce.c
  [DEPS] net/tcp/httpdigest.c
  [DEPS] net/tcp/httpcore.c
  [DEPS] net/tcp/httpconn.c
  [DEPS] net/tcp/http.c
  [DEPS] net/tcp/httpblock.c
  [DEPS] net/tcp/httpbasic.c
  [DEPS] net/tcp/httpauth.c
  [DEPS] net/tcp/ftp.c
  [DEPS] net/vlan.c
  [DEPS] net/validator.c
  [DEPS] net/udp.c
  [DEPS] net/tls.c
  [DEPS] net/tcpip.c
  [DEPS] net/tcp.c
  [DEPS] net/stp.c
  [DEPS] net/socket.c
  [DEPS] net/rndis.c
  [DEPS] net/retry.c
  [DEPS] net/rarp.c
  [DEPS] net/ping.c
  [DEPS] net/peermux.c
  [DEPS] net/peerdist.c
  [DEPS] net/peerdisc.c
  [DEPS] net/peerblk.c
  [DEPS] net/pccrd.c
  [DEPS] net/pccrc.c
  [DEPS] net/nullnet.c
  [DEPS] net/netdev_settings.c
  [DEPS] net/netdevice.c
  [DEPS] net/neighbour.c
  [DEPS] net/ndp.c
  [DEPS] net/ipv6.c
  [DEPS] net/ipv4.c
  [DEPS] net/iobpad.c
  [DEPS] net/infiniband.c
  [DEPS] net/icmpv6.c
  [DEPS] net/icmpv4.c
  [DEPS] net/icmp.c
  [DEPS] net/fragment.c
  [DEPS] net/fcp.c
  [DEPS] net/fcoe.c
  [DEPS] net/fcns.c
  [DEPS] net/fcels.c
  [DEPS] net/fc.c
  [DEPS] net/fakedhcp.c
  [DEPS] net/eth_slow.c
  [DEPS] net/ethernet.c
  [DEPS] net/eapol.c
  [DEPS] net/dhcppkt.c
  [DEPS] net/dhcpopts.c
  [DEPS] net/arp.c
  [DEPS] net/aoe.c
  [DEPS] core/xfer.c
  [DEPS] core/xferbuf.c
  [DEPS] core/wchar.c
  [DEPS] core/vsprintf.c
  [DEPS] core/uuid.c
  [DEPS] core/uri.c
  [DEPS] core/uart.c
  [DEPS] core/timer.c
  [DEPS] core/time.c
  [DEPS] core/stringextra.c
  [DEPS] core/string.c
  [DEPS] core/settings.c
  [DEPS] core/serial.c
  [DEPS] core/sanboot.c
  [DEPS] core/resolv.c
  [DEPS] core/refcnt.c
  [DEPS] core/random.c
  [DEPS] core/quiesce.c
  [DEPS] core/profile.c
  [DEPS] core/process.c
  [DEPS] core/posix_io.c
  [DEPS] core/pool.c
  [DEPS] core/pixbuf.c
  [DEPS] core/pinger.c
  [DEPS] core/pending.c
  [DEPS] core/pcmcia.c
  [DEPS] core/pc_kbd.c
  [DEPS] core/parseopt.c
  [DEPS] core/params.c
  [DEPS] core/open.c
  [DEPS] core/nvo.c
  [DEPS] core/null_time.c
  [DEPS] core/null_sanboot.c
  [DEPS] core/null_reboot.c
  [DEPS] core/null_nap.c
  [DEPS] core/null_acpi.c
  [DEPS] core/netbios.c
  [DEPS] core/monojob.c
  [DEPS] core/menu.c
  [DEPS] core/memmap_settings.c
  [DEPS] core/malloc.c
  [DEPS] core/main.c
  [DEPS] core/log.c
  [DEPS] core/list.c
  [DEPS] core/lineconsole.c
  [DEPS] core/linebuf.c
  [DEPS] core/job.c
  [DEPS] core/isqrt.c
  [DEPS] core/iomap_virt.c
  [DEPS] core/iobuf.c
  [DEPS] core/interface.c
  [DEPS] core/init.c
  [DEPS] core/image.c
  [DEPS] core/i82365.c
  [DEPS] core/hw.c
  [DEPS] core/getopt.c
  [DEPS] core/getkey.c
  [DEPS] core/gdbudp.c
  [DEPS] core/gdbstub.c
  [DEPS] core/gdbserial.c
  [DEPS] core/fnrec.c
  [DEPS] core/fdt.c
  [DEPS] core/fbcon.c
  [DEPS] core/fault.c
  [DEPS] core/exec.c
  [DEPS] core/errno.c
  [DEPS] core/edd.c
  [DEPS] core/dummy_sanboot.c
  [DEPS] core/downloader.c
  [DEPS] core/device.c
  [DEPS] core/debug_md5.c
  [DEPS] core/debug.c
  [DEPS] core/cwuri.c
  [DEPS] core/ctype.c
  [DEPS] core/cpio.c
  [DEPS] core/console.c
  [DEPS] core/blocktrans.c
  [DEPS] core/blockdev.c
  [DEPS] core/bitmap.c
  [DEPS] core/basename.c
  [DEPS] core/base64.c
  [DEPS] core/base16.c
  [DEPS] core/assert.c
  [DEPS] core/asprintf.c
  [DEPS] core/ansiesc.c
  [DEPS] core/ansicoldef.c
  [DEPS] core/ansicol.c
  [DEPS] core/acpi_settings.c
  [DEPS] core/acpi.c
  [DEPS] libgcc/__umoddi3.c
  [DEPS] libgcc/__udivmoddi4.c
  [DEPS] libgcc/__udivdi3.c
  [DEPS] libgcc/__moddi3.c
  [DEPS] libgcc/implicit.c
  [DEPS] libgcc/icc.c
  [DEPS] libgcc/__divmoddi4.c
  [DEPS] libgcc/__divdi3.c
  [DEPS] arch/x86/transitions/librm.S
  [DEPS] arch/x86/prefix/usbdisk.S
  [DEPS] arch/x86/prefix/romprefix.S
  [DEPS] arch/x86/prefix/pciromprefix.S
  [DEPS] arch/x86/prefix/mromprefix.S
  [DEPS] arch/x86/prefix/isaromprefix.S
  [DEPS] drivers/net/ath/ath9k/ath9k_xmit.c
  [DEPS] drivers/net/ath/ath9k/ath9k_recv.c
  [DEPS] drivers/net/ath/ath9k/ath9k_main.c
  [DEPS] drivers/net/ath/ath9k/ath9k_mac.c
  [DEPS] drivers/net/ath/ath9k/ath9k_init.c
  [DEPS] drivers/net/ath/ath9k/ath9k_hw.c
  [DEPS] drivers/net/ath/ath9k/ath9k_eeprom_def.c
  [DEPS] drivers/net/ath/ath9k/ath9k_eeprom.c
  [DEPS] drivers/net/ath/ath9k/ath9k_eeprom_9287.c
  [DEPS] drivers/net/ath/ath9k/ath9k_eeprom_4k.c
  [DEPS] drivers/net/ath/ath9k/ath9k_common.c
  [DEPS] drivers/net/ath/ath9k/ath9k_calib.c
  [DEPS] drivers/net/ath/ath9k/ath9k.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9003_phy.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9003_mac.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9003_hw.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9003_eeprom.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9003_calib.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9002_phy.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9002_mac.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9002_hw.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9002_calib.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ar5008_phy.c
  [DEPS] drivers/net/ath/ath9k/ath9k_ani.c
  [DEPS] drivers/net/ath/ath5k/ath5k_rfkill.c
  [DEPS] drivers/net/ath/ath5k/ath5k_reset.c
  [DEPS] drivers/net/ath/ath5k/ath5k_qcu.c
  [DEPS] drivers/net/ath/ath5k/ath5k_phy.c
  [DEPS] drivers/net/ath/ath5k/ath5k_pcu.c
  [DEPS] drivers/net/ath/ath5k/ath5k_initvals.c
  [DEPS] drivers/net/ath/ath5k/ath5k_gpio.c
  [DEPS] drivers/net/ath/ath5k/ath5k_eeprom.c
  [DEPS] drivers/net/ath/ath5k/ath5k_dma.c
  [DEPS] drivers/net/ath/ath5k/ath5k_desc.c
  [DEPS] drivers/net/ath/ath5k/ath5k_caps.c
  [DEPS] drivers/net/ath/ath5k/ath5k.c
  [DEPS] drivers/net/ath/ath5k/ath5k_attach.c
  [DEPS] drivers/net/ath/ath_regd.c
  [DEPS] drivers/net/ath/ath_key.c
  [DEPS] drivers/net/ath/ath_hw.c
  [DEPS] drivers/net/rtl818x/rtl818x.c
  [DEPS] drivers/net/rtl818x/rtl8185_rtl8225.c
  [DEPS] drivers/net/rtl818x/rtl8185.c
  [DEPS] drivers/net/rtl818x/rtl8180_sa2400.c
  [DEPS] drivers/net/rtl818x/rtl8180_max2820.c
  [DEPS] drivers/net/rtl818x/rtl8180_grf5101.c
  [DEPS] drivers/net/rtl818x/rtl8180.c
  [DEPS] net/80211/wpa_tkip.c
  [DEPS] net/80211/wpa_psk.c
  [DEPS] net/80211/wpa_ccmp.c
  [DEPS] net/80211/wpa.c
  [DEPS] net/80211/wep.c
  [DEPS] net/80211/sec80211.c
  [DEPS] net/80211/rc80211.c
  [DEPS] net/80211/net80211.c
  [DEPS] net/oncrpc/portmap.c
  [DEPS] net/oncrpc/oncrpc_iob.c
  [DEPS] net/oncrpc/nfs_uri.c
  [DEPS] net/oncrpc/nfs_open.c
  [DEPS] net/oncrpc/nfs.c
  [DEPS] net/oncrpc/mount.c
  [DEPS] arch/x86/drivers/net/undirom.c
  [DEPS] arch/x86/drivers/net/undipreload.c
  [DEPS] arch/x86/drivers/net/undionly.c
  [DEPS] arch/x86/drivers/net/undinet.c
  [DEPS] arch/x86/drivers/net/undiload.c
  [DEPS] arch/x86/drivers/net/undi.c
  [DEPS] arch/x86/transitions/librm_test.c
  [DEPS] arch/x86/transitions/librm_mgmt.c
  [DEPS] arch/x86/drivers/hyperv/hyperv.c
  [DEPS] arch/x86/drivers/xen/hvm.c
  [DEPS] arch/x86/hci/commands/pxe_cmd.c
  [DEPS] arch/x86/hci/commands/cpuid_cmd.c
  [DEPS] arch/x86/interface/syslinux/comboot_resolv.c
  [DEPS] arch/x86/interface/syslinux/comboot_call.c
  [DEPS] arch/x86/interface/syslinux/com32_call.c
  [DEPS] arch/x86/interface/vmware/vmconsole.c
  [DEPS] arch/x86/interface/vmware/guestrpc.c
  [DEPS] arch/x86/interface/vmware/guestinfo.c
  [DEPS] arch/x86/interface/efi/efix86_nap.c
  [DEPS] arch/x86/interface/pxe/pxe_undi.c
  [DEPS] arch/x86/interface/pxe/pxe_udp.c
  [DEPS] arch/x86/interface/pxe/pxe_tftp.c
  [DEPS] arch/x86/interface/pxe/pxe_preboot.c
  [DEPS] arch/x86/interface/pxe/pxe_loader.c
  [DEPS] arch/x86/interface/pxe/pxe_file.c
  [DEPS] arch/x86/interface/pxe/pxe_exit_hook.c
  [DEPS] arch/x86/interface/pxe/pxe_call.c
  [DEPS] arch/x86/interface/pcbios/vesafb.c
  [DEPS] arch/x86/interface/pcbios/rtc_time.c
  [DEPS] arch/x86/interface/pcbios/rtc_entropy.c
  [DEPS] arch/x86/interface/pcbios/rsdp.c
  [DEPS] arch/x86/interface/pcbios/pnpbios.c
  [DEPS] arch/x86/interface/pcbios/pcibios.c
  [DEPS] arch/x86/interface/pcbios/memtop_umalloc.c
  [DEPS] arch/x86/interface/pcbios/memmap.c
  [DEPS] arch/x86/interface/pcbios/int13con.c
  [DEPS] arch/x86/interface/pcbios/int13.c
  [DEPS] arch/x86/interface/pcbios/hidemem.c
  [DEPS] arch/x86/interface/pcbios/fakee820.c
  [DEPS] arch/x86/interface/pcbios/bios_timer.c
  [DEPS] arch/x86/interface/pcbios/bios_smbios.c
  [DEPS] arch/x86/interface/pcbios/bios_reboot.c
  [DEPS] arch/x86/interface/pcbios/bios_nap.c
  [DEPS] arch/x86/interface/pcbios/biosint.c
  [DEPS] arch/x86/interface/pcbios/bios_console.c
  [DEPS] arch/x86/interface/pcbios/basemem.c
  [DEPS] arch/x86/interface/pcbios/apm.c
  [DEPS] arch/x86/interface/pcbios/acpi_timer.c
  [DEPS] arch/x86/interface/pcbios/acpipwr.c
  [DEPS] arch/x86/image/sdi.c
  [DEPS] arch/x86/image/pxe_image.c
  [DEPS] arch/x86/image/nbi.c
  [DEPS] arch/x86/image/multiboot.c
  [DEPS] arch/x86/image/initrd.c
  [DEPS] arch/x86/image/elfboot.c
  [DEPS] arch/x86/image/comboot.c
  [DEPS] arch/x86/image/com32.c
  [DEPS] arch/x86/image/bzimage.c
  [DEPS] arch/x86/image/bootsector.c
  [DEPS] arch/x86/core/x86_uart.c
  [DEPS] arch/x86/core/x86_io.c
  [DEPS] arch/x86/core/vram_settings.c
  [DEPS] arch/x86/core/video_subr.c
  [DEPS] arch/x86/core/runtime.c
  [DEPS] arch/x86/core/relocate.c
  [DEPS] arch/x86/core/pit8254.c
  [DEPS] arch/x86/core/pic8259.c
  [DEPS] arch/x86/core/pcidirect.c
  [DEPS] arch/x86/core/pci_autoboot.c
  [DEPS] arch/x86/core/gdbmach.c
  [DEPS] arch/x86/core/dumpregs.c
  [DEPS] arch/x86/core/debugcon.c
  [DEPS] arch/x86/core/cpuid_settings.c
  [DEPS] arch/x86/core/cachedhcp.c
  [DEPS] arch/x86/core/basemem_packet.c
  [DEPS] config/config_usb.c
  [DEPS] config/config_timer.c
  [DEPS] config/config_route.c
  [DEPS] config/config_romprefix.c
  [DEPS] config/config_pixbuf.c
  [DEPS] config/config_pcbios.c
  [DEPS] config/config_net80211.c
  [DEPS] config/config_linux.c
  [DEPS] config/config_infiniband.c
  [DEPS] config/config_http.c
  [DEPS] config/config_fdt.c
  [DEPS] config/config_fc.c
  [DEPS] config/config_ethernet.c
  [DEPS] config/config_efi.c
  [DEPS] config/config_crypto.c
  [DEPS] config/config.c
  [DEPS] config/config_asn1.c
  [DEPS] usr/sync.c
  [DEPS] usr/route_ipv6.c
  [DEPS] usr/route_ipv4.c
  [DEPS] usr/route.c
  [DEPS] usr/pxemenu.c
  [DEPS] usr/profstat.c
  [DEPS] usr/pingmgmt.c
  [DEPS] usr/ntpmgmt.c
  [DEPS] usr/nslookup.c
  [DEPS] usr/neighmgmt.c
  [DEPS] usr/lotest.c
  [DEPS] usr/iwmgmt.c
  [DEPS] usr/imgtrust.c
  [DEPS] usr/imgmgmt.c
  [DEPS] usr/ifmgmt.c
  [DEPS] usr/ibmgmt.c
  [DEPS] usr/fcmgmt.c
  [DEPS] usr/dhcpmgmt.c
  [DEPS] usr/certmgmt.c
  [DEPS] usr/autoboot.c
  [DEPS] hci/mucurses/widgets/editbox.c
  [DEPS] hci/mucurses/windows.c
  [DEPS] hci/mucurses/slk.c
  [DEPS] hci/tui/settings_ui.c
  [DEPS] hci/tui/menu_ui.c
  [DEPS] hci/tui/login_ui.c
  [DEPS] hci/commands/vlan_cmd.c
  [DEPS] hci/commands/time_cmd.c
  [DEPS] hci/commands/sync_cmd.c
  [DEPS] hci/commands/sanboot_cmd.c
  [DEPS] hci/commands/route_cmd.c
  [DEPS] hci/commands/reboot_cmd.c
  [DEPS] hci/commands/profstat_cmd.c
  [DEPS] hci/commands/poweroff_cmd.c
  [DEPS] hci/commands/ping_cmd.c
  [DEPS] hci/commands/pci_cmd.c
  [DEPS] hci/commands/param_cmd.c
  [DEPS] hci/commands/nvo_cmd.c
  [DEPS] hci/commands/ntp_cmd.c
  [DEPS] hci/commands/nslookup_cmd.c
  [DEPS] hci/commands/neighbour_cmd.c
  [DEPS] hci/commands/menu_cmd.c
  [DEPS] hci/commands/lotest_cmd.c
  [DEPS] hci/commands/login_cmd.c
  [DEPS] hci/commands/iwmgmt_cmd.c
  [DEPS] hci/commands/ipstat_cmd.c
  [DEPS] hci/commands/image_trust_cmd.c
  [DEPS] hci/commands/image_cmd.c
  [DEPS] hci/commands/ifmgmt_cmd.c
  [DEPS] hci/commands/ibmgmt_cmd.c
  [DEPS] hci/commands/gdbstub_cmd.c
  [DEPS] hci/commands/fcmgmt_cmd.c
  [DEPS] hci/commands/digest_cmd.c
  [DEPS] hci/commands/dhcp_cmd.c
  [DEPS] hci/commands/console_cmd.c
  [DEPS] hci/commands/config_cmd.c
  [DEPS] hci/commands/cert_cmd.c
  [DEPS] hci/commands/autoboot_cmd.c
  [DEPS] hci/strerror.c
  [DEPS] hci/shell.c
  [DEPS] hci/readline.c
  [DEPS] hci/linux_args.c
  [DEPS] hci/jumpscroll.c
  [DEPS] hci/editstring.c
  [DEPS] crypto/mishmash/rsa_sha512.c
  [DEPS] crypto/mishmash/rsa_sha384.c
  [DEPS] crypto/mishmash/rsa_sha256.c
  [DEPS] crypto/mishmash/rsa_sha224.c
  [DEPS] crypto/mishmash/rsa_sha1.c
  [DEPS] crypto/mishmash/rsa_md5.c
  [DEPS] crypto/mishmash/rsa_aes_cbc_sha256.c
  [DEPS] crypto/mishmash/rsa_aes_cbc_sha1.c
  [DEPS] crypto/mishmash/oid_sha512.c
  [DEPS] crypto/mishmash/oid_sha512_256.c
  [DEPS] crypto/mishmash/oid_sha512_224.c
  [DEPS] crypto/mishmash/oid_sha384.c
  [DEPS] crypto/mishmash/oid_sha256.c
  [DEPS] crypto/mishmash/oid_sha224.c
  [DEPS] crypto/mishmash/oid_sha1.c
  [DEPS] crypto/mishmash/oid_rsa.c
  [DEPS] crypto/mishmash/oid_md5.c
  [DEPS] crypto/mishmash/oid_md4.c
  [DEPS] crypto/x509.c
  [DEPS] crypto/sha512.c
  [DEPS] crypto/sha256.c
  [DEPS] crypto/sha1.c
  [DEPS] crypto/rsa.c
  [DEPS] crypto/rootcert.c
  [DEPS] crypto/rbg.c
  [DEPS] crypto/privkey.c
  [DEPS] crypto/ocsp.c
  [DEPS] crypto/null_entropy.c
  [DEPS] crypto/ntlm.c
  [DEPS] crypto/md5.c
  [DEPS] crypto/md4.c
  [DEPS] crypto/hmac_drbg.c
  [DEPS] crypto/hmac.c
  [DEPS] crypto/hash_df.c
  [DEPS] crypto/entropy.c
  [DEPS] crypto/ecb.c
  [DEPS] crypto/drbg.c
  [DEPS] crypto/deflate.c
  [DEPS] crypto/cms.c
  [DEPS] crypto/chap.c
  [DEPS] crypto/certstore.c
  [DEPS] crypto/cbc.c
  [DEPS] crypto/bigint.c
  [DEPS] crypto/asn1.c
  [DEPS] crypto/aes_wrap.c
  [DEPS] crypto/aes.c
  [DEPS] tests/x509_test.c
  [DEPS] tests/uri_test.c
  [DEPS] tests/umalloc_test.c
  [DEPS] tests/time_test.c
  [DEPS] tests/test.c
  [DEPS] tests/tcpip_test.c
  [DEPS] tests/string_test.c
  [DEPS] tests/settings_test.c
  [DEPS] tests/setjmp_test.c
  [DEPS] tests/rsa_test.c
  [DEPS] tests/profile_test.c
  [DEPS] tests/pnm_test.c
  [DEPS] tests/png_test.c
  [DEPS] tests/pixbuf_test.c
  [DEPS] tests/pem_test.c
  [DEPS] tests/pccrc_test.c
  [DEPS] tests/ocsp_test.c
  [DEPS] tests/ntlm_test.c
  [DEPS] tests/memcpy_test.c
  [DEPS] tests/math_test.c
  [DEPS] tests/list_test.c
  [DEPS] tests/linebuf_test.c
  [DEPS] tests/ipv6_test.c
  [DEPS] tests/iobuf_test.c
  [DEPS] tests/hmac_drbg_test.c
  [DEPS] tests/hash_df_test.c
  [DEPS] tests/entropy_sample.c
  [DEPS] tests/dns_test.c
  [DEPS] tests/digest_test.c
  [DEPS] tests/der_test.c
  [DEPS] tests/deflate_test.c
  [DEPS] tests/cms_test.c
  [DEPS] tests/cipher_test.c
  [DEPS] tests/byteswap_test.c
  [DEPS] tests/bofm_test.c
  [DEPS] tests/bitops_test.c
  [DEPS] tests/bigint_test.c
  [DEPS] tests/asn1_test.c
  [DEPS] tests/aes_test.c
  [DEPS] interface/hyperv/vmbus.c
  [DEPS] interface/xen/xenstore.c
  [DEPS] interface/xen/xengrant.c
  [DEPS] interface/xen/xenbus.c
  [DEPS] interface/bofm/bofm.c
  [DEPS] interface/smbios/smbios_settings.c
  [DEPS] interface/smbios/smbios.c
  [DEPS] interface/efi/efi_watchdog.c
  [DEPS] interface/efi/efi_utils.c
  [DEPS] interface/efi/efi_usb.c
  [DEPS] interface/efi/efi_umalloc.c
  [DEPS] interface/efi/efi_uaccess.c
  [DEPS] interface/efi/efi_time.c
  [DEPS] interface/efi/efi_snp_hii.c
  [DEPS] interface/efi/efi_snp.c
  [DEPS] interface/efi/efi_smbios.c
  [DEPS] interface/efi/efi_reboot.c
  [DEPS] interface/efi/efi_pxe.c
  [DEPS] interface/efi/efiprefix.c
  [DEPS] interface/efi/efi_pci.c
  [DEPS] interface/efi/efi_local.c
  [DEPS] interface/efi/efi_init.c
  [DEPS] interface/efi/efi_hii.c
  [DEPS] interface/efi/efi_file.c
  [DEPS] interface/efi/efi_fbcon.c
  [DEPS] interface/efi/efi_entropy.c
  [DEPS] interface/efi/efidrvprefix.c
  [DEPS] interface/efi/efi_driver.c
  [DEPS] interface/efi/efi_download.c
  [DEPS] interface/efi/efi_console.c
  [DEPS] interface/efi/efi_bofm.c
  [DEPS] interface/efi/efi_block.c
  [DEPS] interface/efi/efi_blacklist.c
  [DEPS] interface/efi/efi_autoboot.c
  [DEPS] interface/efi/efi_acpi.c
  [DEPS] drivers/usb/xhci.c
  [DEPS] drivers/usb/usbnet.c
  [DEPS] drivers/usb/usbkbd.c
  [DEPS] drivers/usb/usbio.c
  [DEPS] drivers/usb/usbhub.c
  [DEPS] drivers/usb/usbhid.c
  [DEPS] drivers/usb/uhci.c
  [DEPS] drivers/usb/ehci.c
  [DEPS] drivers/infiniband/mlx_nodnic/src/mlx_port.c
  [DEPS] drivers/infiniband/mlx_nodnic/src/mlx_device.c
  [DEPS] drivers/infiniband/mlx_nodnic/src/mlx_cmd.c
  [DEPS] drivers/infiniband/mlx_utils/mlx_lib/mlx_mtu/mlx_mtu.c
  [DEPS] drivers/infiniband/mlx_utils/mlx_lib/mlx_link_speed/mlx_link_speed.c
  [DEPS] drivers/infiniband/mlx_utils/mlx_lib/mlx_blink_leds/mlx_blink_leds.c
  [DEPS] drivers/infiniband/mlx_utils/mlx_lib/mlx_vmac/mlx_vmac.c
  [DEPS] drivers/infiniband/mlx_utils/mlx_lib/mlx_nvconfig/mlx_nvconfig_defaults.c
  [DEPS] drivers/infiniband/mlx_utils/mlx_lib/mlx_nvconfig/mlx_nvconfig.c
  [DEPS] drivers/infiniband/mlx_utils/mlx_lib/mlx_reg_access/mlx_reg_access.c
  [DEPS] drivers/infiniband/mlx_utils/src/public/mlx_utils.c
  [DEPS] drivers/infiniband/mlx_utils/src/public/mlx_pci_gw.c
  [DEPS] drivers/infiniband/mlx_utils/src/public/mlx_pci.c
  [DEPS] drivers/infiniband/mlx_utils/src/public/mlx_memory.c
  [DEPS] drivers/infiniband/mlx_utils/src/public/mlx_icmd.c
  [DEPS] drivers/infiniband/mlx_utils_flexboot/src/mlx_utils_priv.c
  [DEPS] drivers/infiniband/mlx_utils_flexboot/src/mlx_pci_priv.c
  [DEPS] drivers/infiniband/mlx_utils_flexboot/src/mlx_memory_priv.c
  [DEPS] drivers/infiniband/qib7322.c
  [DEPS] drivers/infiniband/linda.c
  [DEPS] drivers/infiniband/hermon.c
  [DEPS] drivers/infiniband/golan.c
  [DEPS] drivers/infiniband/flexboot_nodnic.c
  [DEPS] drivers/infiniband/arbel.c
  [DEPS] drivers/bitbash/spi_bit.c
  [DEPS] drivers/bitbash/mii_bit.c
  [DEPS] drivers/bitbash/i2c_bit.c
  [DEPS] drivers/nvs/threewire.c
  [DEPS] drivers/nvs/nvsvpd.c
  [DEPS] drivers/nvs/nvs.c
  [DEPS] drivers/block/srp.c
  [DEPS] drivers/block/scsi.c
  [DEPS] drivers/block/ibft.c
  [DEPS] drivers/block/ata.c
  [DEPS] drivers/net/sfc/sfc_hunt.c
  [DEPS] drivers/net/sfc/efx_hunt.c
  [DEPS] drivers/net/sfc/efx_common.c
  [DEPS] drivers/net/bnxt/bnxt.c
  [DEPS] drivers/net/tg3/tg3_phy.c
  [DEPS] drivers/net/tg3/tg3_hw.c
  [DEPS] drivers/net/tg3/tg3.c
  [DEPS] drivers/net/efi/snponly.c
  [DEPS] drivers/net/efi/snpnet.c
  [DEPS] drivers/net/efi/snp.c
  [DEPS] drivers/net/efi/nii.c
  [DEPS] drivers/net/vxge/vxge_traffic.c
  [DEPS] drivers/net/vxge/vxge_main.c
  [DEPS] drivers/net/vxge/vxge_config.c
  [DEPS] drivers/net/vxge/vxge.c
  [DEPS] drivers/net/phantom/phantom.c
  [DEPS] drivers/net/igbvf/igbvf_vf.c
  [DEPS] drivers/net/igbvf/igbvf_mbx.c
  [DEPS] drivers/net/igbvf/igbvf_main.c
  [DEPS] drivers/net/w89c840.c
  [DEPS] drivers/net/vmxnet3.c
  [DEPS] drivers/net/virtio-net.c
  [DEPS] drivers/net/velocity.c
  [DEPS] drivers/net/tulip.c
  [DEPS] drivers/net/tlan.c
  [DEPS] drivers/net/thunderx.c
  [DEPS] drivers/net/sundance.c
  [DEPS] drivers/net/smscusb.c
  [DEPS] drivers/net/smsc95xx.c
  [DEPS] drivers/net/smsc75xx.c
  [DEPS] drivers/net/smc9000.c
  [DEPS] drivers/net/sky2.c
  [DEPS] drivers/net/skge.c
  [DEPS] drivers/net/skeleton.c
  [DEPS] drivers/net/sis900.c
  [DEPS] drivers/net/sis190.c
  [DEPS] drivers/net/rhine.c
  [DEPS] drivers/net/realtek.c
  [DEPS] drivers/net/prism2_plx.c
  [DEPS] drivers/net/prism2_pci.c
  [DEPS] drivers/net/pnic.c
  [DEPS] drivers/net/pcnet32.c
  [DEPS] drivers/net/ns8390.c
  [DEPS] drivers/net/netvsc.c
  [DEPS] drivers/net/netfront.c
  [DEPS] drivers/net/ne2k_isa.c
  [DEPS] drivers/net/ncm.c
  [DEPS] drivers/net/natsemi.c
  [DEPS] drivers/net/myson.c
  [DEPS] drivers/net/myri10ge.c
  [DEPS] drivers/net/mii.c
  [DEPS] drivers/net/legacy.c
  [DEPS] drivers/net/lan78xx.c
  [DEPS] drivers/net/jme.c
  [DEPS] drivers/net/ipoib.c
  [DEPS] drivers/net/intelxvf.c
  [DEPS] drivers/net/intelxlvf.c
  [DEPS] drivers/net/intelxl.c
  [DEPS] drivers/net/intelx.c
  [DEPS] drivers/net/intelvf.c
  [DEPS] drivers/net/intel.c
  [DEPS] drivers/net/icplus.c
  [DEPS] drivers/net/forcedeth.c
  [DEPS] drivers/net/exanic.c
  [DEPS] drivers/net/etherfabric.c
  [DEPS] drivers/net/epic100.c
  [DEPS] drivers/net/eoib.c
  [DEPS] drivers/net/ena.c
  [DEPS] drivers/net/eepro.c
  [DEPS] drivers/net/eepro100.c
  [DEPS] drivers/net/ecm.c
  [DEPS] drivers/net/dmfe.c
  [DEPS] drivers/net/dm96xx.c
  [DEPS] drivers/net/davicom.c
  [DEPS] drivers/net/cs89x0.c
  [DEPS] drivers/net/bnx2.c
  [DEPS] drivers/net/b44.c
  [DEPS] drivers/net/axge.c
  [DEPS] drivers/net/atl1e.c
  [DEPS] drivers/net/amd8111e.c
  [DEPS] drivers/net/acm.c
  [DEPS] drivers/net/3c90x.c
  [DEPS] drivers/net/3c5x9.c
  [DEPS] drivers/net/3c595.c
  [DEPS] drivers/net/3c529.c
  [DEPS] drivers/net/3c515.c
  [DEPS] drivers/net/3c509-eisa.c
  [DEPS] drivers/net/3c509.c
  [DEPS] drivers/bus/virtio-ring.c
  [DEPS] drivers/bus/virtio-pci.c
  [DEPS] drivers/bus/usb.c
  [DEPS] drivers/bus/pcivpd.c
  [DEPS] drivers/bus/pci_settings.c
  [DEPS] drivers/bus/pcimsix.c
  [DEPS] drivers/bus/pciextra.c
  [DEPS] drivers/bus/pciea.c
  [DEPS] drivers/bus/pci.c
  [DEPS] drivers/bus/pcibackup.c
  [DEPS] drivers/bus/mca.c
  [DEPS] drivers/bus/isapnp.c
  [DEPS] drivers/bus/isa.c
  [DEPS] drivers/bus/eisa.c
  [DEPS] drivers/bus/cdc.c
  [DEPS] image/segment.c
  [DEPS] image/script.c
  [DEPS] image/pnm.c
  [DEPS] image/png.c
  [DEPS] image/pem.c
  [DEPS] image/embedded.c
  [DEPS] image/elf.c
  [DEPS] image/efi_image.c
  [DEPS] image/der.c
  [DEPS] net/infiniband/xsigo.c
  [DEPS] net/infiniband/ib_srp.c
  [DEPS] net/infiniband/ib_smc.c
  [DEPS] net/infiniband/ib_sma.c
  [DEPS] net/infiniband/ib_service.c
  [DEPS] net/infiniband/ib_pathrec.c
  [DEPS] net/infiniband/ib_packet.c
  [DEPS] net/infiniband/ib_mi.c
  [DEPS] net/infiniband/ib_mcast.c
  [DEPS] net/infiniband/ib_cmrc.c
  [DEPS] net/infiniband/ib_cm.c
  [DEPS] net/udp/tftp.c
  [DEPS] net/udp/syslog.c
  [DEPS] net/udp/slam.c
  [DEPS] net/udp/ntp.c
  [DEPS] net/udp/dns.c
  [DEPS] net/udp/dhcpv6.c
  [DEPS] net/udp/dhcp.c
  [DEPS] net/tcp/syslogs.c
  [DEPS] net/tcp/oncrpc.c
  [DEPS] net/tcp/iscsi.c
  [DEPS] net/tcp/https.c
  [DEPS] net/tcp/httpntlm.c
  [DEPS] net/tcp/httpgce.c
  [DEPS] net/tcp/httpdigest.c
  [DEPS] net/tcp/httpcore.c
  [DEPS] net/tcp/httpconn.c
  [DEPS] net/tcp/http.c
  [DEPS] net/tcp/httpblock.c
  [DEPS] net/tcp/httpbasic.c
  [DEPS] net/tcp/httpauth.c
  [DEPS] net/tcp/ftp.c
  [DEPS] net/vlan.c
  [DEPS] net/validator.c
  [DEPS] net/udp.c
  [DEPS] net/tls.c
  [DEPS] net/tcpip.c
  [DEPS] net/tcp.c
  [DEPS] net/stp.c
  [DEPS] net/rndis.c
  [DEPS] net/retry.c
  [DEPS] net/rarp.c
  [DEPS] net/ping.c
  [DEPS] net/peermux.c
  [DEPS] net/peerdist.c
  [DEPS] net/peerdisc.c
  [DEPS] net/peerblk.c
  [DEPS] net/pccrd.c
  [DEPS] net/pccrc.c
  [DEPS] net/nullnet.c
  [DEPS] net/netdev_settings.c
  [DEPS] net/netdevice.c
  [DEPS] net/neighbour.c
  [DEPS] net/ndp.c
  [DEPS] net/ipv6.c
  [DEPS] net/ipv4.c
  [DEPS] net/iobpad.c
  [DEPS] net/infiniband.c
  [DEPS] net/icmpv6.c
  [DEPS] net/icmpv4.c
  [DEPS] net/icmp.c
  [DEPS] net/fragment.c
  [DEPS] net/fcp.c
  [DEPS] net/fcoe.c
  [DEPS] net/fcns.c
  [DEPS] net/fcels.c
  [DEPS] net/fc.c
  [DEPS] net/fakedhcp.c
  [DEPS] net/eth_slow.c
  [DEPS] net/ethernet.c
  [DEPS] net/eapol.c
  [DEPS] net/dhcppkt.c
  [DEPS] net/dhcpopts.c
  [DEPS] net/arp.c
  [DEPS] net/aoe.c
  [DEPS] core/xfer.c
  [DEPS] core/xferbuf.c
  [DEPS] core/uri.c
  [DEPS] core/uart.c
  [DEPS] core/timer.c
  [DEPS] core/time.c
  [DEPS] core/stringextra.c
  [DEPS] core/string.c
  [DEPS] core/settings.c
  [DEPS] core/serial.c
  [DEPS] core/sanboot.c
  [DEPS] core/resolv.c
  [DEPS] core/refcnt.c
  [DEPS] core/random.c
  [DEPS] core/profile.c
  [DEPS] core/process.c
  [DEPS] core/posix_io.c
  [DEPS] core/pool.c
  [DEPS] core/pixbuf.c
  [DEPS] core/pinger.c
  [DEPS] core/pending.c
  [DEPS] core/pc_kbd.c
  [DEPS] core/parseopt.c
  [DEPS] core/params.c
  [DEPS] core/open.c
  [DEPS] core/nvo.c
  [DEPS] core/null_time.c
  [DEPS] core/null_sanboot.c
  [DEPS] core/null_reboot.c
  [DEPS] core/null_nap.c
  [DEPS] core/null_acpi.c
  [DEPS] core/monojob.c
  [DEPS] core/menu.c
  [DEPS] core/memmap_settings.c
  [DEPS] core/malloc.c
  [DEPS] core/main.c
  [DEPS] core/log.c
  [DEPS] core/list.c
  [DEPS] core/linebuf.c
  [DEPS] core/job.c
  [DEPS] core/iomap_virt.c
  [DEPS] core/iobuf.c
  [DEPS] core/interface.c
  [DEPS] core/init.c
  [DEPS] core/image.c
  [DEPS] core/hw.c
  [DEPS] core/getkey.c
  [DEPS] core/gdbudp.c
  [DEPS] core/gdbstub.c
  [DEPS] core/gdbserial.c
  [DEPS] core/fnrec.c
  [DEPS] core/fdt.c
  [DEPS] core/fbcon.c
  [DEPS] core/fault.c
  [DEPS] core/exec.c
  [DEPS] core/edd.c
  [DEPS] core/dummy_sanboot.c
  [DEPS] core/downloader.c
  [DEPS] core/device.c
  [DEPS] core/cwuri.c
  [DEPS] core/console.c
  [DEPS] core/blocktrans.c
  [DEPS] core/blockdev.c
  [DEPS] core/bitmap.c
  [DEPS] core/base64.c
  [DEPS] core/base16.c
  [DEPS] core/assert.c
  [DEPS] core/asprintf.c
  [DEPS] core/ansiesc.c
  [DEPS] core/ansicoldef.c
  [DEPS] core/ansicol.c
  [DEPS] core/acpi_settings.c
  [DEPS] core/acpi.c
  [BUILD] bin/__divdi3.o
  [BUILD] bin/__divmoddi4.o
  [BUILD] bin/icc.o
  [BUILD] bin/implicit.o
  [BUILD] bin/__moddi3.o
  [BUILD] bin/__udivdi3.o
  [BUILD] bin/__udivmoddi4.o
  [BUILD] bin/__umoddi3.o
  [BUILD] bin/acpi.o
  [BUILD] bin/acpi_settings.o
  [BUILD] bin/ansicol.o
  [BUILD] bin/ansicoldef.o
  [BUILD] bin/ansiesc.o
  [BUILD] bin/asprintf.o
  [BUILD] bin/assert.o
  [BUILD] bin/base16.o
  [BUILD] bin/base64.o
  [BUILD] bin/basename.o
  [BUILD] bin/bitmap.o
  [BUILD] bin/blockdev.o
  [BUILD] bin/blocktrans.o
  [BUILD] bin/console.o
  [BUILD] bin/cpio.o
  [BUILD] bin/ctype.o
  [BUILD] bin/cwuri.o
  [BUILD] bin/debug.o
  [BUILD] bin/debug_md5.o
  [BUILD] bin/device.o
  [BUILD] bin/downloader.o
  [BUILD] bin/dummy_sanboot.o
  [BUILD] bin/edd.o
  [BUILD] bin/errno.o
  [BUILD] bin/exec.o
  [BUILD] bin/fault.o
  [BUILD] bin/fbcon.o
  [BUILD] bin/fdt.o
  [BUILD] bin/fnrec.o
  [BUILD] bin/gdbserial.o
  [BUILD] bin/gdbstub.o
  [BUILD] bin/gdbudp.o
  [BUILD] bin/getkey.o
  [BUILD] bin/getopt.o
  [BUILD] bin/hw.o
  [BUILD] bin/i82365.o
  [BUILD] bin/image.o
  [BUILD] bin/init.o
  [BUILD] bin/interface.o
  [BUILD] bin/iobuf.o
  [BUILD] bin/iomap_virt.o
  [BUILD] bin/isqrt.o
  [BUILD] bin/job.o
  [BUILD] bin/linebuf.o
  [BUILD] bin/lineconsole.o
  [BUILD] bin/list.o
  [BUILD] bin/log.o
  [BUILD] bin/main.o
  [BUILD] bin/malloc.o
  [BUILD] bin/memmap_settings.o
  [BUILD] bin/menu.o
  [BUILD] bin/monojob.o
  [BUILD] bin/netbios.o
  [BUILD] bin/null_acpi.o
  [BUILD] bin/null_nap.o
  [BUILD] bin/null_reboot.o
  [BUILD] bin/null_sanboot.o
  [BUILD] bin/null_time.o
  [BUILD] bin/nvo.o
  [BUILD] bin/open.o
  [BUILD] bin/params.o
  [BUILD] bin/parseopt.o
  [BUILD] bin/pc_kbd.o
  [BUILD] bin/pcmcia.o
  [BUILD] bin/pending.o
  [BUILD] bin/pinger.o
  [BUILD] bin/pixbuf.o
  [BUILD] bin/pool.o
  [BUILD] bin/posix_io.o
  [BUILD] bin/process.o
  [BUILD] bin/profile.o
  [BUILD] bin/quiesce.o
  [BUILD] bin/random.o
  [BUILD] bin/refcnt.o
  [BUILD] bin/resolv.o
  [BUILD] bin/sanboot.o
  [BUILD] bin/serial.o
  [BUILD] bin/settings.o
  [BUILD] bin/string.o
  [BUILD] bin/stringextra.o
  [BUILD] bin/time.o
  [BUILD] bin/timer.o
  [BUILD] bin/uart.o
  [BUILD] bin/uri.o
  [BUILD] bin/uuid.o
  [BUILD] bin/vsprintf.o
  [BUILD] bin/wchar.o
  [BUILD] bin/xferbuf.o
  [BUILD] bin/xfer.o
  [BUILD] bin/aoe.o
  [BUILD] bin/arp.o
  [BUILD] bin/dhcpopts.o
  [BUILD] bin/dhcppkt.o
  [BUILD] bin/eapol.o
  [BUILD] bin/ethernet.o
  [BUILD] bin/eth_slow.o
  [BUILD] bin/fakedhcp.o
  [BUILD] bin/fc.o
  [BUILD] bin/fcels.o
  [BUILD] bin/fcns.o
  [BUILD] bin/fcoe.o
  [BUILD] bin/fcp.o
  [BUILD] bin/fragment.o
  [BUILD] bin/icmp.o
  [BUILD] bin/icmpv4.o
  [BUILD] bin/icmpv6.o
  [BUILD] bin/infiniband.o
  [BUILD] bin/iobpad.o
  [BUILD] bin/ipv4.o
  [BUILD] bin/ipv6.o
  [BUILD] bin/ndp.o
  [BUILD] bin/neighbour.o
  [BUILD] bin/netdevice.o
  [BUILD] bin/netdev_settings.o
  [BUILD] bin/nullnet.o
  [BUILD] bin/pccrc.o
  [BUILD] bin/pccrd.o
  [BUILD] bin/peerblk.o
  [BUILD] bin/peerdisc.o
  [BUILD] bin/peerdist.o
  [BUILD] bin/peermux.o
  [BUILD] bin/ping.o
  [BUILD] bin/rarp.o
  [BUILD] bin/retry.o
  [BUILD] bin/rndis.o
  [BUILD] bin/socket.o
  [BUILD] bin/stp.o
  [BUILD] bin/tcp.o
  [BUILD] bin/tcpip.o
  [BUILD] bin/tls.o
  [BUILD] bin/udp.o
  [BUILD] bin/validator.o
  [BUILD] bin/vlan.o
  [BUILD] bin/ftp.o
  [BUILD] bin/httpauth.o
  [BUILD] bin/httpbasic.o
  [BUILD] bin/httpblock.o
  [BUILD] bin/http.o
  [BUILD] bin/httpconn.o
  [BUILD] bin/httpcore.o
  [BUILD] bin/httpdigest.o
  [BUILD] bin/httpgce.o
  [BUILD] bin/httpntlm.o
  [BUILD] bin/https.o
  [BUILD] bin/iscsi.o
  [BUILD] bin/oncrpc.o
  [BUILD] bin/syslogs.o
  [BUILD] bin/dhcp.o
  [BUILD] bin/dhcpv6.o
  [BUILD] bin/dns.o
  [BUILD] bin/ntp.o
  [BUILD] bin/slam.o
  [BUILD] bin/syslog.o
  [BUILD] bin/tftp.o
  [BUILD] bin/ib_cm.o
  [BUILD] bin/ib_cmrc.o
  [BUILD] bin/ib_mcast.o
  [BUILD] bin/ib_mi.o
  [BUILD] bin/ib_packet.o
  [BUILD] bin/ib_pathrec.o
  [BUILD] bin/ib_service.o
  [BUILD] bin/ib_sma.o
  [BUILD] bin/ib_smc.o
  [BUILD] bin/ib_srp.o
  [BUILD] bin/xsigo.o
  [BUILD] bin/der.o
  [BUILD] bin/efi_image.o
  [BUILD] bin/elf.o
  [BUILD] bin/embedded.o
  [BUILD] bin/pem.o
  [BUILD] bin/png.o
  [BUILD] bin/pnm.o
  [BUILD] bin/script.o
  [BUILD] bin/segment.o
  [BUILD] bin/cdc.o
  [BUILD] bin/eisa.o
  [BUILD] bin/isa.o
  [BUILD] bin/isa_ids.o
  [BUILD] bin/isapnp.o
  [BUILD] bin/mca.o
  [BUILD] bin/pcibackup.o
  [BUILD] bin/pci.o
  [BUILD] bin/pciea.o
  [BUILD] bin/pciextra.o
  [BUILD] bin/pcimsix.o
  [BUILD] bin/pci_settings.o
  [BUILD] bin/pcivpd.o
  [BUILD] bin/usb.o
  [BUILD] bin/virtio-pci.o
  [BUILD] bin/virtio-ring.o
  [BUILD] bin/3c503.o
  [BUILD] bin/3c509.o
  [BUILD] bin/3c509-eisa.o
  [BUILD] bin/3c515.o
  [BUILD] bin/3c529.o
  [BUILD] bin/3c595.o
  [BUILD] bin/3c5x9.o
  [BUILD] bin/3c90x.o
  [BUILD] bin/acm.o
  [BUILD] bin/amd8111e.o
  [BUILD] bin/atl1e.o
  [BUILD] bin/axge.o
  [BUILD] bin/b44.o
  [BUILD] bin/bnx2.o
  [BUILD] bin/cs89x0.o
  [BUILD] bin/davicom.o
  [BUILD] bin/depca.o
  [BUILD] bin/dm96xx.o
  [BUILD] bin/dmfe.o
  [BUILD] bin/ecm.o
  [BUILD] bin/eepro100.o
  [BUILD] bin/eepro.o
  [BUILD] bin/ena.o
  [BUILD] bin/eoib.o
  [BUILD] bin/epic100.o
  [BUILD] bin/etherfabric.o
  [BUILD] bin/exanic.o
  [BUILD] bin/forcedeth.o
  [BUILD] bin/icplus.o
  [BUILD] bin/intel.o
  [BUILD] bin/intelvf.o
  [BUILD] bin/intelx.o
  [BUILD] bin/intelxl.o
  [BUILD] bin/intelxlvf.o
  [BUILD] bin/intelxvf.o
  [BUILD] bin/ipoib.o
  [BUILD] bin/jme.o
  [BUILD] bin/lan78xx.o
  [BUILD] bin/legacy.o
  [BUILD] bin/mii.o
  [BUILD] bin/myri10ge.o
  [BUILD] bin/myson.o
  [BUILD] bin/natsemi.o
  [BUILD] bin/ncm.o
  [BUILD] bin/ne2k_isa.o
  [BUILD] bin/ne.o
  [BUILD] bin/netfront.o
  [BUILD] bin/netvsc.o
  [BUILD] bin/ns8390.o
  [BUILD] bin/pcnet32.o
  [BUILD] bin/pnic.o
  [BUILD] bin/prism2_pci.o
  [BUILD] bin/prism2_plx.o
  [BUILD] bin/realtek.o
  [BUILD] bin/rhine.o
  [BUILD] bin/sis190.o
  [BUILD] bin/sis900.o
  [BUILD] bin/skeleton.o
  [BUILD] bin/skge.o
  [BUILD] bin/sky2.o
  [BUILD] bin/smc9000.o
  [BUILD] bin/smsc75xx.o
  [BUILD] bin/smsc95xx.o
  [BUILD] bin/smscusb.o
  [BUILD] bin/sundance.o
  [BUILD] bin/thunderx.o
  [BUILD] bin/tlan.o
  [BUILD] bin/tulip.o
  [BUILD] bin/velocity.o
  [BUILD] bin/virtio-net.o
  [BUILD] bin/vmxnet3.o
  [BUILD] bin/w89c840.o
  [BUILD] bin/wd.o
  [BUILD] bin/igbvf_main.o
  [BUILD] bin/igbvf_mbx.o
  [BUILD] bin/igbvf_vf.o
  [BUILD] bin/phantom.o
  [BUILD] bin/vxge.o
  [BUILD] bin/vxge_config.o
  [BUILD] bin/vxge_main.o
  [BUILD] bin/vxge_traffic.o
  [BUILD] bin/nii.o
  [BUILD] bin/snp.o
  [BUILD] bin/snpnet.o
  [BUILD] bin/snponly.o
  [BUILD] bin/tg3.o
  [BUILD] bin/tg3_hw.o
  [BUILD] bin/tg3_phy.o
  [BUILD] bin/bnxt.o
  [BUILD] bin/efx_common.o
  [BUILD] bin/efx_hunt.o
  [BUILD] bin/sfc_hunt.o
  [BUILD] bin/ata.o
  [BUILD] bin/ibft.o
  [BUILD] bin/scsi.o
  [BUILD] bin/srp.o
  [BUILD] bin/nvs.o
  [BUILD] bin/nvsvpd.o
  [BUILD] bin/spi.o
  [BUILD] bin/threewire.o
  [BUILD] bin/bitbash.o
  [BUILD] bin/i2c_bit.o
  [BUILD] bin/mii_bit.o
  [BUILD] bin/spi_bit.o
  [BUILD] bin/arbel.o
  [BUILD] bin/flexboot_nodnic.o
  [BUILD] bin/golan.o
  [BUILD] bin/hermon.o
  [BUILD] bin/linda.o
  [BUILD] bin/linda_fw.o
  [BUILD] bin/qib7322.o
  [BUILD] bin/mlx_memory_priv.o
  [BUILD] bin/mlx_pci_priv.o
  [BUILD] bin/mlx_utils_priv.o
  [BUILD] bin/mlx_icmd.o
  [BUILD] bin/mlx_memory.o
  [BUILD] bin/mlx_pci.o
  [BUILD] bin/mlx_pci_gw.o
  [BUILD] bin/mlx_utils.o
  [BUILD] bin/mlx_reg_access.o
  [BUILD] bin/mlx_nvconfig.o
  [BUILD] bin/mlx_nvconfig_defaults.o
  [BUILD] bin/mlx_vmac.o
  [BUILD] bin/mlx_blink_leds.o
  [BUILD] bin/mlx_link_speed.o
  [BUILD] bin/mlx_mtu.o
  [BUILD] bin/mlx_cmd.o
  [BUILD] bin/mlx_device.o
  [BUILD] bin/mlx_port.o
  [BUILD] bin/ehci.o
  [BUILD] bin/uhci.o
  [BUILD] bin/usbhid.o
  [BUILD] bin/usbhub.o
  [BUILD] bin/usbio.o
  [BUILD] bin/usbkbd.o
  [BUILD] bin/usbnet.o
  [BUILD] bin/xhci.o
  [BUILD] bin/efi_acpi.o
  [BUILD] bin/efi_autoboot.o
  [BUILD] bin/efi_blacklist.o
  [BUILD] bin/efi_block.o
  [BUILD] bin/efi_bofm.o
  [BUILD] bin/efi_console.o
  [BUILD] bin/efi_debug.o
  [BUILD] bin/efi_download.o
  [BUILD] bin/efi_driver.o
  [BUILD] bin/efidrvprefix.o
  [BUILD] bin/efi_entropy.o
  [BUILD] bin/efi_fbcon.o
  [BUILD] bin/efi_fdt.o
  [BUILD] bin/efi_file.o
  [BUILD] bin/efi_guid.o
  [BUILD] bin/efi_hii.o
  [BUILD] bin/efi_init.o
  [BUILD] bin/efi_local.o
  [BUILD] bin/efi_pci.o
  [BUILD] bin/efiprefix.o
  [BUILD] bin/efi_pxe.o
  [BUILD] bin/efi_reboot.o
  [BUILD] bin/efi_smbios.o
  [BUILD] bin/efi_snp.o
  [BUILD] bin/efi_snp_hii.o
  [BUILD] bin/efi_strings.o
  [BUILD] bin/efi_time.o
  [BUILD] bin/efi_timer.o
  [BUILD] bin/efi_uaccess.o
  [BUILD] bin/efi_umalloc.o
  [BUILD] bin/efi_usb.o
  [BUILD] bin/efi_utils.o
  [BUILD] bin/efi_watchdog.o
  [BUILD] bin/efi_wrap.o
  [BUILD] bin/smbios.o
  [BUILD] bin/smbios_settings.o
  [BUILD] bin/bofm.o
  [BUILD] bin/xenbus.o
  [BUILD] bin/xengrant.o
  [BUILD] bin/xenstore.o
  [BUILD] bin/vmbus.o
  [BUILD] bin/aes_test.o
  [BUILD] bin/asn1_test.o
  [BUILD] bin/base16_test.o
  [BUILD] bin/base64_test.o
  [BUILD] bin/bigint_test.o
  [BUILD] bin/bitops_test.o
  [BUILD] bin/bofm_test.o
  [BUILD] bin/byteswap_test.o
  [BUILD] bin/cipher_test.o
  [BUILD] bin/cms_test.o
  [BUILD] bin/crc32_test.o
  [BUILD] bin/deflate_test.o
  [BUILD] bin/der_test.o
  [BUILD] bin/digest_test.o
  [BUILD] bin/dns_test.o
  [BUILD] bin/entropy_sample.o
  [BUILD] bin/hash_df_test.o
  [BUILD] bin/hmac_drbg_test.o
  [BUILD] bin/iobuf_test.o
  [BUILD] bin/ipv4_test.o
  [BUILD] bin/ipv6_test.o
  [BUILD] bin/linebuf_test.o
  [BUILD] bin/list_test.o
  [BUILD] bin/math_test.o
  [BUILD] bin/md4_test.o
  [BUILD] bin/md5_test.o
  [BUILD] bin/memcpy_test.o
  [BUILD] bin/memset_test.o
  [BUILD] bin/ntlm_test.o
  [BUILD] bin/ocsp_test.o
  [BUILD] bin/pccrc_test.o
  [BUILD] bin/pem_test.o
  [BUILD] bin/pixbuf_test.o
  [BUILD] bin/png_test.o
  [BUILD] bin/pnm_test.o
  [BUILD] bin/profile_test.o
  [BUILD] bin/rsa_test.o
  [BUILD] bin/setjmp_test.o
  [BUILD] bin/settings_test.o
  [BUILD] bin/sha1_test.o
  [BUILD] bin/sha256_test.o
  [BUILD] bin/sha512_test.o
  [BUILD] bin/string_test.o
  [BUILD] bin/tcpip_test.o
  [BUILD] bin/test.o
  [BUILD] bin/tests.o
  [BUILD] bin/time_test.o
  [BUILD] bin/umalloc_test.o
  [BUILD] bin/uri_test.o
  [BUILD] bin/vsprintf_test.o
  [BUILD] bin/x509_test.o
  [BUILD] bin/aes.o
  [BUILD] bin/aes_wrap.o
  [BUILD] bin/arc4.o
  [BUILD] bin/asn1.o
  [BUILD] bin/bigint.o
  [BUILD] bin/cbc.o
  [BUILD] bin/certstore.o
  [BUILD] bin/chap.o
  [BUILD] bin/cms.o
  [BUILD] bin/crc32.o
  [BUILD] bin/crypto_null.o
  [BUILD] bin/deflate.o
  [BUILD] bin/drbg.o
  [BUILD] bin/ecb.o
  [BUILD] bin/entropy.o
  [BUILD] bin/hash_df.o
  [BUILD] bin/hmac.o
  [BUILD] bin/hmac_drbg.o
  [BUILD] bin/md4.o
  [BUILD] bin/md5.o
  [BUILD] bin/ntlm.o
  [BUILD] bin/null_entropy.o
  [BUILD] bin/ocsp.o
  [BUILD] bin/privkey.o
  [BUILD] bin/random_nz.o
  [BUILD] bin/rbg.o
  [BUILD] bin/rootcert.o
  [BUILD] bin/rsa.o
  [BUILD] bin/sha1.o
  [BUILD] bin/sha1extra.o
  [BUILD] bin/sha224.o
  [BUILD] bin/sha256.o
  [BUILD] bin/sha384.o
  [BUILD] bin/sha512_224.o
  [BUILD] bin/sha512_256.o
  [BUILD] bin/sha512.o
  [BUILD] bin/x509.o
  [BUILD] bin/oid_md4.o
  [BUILD] bin/oid_md5.o
  [BUILD] bin/oid_rsa.o
  [BUILD] bin/oid_sha1.o
  [BUILD] bin/oid_sha224.o
  [BUILD] bin/oid_sha256.o
  [BUILD] bin/oid_sha384.o
  [BUILD] bin/oid_sha512_224.o
  [BUILD] bin/oid_sha512_256.o
  [BUILD] bin/oid_sha512.o
  [BUILD] bin/rsa_aes_cbc_sha1.o
  [BUILD] bin/rsa_aes_cbc_sha256.o
  [BUILD] bin/rsa_md5.o
  [BUILD] bin/rsa_sha1.o
  [BUILD] bin/rsa_sha224.o
  [BUILD] bin/rsa_sha256.o
  [BUILD] bin/rsa_sha384.o
  [BUILD] bin/rsa_sha512.o
  [BUILD] bin/editstring.o
  [BUILD] bin/jumpscroll.o
  [BUILD] bin/linux_args.o
  [BUILD] bin/readline.o
  [BUILD] bin/shell.o
  [BUILD] bin/strerror.o
  [BUILD] bin/wireless_errors.o
  [BUILD] bin/autoboot_cmd.o
  [BUILD] bin/cert_cmd.o
  [BUILD] bin/config_cmd.o
  [BUILD] bin/console_cmd.o
  [BUILD] bin/dhcp_cmd.o
  [BUILD] bin/digest_cmd.o
  [BUILD] bin/fcmgmt_cmd.o
  [BUILD] bin/gdbstub_cmd.o
  [BUILD] bin/ibmgmt_cmd.o
  [BUILD] bin/ifmgmt_cmd.o
  [BUILD] bin/image_cmd.o
  [BUILD] bin/image_trust_cmd.o
  [BUILD] bin/ipstat_cmd.o
  [BUILD] bin/iwmgmt_cmd.o
  [BUILD] bin/login_cmd.o
  [BUILD] bin/lotest_cmd.o
  [BUILD] bin/menu_cmd.o
  [BUILD] bin/neighbour_cmd.o
  [BUILD] bin/nslookup_cmd.o
  [BUILD] bin/ntp_cmd.o
  [BUILD] bin/nvo_cmd.o
  [BUILD] bin/param_cmd.o
  [BUILD] bin/pci_cmd.o
  [BUILD] bin/ping_cmd.o
  [BUILD] bin/poweroff_cmd.o
  [BUILD] bin/profstat_cmd.o
  [BUILD] bin/reboot_cmd.o
  [BUILD] bin/route_cmd.o
  [BUILD] bin/sanboot_cmd.o
  [BUILD] bin/sync_cmd.o
  [BUILD] bin/time_cmd.o
  [BUILD] bin/vlan_cmd.o
  [BUILD] bin/login_ui.o
  [BUILD] bin/menu_ui.o
  [BUILD] bin/settings_ui.o
  [BUILD] bin/alert.o
  [BUILD] bin/ansi_screen.o
  [BUILD] bin/clear.o
  [BUILD] bin/colour.o
  [BUILD] bin/edging.o
  [BUILD] bin/kb.o
  [BUILD] bin/mucurses.o
  [BUILD] bin/print.o
  [BUILD] bin/print_nadv.o
  [BUILD] bin/slk.o
  [BUILD] bin/winattrs.o
  [BUILD] bin/windows.o
  [BUILD] bin/wininit.o
  [BUILD] bin/editbox.o
  [BUILD] bin/keymap_al.o
  [BUILD] bin/keymap_az.o
  [BUILD] bin/keymap_bg.o
  [BUILD] bin/keymap_by.o
  [BUILD] bin/keymap_cf.o
  [BUILD] bin/keymap_cz.o
  [BUILD] bin/keymap_de.o
  [BUILD] bin/keymap_dk.o
  [BUILD] bin/keymap_es.o
  [BUILD] bin/keymap_et.o
  [BUILD] bin/keymap_fi.o
  [BUILD] bin/keymap_fr.o
  [BUILD] bin/keymap_gr.o
  [BUILD] bin/keymap_hu.o
  [BUILD] bin/keymap_il.o
  [BUILD] bin/keymap_it.o
  [BUILD] bin/keymap_lt.o
  [BUILD] bin/keymap_mk.o
  [BUILD] bin/keymap_mt.o
  [BUILD] bin/keymap_nl.o
  [BUILD] bin/keymap_no.o
  [BUILD] bin/keymap_no-latin1.o
  [BUILD] bin/keymap_pl.o
  [BUILD] bin/keymap_pt.o
  [BUILD] bin/keymap_ro.o
  [BUILD] bin/keymap_ru.o
  [BUILD] bin/keymap_sg.o
  [BUILD] bin/keymap_sr.o
  [BUILD] bin/keymap_th.o
  [BUILD] bin/keymap_ua.o
  [BUILD] bin/keymap_uk.o
  [BUILD] bin/keymap_us.o
  [BUILD] bin/keymap_wo.o
  [BUILD] bin/autoboot.o
  [BUILD] bin/certmgmt.o
  [BUILD] bin/dhcpmgmt.o
  [BUILD] bin/fcmgmt.o
  [BUILD] bin/ibmgmt.o
  [BUILD] bin/ifmgmt.o
  [BUILD] bin/imgmgmt.o
  [BUILD] bin/imgtrust.o
  [BUILD] bin/ipstat.o
  [BUILD] bin/iwmgmt.o
  [BUILD] bin/lotest.o
  [BUILD] bin/neighmgmt.o
  [BUILD] bin/nslookup.o
  [BUILD] bin/ntpmgmt.o
  [BUILD] bin/pingmgmt.o
  [BUILD] bin/profstat.o
  [BUILD] bin/prompt.o
  [BUILD] bin/pxemenu.o
  [BUILD] bin/route.o
  [BUILD] bin/route_ipv4.o
  [BUILD] bin/route_ipv6.o
  [BUILD] bin/sync.o
  [BUILD] bin/config_asn1.o
  [BUILD] bin/config.o
  [BUILD] bin/config_crypto.o
  [BUILD] bin/config_efi.o
  [BUILD] bin/config_ethernet.o
  [BUILD] bin/config_fc.o
  [BUILD] bin/config_fdt.o
  [BUILD] bin/config_http.o
  [BUILD] bin/config_infiniband.o
  [BUILD] bin/config_linux.o
  [BUILD] bin/config_net80211.o
  [BUILD] bin/config_pcbios.o
  [BUILD] bin/config_pixbuf.o
  [BUILD] bin/config_romprefix.o
  [BUILD] bin/config_route.o
  [BUILD] bin/config_timer.o
  [BUILD] bin/config_usb.o
  [BUILD] bin/nulltrap.o
  [BUILD] bin/basemem_packet.o
  [BUILD] bin/cachedhcp.o
  [BUILD] bin/cpuid.o
  [BUILD] bin/cpuid_settings.o
  [BUILD] bin/debugcon.o
  [BUILD] bin/dumpregs.o
  [BUILD] bin/gdbmach.o
  [BUILD] bin/pci_autoboot.o
  [BUILD] bin/pcidirect.o
  [BUILD] bin/pic8259.o
  [BUILD] bin/pit8254.o
  [BUILD] bin/rdtsc_timer.o
  [BUILD] bin/relocate.o
  [BUILD] bin/runtime.o
  [BUILD] bin/video_subr.o
  [BUILD] bin/vram_settings.o
  [BUILD] bin/x86_bigint.o
  [BUILD] bin/x86_io.o
  [BUILD] bin/x86_string.o
  [BUILD] bin/x86_tcpip.o
  [BUILD] bin/x86_uart.o
  [BUILD] bin/bootsector.o
  [BUILD] bin/bzimage.o
  [BUILD] bin/com32.o
  [BUILD] bin/comboot.o
  [BUILD] bin/elfboot.o
  [BUILD] bin/initrd.o
  [BUILD] bin/multiboot.o
  [BUILD] bin/nbi.o
  [BUILD] bin/pxe_image.o
  [BUILD] bin/sdi.o
  [BUILD] bin/acpipwr.o
  [BUILD] bin/acpi_timer.o
  [BUILD] bin/apm.o
  [BUILD] bin/basemem.o
  [BUILD] bin/bios_console.o
  [BUILD] bin/biosint.o
  [BUILD] bin/bios_nap.o
  [BUILD] bin/bios_reboot.o
  [BUILD] bin/bios_smbios.o
  [BUILD] bin/bios_timer.o
  [BUILD] bin/fakee820.o
  [BUILD] bin/hidemem.o
  [BUILD] bin/int13.o
  [BUILD] bin/int13con.o
  [BUILD] bin/memmap.o
  [BUILD] bin/memtop_umalloc.o
  [BUILD] bin/pcibios.o
  [BUILD] bin/pnpbios.o
  [BUILD] bin/rsdp.o
  [BUILD] bin/rtc_entropy.o
  [BUILD] bin/rtc_time.o
  [BUILD] bin/vesafb.o
  [BUILD] bin/pxe_call.o
  [BUILD] bin/pxe_exit_hook.o
  [BUILD] bin/pxe_file.o
  [BUILD] bin/pxe_loader.o
  [BUILD] bin/pxe_preboot.o
  [BUILD] bin/pxe_tftp.o
  [BUILD] bin/pxe_udp.o
  [BUILD] bin/pxe_undi.o
  [BUILD] bin/efix86_nap.o
  [BUILD] bin/guestinfo.o
  [BUILD] bin/guestrpc.o
  [BUILD] bin/vmconsole.o
  [BUILD] bin/vmware.o
  [BUILD] bin/com32_call.o
  [BUILD] bin/comboot_call.o
  [BUILD] bin/comboot_resolv.o
  [BUILD] bin/cpuid_cmd.o
  [BUILD] bin/pxe_cmd.o
  [BUILD] bin/hvm.o
  [BUILD] bin/hyperv.o
  [BUILD] bin/librm_mgmt.o
  [BUILD] bin/librm_test.o
  [BUILD] bin/undi.o
  [BUILD] bin/undiload.o
  [BUILD] bin/undinet.o
  [BUILD] bin/undionly.o
  [BUILD] bin/undipreload.o
  [BUILD] bin/undirom.o
  [BUILD] bin/mount.o
  [BUILD] bin/nfs.o
  [BUILD] bin/nfs_open.o
  [BUILD] bin/nfs_uri.o
  [BUILD] bin/oncrpc_iob.o
  [BUILD] bin/portmap.o
  [BUILD] bin/net80211.o
  [BUILD] bin/rc80211.o
  [BUILD] bin/sec80211.o
  [BUILD] bin/wep.o
  [BUILD] bin/wpa.o
  [BUILD] bin/wpa_ccmp.o
  [BUILD] bin/wpa_psk.o
  [BUILD] bin/wpa_tkip.o
  [BUILD] bin/rtl8180.o
  [BUILD] bin/rtl8180_grf5101.o
  [BUILD] bin/rtl8180_max2820.o
  [BUILD] bin/rtl8180_sa2400.o
  [BUILD] bin/rtl8185.o
  [BUILD] bin/rtl8185_rtl8225.o
  [BUILD] bin/rtl818x.o
  [BUILD] bin/ath_hw.o
  [BUILD] bin/ath_key.o
  [BUILD] bin/ath_regd.o
  [BUILD] bin/ath5k_attach.o
  [BUILD] bin/ath5k.o
  [BUILD] bin/ath5k_caps.o
  [BUILD] bin/ath5k_desc.o
  [BUILD] bin/ath5k_dma.o
  [BUILD] bin/ath5k_eeprom.o
  [BUILD] bin/ath5k_gpio.o
  [BUILD] bin/ath5k_initvals.o
  [BUILD] bin/ath5k_pcu.o
  [BUILD] bin/ath5k_phy.o
  [BUILD] bin/ath5k_qcu.o
  [BUILD] bin/ath5k_reset.o
  [BUILD] bin/ath5k_rfkill.o
  [BUILD] bin/ath9k_ani.o
  [BUILD] bin/ath9k_ar5008_phy.o
  [BUILD] bin/ath9k_ar9002_calib.o
  [BUILD] bin/ath9k_ar9002_hw.o
  [BUILD] bin/ath9k_ar9002_mac.o
  [BUILD] bin/ath9k_ar9002_phy.o
  [BUILD] bin/ath9k_ar9003_calib.o
  [BUILD] bin/ath9k_ar9003_eeprom.o
  [BUILD] bin/ath9k_ar9003_hw.o
  [BUILD] bin/ath9k_ar9003_mac.o
  [BUILD] bin/ath9k_ar9003_phy.o
  [BUILD] bin/ath9k.o
  [BUILD] bin/ath9k_calib.o
  [BUILD] bin/ath9k_common.o
  [BUILD] bin/ath9k_eeprom_4k.o
  [BUILD] bin/ath9k_eeprom_9287.o
  [BUILD] bin/ath9k_eeprom.o
  [BUILD] bin/ath9k_eeprom_def.o
  [BUILD] bin/ath9k_hw.o
  [BUILD] bin/ath9k_init.o
  [BUILD] bin/ath9k_mac.o
  [BUILD] bin/ath9k_main.o
  [BUILD] bin/ath9k_recv.o
  [BUILD] bin/ath9k_xmit.o
  [BUILD] bin/gdbidt.o
  [BUILD] bin/setjmp.o
  [BUILD] bin/gdbstub_test.o
  [BUILD] bin/patch_cf.o
  [BUILD] bin/stack16.o
  [BUILD] bin/stack.o
  [BUILD] bin/e820mangler.o
  [BUILD] bin/pxe_entry.o
  [BUILD] bin/com32_wrapper.o
  [BUILD] bin/bootpart.o
  [BUILD] bin/dskprefix.o
  [BUILD] bin/exeprefix.o
  [BUILD] bin/hdprefix.o
  [BUILD] bin/isaromprefix.o
  [BUILD] bin/kkkpxeprefix.o
  [BUILD] bin/kkpxeprefix.o
  [BUILD] bin/kpxeprefix.o
  [BUILD] bin/libprefix.o
  [BUILD] bin/lkrnprefix.o
  [BUILD] bin/mbr.o
  [BUILD] bin/mromprefix.o
  [BUILD] bin/nbiprefix.o
  [BUILD] bin/nullprefix.o
  [BUILD] bin/pciromprefix.o
  [BUILD] bin/pxeprefix.o
  [BUILD] bin/romprefix.o
  [BUILD] bin/undiloader.o
  [BUILD] bin/unlzma16.o
  [BUILD] bin/unlzma.o
  [BUILD] bin/usbdisk.o
  [BUILD] bin/liba20.o
  [BUILD] bin/libkir.o
  [BUILD] bin/libpm.o
  [BUILD] bin/librm.o
  [BUILD] bin/undiisr.o
  [BUILD] bin/3c509.ids.o
  [BUILD] bin/3c509-eisa.ids.o
  [BUILD] bin/3c515.ids.o
  [BUILD] bin/3c529.ids.o
  [BUILD] bin/3c595.ids.o
  [BUILD] bin/3c90x.ids.o
  [BUILD] bin/amd8111e.ids.o
  [BUILD] bin/atl1e.ids.o
  [BUILD] bin/b44.ids.o
  [BUILD] bin/bnx2.ids.o
  [BUILD] bin/cs89x0.ids.o
  [BUILD] bin/davicom.ids.o
  [BUILD] bin/depca.ids.o
  [BUILD] bin/dmfe.ids.o
  [BUILD] bin/eepro100.ids.o
  [BUILD] bin/eepro.ids.o
  [BUILD] bin/ena.ids.o
  [BUILD] bin/epic100.ids.o
  [BUILD] bin/etherfabric.ids.o
  [BUILD] bin/exanic.ids.o
  [BUILD] bin/forcedeth.ids.o
  [BUILD] bin/icplus.ids.o
  [BUILD] bin/intel.ids.o
  [BUILD] bin/intelx.ids.o
  [BUILD] bin/intelxl.ids.o
  [BUILD] bin/intelxlvf.ids.o
  [BUILD] bin/intelxvf.ids.o
  [BUILD] bin/jme.ids.o
  [BUILD] bin/myri10ge.ids.o
  [BUILD] bin/myson.ids.o
  [BUILD] bin/natsemi.ids.o
  [BUILD] bin/ne2k_isa.ids.o
  [BUILD] bin/ns8390.ids.o
  [BUILD] bin/pcnet32.ids.o
  [BUILD] bin/pnic.ids.o
  [BUILD] bin/prism2_pci.ids.o
  [BUILD] bin/prism2_plx.ids.o
  [BUILD] bin/realtek.ids.o
  [BUILD] bin/rhine.ids.o
  [BUILD] bin/sis190.ids.o
  [BUILD] bin/sis900.ids.o
  [BUILD] bin/skeleton.ids.o
  [BUILD] bin/skge.ids.o
  [BUILD] bin/sky2.ids.o
  [BUILD] bin/smc9000.ids.o
  [BUILD] bin/sundance.ids.o
  [BUILD] bin/thunderx.ids.o
  [BUILD] bin/tlan.ids.o
  [BUILD] bin/tulip.ids.o
  [BUILD] bin/velocity.ids.o
  [BUILD] bin/virtio-net.ids.o
  [BUILD] bin/vmxnet3.ids.o
  [BUILD] bin/w89c840.ids.o
  [BUILD] bin/igbvf_main.ids.o
  [BUILD] bin/phantom.ids.o
  [BUILD] bin/vxge.ids.o
  [BUILD] bin/tg3.ids.o
  [BUILD] bin/sfc_hunt.ids.o
  [BUILD] bin/arbel.ids.o
  [BUILD] bin/golan.ids.o
  [BUILD] bin/hermon.ids.o
  [BUILD] bin/linda.ids.o
  [BUILD] bin/qib7322.ids.o
  [BUILD] bin/ehci.ids.o
  [BUILD] bin/uhci.ids.o
  [BUILD] bin/xhci.ids.o
  [BUILD] bin/hvm.ids.o
  [BUILD] bin/undi.ids.o
  [BUILD] bin/rtl8180.ids.o
  [BUILD] bin/rtl8185.ids.o
  [BUILD] bin/ath5k.ids.o
  [BUILD] bin/ath9k.ids.o
  [AR] bin/blib.a
ar: creating bin/blib.a
  [HOSTCC] util/zbin
  [VERSION] bin/version.ipxe.dsk.o
  [LD] bin/ipxe.dsk.tmp
  [BIN] bin/ipxe.dsk.bin
  [ZINFO] bin/ipxe.dsk.zinfo
  [ZBIN] bin/ipxe.dsk.zbin
  [FINISH] bin/ipxe.dsk
  [VERSION] bin/version.ipxe.lkrn.o
  [LD] bin/ipxe.lkrn.tmp
  [BIN] bin/ipxe.lkrn.bin
  [ZINFO] bin/ipxe.lkrn.zinfo
  [ZBIN] bin/ipxe.lkrn.zbin
  [FINISH] bin/ipxe.lkrn
  [GENISO] bin/ipxe.iso
  [LD] bin/usbdisk.tmp
  [BIN] bin/usbdisk.bin
  [VERSION] bin/version.ipxe.hd.o
  [LD] bin/ipxe.hd.tmp
  [BIN] bin/ipxe.hd.bin
  [ZINFO] bin/ipxe.hd.zinfo
  [ZBIN] bin/ipxe.hd.zbin
  [FINISH] bin/ipxe.hd
  [FINISH] bin/ipxe.usb
  [VERSION] bin/version.ipxe.pxe.o
  [LD] bin/ipxe.pxe.tmp
  [BIN] bin/ipxe.pxe.bin
  [ZINFO] bin/ipxe.pxe.zinfo
  [ZBIN] bin/ipxe.pxe.zbin
  [FINISH] bin/ipxe.pxe
  [VERSION] bin/version.undionly.kpxe.o
  [LD] bin/undionly.kpxe.tmp
  [BIN] bin/undionly.kpxe.bin
  [ZINFO] bin/undionly.kpxe.zinfo
  [ZBIN] bin/undionly.kpxe.zbin
  [FINISH] bin/undionly.kpxe
  [VERSION] bin/version.rtl8139.rom.o
  [LD] bin/rtl8139.rom.tmp
  [BIN] bin/rtl8139.rom.bin
  [ZINFO] bin/rtl8139.rom.zinfo
  [ZBIN] bin/rtl8139.rom.zbin
  [FINISH] bin/rtl8139.rom
  [VERSION] bin/version.8086100e.mrom.o
  [LD] bin/8086100e.mrom.tmp
  [BIN] bin/8086100e.mrom.bin
  [ZINFO] bin/8086100e.mrom.zinfo
  [ZBIN] bin/8086100e.mrom.zbin
  [FINISH] bin/8086100e.mrom
  [VERSION] bin/version.80861209.rom.o
  [LD] bin/80861209.rom.tmp
  [BIN] bin/80861209.rom.bin
  [ZINFO] bin/80861209.rom.zinfo
  [ZBIN] bin/80861209.rom.zbin
  [FINISH] bin/80861209.rom
  [VERSION] bin/version.10500940.rom.o
  [LD] bin/10500940.rom.tmp
  [BIN] bin/10500940.rom.bin
  [ZINFO] bin/10500940.rom.zinfo
  [ZBIN] bin/10500940.rom.zbin
  [FINISH] bin/10500940.rom
  [VERSION] bin/version.10222000.rom.o
  [LD] bin/10222000.rom.tmp
  [BIN] bin/10222000.rom.bin
  [ZINFO] bin/10222000.rom.zinfo
  [ZBIN] bin/10222000.rom.zbin
  [FINISH] bin/10222000.rom
  [VERSION] bin/version.10ec8139.rom.o
  [LD] bin/10ec8139.rom.tmp
  [BIN] bin/10ec8139.rom.bin
  [ZINFO] bin/10ec8139.rom.zinfo
  [ZBIN] bin/10ec8139.rom.zbin
  [FINISH] bin/10ec8139.rom
  [VERSION] bin/version.1af41000.rom.o
  [LD] bin/1af41000.rom.tmp
  [BIN] bin/1af41000.rom.bin
  [ZINFO] bin/1af41000.rom.zinfo
  [ZBIN] bin/1af41000.rom.zbin
  [FINISH] bin/1af41000.rom
  [VERSION] bin/version.8086100f.mrom.o
  [LD] bin/8086100f.mrom.tmp
  [BIN] bin/8086100f.mrom.bin
  [ZINFO] bin/8086100f.mrom.zinfo
  [ZBIN] bin/8086100f.mrom.zbin
  [FINISH] bin/8086100f.mrom
  [VERSION] bin/version.808610d3.mrom.o
  [LD] bin/808610d3.mrom.tmp
  [BIN] bin/808610d3.mrom.bin
  [ZINFO] bin/808610d3.mrom.zinfo
  [ZBIN] bin/808610d3.mrom.zbin
  [FINISH] bin/808610d3.mrom
  [VERSION] bin/version.15ad07b0.rom.o
  [LD] bin/15ad07b0.rom.tmp
  [BIN] bin/15ad07b0.rom.bin
  [ZINFO] bin/15ad07b0.rom.zinfo
  [ZBIN] bin/15ad07b0.rom.zbin
  [FINISH] bin/15ad07b0.rom
  [VERSION] bin/version.3c509.rom.o
  [LD] bin/3c509.rom.tmp
  [BIN] bin/3c509.rom.bin
  [ZINFO] bin/3c509.rom.zinfo
  [ZBIN] bin/3c509.rom.zbin
  [FINISH] bin/3c509.rom
  [VERSION] bin/version.intel.rom.o
  [LD] bin/intel.rom.tmp
  [BIN] bin/intel.rom.bin
  [ZINFO] bin/intel.rom.zinfo
  [ZBIN] bin/intel.rom.zbin
  [FINISH] bin/intel.rom
  [VERSION] bin/version.intel.mrom.o
  [LD] bin/intel.mrom.tmp
  [BIN] bin/intel.mrom.bin
  [ZINFO] bin/intel.mrom.zinfo
  [ZBIN] bin/intel.mrom.zbin
  [FINISH] bin/intel.mrom
rm bin/undionly.kpxe.bin bin/ipxe.hd.zinfo bin/1af41000.rom.bin bin/version.10ec8139.rom.o bin/intel.mrom.zinfo bin/rtl8139.rom.bin bin/10222000.rom.bin bin/10222000.rom.zbin bin/version.8086100e.mrom.o bin/ipxe.hd.bin bin/intel.rom.bin bin/ipxe.hd.zbin bin/15ad07b0.rom.zinfo bin/3c509.rom.zinfo bin/version.8086100f.mrom.o bin/10500940.rom.zinfo bin/10ec8139.rom.zbin bin/version.15ad07b0.rom.o bin/10500940.rom.zbin bin/8086100f.mrom.zinfo bin/ipxe.dsk.zinfo bin/ipxe.lkrn.bin bin/ipxe.pxe.zinfo bin/ipxe.lkrn.zinfo bin/1af41000.rom.zinfo bin/ipxe.lkrn.zbin bin/80861209.rom.bin bin/ipxe.dsk.zbin bin/version.ipxe.hd.o bin/version.10222000.rom.o bin/intel.rom.zbin bin/intel.mrom.zbin bin/8086100e.mrom.bin bin/version.808610d3.mrom.o bin/8086100f.mrom.zbin bin/8086100e.mrom.zinfo bin/15ad07b0.rom.bin bin/usbdisk.bin bin/3c509.rom.zbin bin/version.intel.rom.o bin/808610d3.mrom.zbin bin/ipxe.pxe.bin bin/10ec8139.rom.zinfo bin/intel.mrom.bin bin/808610d3.mrom.bin bin/10ec8139.rom.bin bin/15ad07b0.rom.zbin bin/version.80861209.rom.o bin/version.1af41000.rom.o bin/ipxe.hd bin/undionly.kpxe.zinfo bin/3c509.rom.bin bin/version.ipxe.dsk.o bin/version.rtl8139.rom.o bin/ipxe.dsk.bin bin/version.intel.mrom.o bin/version.ipxe.lkrn.o bin/version.ipxe.pxe.o bin/version.3c509.rom.o bin/80861209.rom.zbin bin/intel.rom.zinfo bin/808610d3.mrom.zinfo bin/version.undionly.kpxe.o bin/8086100e.mrom.zbin bin/80861209.rom.zinfo bin/version.10500940.rom.o bin/1af41000.rom.zbin bin/ipxe.pxe.zbin bin/10500940.rom.bin bin/rtl8139.rom.zinfo bin/undionly.kpxe.zbin bin/10222000.rom.zinfo bin/rtl8139.rom.zbin bin/8086100f.mrom.bin
rm -f bin-x86_64-pcbios/*.*  bin-x86_64-pcbios/.certificate.* bin-x86_64-pcbios/.certificates.* bin-x86_64-pcbios/.private_key.* bin-x86_64-pcbios/errors	 bin-x86_64-pcbios/NIC	 ./util/zbin ./util/elf2efi32 ./util/elf2efi64 ./util/efirom ./util/efifatbin ./util/iccfix ./util/einfo TAGS bin-x86_64-pcbios/symtab
  [PARSEROM]
  [DEPS] arch/x86/drivers/net/undiisr.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/transitions/librm.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/transitions/libpm.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/transitions/libkir.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/transitions/liba20.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/prefix/usbdisk.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/prefix/unlzma.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/prefix/unlzma16.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/prefix/undiloader.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/prefix/romprefix.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/prefix/pxeprefix.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/prefix/pciromprefix.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/prefix/nullprefix.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/prefix/nbiprefix.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/prefix/mromprefix.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/prefix/mbr.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/prefix/lkrnprefix.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/prefix/libprefix.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/prefix/kpxeprefix.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/prefix/kkpxeprefix.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/prefix/kkkpxeprefix.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/prefix/isaromprefix.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/prefix/hdprefix.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/prefix/exeprefix.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/prefix/dskprefix.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/prefix/bootpart.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/syslinux/com32_wrapper.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pxe/pxe_entry.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/e820mangler.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/stack.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/stack16.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/patch_cf.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86_64/core/setjmp.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86_64/core/gdbidt.S
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_xmit.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_recv.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_main.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_mac.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_init.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_hw.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_eeprom_def.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_eeprom.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_eeprom_9287.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_eeprom_4k.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_common.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_calib.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9003_phy.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9003_mac.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9003_hw.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9003_eeprom.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9003_calib.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9002_phy.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9002_mac.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9002_hw.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_ar9002_calib.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_ar5008_phy.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath9k/ath9k_ani.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath5k/ath5k_rfkill.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath5k/ath5k_reset.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath5k/ath5k_qcu.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath5k/ath5k_phy.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath5k/ath5k_pcu.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath5k/ath5k_initvals.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath5k/ath5k_gpio.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath5k/ath5k_eeprom.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath5k/ath5k_dma.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath5k/ath5k_desc.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath5k/ath5k_caps.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath5k/ath5k.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath5k/ath5k_attach.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath_regd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath_key.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ath/ath_hw.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/rtl818x/rtl818x.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/rtl818x/rtl8185_rtl8225.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/rtl818x/rtl8185.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/rtl818x/rtl8180_sa2400.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/rtl818x/rtl8180_max2820.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/rtl818x/rtl8180_grf5101.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/rtl818x/rtl8180.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/80211/wpa_tkip.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/80211/wpa_psk.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/80211/wpa_ccmp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/80211/wpa.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/80211/wep.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/80211/sec80211.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/80211/rc80211.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/80211/net80211.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/oncrpc/portmap.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/oncrpc/oncrpc_iob.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/oncrpc/nfs_uri.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/oncrpc/nfs_open.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/oncrpc/nfs.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/oncrpc/mount.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/drivers/net/undirom.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/drivers/net/undipreload.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/drivers/net/undionly.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/drivers/net/undinet.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/drivers/net/undiload.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/drivers/net/undi.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/transitions/librm_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/transitions/librm_mgmt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/drivers/hyperv/hyperv.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/drivers/xen/hvm.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/hci/commands/pxe_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/hci/commands/cpuid_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/syslinux/comboot_resolv.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/syslinux/comboot_call.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/syslinux/com32_call.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/vmware/vmware.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/vmware/vmconsole.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/vmware/guestrpc.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/vmware/guestinfo.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/efi/efix86_nap.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pxe/pxe_undi.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pxe/pxe_udp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pxe/pxe_tftp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pxe/pxe_preboot.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pxe/pxe_loader.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pxe/pxe_file.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pxe/pxe_exit_hook.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pxe/pxe_call.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/vesafb.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/rtc_time.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/rtc_entropy.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/rsdp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/pnpbios.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/pcibios.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/memtop_umalloc.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/memmap.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/int13con.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/int13.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/hidemem.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/fakee820.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/bios_timer.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/bios_smbios.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/bios_reboot.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/bios_nap.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/biosint.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/bios_console.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/basemem.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/apm.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/acpi_timer.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/interface/pcbios/acpipwr.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/image/sdi.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/image/pxe_image.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/image/nbi.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/image/multiboot.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/image/initrd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/image/elfboot.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/image/comboot.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/image/com32.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/image/bzimage.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/image/bootsector.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/x86_uart.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/x86_tcpip.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/x86_string.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/x86_io.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/x86_bigint.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/vram_settings.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/video_subr.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/runtime.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/relocate.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/rdtsc_timer.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/pit8254.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/pic8259.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/pcidirect.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/pci_autoboot.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/gdbmach.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/dumpregs.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/debugcon.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/cpuid_settings.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/cpuid.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/cachedhcp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] arch/x86/core/basemem_packet.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] config/config_usb.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] config/config_timer.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] config/config_route.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] config/config_romprefix.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] config/config_pixbuf.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] config/config_pcbios.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] config/config_net80211.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] config/config_linux.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] config/config_infiniband.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] config/config_http.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] config/config_fdt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] config/config_fc.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] config/config_ethernet.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] config/config_efi.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] config/config_crypto.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] config/config.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] config/config_asn1.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/sync.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/route_ipv6.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/route_ipv4.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/route.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/pxemenu.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/prompt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/profstat.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/pingmgmt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/ntpmgmt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/nslookup.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/neighmgmt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/lotest.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/iwmgmt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/ipstat.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/imgtrust.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/imgmgmt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/ifmgmt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/ibmgmt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/fcmgmt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/dhcpmgmt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/certmgmt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] usr/autoboot.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_wo.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_us.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_uk.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_ua.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_th.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_sr.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_sg.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_ru.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_ro.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_pt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_pl.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_no-latin1.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_no.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_nl.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_mt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_mk.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_lt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_it.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_il.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_hu.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_gr.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_fr.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_fi.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_et.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_es.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_dk.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_de.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_cz.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_cf.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_by.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_bg.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_az.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/keymap/keymap_al.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/mucurses/widgets/editbox.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/mucurses/wininit.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/mucurses/windows.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/mucurses/winattrs.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/mucurses/slk.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/mucurses/print_nadv.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/mucurses/print.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/mucurses/mucurses.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/mucurses/kb.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/mucurses/edging.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/mucurses/colour.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/mucurses/clear.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/mucurses/ansi_screen.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/mucurses/alert.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/tui/settings_ui.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/tui/menu_ui.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/tui/login_ui.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/vlan_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/time_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/sync_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/sanboot_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/route_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/reboot_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/profstat_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/poweroff_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/ping_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/pci_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/param_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/nvo_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/ntp_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/nslookup_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/neighbour_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/menu_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/lotest_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/login_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/iwmgmt_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/ipstat_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/image_trust_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/image_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/ifmgmt_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/ibmgmt_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/gdbstub_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/fcmgmt_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/digest_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/dhcp_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/console_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/config_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/cert_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/commands/autoboot_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/wireless_errors.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/strerror.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/shell.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/readline.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/linux_args.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/jumpscroll.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] hci/editstring.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/mishmash/rsa_sha512.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/mishmash/rsa_sha384.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/mishmash/rsa_sha256.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/mishmash/rsa_sha224.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/mishmash/rsa_sha1.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/mishmash/rsa_md5.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/mishmash/rsa_aes_cbc_sha256.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/mishmash/rsa_aes_cbc_sha1.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/mishmash/oid_sha512.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/mishmash/oid_sha512_256.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/mishmash/oid_sha512_224.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/mishmash/oid_sha384.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/mishmash/oid_sha256.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/mishmash/oid_sha224.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/mishmash/oid_sha1.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/mishmash/oid_rsa.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/mishmash/oid_md5.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/mishmash/oid_md4.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/x509.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/sha512.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/sha512_256.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/sha512_224.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/sha384.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/sha256.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/sha224.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/sha1extra.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/sha1.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/rsa.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/rootcert.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/rbg.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/random_nz.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/privkey.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/ocsp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/null_entropy.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/ntlm.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/md5.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/md4.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/hmac_drbg.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/hmac.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/hash_df.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/entropy.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/ecb.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/drbg.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/deflate.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/crypto_null.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/crc32.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/cms.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/chap.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/certstore.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/cbc.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/bigint.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/asn1.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/arc4.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/aes_wrap.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/aes.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/x509_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/vsprintf_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/uri_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/umalloc_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/time_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/tests.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/tcpip_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/string_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/sha512_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/sha256_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/sha1_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/settings_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/setjmp_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/rsa_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/profile_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/pnm_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/png_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/pixbuf_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/pem_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/pccrc_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/ocsp_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/ntlm_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/memset_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/memcpy_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/md5_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/md4_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/math_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/list_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/linebuf_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/ipv6_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/ipv4_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/iobuf_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/hmac_drbg_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/hash_df_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/entropy_sample.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/dns_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/digest_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/der_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/deflate_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/crc32_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/cms_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/cipher_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/byteswap_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/bofm_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/bitops_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/bigint_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/base64_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/base16_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/asn1_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] tests/aes_test.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/hyperv/vmbus.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/xen/xenstore.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/xen/xengrant.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/xen/xenbus.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/bofm/bofm.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/smbios/smbios_settings.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/smbios/smbios.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_wrap.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_watchdog.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_utils.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_usb.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_umalloc.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_uaccess.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_timer.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_time.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_strings.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_snp_hii.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_snp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_smbios.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_reboot.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_pxe.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efiprefix.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_pci.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_local.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_init.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_hii.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_guid.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_file.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_fdt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_fbcon.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_entropy.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efidrvprefix.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_driver.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_download.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_debug.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_console.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_bofm.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_block.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_blacklist.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_autoboot.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] interface/efi/efi_acpi.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/usb/xhci.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/usb/usbnet.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/usb/usbkbd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/usb/usbio.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/usb/usbhub.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/usb/usbhid.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/usb/uhci.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/usb/ehci.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/mlx_nodnic/src/mlx_port.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/mlx_nodnic/src/mlx_device.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/mlx_nodnic/src/mlx_cmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/mlx_utils/mlx_lib/mlx_mtu/mlx_mtu.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/mlx_utils/mlx_lib/mlx_link_speed/mlx_link_speed.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/mlx_utils/mlx_lib/mlx_blink_leds/mlx_blink_leds.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/mlx_utils/mlx_lib/mlx_vmac/mlx_vmac.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/mlx_utils/mlx_lib/mlx_nvconfig/mlx_nvconfig_defaults.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/mlx_utils/mlx_lib/mlx_nvconfig/mlx_nvconfig.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/mlx_utils/mlx_lib/mlx_reg_access/mlx_reg_access.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/mlx_utils/src/public/mlx_utils.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/mlx_utils/src/public/mlx_pci_gw.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/mlx_utils/src/public/mlx_pci.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/mlx_utils/src/public/mlx_memory.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/mlx_utils/src/public/mlx_icmd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/mlx_utils_flexboot/src/mlx_utils_priv.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/mlx_utils_flexboot/src/mlx_pci_priv.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/mlx_utils_flexboot/src/mlx_memory_priv.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/qib7322.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/linda_fw.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/linda.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/hermon.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/golan.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/flexboot_nodnic.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/infiniband/arbel.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/bitbash/spi_bit.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/bitbash/mii_bit.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/bitbash/i2c_bit.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/bitbash/bitbash.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/nvs/threewire.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/nvs/spi.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/nvs/nvsvpd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/nvs/nvs.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/block/srp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/block/scsi.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/block/ibft.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/block/ata.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/sfc/sfc_hunt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/sfc/efx_hunt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/sfc/efx_common.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/bnxt/bnxt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/tg3/tg3_phy.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/tg3/tg3_hw.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/tg3/tg3.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/efi/snponly.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/efi/snpnet.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/efi/snp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/efi/nii.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/vxge/vxge_traffic.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/vxge/vxge_main.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/vxge/vxge_config.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/vxge/vxge.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/phantom/phantom.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/igbvf/igbvf_vf.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/igbvf/igbvf_mbx.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/igbvf/igbvf_main.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/wd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/w89c840.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/vmxnet3.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/virtio-net.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/velocity.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/tulip.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/tlan.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/thunderx.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/sundance.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/smscusb.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/smsc95xx.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/smsc75xx.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/smc9000.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/sky2.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/skge.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/skeleton.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/sis900.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/sis190.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/rhine.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/realtek.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/prism2_plx.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/prism2_pci.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/pnic.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/pcnet32.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ns8390.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/netvsc.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/netfront.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ne.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ne2k_isa.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ncm.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/natsemi.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/myson.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/myri10ge.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/mii.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/legacy.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/lan78xx.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/jme.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ipoib.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/intelxvf.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/intelxlvf.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/intelxl.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/intelx.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/intelvf.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/intel.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/icplus.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/forcedeth.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/exanic.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/etherfabric.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/epic100.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/eoib.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ena.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/eepro.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/eepro100.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/ecm.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/dmfe.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/dm96xx.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/depca.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/davicom.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/cs89x0.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/bnx2.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/b44.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/axge.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/atl1e.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/amd8111e.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/acm.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/3c90x.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/3c5x9.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/3c595.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/3c529.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/3c515.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/3c509-eisa.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/3c509.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/net/3c503.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/bus/virtio-ring.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/bus/virtio-pci.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/bus/usb.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/bus/pcivpd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/bus/pci_settings.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/bus/pcimsix.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/bus/pciextra.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/bus/pciea.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/bus/pci.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/bus/pcibackup.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/bus/mca.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/bus/isapnp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/bus/isa_ids.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/bus/isa.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/bus/eisa.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] drivers/bus/cdc.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] image/segment.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] image/script.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] image/pnm.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] image/png.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] image/pem.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] image/embedded.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] image/elf.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] image/efi_image.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] image/der.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/infiniband/xsigo.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/infiniband/ib_srp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/infiniband/ib_smc.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/infiniband/ib_sma.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/infiniband/ib_service.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/infiniband/ib_pathrec.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/infiniband/ib_packet.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/infiniband/ib_mi.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/infiniband/ib_mcast.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/infiniband/ib_cmrc.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/infiniband/ib_cm.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/udp/tftp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/udp/syslog.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/udp/slam.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/udp/ntp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/udp/dns.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/udp/dhcpv6.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/udp/dhcp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/tcp/syslogs.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/tcp/oncrpc.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/tcp/iscsi.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/tcp/https.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/tcp/httpntlm.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/tcp/httpgce.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/tcp/httpdigest.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/tcp/httpcore.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/tcp/httpconn.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/tcp/http.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/tcp/httpblock.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/tcp/httpbasic.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/tcp/httpauth.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/tcp/ftp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/vlan.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/validator.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/udp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/tls.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/tcpip.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/tcp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/stp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/socket.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/rndis.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/retry.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/rarp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/ping.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/peermux.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/peerdist.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/peerdisc.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/peerblk.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/pccrd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/pccrc.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/nullnet.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/netdev_settings.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/netdevice.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/neighbour.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/ndp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/ipv6.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/ipv4.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/iobpad.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/infiniband.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/icmpv6.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/icmpv4.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/icmp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/fragment.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/fcp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/fcoe.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/fcns.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/fcels.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/fc.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/fakedhcp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/eth_slow.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/ethernet.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/eapol.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/dhcppkt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/dhcpopts.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/arp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] net/aoe.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/xfer.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/xferbuf.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/wchar.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/vsprintf.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/uuid.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/uri.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/uart.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/timer.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/time.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/stringextra.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/string.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/settings.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/serial.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/sanboot.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/resolv.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/refcnt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/random.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/quiesce.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/profile.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/process.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/posix_io.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/pool.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/pixbuf.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/pinger.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/pending.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/pcmcia.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/pc_kbd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/parseopt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/params.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/open.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/nvo.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/null_time.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/null_sanboot.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/null_reboot.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/null_nap.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/null_acpi.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/netbios.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/monojob.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/menu.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/memmap_settings.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/malloc.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/main.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/log.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/list.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/lineconsole.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/linebuf.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/job.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/isqrt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/iomap_virt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/iobuf.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/interface.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/init.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/image.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/i82365.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/hw.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/getopt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/getkey.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/gdbudp.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/gdbstub.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/gdbserial.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/fnrec.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/fdt.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/fbcon.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/fault.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/exec.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/errno.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/edd.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/dummy_sanboot.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/downloader.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/device.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/debug_md5.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/debug.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/cwuri.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/ctype.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/cpio.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/console.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/blocktrans.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/blockdev.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/bitmap.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/basename.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/base64.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/base16.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/assert.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/asprintf.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/ansiesc.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/ansicoldef.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/ansicol.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/acpi_settings.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] core/acpi.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] libgcc/__umoddi3.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] libgcc/__udivmoddi4.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] libgcc/__udivdi3.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] libgcc/__moddi3.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] libgcc/implicit.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] libgcc/icc.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] libgcc/__divmoddi4.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] libgcc/__divdi3.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/privkey.c
cc1: error: code model kernel does not support PIC mode
  [DEPS] crypto/certstore.c
cc1: error: code model kernel does not support PIC mode
  [BUILD] bin-x86_64-pcbios/__divdi3.o
cc1: error: code model kernel does not support PIC mode
make[2]: *** [Makefile.housekeeping:946: bin-x86_64-pcbios/__divdi3.o] Error 1
make[1]: *** [Makefile.housekeeping:276: bin-x86_64-pcbios/8086100e.mrom] Error 2
make: *** [Makefile:168: everything] Error 2
-------------- next part --------------
make[2]: 'bin/blib.a' is up to date.
  [HOSTCC] util/zbin
  [BIN] bin/ipxe.dsk.bin
  [ZINFO] bin/ipxe.dsk.zinfo
  [ZBIN] bin/ipxe.dsk.zbin
  [FINISH] bin/ipxe.dsk
  [BIN] bin/ipxe.lkrn.bin
  [ZINFO] bin/ipxe.lkrn.zinfo
  [ZBIN] bin/ipxe.lkrn.zbin
  [FINISH] bin/ipxe.lkrn
  [GENISO] bin/ipxe.iso
  [BIN] bin/usbdisk.bin
  [BIN] bin/ipxe.hd.bin
  [ZINFO] bin/ipxe.hd.zinfo
  [ZBIN] bin/ipxe.hd.zbin
  [FINISH] bin/ipxe.hd
  [FINISH] bin/ipxe.usb
  [BIN] bin/ipxe.pxe.bin
  [ZINFO] bin/ipxe.pxe.zinfo
  [ZBIN] bin/ipxe.pxe.zbin
  [FINISH] bin/ipxe.pxe
  [BIN] bin/undionly.kpxe.bin
  [ZINFO] bin/undionly.kpxe.zinfo
  [ZBIN] bin/undionly.kpxe.zbin
  [FINISH] bin/undionly.kpxe
  [BIN] bin/rtl8139.rom.bin
  [ZINFO] bin/rtl8139.rom.zinfo
  [ZBIN] bin/rtl8139.rom.zbin
  [FINISH] bin/rtl8139.rom
  [BIN] bin/8086100e.mrom.bin
  [ZINFO] bin/8086100e.mrom.zinfo
  [ZBIN] bin/8086100e.mrom.zbin
  [FINISH] bin/8086100e.mrom
  [BIN] bin/80861209.rom.bin
  [ZINFO] bin/80861209.rom.zinfo
  [ZBIN] bin/80861209.rom.zbin
  [FINISH] bin/80861209.rom
  [BIN] bin/10500940.rom.bin
  [ZINFO] bin/10500940.rom.zinfo
  [ZBIN] bin/10500940.rom.zbin
  [FINISH] bin/10500940.rom
  [BIN] bin/10222000.rom.bin
  [ZINFO] bin/10222000.rom.zinfo
  [ZBIN] bin/10222000.rom.zbin
  [FINISH] bin/10222000.rom
  [BIN] bin/10ec8139.rom.bin
  [ZINFO] bin/10ec8139.rom.zinfo
  [ZBIN] bin/10ec8139.rom.zbin
  [FINISH] bin/10ec8139.rom
  [BIN] bin/1af41000.rom.bin
  [ZINFO] bin/1af41000.rom.zinfo
  [ZBIN] bin/1af41000.rom.zbin
  [FINISH] bin/1af41000.rom
  [BIN] bin/8086100f.mrom.bin
  [ZINFO] bin/8086100f.mrom.zinfo
  [ZBIN] bin/8086100f.mrom.zbin
  [FINISH] bin/8086100f.mrom
  [BIN] bin/808610d3.mrom.bin
  [ZINFO] bin/808610d3.mrom.zinfo
  [ZBIN] bin/808610d3.mrom.zbin
  [FINISH] bin/808610d3.mrom
  [BIN] bin/15ad07b0.rom.bin
  [ZINFO] bin/15ad07b0.rom.zinfo
  [ZBIN] bin/15ad07b0.rom.zbin
  [FINISH] bin/15ad07b0.rom
  [BIN] bin/3c509.rom.bin
  [ZINFO] bin/3c509.rom.zinfo
  [ZBIN] bin/3c509.rom.zbin
  [FINISH] bin/3c509.rom
  [BIN] bin/intel.rom.bin
  [ZINFO] bin/intel.rom.zinfo
  [ZBIN] bin/intel.rom.zbin
  [FINISH] bin/intel.rom
  [BIN] bin/intel.mrom.bin
  [ZINFO] bin/intel.mrom.zinfo
  [ZBIN] bin/intel.mrom.zbin
  [FINISH] bin/intel.mrom
rm bin/undionly.kpxe.bin bin/ipxe.hd.zinfo bin/1af41000.rom.bin bin/intel.mrom.zinfo bin/rtl8139.rom.bin bin/10222000.rom.bin bin/10222000.rom.zbin bin/ipxe.hd.bin bin/intel.rom.bin bin/ipxe.hd.zbin bin/15ad07b0.rom.zinfo bin/3c509.rom.zinfo bin/10500940.rom.zinfo bin/10ec8139.rom.zbin bin/10500940.rom.zbin bin/8086100f.mrom.zinfo bin/ipxe.dsk.zinfo bin/ipxe.lkrn.bin bin/ipxe.pxe.zinfo bin/ipxe.lkrn.zinfo bin/1af41000.rom.zinfo bin/ipxe.lkrn.zbin bin/80861209.rom.bin bin/ipxe.dsk.zbin bin/intel.rom.zbin bin/intel.mrom.zbin bin/8086100e.mrom.bin bin/8086100f.mrom.zbin bin/8086100e.mrom.zinfo bin/15ad07b0.rom.bin bin/usbdisk.bin bin/3c509.rom.zbin bin/808610d3.mrom.zbin bin/ipxe.pxe.bin bin/10ec8139.rom.zinfo bin/intel.mrom.bin bin/808610d3.mrom.bin bin/10ec8139.rom.bin bin/15ad07b0.rom.zbin bin/ipxe.hd bin/undionly.kpxe.zinfo bin/3c509.rom.bin bin/ipxe.dsk.bin bin/80861209.rom.zbin bin/intel.rom.zinfo bin/808610d3.mrom.zinfo bin/8086100e.mrom.zbin bin/80861209.rom.zinfo bin/1af41000.rom.zbin bin/ipxe.pxe.zbin bin/10500940.rom.bin bin/rtl8139.rom.zinfo bin/undionly.kpxe.zbin bin/10222000.rom.zinfo bin/rtl8139.rom.zbin bin/8086100f.mrom.bin
  [BUILD] bin-x86_64-pcbios/__divdi3.o
cc1: error: code model kernel does not support PIC mode
make[2]: *** [Makefile.housekeeping:946: bin-x86_64-pcbios/__divdi3.o] Error 1
make[1]: *** [Makefile.housekeeping:276: bin-x86_64-pcbios/8086100e.mrom] Error 2
make: *** [Makefile:168: everything] Error 2
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 899 bytes
Desc: OpenPGP digital signature
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20200624/b9775893/attachment-0001.sig>

From skilly at gmx.de  Wed Jun 24 08:43:32 2020
From: skilly at gmx.de (=?UTF-8?Q?Eichh=c3=b6rnchen?=)
Date: Wed, 24 Jun 2020 08:43:32 -0000
Subject: [ipxe-devel] Great work folks
Message-ID: <746b8410-f351-2188-cf4b-132c96cd0f4f@gmx.de>

Hey guys,

Thank you for all the time you have invested in the project. Good work.
I love it.

Best regards