r350845 manu Aug. 10, 2019, 6:58 p.m.
r350844 manu Aug. 10, 2019, 6:50 p.m.
We used the aw_clk_nm clock for clock with only one divider factor
and used a fake multiplier factor. This cannot work properly as we
end up writing the "fake" factor to the register (and so always set
the LSB to 1).
Create a new clock for those.
The reason for not using the clk_div clock is because those clocks are
a bit special. Since they are (almost) all related to video we also need
to set the parent clock (the main PLL) to a frequency that they can support.
As the main PLL have some minimal frequency that they can support we need to
be able to set the main PLL to a multiple of the desired frequency.
Let say you want to have a 71Mhz pixel clock (typical for a 1280x800 display)
and the main PLL cannot go under 192Mhz, you need to set it to 3 times the
desired frequency and set the divider to 3 on the hdmi clock.
So this also introduce the CLK_SET_ROUND_MULTIPLE flag that allow for this kind
of scenario.
r350843 cem Aug. 10, 2019, 6:22 p.m.
r350842 manu Aug. 10, 2019, 5:58 p.m.
- Put all clock and control unit driver in BUS_PASS_RESOURCE except
  for the DE2 CCU as it needs the main CCU to be available.
- Use BUS_PASS_CPU for a20_cpu_cfg as it makes more sense.
- For aw_syscon use SCHEDULER pass as we need it early for drivers
  that attach in BUS_PASS_SUPPORTDEV
- For the rest we can use BUS_PASS_SUPPORTDEV
r350841 ian Aug. 10, 2019, 5:48 p.m.
thread to do the work that involves i2c IO, which sleeps while the IO is
in progress.
r350840 ian Aug. 10, 2019, 5:28 p.m.
buffer allocated at that fixed size anymore).
r350838 ian Aug. 10, 2019, 5:14 p.m.
PR:		239697
Submitted by:	Chuhong Yuan
r350837 ngie Aug. 10, 2019, 3:53 p.m.
This change makes required modifications in runtests to also only require the
aesni module on Intel (i386/amd64) platforms, as it is an Intel specific

MFC after:	1 month
MFC to:		^/stable/12 (support not present on ^/stable/11)
Submitted by:	Greg V <greg@unrelenting.technology>
Differential Revision:	https://reviews.freebsd.org/D21018
r350830 imp Aug. 10, 2019, 4:15 a.m.
We don't need to omit ep and ex from LINT since they have been removed from the
r350827 brooks Aug. 9, 2019, 11:50 p.m.
This is a gcc 8.0+ warning which needed to be silenced on for the riscv
build.  amd64-xtoolchain-gcc still uses gcc 6.4.0 and does not understand
this flag.

Reviewed by:	asomers
Feedback from:	imp
Differential Revision:	https://reviews.freebsd.org/D21195
r350826 bdragon Aug. 9, 2019, 8:16 p.m.
As per r177853, we need to avoid using errno inside user mutex code, since
 signal handlers can interfere with it and mess up libthr internal state.

So, implement _umtx_op_err() instead, which makes a raw syscall and
returns the error value directly instead of using errno.

Approved by: jhibbits (mentor)
Differential Revision: https://reviews.freebsd.org/D20946
r350825 tsoome Aug. 9, 2019, 7:09 p.m.
We can error out due to memory allocation errors, we can not recover from
those and need to get out.
r350816 ae Aug. 9, 2019, 8:58 a.m.
PR:		239694
MFC after:	1 week
r350815 jtl Aug. 9, 2019, 5:18 a.m.
ensure that the subsequent mbuf contains the remainder of the bytes
the caller sought. If this is not the case, fall through to the code
which gathers the bytes in a new mbuf.

This fixes a bug where m_pulldown() could fail to gather all the desired
bytes into consecutive memory.

PR:		238787
Reported by:	A reddit user
Discussed with:	emaste
Obtained from:	NetBSD
MFC after:	3 days
r350814 jhibbits Aug. 9, 2019, 2:20 a.m.
time_t should be printed as intmax_t.  Even though duration should be short, the
correct way to print is intmax_t, not long.

Reported by:	ian,imp