Fork of ipxe; additional commands and features https://git.openslx.org/openslx-ng/ipxe.git/atom/src/arch/i386?h=v0.9.7 2009-02-23T08:43:27+00:00 2009-02-23T08:43:27+00:00 Michael Brown 2009-02-23T08:43:27+00:00 urn:sha1:784d3f336eced5db53a02b272e77927ce20c2236 This is not strictly an entry requirement, but it does mean that a PXE NBP returning without setting %ax will appear to have returned success. 2009-02-23T02:53:38+00:00 H. Peter Anvin 2009-02-18T05:56:08+00:00 urn:sha1:6a3f5d6db7d00a0ce3bd228188d478700f4a0c31 Search for the PXE entry points (via the !PXE or PXENV+ structures) through all known combinations of search methods. Furthermore, if we find a PXENV+ structure, attempt to use it to find the !PXE structure if at all possible. 2009-02-20T21:41:00+00:00 Michael Brown 2009-02-20T21:41:00+00:00 urn:sha1:4dd746a725f69d7b13b24dccff0112158c38dbe3 Avoid passing credentials in the iBFT that were available but not required for login. This works around a problem in the Microsoft iSCSI initiator, which will refuse to initiate sessions if the CHAP password is fewer than 12 characters, even if the target ends up not asking for CHAP authentication. 2009-02-18T18:13:20+00:00 H. Peter Anvin 2009-02-18T06:28:46+00:00 urn:sha1:aaa26f3bd355e20554d142eaded0657e7c351dac The PXE 1.x spec specifies that on NBP entry or on return from INT 1Ah AX=5650h, EDX shall point to the physical address of the PXENV+ structure. The PXE 2.x spec drops this requirement, simply stating that EDX is clobbered. Given the principle "be conservative in what you send, liberal in what you accept", however, we should implement this anyway. 2009-02-18T18:12:32+00:00 Michael Brown 2008-10-27T01:06:00+00:00 urn:sha1:b5577553e59391653f47b9edb12775c080665db0 Certain combinations of PXE stack and BIOS result in a broken INT 18 call, which will leave the system displaying a "PRESS ANY KEY TO REBOOT" message instead of proceeding to the next boot device. On these systems, returning via the PXE stack is the only way to continue to the next boot device. Returning via the PXE stack works only if we haven't already blown away the PXE base code in pxeprefix.S. In most circumstances, we do want to blow away the PXE base code. Base memory is a limited resource, and it is desirable to reclaim as much as possible. When we perform an iSCSI boot, we need to place the iBFT above the 512kB mark, because otherwise it may not be detected by the loaded OS; this may not be possible if the PXE base code is still occupying that memory. Introduce a new prefix type .kkpxe which will preserve both the PXE base code and the UNDI driver (as compared to .kpxe, which preserves the UNDI driver but uninstalls the PXE base code). This prefix type can be used on systems that are known to experience the specific problem of INT 18 being broken, or in builds (such as gpxelinux.0) for which it is particularly important to know that returning to the BIOS will work. Written by H. Peter Anvin <hpa@zytor.com> and Stefan Hajnoczi <stefanha@gmail.com>, minor structural alterations by Michael Brown <mcb30@etherboot.org>. 2009-02-18T04:48:30+00:00 Michael Brown 2009-02-18T04:48:30+00:00 urn:sha1:dd44a7c3140f489b1be7f44a1335732f2b47c63d 2009-02-17T03:52:44+00:00 Daniel Verkamp 2008-09-29T15:45:57+00:00 urn:sha1:dbbd81c1408df1ea62790248455f84f2082418ee 2009-02-17T03:38:40+00:00 Michael Brown 2009-02-17T03:33:26+00:00 urn:sha1:5026a35fef9d036be304d2e3923d40f613531f1b COMBOOT images use INTs to issue API calls; these end up making calls into gPXE from real mode, and so temporarily change the real-mode stack pointer. When our COMBOOT code uses a longjmp() to implement the various "exit COMBOOT image" API calls, this leaves the real-mode stack pointer stuck with its temporary value, which causes problems if we eventually try to exit out of gPXE back to the BIOS. Fix by adding rmsetjmp() and rmlongjmp() calls (analogous to sigsetjmp()/siglongjmp()); these save and restore the additional state needed for real-mode calls to function correctly. 2009-02-17T02:03:16+00:00 Michael Brown 2009-02-17T02:03:16+00:00 urn:sha1:7f903f03afbadd809923a10fac57d59400e94182 2009-02-17T01:45:12+00:00 Michael Brown 2009-02-17T01:45:12+00:00 urn:sha1:14eafc5b8de58c4495087cddfefe89e03ccda70c When chaining COMBOOT images, the old images now get freed correctly.