Displaying 2 results from an estimated 2 matches for "c64747d".
Did you mean:
647474
2015 Oct 25
4
Confusion on lpxelinux vs. gpxelinux vs. ipxe vs gpxe.
On Sat, Oct 24, 2015 at 6:15 PM, Michael Brown via Syslinux
<syslinux at zytor.com> wrote:
> Also, not a fork: http://git.ipxe.org/ipxe.git/commitdiff/8406115
A fork is a fork, regardless the reasons behind it (yes, I have some
understanding in this case). iPXE is based off of forking further
development as of a certain gPXE commit with some backporting of gPXE
development to iPXE.
--
2015 Oct 25
0
Confusion on lpxelinux vs. gpxelinux vs. ipxe vs gpxe.
...PXE real-mode operations that show
up on pre-Westmere CPUs with newer (and stricter) versions of KVM. This
was fixed in a series of commits last year:
http://git.ipxe.org/ipxe.git/commitdiff/6d4deee
http://git.ipxe.org/ipxe.git/commitdiff/5a08b63
http://git.ipxe.org/ipxe.git/commitdiff/c64747d
http://git.ipxe.org/ipxe.git/commitdiff/bcfaf11
along with some patches to avoid unnecessary real-mode transitions
entirely (e.g. by allowing the system timer tick interrupt to happen in
protected mode).
A quick test just now under current KVM (running on a five-year-old Core
i5) shows a do...