KeepPXE was broken in 3.74, because we tried to use both bits 0 and 1,
but failed to actually test both bits.  Instead, just use bit 0, but
move the place where we clear the bits.

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

ipappend information is needed for the plain cmdline too, since it may
be used by linux.c32.  While we're at it, clean up the handling of
ipappend lines -- we can rather obviously use a loop for them.

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

Update copyright notices.  Per agreement with my new employer, Intel
Corporation, add Intel copyright notices where appropriate.

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

Impact: bug fix

We were incorrectly looking at [ds:di] instead of [es:di] for
verifying that a command was properly terminated.  Fix.

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

Further simplifications to the command-line parser, both from a code
size and a usability perspective.

Refactor the command line parser to be more of a general parser
instead of treating each option as an ad hoc feature.

Suppress the Loading... prompt if "quiet" is specified on the command
line.  Some messed-up people want it this way.

Make sure no part of the initrd extends into memory that is in a
fractional page at the end of memory.  The kernel may not be able to
map such a fractional page, and therefore will be unable to access
that memory.

Signed-off-by: Sergey Vlasov <vsu@altlinux.ru>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>

The address in EDI returned by the load_high call used to load the
kernel needs to be passed to parse_load_initrd, but the code which
clears memory after setup sectors for 1.2.x kernels was corrupting
low 16 bits of EDI.  In most cases this corruption was not noticed,
because with usual setup sizes DI was set to 0xf800, therefore the
chance of getting the kernel size such that initrd would actually
overwrite the kernel was about 3%.

Signed-off-by: Sergey Vlasov <vsu@altlinux.ru>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>

Attempts to load *.lkrn images were failing with "Not enough memory
to load specified image".  These images have the su_ramdisk_max
header field set to zero, and the code in core/runkernel.inc was
limiting MyHighMemSize too early (before the load_high call used to
load the main part of the kernel).

Signed-off-by: Sergey Vlasov <vsu@altlinux.ru>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>