Address another warnings reported by Patrick Laimbock when compiling
in userspace. While there, improve consistency.

MFC after: 1 week
Address warnings generated by the clang analyzer.

MFC after: 1 week
Generalise the va to pa code and use it when starting secondary cores

Reviewed by:	ian@, rpaulo@
Differential Revision: https://reviews.freebsd.org/D736
Remove Lvirtaddr and Lphysaddr, these don't appear to be used.
Remove redundant kern conf entries that are inherited via include

Move cfg to spi1 as that's where it is located from the factory
When entering the kernel with the MMU off assume we are running from a
va == pa map.

I'm not sure the code would work if we are not running from the identity
map as the ARM core may attempt to read the next instruction from an
invalid memory location.
Include src.opts.mk after SHLIBDIR has been defined so libnv is installed to
/lib , not /usr/lib

MFC after: 3 days
Approved by: rpaulo (mentor)
Submitted by: antoine
Pointyhat to: me
Phabric: D739
Make two functions static and eliminate an unused #define.
Oops.  vm_map_simplify_entry() is used by mac_proc_vm_revoke_recurse(), so
it can't be static.
Silence a bmake(1) warning in the gif(4) module build
when built with WITHOUT_INET6.

LGTM: 		sbruno
Sponsored by:	The FreeBSD Foundation
Bring over some more status codes from the Linux iwlwifi driver.

The (eventual) intention is to create MIB counters for transmitted
frame completion to count how many packets with each status are
transmitted.

Note the difference between A-MPDU and non A-MPDU status.

Obtained from:	Linux iwlwifi/dvm driver
(more) correctly account TX completion status for A-MPDU session frames.

The rules turn out to be:

* for non-aggregation session TX queues - it's either sent or not sent.
* for aggregation session TX queues - if nframes=1, then the status reflects
  the completed transmission.
* however, for nframes > 1, then this is just a status reflecting what
  the initial transmission did.  The compressed BA (immediate or delayed)
  may not have yet been received, so the actual frame status is in the
  compressed BA updates.

Whilst here, I fiddled with debugging and formatting a bit.

There's also RTS attempts (what the atheros chips call "short retries")
which weren't being logged and they aren't yet being used in the rate
control statistics updates.  For now, at least log them.

TODO:

* This still isn't 100% correct! So I have to tinker with this some more.
  (The failures aren't always failures..)
* Extend the rate control API in net80211 so it can take both short and
  long retry counts.

Tested:

* Intel 5100, STA mode