| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
RB_MULTIPLE since this seems to be the easiest way to add these flags
for non-forth loaders etc.
|
|
|
|
|
|
|
|
|
|
|
| |
- Don't include ia64_cpu.h and cpu.h
- Guard definitions by _NO_NAMESPACE_POLLUTION
- Move definition of KERNBASE to vmparam.h
o Move definitions of IA64_RR_{BASE|MASK} to vmparam.h
o Move definitions of IA64_PHYS_TO_RR{6|7} to vmparam.h
o While here, remove some left-over Alpha references.
|
|
|
|
|
| |
INTERNALLIB now implies NOPIC and NOPROFILE.
Removed gratuitous NOMAN.
|
|
|
|
|
| |
defining so many extra things in addition to INTERNALLIB. We don't like
repetitive C code and we shouldn't for make code either.
|
|
|
|
| |
INTERNALLIB now.
|
|
|
|
|
| |
(also resort some CFLAGS such that the more "important" value are first so
they are easier to see)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o We don't expect the PLT relocations to follow the .rela section
anymore. We still assume that PLT relocations are long formed,
o Document register usage,
o Improve ILP,
o Fix the FPTR relocation by creating unique OPDs per function.
Comparing functions is valid now,
o The IPLT relocation naturally handles the addend. Deal with it.
We ignore the addend for FPTR relocations for now. It's not at
all clear what it means anyway.
Fix ABI misinterpretation:
o For Elf_Rela relocations, the addend is explicit and should not
be loaded from the memory address we're relocating. Only do that
for Elf_Rel relocations (ie the short form).
o DIR64LSB is not the same as REL64LSB. DIR64LSB applies to a
symbol (S+A), whereas REL64LSB applies to the base address (BD+A),
|
|
|
|
| |
hardwiring the location.
|
|
|
|
| |
resulting binary will be damaged and no longer work.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
instead.
|
|
|
|
| |
fact that the 'ia64-make' wrapper explicitly set it.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
detects and uses the gas section merge support. As a result, a whole bunch
of new sections arrive, including .rodata.str1.8, which was not included
in our custom ldscript.ia64. The result was a loader binary that EFI
rejected.
While here, collect the loader shell commands linker set and include it
in the data area rather than having its own section.
/boot/loader.efi was the last holdout for having a 100% self built ia64
system.
|
|
|
|
| |
or may have the wrong header files.
|
|
|
|
|
| |
in both the condition and for the install. We expect to find
the help file in ${.OBJDIR}.
|
|
|
|
| |
r8. Keep it at the hardwired address for now. Bump the version.
|
|
|
|
|
|
|
|
|
| |
register r8. We continue to write the bootinfo block at the same
hardwired address, because the kernel still expects it there.
It is expected that future kernels use register r8 to get to the
bootinfo block and don't depend on the hardwired address anymore.
Bump the loader version once again due to the interface change.
|
|
|
|
|
|
|
|
| |
only care if it's network or not at this time. If we're loaded from
the network, we set currdev (=loaddev) so that the kernel is loaded
from the network as well. In all other cases we initialize to disk.
This makes netbooting more convenient and can easily be enhanced to
do more elaborate checking.
|
|
|
|
|
|
|
| |
Most significantly (from an interfacing point of view) is the
support for the FPSWA pointer passing. Even though that was added
4 months ago, it's probably not a bad idea to bump the version
number to reflect this.
|
|
|
|
|
|
|
|
|
| |
exists, otherwise we install it anyway. I interpret this as a very
high desire to install ${PROG}.help. Alas, ${PROG}.help doesn't exist
at the moment and neither does loader.help, so in practice this just
doesn't work, no matter how you interpret it. The compromise is to
install ${PROG}.help IFF it exists. I realize we lost creativity with
this commit, but style should have been preserved, AFAICT :-)
|
| |
|
|
|
|
|
| |
o Add -j .dynstr to objcopy. This makes .efi binaries work
when built with a 3.x based toolchain.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
kernel before we call ExitBootServices(). I've typed the definitions
in efifpswa.h from the Intel FPSWA manual (urk).
|
|
|
|
|
| |
should go away on ia64, we should be loader metadata based since that is
the only way we can boot (loader, skiload).
|
| |
|
|
|
|
| |
with the -D flag.
|
|
|
|
| |
the VM registers. This ought to make things slightly more reliable here.
|
|
|
|
|
| |
respectively. This makes IPLTLSB relocations work properly (these are
generated for weak symbols, particularly for _longjmp).
|
|
|
|
| |
work right though - I can't figure out why.
|
| |
|
| |
|
|
|
|
| |
of minor problems and remove some debugging code.
|
| |
|
|
|
|
| |
it to call ExitBootServices.
|
|
|
|
|
| |
we start changing translation registers. Also, call ExitBootServices
before we jump into the kernel.
|
| |
|
| |
|
|
|
|
| |
* Add EFI network support.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|