Fix wrong err(3) message (no such thing as IOC_CPU_GETINFO).
mknative files for arm / binutils 2.21.1a
(built with a hack to gas/config/tc-arm.c.)
mknative files for armeb / binutils 2.21.1a
use gstdint.h from libdecnumber.
Regenerate these compiled files properly in our own
xsrc/external/mit/xkeyboard-config/dist/ directory, i.e.
- pull changes from xkeyboard-config 2.0 to 2.3
- put back entries for sharp machines (zaurus and hpcarm wzero3s)
  removed in rev 1.4 (xkeyboard-config 2.0 merge)

XXX1: can't we generate these files during build?
XXX2: hpcarm W-ZERO3 keyboard on X still has some troubles...
Define and use symbolic bits in registers.
Set WARNS?=2.
options PMS_DISABLE_POWERHOOK is obsolete.
Resurrect old thread debugging code. Not hooked in, compiles.
Update description for V4.
Provide regset functions and gut parts that the new debugging thread library
does not provide yet, so that we can link. As expected this does not work
yet.
remove pre-gcc-4.5 mknative remnants that have long ceased to function.
Fix a fallout with my xensuspend merge: talk_to_backend() returns a
boolean, so checking for "true" with "== 0" is... wrong.

Now xennet(4) should work as expected, and not stay in the InitWait state
(which blocks network communication with the backend).

Thanks to riz@ and sborrill@ for reporting breakage with -current
xennet(4) after my merge.
compute the entry size correctly.
move the size marker back to where it was, but fix the name.
Document new *ASSERTMSG() prototype, and update KASSERT(9).

See also
http://mail-index.netbsd.org/tech-kern/2011/09/07/msg011427.html
return the namemax from the bsd statvfs which is filesystem dependent, not
a random value.
use CODA_MAXNAMLEN instead of bogus MAXNAMLEN
use the filesystem specific namemax not a hard-coded MAXNAMLEN
define and use ISO_MAXNAMLEN instead of MAXNAMLEN