History log of /dragonfly/sys/dev/netif/re/if_re.c (Results 1 – 25 of 175)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
# bf80ef97 21-Feb-2024 Shingy Shabooya <shingy_shabooya@yahoo.com>

Added support for Realtek E2600 (Killer Ethernet Adapter E2600).


# 030b0c8c 09-Dec-2023 Michael Neumann <mneumann@ntecs.de>

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 ...


Revision tags: v6.4.0, v6.4.0rc1, v6.5.0, v6.2.2, v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0
# 1e1c5fac 02-Dec-2020 Sepherosa Ziehau <sephe@dragonflybsd.org>

ifmedia: Port SIOCGIFXMEDIA from FreeBSD

- Max # of media type is 255 on DragonFly; additional bit was used.
- Description of the media is changed to ###baseXX instead of
###Base-XX; it is more co

ifmedia: Port SIOCGIFXMEDIA from FreeBSD

- Max # of media type is 255 on DragonFly; additional bit was used.
- Description of the media is changed to ###baseXX instead of
###Base-XX; it is more consistent with what we already have.
- Fix some media types in vke(4), e.g. 1000baseT <half-duplex>
is actually never deployed anywhere.
- Use ULL consistently in bce(4) for the if_baudrate.
- Setup if_baudrate properly for re(4).
- Fix typo in mii(4).
- Handle SIOCGIFXMEDIA in re(4) (for 2500baseT) and vke(4) (for
all newly added types).
- Bump kernel version.

show more ...


# 80492964 04-Nov-2020 Sepherosa Ziehau <sephe@dragonflybsd.org>

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 ...


Revision tags: 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
# 52bafeb8 09-Jun-2018 Sepherosa Ziehau <sephe@dragonflybsd.org>

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

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


Revision tags: 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
# a57bab71 27-Feb-2017 Sepherosa Ziehau <sephe@dragonflybsd.org>

re: Only limited versions of this chip require explicit padding.

Certain versions of this chip fail to generate correct UDP checksum
on explicitly padded UDP datagrams.

Reported-and-Tested-by: Dani

re: Only limited versions of this chip require explicit padding.

Certain versions of this chip fail to generate correct UDP checksum
on explicitly padded UDP datagrams.

Reported-and-Tested-by: Daniel Bilik

show more ...


# 1f7ae36f 24-Feb-2017 Sepherosa Ziehau <sephe@dragonflybsd.org>

re: Fix typo for disabling txcsum.

Submitted-by: Daniel Bilik


# 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
# c6d0b8bd 04-Jan-2016 Sepherosa Ziehau <sephe@dragonflybsd.org>

re: Only probe fixed PHY location

Obtained-from: FreeBSD


# 6bab7ea6 04-Jan-2016 Sepherosa Ziehau <sephe@dragonflybsd.org>

re: Reduce GMII PHY read/write timeout

Obtained-from: FreeBSD


# 727ad3a3 04-Jan-2016 Sepherosa Ziehau <sephe@dragonflybsd.org>

re: Change CFG1 and CFG5 after flip EECMD

Obtained-from: FreeBSD


# d7c373a4 03-Jan-2016 Sepherosa Ziehau <sephe@dragonflybsd.org>

re: Disable ASPM

Referenced: 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
# 14929979 25-Jul-2015 Sepherosa Ziehau <sephe@dragonflybsd.org>

netif: Configure mbuf clusters/jclusters limits

Default mbuf clusters limit work for most of the network device
drivers. The drivers modified by this commit:
- Use mbuf jclusters.
- Size of the rec

netif: Configure mbuf clusters/jclusters limits

Default mbuf clusters limit work for most of the network device
drivers. The drivers modified by this commit:
- Use mbuf jclusters.
- Size of the reception queues could be configured.
- Support multiple reception queues.

et(4) and mxge(4) are special; they use non-cluster mbuf for small
packets reception, so we adjust non-cluster mbuf limit manually in
these two drivers.

show more ...


Revision tags: v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5, v4.0.4
# b5523eac 19-Feb-2015 Sascha Wildner <saw@online.de>

