busdma - Remove filter functionality

- Remove filtfunc and filtarg arguments from bus_dma_tag_create() and
fix all callers. All callers use NULL today for both filterfunc and
filterarg with one

busdma - Remove filter functionality

- Remove filtfunc and filtarg arguments from bus_dma_tag_create() and
fix all callers. All callers use NULL today for both filterfunc and
filterarg with one exception: if_jme.

- Remove filter functionality internally and parent tag tracking.
Without filter functions, we do not need to keep track of tag
ancestry. All inheritance of the parent tag's parameters occurs when
creating the new child tag.

- rename run_filter() to addr_needs_bounce().

- FreeBSD keeps the filtfunc and filtarg arguments but requires them to
be NULL.

- Drop filterfunc usage from if_jme.

In case of "JMC260 chip full mask revision 2", which has a hardware bug
when it comes to DMA transfers crossing the 4 GB bounday, the parent
buffer tag already limits DMA memory to 32bit address space. As such it
should be safe to drop the filterfunc. The filterfunc was checking if
the lower 32bits of the physical address used for DMA are all 0. In case
of a 32bit address space, the only address where all lower 32-bits are
all zero is 0 itself and I am here assuming that the physical address 0
is not used for DMA transfers!

Mainly obtained from: FreeBSD (commits 7cb028de, 900907f4, 1228b93b, 3933ff56)

show more ...

libkern: Remove karc4rand() in favor of karc4random_buf()

The latter karc4random_buf()/arc4random_buf() sees more adoptions in
other BSDs as well as the userland. So only reserve the latter and
rem

libkern: Remove karc4rand() in favor of karc4random_buf()

The latter karc4random_buf()/arc4random_buf() sees more adoptions in
other BSDs as well as the userland. So only reserve the latter and
remove the former.

Update the kernel code accordingly to use karc4random_buf() only.

show more ...

re: Sync with Realtek's re-196.04; and fix re_start/re_tx_collect.

- Add several new chips' support, noticably RTL8125 support.
- Reorder chip related initializaton on the attach path a bit;
mainl

re: Sync with Realtek's re-196.04; and fix re_start/re_tx_collect.

- Add several new chips' support, noticably RTL8125 support.
- Reorder chip related initializaton on the attach path a bit;
mainly to make sure ifnet is initialized.
- In re_start(), solely rely on the re_tx_free for the TX descriptor
setup loop. This avoids the fixup on the end of the loop. Add
assertion that the TX descriptor's corresponding mbuf is not setup
yet.
- On RTL8125, the EOF in the TX descriptor is no longer left uncleared
upon TX done, so simply rely on whether the TX descriptor's
corresponding mbuf is set or not to unload the busdma(9) and free the
TX mbuf. We actually should do this instead of rely on the EOF.

Tested-by: me (8101, 8111, 8168, 8125)
Romick <yellowrabbit2010 gmail.com> (8111)
Daniel Fojt <df neosystem.org> (8111)

show more ...

re(4): Fix a wrong check. Looks like copy/paste but not adjusted properly.

This is also in Realtek's v196.04.

Reviewed-by: sephe

netif/re: Sync with Realtek's re-1.95.

Mainly fix some register settings.

kernel: Use NULL for pointers in DRIVER_MODULE().

re: MACFG50 requires defragmentation in software, but no padding for runt.

Reported-by: YONETANI Tomokazu
Tested-by: YONETANI Tomokazu

re: Sync with Realtek's re-1.94

Add two more chips' support.

Tested-by: zrj, Daniel Bilik <ddb neosystem org>

re: Update to Realtek 1.93

Tested-by: me, Tim Darby

kernel/re: Fix hw.re.phy_mdix_mode tunable.

kernel/if_re: Adjust permissions.

re: Leverage Realtek driver's chip/PHY initialization/reset.

It is mainly used to solve all kinds of weirdness, e.g. hanging after
watchdog timeout, and PHY read failure, we have encountered so far

re: Leverage Realtek driver's chip/PHY initialization/reset.

It is mainly used to solve all kinds of weirdness, e.g. hanging after
watchdog timeout, and PHY read failure, we have encountered so far on
these chips.

The DEVMETHODs, ifnet setup, and data path are still ours. miibus(4)
is no longer used, ifmedia(4) is used directly.

NOTE: This change drops the 8139C+ and 8169 w/ external PHY support,
which are deemed to be too old.

Realtek's driver is taken from their website: version 1.92 (2016/10/25).

Tested-by: dillon, zrj

show more ...