Merge thorpej-cfargs2.

branches: 1.16.8;
Merge thorpej-cfargs branch:

Simplify and make extensible the config_search() / config_found() /
config_attach() interfaces: rather than having different variants for
which arguments you want pass along, just have a single call that
takes a variadic list of tag-value arguments.

Adjust all call sites:
- Simplify wherever possible; don't pass along arguments that aren't
actually needed.
- Don't be explicit about what interface attribute is attaching if
the device only has one. (More simplification.)
- Add a config_probe() function to be used in indirect configuiration
situations, making is visibly easier to see when indirect config is
in play, and allowing for future change in semantics. (As of now,
this is just a wrapper around config_match(), but that is an
implementation detail.)

Remove unnecessary or redundant interface attributes where they're not
needed.

There are currently 5 "cfargs" defined:
- CFARG_SUBMATCH (submatch function for direct config)
- CFARG_SEARCH (search function for indirect config)
- CFARG_IATTR (interface attribte)
- CFARG_LOCATORS (locators array)
- CFARG_DEVHANDLE (devhandle_t - wraps OFW, ACPI, etc. handles)

...and a sentinel value CFARG_EOL.

Add some extra sanity checking to ensure that interface attributes
aren't ambiguous.

Use CFARG_DEVHANDLE in MI FDT, OFW, and ACPI code, and macppc and shark
ports to associate those device handles with device_t instance. This
will trickle trough to more places over time (need back-end for pre-OFW
Sun OBP; any others?).

branches: 1.15.8;
RPi4 UEFI firmware 1.1 reports the wrong IRQ for the VC mailbox. Use
polling mode for now until this is sorted out.

branches: 1.14.2;
Split bcm2835 mbox driver into separate fdt and acpi frontends.

Clean up leftover when converting intr_establish() to fdtbus_intr_establish().
The latter accept only flags 0 or FDT_INTR_MPSAFE. For both cases, it add
IST_LEVEL flag for underlying intr_establish() function.

OK skrll

branches: 1.12.2; 1.12.4;
FDTise RapberryPI support. Thanks for jmcneill for a lot of help with this.

The kernel image that the RPI firmware boots is now netbsd.img in the
kernel build directory.

XXX fdtbus_get_reg needs reworking

When expanding an inline function make sure you get the argument order
correct!

Now there's no functional change to expanding bcm2835_intr_establish

Expand the bcm2835_intr_establish inline.

No functional change.

branches: 1.9.2;
Whitespace.

Mailbox improvements from mlelstv@

Serialise access to the mailbox and use interrupts.

XXX if (cold) should go

Ensure correctness of bus_dmamap_sync operations. Shouldn't affect RPI.

Trailing whitespace

branches: 1.5.2;
Whitespace

serialize bcmmbox_request

allow for a single board specific device to attach to the mbox driver

branches: 1.2.2; 1.2.4;
As we'll soon get boot-time information via the mailbox method, seperate
the actual access code into a seperate file that can be used by itself.

First pass at a VC mailbox driver.

Merge thorpej-cfargs branch:

Simplify and make extensible the config_search() / config_found() /
config_attach() interfaces: rather than having different variants for
which arguments you want pass along, just have a single call that
takes a variadic list of tag-value arguments.

Adjust all call sites:
- Simplify wherever possible; don't pass along arguments that aren't
actually needed.
- Don't be explicit about what interface attribute is attaching if
the device only has one. (More simplification.)
- Add a config_probe() function to be used in indirect configuiration
situations, making is visibly easier to see when indirect config is
in play, and allowing for future change in semantics. (As of now,
this is just a wrapper around config_match(), but that is an
implementation detail.)

Remove unnecessary or redundant interface attributes where they're not
needed.

There are currently 5 "cfargs" defined:
- CFARG_SUBMATCH (submatch function for direct config)
- CFARG_SEARCH (search function for indirect config)
- CFARG_IATTR (interface attribte)
- CFARG_LOCATORS (locators array)
- CFARG_DEVHANDLE (devhandle_t - wraps OFW, ACPI, etc. handles)

...and a sentinel value CFARG_EOL.

Add some extra sanity checking to ensure that interface attributes
aren't ambiguous.

Use CFARG_DEVHANDLE in MI FDT, OFW, and ACPI code, and macppc and shark
ports to associate those device handles with device_t instance. This
will trickle trough to more places over time (need back-end for pre-OFW
Sun OBP; any others?).

branches: 1.15.8;
RPi4 UEFI firmware 1.1 reports the wrong IRQ for the VC mailbox. Use
polling mode for now until this is sorted out.

branches: 1.14.2;
Split bcm2835 mbox driver into separate fdt and acpi frontends.

Clean up leftover when converting intr_establish() to fdtbus_intr_establish().
The latter accept only flags 0 or FDT_INTR_MPSAFE. For both cases, it add
IST_LEVEL flag for underlying intr_establish() function.

OK skrll

branches: 1.12.2; 1.12.4;
FDTise RapberryPI support. Thanks for jmcneill for a lot of help with this.

The kernel image that the RPI firmware boots is now netbsd.img in the
kernel build directory.

XXX fdtbus_get_reg needs reworking

When expanding an inline function make sure you get the argument order
correct!

Now there's no functional change to expanding bcm2835_intr_establish

Expand the bcm2835_intr_establish inline.

No functional change.

branches: 1.9.2;
Whitespace.

Mailbox improvements from mlelstv@

Serialise access to the mailbox and use interrupts.