kernel: Move us to using M_NOWAIT and M_WAITOK for mbuf functions.

The main reason is that our having to use the MB_WAIT and MB_DONTWAIT
flags was a recurring issue when porting drivers from FreeBSD

kernel: Move us to using M_NOWAIT and M_WAITOK for mbuf functions.

The main reason is that our having to use the MB_WAIT and MB_DONTWAIT
flags was a recurring issue when porting drivers from FreeBSD because
it tended to get forgotten and the code would compile anyway with the
wrong constants. And since MB_WAIT and MB_DONTWAIT ended up as ocflags
for an objcache_get() or objcache_reclaimlist call (which use M_WAITOK
and M_NOWAIT), it was just one big converting back and forth with some
sanitization in between.

This commit allows M_* again for the mbuf functions and keeps the
sanitizing as it was before: when M_WAITOK is among the passed flags,
objcache functions will be called with M_WAITOK and when it is absent,
they will be called with M_NOWAIT. All other flags are scrubbed by the
MB_OCFLAG() macro which does the same as the former MBTOM().

Approved-by: dillon

show more ...


# e7717326 31-Jan-2015 Matthew Dillon <dillon@apollo.backplane.com>

kernel - Remove if_re debugging message

* Remove the 'Debug: OACTIVE was not set when re_tx_free was below minimum!'
kprintf. The case is known to happen every once in a while, we no longer
nee

kernel - Remove if_re debugging message

* Remove the 'Debug: OACTIVE was not set when re_tx_free was below minimum!'
kprintf. The case is known to happen every once in a while, we no longer
need to validate that the path is being hit.

Reported-by: Tim Darby

show more ...


Revision tags: v4.0.3, v4.0.2
# 26595b18 28-Nov-2014 Sascha Wildner <saw@online.de>

kernel: Use the new auto-created sysctl ctx/tree in various drivers.

Everywhere where we formerly rolled a hw.fooX.* per-device ctx/tree
ourselves.

This commit switches it to dev.foo.X.*


Revision tags: v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2
# 0545a061 19-Jul-2014 François Tigeot <ftigeot@wolfpond.org>

re(4): Use MPSAFE callout

The callout function was already protected by a serializer.


# 73029d08 29-Jun-2014 Franco Fichtner <franco@lastsummer.de>

kernel: make pktinfo and cpuid native to ip_input()

In order to remove ether_input_pkt(), switch the prototype
of if_input() and adjust all callers. While there, consolidate
the style of the invoke

kernel: make pktinfo and cpuid native to ip_input()

In order to remove ether_input_pkt(), switch the prototype
of if_input() and adjust all callers. While there, consolidate
the style of the invoke.

Suggested and reviewed by: sephe

show more ...


Revision tags: v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1
# dcb4b80d 27-Nov-2013 Sascha Wildner <saw@online.de>

kernel: Generate miidevs.h, pccarddevs.h and pcidevs.h on the fly.

It removes the need to regenerate those header file after first editing
the associated list of IDs (miidevs, pccarddevs or pcidevs)

kernel: Generate miidevs.h, pccarddevs.h and pcidevs.h on the fly.

It removes the need to regenerate those header file after first editing
the associated list of IDs (miidevs, pccarddevs or pcidevs). After this
commit, editing the list alone is enough to add IDs.

We already did it like that for usb4bsd's usbdevs.h before. This commit
adjusts things for the remaining ID lists.

show more ...


Revision tags: v3.6.0, v3.7.1, v3.6.0rc, v3.7.0
# 4c04919c 04-Sep-2013 Sepherosa Ziehau <sephe@dragonflybsd.org>

re: Add 8401/8402/8106 support

- Fix setup for certain generation of 8105E
- 8101, 8102 and 8105 all need to extract ethernet address from EEPROM


# b991d8c6 04-Sep-2013 Sepherosa Ziehau <sephe@dragonflybsd.org>

re: Add 8411/8168G/8168EP/8168GU/8411B support


# e1ee54f4 04-Sep-2013 Sepherosa Ziehau <sephe@dragonflybsd.org>

re: Remove the macver, which only serves proper EEPROM address handling


1234567