r368030 ian Nov. 25, 2020, 8:05 p.m.
to work with the pmu and tempmon nodes as well as the soc node.  This allows
interrupts to work on the pmu and tempmon devices even though we don't have
a driver for the low-power gpc interrupt controller (which is not a problem
because we also don't have support for entering deep power-down modes where
it gets used).
r368029 ian Nov. 25, 2020, 7:10 p.m.
This is required for it to work correctly in the GENERIC kernel.
r368028 ian Nov. 25, 2020, 7:08 p.m.
Some imx6 drivers are being converted to use features that weren't available
when they were first written (such as accessing shared device registers via
the syscon pseudo-device), so imx6 custom kernels that reference those
devices will now need this infrastructure in place.
r368026 ian Nov. 25, 2020, 6:09 p.m.
Attach after interrupt controllers, since the attach function tries to
set up an interrupt handler.

Check for the availability of the required firmware early in the attach
code (before allocating resources).  If the firmware is not available, set
a static var to remember that, so that if the device is re-probed on later
passes it won't repeatedly try to attach and then complain again about
missing firmware.
r368025 kp Nov. 25, 2020, 5:15 p.m.
if_link_ifnet() and if_unlink_ifnet() are needed even when VIMAGE is not

MFC after:	2 weeks
Sponsored by:	Modirum MDPay
r368024 kib Nov. 25, 2020, 5:12 p.m.
Reported by:	markj, pho
Tested by:	pho
Sponsored by:	The FreeBSD Foundation
MFC after:	1 week
r368023 kib Nov. 25, 2020, 5:04 p.m.
Sponsored by:	The FreeBSD Foundation
MFC after:	1 week
r368022 kaktus Nov. 25, 2020, 4:30 p.m.
r352913 added decoding of mmap PROT_MAX()'d flags but didn’t account for the
case where different values were specified for PROT_MAX and regular flags.
Fix it.

Submitted by:	sigsys_gmail.com
Reported by:	sigsys_gmail.com
MFC after:	7 days
Differential Revision:	https://reviews.freebsd.org/D27312
r368021 ian Nov. 25, 2020, 3:45 p.m.
This prevents attaching on non-TI systems in the GENERIC kernel.

Reviewed by:	manu@, mmel@
r368020 kp Nov. 25, 2020, 3:07 p.m.
When we terminate a vnet (i.e. jail) we move interfaces back to their home
vnet. We need to protect our access to the V_ifnet CK_LIST.

We could enter NET_EPOCH, but if_detach_internal() (called from if_vmove())
waits for net epoch callback completion. That's not possible from NET_EPOCH.
Instead, we take the IFNET_WLOCK, build a list of the interfaces that need to
move and, once we've released the lock, move them back to their home vnet.

We cannot hold the IFNET_WLOCK() during if_vmove(), because that results in a
LOR between ifnet_sx, in_multi_sx and iflib ctx lock.

Separate out moving the ifp into or out of V_ifnet, so we can hold the lock as
we do the list manipulation, but do not hold it as we if_vmove().

Reviewed by:	melifaro
MFC after:	2 weeks
Sponsored by:	Modirum MDPay
Differential Revision:	https://reviews.freebsd.org/D27279
r368019 emaste Nov. 25, 2020, 2:26 p.m.
-fstack-clash-protection was added in Clang commit e67cbac81211 but was
enabled only on Linux.  It should work fine on FreeBSD as well, so
enable it.

To be discussed and upstreamed with a test.  The OS test should probably
just be removed.

Reviewed by:	dim
MFC after:	1 week
Sponsored by:	The FreeBSD Foundation
Differential Revision:	https://reviews.freebsd.org/D27366
r368018 manu Nov. 25, 2020, 11:21 a.m.
r368017 manu Nov. 25, 2020, 11:20 a.m.
r368016 manu Nov. 25, 2020, 11:19 a.m.
The clock configured by the registers are the 4x version not the 1x.
r368015 kp Nov. 25, 2020, 10:56 a.m.
It no longer serves any purpose, as evidenced by the fact that we never take it
without ifnet_sxlock.

Sponsored by:	Modirum MDPay
Differential Revision:	https://reviews.freebsd.org/D27278