|
Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1 |
|
| #
e6e07291 |
| 18-Oct-2017 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
re: Sync with Realtek's re-1.94
Add two more chips' support.
Tested-by: zrj, Daniel Bilik <ddb neosystem org>
|
|
Revision tags: v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc |
|
| #
e5a5a436 |
| 03-Nov-2016 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
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 ...
|