I haven't contributed to iPXE in many years, so I don't have write access to
the Github repo, but this PR looks good to me.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I wrote the original WPA code in 2009, and definitely successfully booted with
it at that time. It looks like the incorrect-polarity memcmp() was only
introduced in 2014:
https://github.com/ipxe/ipxe/commit/8ee39f7432e63c2382ab3e7d24e234310f4532c9
--
You are receiving this because you are
On Sat, Dec 22, 2012 at 11:19 PM, Matthew Helton mwhel...@gmail.com wrote:
The stray thought occured to me that instead of scripting
whitelists/blacklists by system model, or relying on external detection
methods (Syslinux or HDT) for NICs, could be ipxe.pxe be altered to carry an
alternate
On Thu, Oct 18, 2012 at 2:28 PM, Kalpesh Patel
kalpesh.pa...@glgroup.com wrote:
Hi,
Is there a comprehensive list of modules that can be built with debug turned
on?
In particular, I am looking for additional non-hardware modules that can be
included:
Hi Kalpesh,
Every source file in
On Thu, Jan 5, 2012 at 12:22 AM, Pete Holland phollan...@gmail.com wrote:
So I'm working on a port of the vmxnet3 driver to ipxe (mainly because
the default pxe client in ESX is not suitable for my needs).
One problem I've run into is that the vmxnet3 driver seems to require
far more memory
On Sat, Jul 31, 2010 at 3:08 AM, Stefan Hajnoczi stefanha at gmail.com wrote:
Josh: I have CCed you explicitly because I think you had ideas on this
some time ago.
The question of multiple PCI IDs for a single gPXE ROM came up
recently on IRC. ?It can be useful to have a single gPXE ROM file
6 matches
Mail list logo
