Pull up following revision(s) (requested by jmcneill in ticket #241):
	sys/arch/evbarm/conf/BPI: revision 1.12
	sys/arch/arm/allwinner/awin_ir.c: revision 1.2
	sys/arch/arm/allwinner/awin_ir.c: revision 1.3
	sys/arch/arm/allwinner/awin_ir.c: revision 1.4
	sys/arch/evbarm/conf/CUBIEBOARD: revision 1.35
	sys/arch/arm/allwinner/awin_reg.h: revision 1.50
	sys/arch/arm/allwinner/awin_reg.h: revision 1.51
Fix CIR setup. Works on A31 now.
hide a debug printf
add A20 IR support
enable awinir, cir
Pull up following revision(s) (requested by christos in ticket #242):
	distrib/utils/libhack/multibyte.c: revision 1.6
handle the "special" wc NULL case.
Ticket #241 and #242
Additionally pull up revision 1.7 of src/distrib/utils/libhack/multibyte.c,
requested by tsutsui in #242
Update entry for #242
Pull up following revision(s) (requested by oster in ticket #243):
	sys/dev/raidframe/raidframevar.h: revision 1.17
	sys/dev/raidframe/rf_netbsdkintf.c: revision 1.316
	sys/dev/raidframe/rf_reconstruct.c: revision 1.121
Fix a long-standing bug related to rebooting while a
reconstruct-to-spare is underway but not yet complete.
The issue was that a component was being marked as a used_spare when
the rebuild started, not when the rebuild was actually finished.
Marking it as a used_spare meant that the component label on the spare
was being updated such that after a reboot the component would be
considered up-to-date, regardless of whether the rebuild actually
completed!
This fix includes:
 1) Add an additional state "rf_ds_rebuilding_spare" which is used
    to denote that a spare is currently being rebuilt from the live
    components.
 2) Update the comments on the disk states, which were out-of-sync
    with reality.
 3) When rebuilding to a spare component, that spare now enters the
    state rf_ds_rebuilding_spare instead of the state rf_ds_used_spare.
 4) When the rebuild is actually complete then the spare component
    enters the rf_ds_used_spare state.  rf_ds_used_spare is now used
    exclusively for the case where the rebuilding to the spare has
    completed successfully.
