src/sys/boot/alpha/libalpha/bootinfo.c, branch release/4.1.0_cvs

This commit was manufactured by cvs2svn to create tag

2000-07-26T21:12:35+00:00

'RELENG_4_1_0_RELEASE'.

This commit was manufactured to restore the state of the 4.1-RELEASE image.
Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs.

* Fix a stack of warnings.

1999-09-01T09:11:14+00:00

* Make it possible to type a filename to boot1 so that it is possible to
  recover from fatally broken versions of /boot/loader.
* Make a start at a CD boot program (not yet functional).

$Id$ -> $FreeBSD$

1999-08-28T01:08:13+00:00

Walk around the end of all the silly guessing of device types and unit

1999-07-21T00:08:54+00:00

numbers that we have been doing in the past, and read /etc/fstab off the
proposed root filesystem to determine the actual device name and vfs
type for the root filesystem.  These are then exported to the kernel
via the environment variable vfs.root.mountfrom.

Revert bootinfo to 1.4 and use a different solution to NULL m_args

1999-03-20T14:13:09+00:00

instead (don't copy).

Don't choke in MOD_ARGS() if mp->m_args is NULL.

1999-03-18T11:00:48+00:00

Add MODINFO_ARGS, parameters passed to a module at load time.

1999-03-08T11:05:52+00:00

VS: ----------------------------------------------------------------------

Fix the bootinfo so that the right values actual make it into the kernel.

1998-10-15T21:55:58+00:00

Get the last used address via a more conservative method, don't depend

1998-10-15T17:06:36+00:00

on the module chain being in increasing address order.

Initial attempt to update the Alpha loader and kernel to use the machine

1998-10-14T09:53:25+00:00

independent elf loader and have access to kld modules.  Jordan and I were
not sure how to create boot floppies, and the things we tried just made
SRM laugh in our faces - but it was upset at boot1 which was not touched
by these changes.  Essentially this has been untested. :-(

What this does is to steal the last three slots from the nine spare longs
in the bootinfo_v1 struct to pass the module base pointer through.

The startup code now to set up and fills in the module and environment
structures, hopefully close enough to the i386 layout to be able to use
the same kernel code.  We now pass though the updated end of the kernel
space used, rather than _end. (like the i386).

If this does not work, it needs to be beaten into shape pronto.  Otherwise
it should be backed out before 3.0.

Pre-approved in principle by: dfr