delta/syslinux.git/core, branch syslinux-3.83-pre2 git.kernel.org: pub/scm/boot/syslinux/syslinux.git PXELINUX: allow filenames up to 251 characters long 2009-07-29T03:20:16+00:00 H. Peter Anvin hpa@zytor.com 2009-07-29T03:19:14+00:00 3cdc491e358508621ce19d851f148aa2932b87bf At least one users really need this, so be nice and provide it... Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
At least one users really need this, so be nice and provide it...

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
PXELINUX: when chaining an NBP, restore *all* registers 2009-06-14T23:01:30+00:00 H. Peter Anvin hpa@zytor.com 2009-06-14T23:01:30+00:00 fd4cab20788d3bf35b76f59dc9b3f1c06587b5e8 On at least ASUS A8N-E, unless *all* registers are restored to pre-PXE status, localboot doesn't work. We were clobbering DS, ESI and EDX when chainloading an NBP, which meant that localboot wouldn't work in the chainloaded NBP. Fix this. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
On at least ASUS A8N-E, unless *all* registers are restored to pre-PXE
status, localboot doesn't work.  We were clobbering DS, ESI and EDX
when chainloading an NBP, which meant that localboot wouldn't work in
the chainloaded NBP.  Fix this.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
bootsect: zero memory above a chainloaded boot sector/NBP 2009-06-14T21:32:42+00:00 H. Peter Anvin hpa@zytor.com 2009-06-14T21:32:42+00:00 18ca4d8cc87761c6a5ab763069fad562fec69b59 Windows RIS has been reported to make inappropriate use of data found in uninitialized memory. To avoid that, clear memory between a chainloaded boot sector or NBP and Free Base Memory. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
Windows RIS has been reported to make inappropriate use of data found
in uninitialized memory.  To avoid that, clear memory between
a chainloaded boot sector or NBP and Free Base Memory.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
pxelinux: actually stop parsing on a null option 2009-06-09T17:19:25+00:00 H. Peter Anvin hpa@zytor.com 2009-06-09T17:19:25+00:00 38e1c74db64e02152e525c2d5c135cb5793d847e Stop the OACK parsing on a null option, even if it isn't the very first option. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
Stop the OACK parsing on a null option, even if it isn't the very
first option.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
pxelinux: revert to using TFTP error 8 2009-06-09T15:51:45+00:00 H. Peter Anvin hpa@zytor.com 2009-06-09T15:51:45+00:00 1869311343efb546ea0a5a47cda7572d863a029a The main reason for ERROR is OACK parsing failure, so revert to using error code 8 (but a fixed text error.) Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
The main reason for ERROR is OACK parsing failure, so revert to using
error code 8 (but a fixed text error.)

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
pxelinux: cleaner test for OACK trailing null bytes 2009-06-09T14:29:13+00:00 H. Peter Anvin hpa@zytor.com 2009-06-09T14:29:13+00:00 1feb9b05ea0b9690a5e5af8b5919d63d6979a2eb Instead of looking for a string of null bytes at the end of the OACK string, simply abort parsing if we run into a null byte where an option is expected; either we are seeing junk at the end of the packet, or we are hopelessly confused about how to make sense of the rest of the packet -- in either case, ignoring is the "liberal" option. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
Instead of looking for a string of null bytes at the end of the OACK
string, simply abort parsing if we run into a null byte where an
option is expected; either we are seeing junk at the end of the
packet, or we are hopelessly confused about how to make sense of the
rest of the packet -- in either case, ignoring is the "liberal"
option.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
PXELINUX: handle OACK packets with extra NULs, cleaner TFTP error 2009-06-09T05:19:41+00:00 H. Peter Anvin hpa@zytor.com 2009-06-09T05:19:41+00:00 6e969f3b4359125780868d9747bc59bbeee86a9e There are apparently TFTP servers in the field which will send OACK packets with extra NUL bytes appended at the end. If we find an OACK packet where the only thing left at some point during processing is NULs, then just consider the packet processed. We have reported all TFTP protocol errors as "tsize required", which is definitely not true anymore. Change error code to 0 (undefined) and the error string to "TFTP error". When this code gets converted to C we'll do better. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
There are apparently TFTP servers in the field which will send OACK
packets with extra NUL bytes appended at the end.  If we find an OACK
packet where the only thing left at some point during processing is
NULs, then just consider the packet processed.

We have reported all TFTP protocol errors as "tsize required", which
is definitely not true anymore.  Change error code to 0 (undefined)
and the error string to "TFTP error".  When this code gets converted
to C we'll do better.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
core: prevent buggy INT 13h from leaving IF=0 2009-06-05T00:24:58+00:00 H. Peter Anvin hpa@zytor.com 2009-06-05T00:24:58+00:00 9147554cd1ab47d51fd4f50a001f05fa665ecfd0 If it can happen for CD-ROM BIOSes, it can probably happen elsewhere, too; make sure we don't leave interrupts disabled after broken INT 13h calls. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
If it can happen for CD-ROM BIOSes, it can probably happen elsewhere,
too; make sure we don't leave interrupts disabled after broken INT 13h
calls.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
isolinux: can't clobber edx when dx contains the drive number... 2009-06-01T04:29:12+00:00 H. Peter Anvin hpa@zytor.com 2009-06-01T04:29:12+00:00 63916a56b59d4f9a873c1a548d0bda5473f456b7 Use ebx to hold the upper half of the partition offset, not edx. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
Use ebx to hold the upper half of the partition offset, not edx.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>
core: when calling abort_check, we're not idle 2009-06-01T03:23:58+00:00 H. Peter Anvin hpa@zytor.com 2009-06-01T03:23:58+00:00 e172b7473502500f0d557134cb9f504e147d0826 When we call abort_check, we're not idle even though we are polling the keyboard. Handle that by calling reset_idle near the top. Signed-off-by: H. Peter Anvin <hpa@zytor.com> 
When we call abort_check, we're not idle even though we are polling
the keyboard.  Handle that by calling reset_idle near the top.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>