| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
savings of 68 bytes in boot2.
- Also add a comment warning that you can't remove the empty exit()
function.
|
|
|
|
|
| |
method similar to that of the loader to avoid potentially breaking older
drives in that we only use EDD if the desired cylinder is > 1023.
|
|
|
|
| |
PR: 19215
|
|
|
|
|
|
|
|
| |
with the new binutils. Now that we have a decent assembler, all the old
m4 macros are no longer needed. Instead, straight assembly can be used
since as(1) now understands 16-bit addressing, branches, etc. Also,
several bugs have been fixed in as(1), allowing boot0.s to be further
cleaned up.
|
| |
|
|
|
|
|
| |
Reviewed by: jkh, msmith, sos
Approved by: jkh
|
|
|
|
|
|
|
|
|
|
| |
-fschedule-insns as it wasn't such a big win with 2.95 after all.
Add the *BIG* win "-mpreferred-stack-boundary=2" optimiztion submitted by
Dima. GCC 2.95 ensures the stack frame is always properly [opitimally]
aligned by surrounding every function call by code simular to
"addl $-12, %esp" / "addl $12, %esp". Here we need the reduction in space,
with speed not an issue.
|
|
|
|
|
| |
optimizations, we can go from 3 bytes free with the spammed version, to
279 bytes free with the full version.
|
|
|
|
|
|
|
|
| |
Remove some printf() calls, reduce size of buffers, and abbreviate
some strings.
Hopefully the boot people will fix this spamage after the cut over to
Gcc 2.95.2 as the system compiler.
|
|
|
|
|
|
| |
either one gives us an additional 32 bytes of additional space available
when using EGCS 1.1.2. With GCC 2.95.2 -fforce-addr gives us 12 more bytes,
and adding -fschedule-insns gives us an additional 4 bytes.
|
| |
|
|
|
|
| |
means of a build option.
|
| |
|
| |
|
|
|
|
| |
Thanks to: jdp
|
|
|
|
|
| |
boot2 by 16 bytes. I expect this to be temperary until the boot2 authors
can do the proper fix.
|
|
|
|
| |
serial terminals use this as their default rubout key.
|
| |
|
|
|
|
| |
guess this value well in anything other than the simplest of situations.
|
| |
|
|
|
|
|
| |
Submitted by: rvb
Reviewed by: bde
|
|
|
|
|
|
|
|
|
|
| |
Move the relocated boot1 and arg transfer space from 0x600/0x800 to
0x700/0x900. In theory this should make no difference, apart from the fact
that Buslogic controllers happen to use a few bytes at 0x600 for some sort
of scratch space for it's int 0x13 hook (!!!), causing the machine to crash
badly when the boot2 code makes it's callbacks into boot1 for disk IO.
Submitted by: Robert Nordier <rnordier@freebsd.org>
|
| |
|
|
|
|
|
|
| |
loading. This eliminates noise when loading boot/loader; and when
loading a kernel, they generally flash by too fast to be
intelligible anyway.
|
|
|
|
|
|
|
|
| |
interface. Do some general consistency fixes and space optimizations.
Use of some freed-up space to defend against possible BIOS misfeatures.
boot2: Revise disk read interface to provide for boot1 changes. Free
up space for this.
|
|
|
|
| |
by default.
|
|
|
|
|
|
| |
Noticed by: abial
Optimize away a few bytes to make space for the above.
|
| |
|
|
|
|
|
|
| |
Don't display a \b if not acting on it.
Don't process binary zero chars (which result from pressing function
keys, etc. on the PC).
|
| |
|
|
|
|
|
|
|
|
| |
the boot.config settings are persistent, this seems to provide a
useful override capability, and should break only on broken
boot.config's.
Output a cosmetic newline if booting with no input.
|
|
|
|
| |
If we have a boot.config command, display it.
|
|
|
|
|
|
|
| |
Read boot.help before parsing boot.config. We were parsing
boot.config first, which could result in boot.help being read
from a different location (or not found), which would probably
just cause surprise, without being useful.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
cosmetics.
|
|
|
|
| |
twiddle.
|
|
|
|
| |
Optimize reading of system time.
|
|
|
|
| |
Refine slice-handling.
|
|
|
|
| |
Noticed by: Scott Mace <smace@intt.org>
|
| |
|
|
multiple 0xa5 slices; etc.
|