Add range for local interrupt to ranges property. Somehow, it was missed.

In D5730#123890, @andrew wrote:

This feels a little over engineered.

(1) An ipi argument was added to PIC_IPI_SEND method to explicitly specify which ipi should be send. Some controllers use one ISRC for all IPIs (e.g. RPI2 uses a mailbox interrupt), so this simplifies things for them.
(2) Update to current was done.

Change intr_isrc_dispatch() return value from void to int to signal that an interrupt (ISRC) was not handled. Even ISRC with handlers does not guarantee that it happens. So, it's only a PIC responsibility now to act with a stray interrupt - e.g., disable interrupt and does EOI. Note that calling of PIC_DISABLE_INTR() from INTRNG was not enough.

Remove unused ipi_next_num variable.
Include opt_acpi.h to subr_intr.c.
Remove FDT ifdefs from mpic.c as the driver is only for FDT.

Was this committed in r282779? Could it be closed?

D2035 was committed in r283947. Can this be closed/abandoned?

Commited in r282547. Can it be closed?

In D4009#89373, @wma_semihalf.com wrote:

Thanks. In that case I'll wait for the generic minidump format to be integrated first.

Update the patch to r294822.

Yes, in case of LPAE, the interface is general and only thing which will be different (but transparent) is pt2_entry_t definition. It's same as in vm_paddr_t case. Then, of course, the mapping size for 4K page won't be 4 bytes.