XXX: Someday we need to teach raidctl(8) about this new state, and
take out the backwards compatibility code in rf_netbsdkintf.c (see
RAIDFRAME_GET_INFO in raidioctl()).  For today, this fix needs to be
generic enough that it can get backported without major grief.
XXX: Needs pullup to netbsd-5*, netbsd-6*, and netbsd-7
Fixes PR#49244.
Pull up following revision(s) (requested by jmcneill in ticket #244):
	sys/arch/arm/allwinner/awin_hdmi.c: revision 1.13-1.15
	sys/arch/arm/allwinner/awin_hdmiaudio.c: revision 1.4
	sys/arch/arm/allwinner/awin_var.h: revision 1.25
	sys/arch/evbarm/awin/awin_machdep.c: revision 1.29
	sys/dev/i2c/ddc.c: revision 1.4
	sys/dev/i2c/ddcvar.h: revision 1.2
	sys/dev/videomode/edid.c: revision 1.13
	sys/dev/videomode/edidreg.h: revision 1.4
	sys/dev/videomode/edidvar.h: revision 1.3
Parse the extension block count field, and make it available in struct edid_info
--
add ddc_read_edid_block, which is the same as ddc_read_edid but takes an additional block number argument
--
Add support for DVI displays. Detect HDMI vs DVI mode by looking for a
CEA-861-D extension block in the EDID, and then searching this block for
an HDMI vendor-specific data block (HDMI VSDB).
--
Allow for overriding DVI/HDMI detection with a kernel boot arg. Set
hdmi.forcemode=dvi or hdmi.forcemode=hdmi to disable auto-detection.
--
report hotplug status for AUDIO_GETDEV fields, only allow playback if a capable display is connected
--
clear repeater sel bits before setting -- would cause an issue if we ever switched away from a pixel doubling mode
Apply patch (requested by apb in ticket #245):
Update tzdata from 2014g to 2014j.  Some of the changes are:
* A new Zone Pacific/Bougainville, for the part of Papua New Guinea
  that plans to switch from UTC+10 to UTC+11 on 2014-12-28 at 02:00.
* Changes for Fiji, Belarus, and Turks & Caicos that take effect
  at various times in 2014.
* Changes to historical data.
Pull up following revision(s) (requested by manu in ticket #246):
	sys/kern/vfs_mount.c: revision 1.31
	sys/ufs/ffs/ffs_vfsops.c: revision 1.302
	sys/ufs/ufs/ufs_extattr.c: revision 1.44
Fix use-after-free on failed unmount with extended attribute enabled
When unmount failed, for instance because the mount is still busy,
UFS1 extended attributes structures were left freed while the kernel
assumes extended attributes were still enabled. This led to using
UFS1 extended attributes structures after free. With LOCKDEBUG, with
quickly triggers a panic.
The problem is fixed by:
1) clear MNT_EXTATTR flag after extended attributes structures are freed
2) attempt to restart extended attributes after failed unmount
2) set MNT_EXTATTR correctly after extended attributes restart
As a side effect, extended attribute structures are now only initialized
when extended attributes are started for the filesystem.
Pull up following revision(s) (requested by manu in ticket #247):
	sys/ufs/ufs/ufs_extattr.c: revision 1.45
Fix UFS1 extended attribute backend autocreation deadlock
UFS1 extended attribute backend autocration goes through a vn_open()
to create the backend file, and this forces us to release the lock
on the target node, in case the target is within the parents of the
backend file. That created a window within which another thread could
acquire a lock on the target vnode and deadlock awaiting for the
mount extended attribute lock.
We fix the problem by also releasing the mount extended attribute lock
when calling vn_open(), but that lets another thread race us for backend
creation. We just detect this using O_EXCL for vn_open() and by checking
for EEXIST return code. If we are raced, we fail backend creation but
this is not a problem since another thread succeeded on it: we just have
to use the result.
Pull up following revision(s) (requested by plunky in ticket #248):
	sys/netbt/rfcomm_upper.c: revision 1.22
since rfcomm_attach_pcb may be called from (soft) interrupt context
(for incoming connections), use kmem_intr_()
Pull up following revision(s) (requested by skrll in ticket #250):
	sys/arch/arm/allwinner/awin_cnt.c: revision 1.2
s/IPL_SCHED/IPL_HIGH/
This allows binuptime to be called from any interrupt handler.
Pull up following revision(s) (requested by manu in ticket #251):
	sys/arch/acorn26/conf/GENERIC: revision 1.81
	sys/arch/acorn32/conf/GENERIC: revision 1.116
	sys/arch/alpha/conf/GENERIC: revision 1.362
	sys/arch/amd64/conf/ALL: revision 1.23
	sys/arch/amd64/conf/GENERIC: revision 1.404
	sys/arch/amd64/conf/XEN3_DOM0: revision 1.112
	sys/arch/amd64/conf/XEN3_DOMU: revision 1.60
	sys/arch/amiga/conf/GENERIC.in: revision 1.129
	sys/arch/amiga/conf/GENERIC: revision 1.311
	sys/arch/amigappc/conf/GENERIC: revision 1.24
	sys/arch/arc/conf/GENERIC: revision 1.184
	sys/arch/bebox/conf/GENERIC: revision 1.145
	sys/arch/cats/conf/GENERIC: revision 1.155
	sys/arch/cesfic/conf/GENERIC: revision 1.65
	sys/arch/cobalt/conf/GENERIC: revision 1.147
	sys/arch/dreamcast/conf/GENERIC: revision 1.121
	sys/arch/emips/conf/GENERIC: revision 1.15
	sys/arch/epoc32/conf/GENERIC: revision 1.8
	sys/arch/ews4800mips/conf/GENERIC: revision 1.51
	sys/arch/hp300/conf/GENERIC: revision 1.190
	sys/arch/hpcmips/conf/GENERIC: revision 1.229
	sys/arch/hpcsh/conf/GENERIC: revision 1.106
	sys/arch/hppa/conf/GENERIC: revision 1.6
	sys/arch/i386/conf/ALL: revision 1.389
	sys/arch/i386/conf/GENERIC: revision 1.1118
	sys/arch/i386/conf/XEN3_DOM0: revision 1.93
	sys/arch/i386/conf/XEN3_DOMU: revision 1.65
	sys/arch/ibmnws/conf/GENERIC: revision 1.46
	sys/arch/iyonix/conf/GENERIC: revision 1.88
	sys/arch/landisk/conf/GENERIC: revision 1.45
	sys/arch/luna68k/conf/GENERIC: revision 1.119
	sys/arch/mac68k/conf/GENERIC: revision 1.220
	sys/arch/macppc/conf/GENERIC: revision 1.320
	sys/arch/macppc/conf/MAMBO: revision 1.24
	sys/arch/macppc/conf/POWERMAC_G5: revision 1.25
	sys/arch/mipsco/conf/GENERIC: revision 1.88
	sys/arch/mmeye/conf/GENERIC: revision 1.120
	sys/arch/mvme68k/conf/GENERIC: revision 1.94
	sys/arch/mvmeppc/conf/GENERIC: revision 1.24
	sys/arch/netwinder/conf/GENERIC: revision 1.126
	sys/arch/news68k/conf/GENERIC: revision 1.125
	sys/arch/newsmips/conf/GENERIC: revision 1.129
	sys/arch/next68k/conf/GENERIC: revision 1.139
	sys/arch/ofppc/conf/GENERIC: revision 1.157
	sys/arch/pmax/conf/GENERIC64: revision 1.21
	sys/arch/pmax/conf/GENERIC: revision 1.185
	sys/arch/prep/conf/GENERIC: revision 1.174
	sys/arch/rs6000/conf/GENERIC: revision 1.33
	sys/arch/sandpoint/conf/GENERIC: revision 1.88
	sys/arch/sbmips/conf/GENERIC: revision 1.101
	sys/arch/sgimips/conf/GENERIC32_IP12: revision 1.28
	sys/arch/sgimips/conf/GENERIC32_IP2x: revision 1.104
	sys/arch/sgimips/conf/GENERIC32_IP3x: revision 1.106
	sys/arch/shark/conf/GENERIC: revision 1.121
	sys/arch/sparc/conf/GENERIC: revision 1.248
	sys/arch/sparc/conf/TADPOLE3GX: revision 1.65
	sys/arch/sparc64/conf/GENERIC: revision 1.177
	sys/arch/sparc64/conf/NONPLUS64: revision 1.44
	sys/arch/sun2/conf/GENERIC: revision 1.94
	sys/arch/sun3/conf/GENERIC: revision 1.171
	sys/arch/vax/conf/GENERIC: revision 1.193
	sys/arch/vax/conf/VAX780: revision 1.19
	sys/arch/x68k/conf/GENERIC: revision 1.179
	sys/arch/zaurus/conf/GENERIC: revision 1.65
	sys/ufs/files.ufs: revision 1.38
Remove unused extended attributes kernel options

As Masao Uebayashi pointed to me, UFS_EXTATTR_AUTOSTART, LFS_EXTATTR_AUTOSTART
and UFS_EXTATTR_AUTOCREATE are not used anywhere in the code. Remove them
as they have been obsolete for a long time:
UFS_EXTATTR_AUTOSTART was replaced by mount -o extattr
LFS_EXTATTR_AUTOSTART was created to match obsolete UFS_EXTATTR_AUTOSTART
UFS_EXTATTR_AUTOCREATE was replaced by sysctl vfs.ffs.extattr_autocreate
tickets 243-248, 250 & 251
Pull up following revision(s) (requested by skrll in ticket #252):
	sys/arch/arm/allwinner/awin_usb.c: revision 1.17
IPL_SCHED -> IPL_VM
Something isn't MP safe.
Pull up following revision(s) (requested by jmcneill in ticket #253):
	external/mit/xorg/lib/libXft/Makefile: revision 1.6
compile xftrender.c with -O0 to workaround a crash in XftGlyphSpecRender
on earm with gcc 4.8.4
tickes 252 & 253