XXX if (cold) should go

Ensure correctness of bus_dmamap_sync operations. Shouldn't affect RPI.

Trailing whitespace

branches: 1.5.2;
Whitespace

serialize bcmmbox_request

allow for a single board specific device to attach to the mbox driver

branches: 1.2.2; 1.2.4;
As we'll soon get boot-time information via the mailbox method, seperate
the actual access code into a seperate file that can be used by itself.

First pass at a VC mailbox driver.

RPi4 UEFI firmware 1.1 reports the wrong IRQ for the VC mailbox. Use
polling mode for now until this is sorted out.

Split bcm2835 mbox driver into separate fdt and acpi frontends.

Clean up leftover when converting intr_establish() to fdtbus_intr_establish().
The latter accept only flags 0 or FDT_INTR_MPSAFE. For both cases, it add
IST_LEVEL flag for underlying intr_establish() function.

OK skrll

branches: 1.12.2; 1.12.4;
FDTise RapberryPI support. Thanks for jmcneill for a lot of help with this.

The kernel image that the RPI firmware boots is now netbsd.img in the
kernel build directory.

XXX fdtbus_get_reg needs reworking

When expanding an inline function make sure you get the argument order
correct!

Now there's no functional change to expanding bcm2835_intr_establish

Expand the bcm2835_intr_establish inline.

No functional change.

branches: 1.9.2;
Whitespace.

Mailbox improvements from mlelstv@

Serialise access to the mailbox and use interrupts.

XXX if (cold) should go

Ensure correctness of bus_dmamap_sync operations. Shouldn't affect RPI.

Trailing whitespace

branches: 1.5.2;
Whitespace

serialize bcmmbox_request

allow for a single board specific device to attach to the mbox driver

branches: 1.2.2; 1.2.4;
As we'll soon get boot-time information via the mailbox method, seperate
the actual access code into a seperate file that can be used by itself.

First pass at a VC mailbox driver.

Split bcm2835 mbox driver into separate fdt and acpi frontends.

Clean up leftover when converting intr_establish() to fdtbus_intr_establish().
The latter accept only flags 0 or FDT_INTR_MPSAFE. For both cases, it add
IST_LEVEL flag for underlying intr_establish() function.

OK skrll

branches: 1.12.2; 1.12.4;
FDTise RapberryPI support. Thanks for jmcneill for a lot of help with this.

The kernel image that the RPI firmware boots is now netbsd.img in the
kernel build directory.

XXX fdtbus_get_reg needs reworking

When expanding an inline function make sure you get the argument order
correct!

Now there's no functional change to expanding bcm2835_intr_establish

Expand the bcm2835_intr_establish inline.

No functional change.

branches: 1.9.2;
Whitespace.

Mailbox improvements from mlelstv@

Serialise access to the mailbox and use interrupts.

XXX if (cold) should go

Ensure correctness of bus_dmamap_sync operations. Shouldn't affect RPI.

Trailing whitespace

branches: 1.5.2;
Whitespace

serialize bcmmbox_request

allow for a single board specific device to attach to the mbox driver

branches: 1.2.2; 1.2.4;
As we'll soon get boot-time information via the mailbox method, seperate
the actual access code into a seperate file that can be used by itself.

First pass at a VC mailbox driver.

Clean up leftover when converting intr_establish() to fdtbus_intr_establish().
The latter accept only flags 0 or FDT_INTR_MPSAFE. For both cases, it add
IST_LEVEL flag for underlying intr_establish() function.

OK skrll

branches: 1.12.2;
FDTise RapberryPI support. Thanks for jmcneill for a lot of help with this.

The kernel image that the RPI firmware boots is now netbsd.img in the
kernel build directory.

XXX fdtbus_get_reg needs reworking

When expanding an inline function make sure you get the argument order
correct!

Now there's no functional change to expanding bcm2835_intr_establish

Expand the bcm2835_intr_establish inline.

No functional change.

branches: 1.9.2;
Whitespace.

Mailbox improvements from mlelstv@

Serialise access to the mailbox and use interrupts.

XXX if (cold) should go

Ensure correctness of bus_dmamap_sync operations. Shouldn't affect RPI.

Trailing whitespace

branches: 1.5.2;
Whitespace

serialize bcmmbox_request

allow for a single board specific device to attach to the mbox driver

branches: 1.2.2; 1.2.4;
As we'll soon get boot-time information via the mailbox method, seperate
the actual access code into a seperate file that can be used by itself.

First pass at a VC mailbox driver.

FDTise RapberryPI support. Thanks for jmcneill for a lot of help with this.

The kernel image that the RPI firmware boots is now netbsd.img in the
kernel build directory.

XXX fdtbus_get_reg needs reworking

When expanding an inline function make sure you get the argument order
correct!

Now there's no functional change to expanding bcm2835_intr_establish

Expand the bcm2835_intr_establish inline.

No functional change.

branches: 1.9.2;
Whitespace.

Mailbox improvements from mlelstv@

Serialise access to the mailbox and use interrupts.

XXX if (cold) should go

Ensure correctness of bus_dmamap_sync operations. Shouldn't affect RPI.

Trailing whitespace

branches: 1.5.2;
Whitespace

serialize bcmmbox_request

allow for a single board specific device to attach to the mbox driver

branches: 1.2.2; 1.2.4;
As we'll soon get boot-time information via the mailbox method, seperate
the actual access code into a seperate file that can be used by itself.

First pass at a VC mailbox driver.