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, 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 ...
|
Revision tags: v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2 |
|
#
727ad3a3 |
| 04-Jan-2016 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
re: Change CFG1 and CFG5 after flip EECMD
Obtained-from: FreeBSD
|
#
5b1a5f62 |
| 03-Jan-2016 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
re: Update Realtek PHY power management related bits
Obtained-from: FreeBSD
|
Revision tags: v4.4.1, v4.4.0, v4.5.0, v4.4.0rc |
|
#
bffe841b |
| 06-Nov-2015 |
Sascha Wildner <saw@online.de> |
kernel/if_re: Add support for the Realtek 8168H.
It is found in the Intel NUC5CPYH, for example.
Adapted from FreeBSD.
Reported-and-tested-by: Michael Iline <michael.iline@yahoo.com>
|
Revision tags: v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.7.0 |
|
#
e0e8cd1d |
| 04-Sep-2013 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
re: Add more hardware revision for 10/100 chips
|
#
fbe179e9 |
| 04-Sep-2013 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
re: Add more hardware revision for 8411 and newer 8168
|
#
ae079f0d |
| 04-Sep-2013 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
re: Change the hardware revision mask
This keeps us align w/ Realtek's 8168/8101 Linux driver
|
Revision tags: v3.4.3, v3.4.2, v3.4.0, v3.4.1, v3.4.0rc, v3.5.0 |
|
#
f922383e |
| 22-Dec-2012 |
YONETANI Tomokazu <y0netan1@dragonflybsd.org> |
re: RealTek8111F found in ASUS C60M1-I
DragonFly-issue: http://bugs.dragonflybsd.org/issue2479
|
Revision tags: v3.2.2, v3.2.1, v3.2.0, v3.3.0, v3.0.3 |
|
#
0abd0dff |
| 12-May-2012 |
Sascha Wildner <saw@online.de> |
re(4): Add support for the 8105E found in the Acer Aspire One D257.
Submitted-by: Francis Gudin <fgudin@nerim.net>
|
Revision tags: v3.0.2, v3.0.1, v3.1.0, v3.0.0 |
|
#
86d7f5d3 |
| 26-Nov-2011 |
John Marino <draco@marino.st> |
Initial import of binutils 2.22 on the new vendor branch
Future versions of binutils will also reside on this branch rather than continuing to create new binutils branches for each new version.
|
Revision tags: v2.12.0, v2.13.0 |
|
#
6b0184c4 |
| 27-May-2011 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
re(4): Correct EEPROM location for certain versions of 8168F/8168E-VL
|
#
0f4de8aa |
| 27-May-2011 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
re(4): Preliminary 8168F support
|
#
6feb3493 |
| 27-May-2011 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
re(4): Add 8168DP support
|
Revision tags: v2.10.1, v2.11.0, v2.10.0, v2.9.1, v2.8.2, v2.8.1, v2.8.0, v2.9.0, v2.6.3, v2.7.3, v2.6.2, v2.7.2, v2.7.1, v2.6.1, v2.7.0, v2.6.0, v2.5.1, v2.4.1, v2.5.0, v2.4.0, v2.3.2, v2.3.1, v2.2.1, v2.2.0, v2.3.0, v2.1.1 |
|
#
7fbab15d |
| 30-Nov-2008 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
Filter out 8139 chips by PCI revid. It looks like certain 8139 does have same hardware revision (in TXCFG) as 8139C+.
Reported-by: Antonio Huete Jimenez <ahuete.devel@gmail.com> Obtained-from: Free
Filter out 8139 chips by PCI revid. It looks like certain 8139 does have same hardware revision (in TXCFG) as 8139C+.
Reported-by: Antonio Huete Jimenez <ahuete.devel@gmail.com> Obtained-from: FreeBSD
show more ...
|
#
0d73dcef |
| 19-Oct-2008 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
- In re_stop(), call re_reset(), which is supposed to stop TX/RX engines. - In re_reset(), don't touch 0x82 (a magic CSR), which seems to be 8110/8169 specific. Write 1 to it on attach path. Acc
- In re_stop(), call re_reset(), which is supposed to stop TX/RX engines. - In re_reset(), don't touch 0x82 (a magic CSR), which seems to be 8110/8169 specific. Write 1 to it on attach path. According-to: RealTek r8169-6.007.00 - For certain chips (looks like all MAC2 chips), RE_CMD_RESET will not stop TX/RX engines, a seperate command (RE_CMD_STOPREQ) must be issued before RE_CMD_RESET. According-to: RealTek r8168-8.008.00
show more ...
|
#
afdeb9da |
| 16-Oct-2008 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
Add hardware csum offload support for MAC style 2 chips, which include 8102E, 8102EL, 8168C, 8168CP and 8168D.
Obtained-from: RealTek r8101-1.009.00 r8168-8.008.00
Add RE_C_AUTOPAD capability to i
Add hardware csum offload support for MAC style 2 chips, which include 8102E, 8102EL, 8168C, 8168CP and 8168D.
Obtained-from: RealTek r8101-1.009.00 r8168-8.008.00
Add RE_C_AUTOPAD capability to indicate hardware could correctly pad short ether frames. Turn it on for newer version of 8168B (0x38000000 and 0xb8000000) and MAC style 2 chips; manually padding short UDP packets for newer version 8168B will result in incorrect UDP csum, while manually padding short ICMP packets for MAC style 2 chips will result in both incorrect IP header csum and incorrect IP length (o_O)
show more ...
|
#
b7bb5f55 |
| 14-Oct-2008 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
- Adjust PCI latency timer on all types of chips - Adjust PCI cache line size for 8110/8169 chips - For certain revision of 8101E, reading MAC address from IDRx may not work; read from EEPROM inste
- Adjust PCI latency timer on all types of chips - Adjust PCI cache line size for 8110/8169 chips - For certain revision of 8101E, reading MAC address from IDRx may not work; read from EEPROM instead - Add comment that adjusting config1 and config5 may cause unrecoverible disaster
Obtained-from: RealTek Linux drivers
show more ...
|
#
be31f077 |
| 14-Oct-2008 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
0x28000000 is 8168D according to Realtek r8168-8.008.00 driver
|
#
3e2dae44 |
| 13-Oct-2008 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
Bring in some PCI register settings from RealTek BSD driver v176. Disable the PCI register configuration for "style 2 MAC", add comment about it.
|
#
a1b67fc3 |
| 12-Oct-2008 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
- Nuke re_type, add RE_C_8139CP to indicate the chip is 8139C+ - Change hardware revision mask from 0x7cc00000 to 0xfc800000 Obtained-from: Realtek BSD driver v176 - Convert MAC mode to MAC version
- Nuke re_type, add RE_C_8139CP to indicate the chip is 8139C+ - Change hardware revision mask from 0x7cc00000 to 0xfc800000 Obtained-from: Realtek BSD driver v176 - Convert MAC mode to MAC version and save MAC version in softc Obtained-from: Realtek BSD driver v176 - Add hardware revision 0x34800000(8102E) and 0x28000000(chip name is unknown) Obtained-from: Realtek BSD driver v176
show more ...
|
#
9a1a3916 |
| 09-Oct-2008 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
Rename some HWREV
|
#
d4d77345 |
| 09-Oct-2008 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
Use hardware timer to simulate interrupt moderation. Old devices will no longer be livelocked when they are receiving on GigE line. Newer devices also gain well controlled interrupt rate.
If hardw
Use hardware timer to simulate interrupt moderation. Old devices will no longer be livelocked when they are receiving on GigE line. Newer devices also gain well controlled interrupt rate.
If hardware supports interrupt moderation (e.g. 8168B, 8168C), you could also use hardware based interrupt moderation, however, due to lack of necessary information it does not work as reliably as simulated interrupt moderation. It is _not_ recommended currently.
By default, PCI-E devices' simulated interrupt moderation timer is set to 75us, while PCI devices' is set to 125us.
show more ...
|
#
7833c21f |
| 08-Oct-2008 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
LINKCHG interrupt is still needed
|
#
92d4e6ac |
| 07-Oct-2008 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
- Nuke interrupt bits definition which don't apply to 8169 - Don't test TX desc unavailable bit in re_intr, since it is never enabled
|
#
931d6f1f |
| 06-Oct-2008 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
Add RX interrupt moderation suport for PCI-E GigaE chips.
Interrupt moderation register position is obtained from Realtek's BSD driver v176. The meaning of the IM register bits is partially reverse
Add RX interrupt moderation suport for PCI-E GigaE chips.
Interrupt moderation register position is obtained from Realtek's BSD driver v176. The meaning of the IM register bits is partially reverse engineered: RX timer position and unit.
This kind of interrupt moderation does not work on PCI GigaE chips.
show more ...
|