<vm/pglist.h> -> <uvm/uvm_pglist.h>
<vm/vm_inherit.h> -> <uvm/uvm_inherit.h>
<vm/vm_kern.h> -> into <uvm/uvm_extern.h>
<vm/vm_object.h> -> nothing
<vm/vm_pager.h> -> into <uvm/uvm_pager.h>
also includes a bunch of <vm/vm_page.h> include removals (due to redudancy
with <vm/vm.h>), and a scattering of other similar headers.
such as the LM78 and VT82C686A (and eventually ACPI). Multiple
sensor devices can be hooked registered with `sysmon', and eventually
sysmon will also handle hardware (and software) watchdog timers.
Convert the `lm' and `viaenv' drivers to the new interface.
all the time (which crashes some vaios), get the static configuration,
and if config_search() finds a node, then do the dynamic configuration.
This seems to work fine on multiple vaios (which seem to crash
in different places...go figure).
Also, bring prototypes in-line with KNF and declare static as appropriate.
"#if 0" out pnpbios_getapmtable() and pnpbios_setnode() as they
are not called.
Fix printf()s to print out dv_xname.
Fix a comment typo.
Use manifest constants (PNP_CF_DEVCONF_DYNAMIC, etc.) in calls to
pnpbios_getnode() instead of hardcoded constants.
so that the docking/undocking process can actually complete.
- Track the current docking state, and report the current state when it
changes.
- Make it possible to enable pnpbios verbosity at run-time.
yet.. the keyboard controller actually has 2 PNPBIOS nodes (one to
represent the controller I/O resources and the kbd port IRQ, and one
for the aux port IRQ). To cope with this, we're attaching two instances
of the driver and forge on ahead once both nodes have been seen.
If someone has a better way, please feel free to step forward.
add a lot of skeletal work to pnpbios.
option to handle events from pnpbios in a thread (e.g., hot-doc)
add calls for the other pnpbios functions (e.g., send message etc..)
add most defintions from the pnp doc to new reg file
needed to deal with disabled nodes
-Parse "fixed io descriptors". Their use in nonsense in principle
because 10-bit decoding is implied. Hope this is not real...
-Tolerate mismatches between node size and actually used space
as long as the used size is smaller than the buffer size. There
is at least one broken BIOS which reports node sizes larger than
the used one, and windows obviously doesn't complain...
BIOS and attaches devices to it.
While it is potentially able to deal with all the motherboard ISA
devices, it is only used in hairy cases for now - laptop stuff in
particular.
mrg