| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
"boot_dfltroot", "boot_mute", and "boot_pause" respectively.
|
| |
|
|
| |
did anything, so this commit should be considered a NO-OP.
|
| |
|
|
|
| |
and efi_readin(). This removes MD code from copy.c.
o Don't unconditionally add pal.S to SRCS. It's specific to ia64.
|
| |
|
|
|
| |
bit-fields. Unify the PTE defines accordingly and update all
uses.
|
| |
|
|
|
|
| |
per letter dated July 22, 1999.
Approved by: core
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
things over floppy size limits, I can exclude it for release builds or
something like that. Most of the changes are to get the load_elf.c file
into a seperate elf32_ or elf64_ namespace so that you can have two
ELF loaders present at once. Note that for 64 bit kernels, it actually
starts up the kernel already in 64 bit mode with paging enabled. This
is really easy because we have a known minimum feature set.
Of note is that for amd64, we have to pass in the bios int 15 0xe821
memory map because once in long mode, you absolutely cannot make VM86
calls. amd64 does not use 'struct bootinfo' at all. It is a pure loader
metadata startup, just like sparc64 and powerpc. Much of the
infrastructure to support this was adapted from sparc64.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
NULL is passed. The address of the HCDP table can be found by
iterating over the configuration tables in the EFI system table.
To avoid more duplication, a function can be called with the GUID
of interest. The function will do the scanning. Use the function
in all places where we iterate over the configuration tables in
an attempt to find a specific one.
Bump the loader version number as the result of this.
Approved by: re (blanket)
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Previous kernels unwantingly depended on this mapping, but as
of version 1.123 of src/sys/ia64/ia64/machdep.c this dependency
has been removed. Consequently, one has to update the kernel
before updating the loader. The documented/recommended upgrade
will suffice in this case.
Due to a visible (from the kernels point of view) change in
behaviour, bump the loader version number from 0.3 to 1.0.
Approved by: re (carte blanc)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
pages are 4KB.
o As a second order fix, don't assume we have enough space
after the bootinfo block left in a page to hold the memory
map.
o A third order fix as that we removed the assumption that a
bootinfo block fits in a single 8KB page.
PR: ia64/39415
submitted by: Espen Skoglund <esk@ira.uka.de>
|
| |
|
|
|
| |
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.
|
| |
|
|
| |
hardwiring the location.
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
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.
|
| |
|
|
| |
it to call ExitBootServices.
|
| |
|
|
|
| |
we start changing translation registers. Also, call ExitBootServices
before we jump into the kernel.
|
| |
|
|
| |
* Add EFI network support.
|
| | |
|
| |
|
|
| |
that the kernel loads into using the EFI AllocatePages call.
|
| | |
|
| | |
|
| |
|
