en Copyright 2015 Java http://kernelsources.org:8080/source/history/freebsd/sys/modules/re/Makefile#e9ac41698b2f322d55ccf9da50a3596edb2c1800 Remove residual blank line at start of MakefileThis is a residual of the $FreeBSD$ removal.MFC After: 3 days (though I'll just run the command on the branches)Sponsored by: Netflix List of files: /freebsd/sys/modules/re/Makefile Mon, 15 Jul 2024 06:46:32 +0200 Warner Losh <imp@FreeBSD.org> http://kernelsources.org:8080/source/history/freebsd/sys/modules/re/Makefile#031beb4e239bfce798af17f5fe8dba8bcaf13d99 sys: Remove $FreeBSD$: one-line sh patternRemove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/ List of files: /freebsd/sys/modules/re/Makefile Wed, 16 Aug 2023 19:54:58 +0200 Warner Losh <imp@FreeBSD.org> http://kernelsources.org:8080/source/history/freebsd/sys/modules/re/Makefile#b111430e54537a66080df115c3a2950a2922da5a mii: Add opt_platform.h to all miibus driversmiivar.h includes opt_platform.h. Make sure all the drivers that use themiibus_if.h interface file have opt_platform.h as well. While some ofthese may not, strictly speaking, need it, it's easier to include ituniversally for miibus.Sponsored by: Netflix List of files: /freebsd/sys/modules/re/Makefile Tue, 05 Apr 2022 21:40:01 +0200 Warner Losh <imp@FreeBSD.org> http://kernelsources.org:8080/source/history/freebsd/sys/modules/re/Makefile#193d9e768ba63fcfb187cfd17f461f7d41345048 sys/modules: normalize .CURDIR-relative paths to SRCTOPThis simplifies make output/logicTested with: `cd sys/modules; make ALL_MODULES=` on amd64MFC after: 1 monthSponsored by: Dell EMC Isilon List of files: /freebsd/sys/modules/re/Makefile Sat, 04 Mar 2017 11:10:17 +0100 Enji Cooper <ngie@FreeBSD.org> http://kernelsources.org:8080/source/history/freebsd/sys/modules/re/Makefile#b6de9e91bd2c47efaeec72a08642f8fd99cc7b20 Remove bridge(4) from the tree. if_bridge(4) is a full functionalreplacement and has additional features which make it superior.Discussed on: -archReviewed by: thompsaX-MFC-after: never (RELENG_6 as transition period) List of files: /freebsd/sys/modules/re/Makefile Tue, 27 Sep 2005 20:10:43 +0200 Max Laier <mlaier@FreeBSD.org> http://kernelsources.org:8080/source/history/freebsd/sys/modules/re/Makefile#3ad525ef3c88e26f354fb6149970e848522b0235 Fix PATH: directive in sys/modules/re/Makefile, and add the re(4) driver todevd.conf.Pointed out by: Larry Rosenman List of files: /freebsd/sys/modules/re/Makefile Mon, 08 Sep 2003 05:24:29 +0200 Bill Paul <wpaul@FreeBSD.org> http://kernelsources.org:8080/source/history/freebsd/sys/modules/re/Makefile#a94100fa9b9ddccb74164cb9407e69fba557dbac Take the support for the 8139C+/8169/8169S/8110S chips out of therl(4) driver and put it in a new re(4) driver. The re(4) driver sharesthe if_rlreg.h file with rl(4) but is a separate module. (UltimatelyI may change this. For now, it's convenient.)rl(4) has been modified so that it will never attach to an 8139C+chip, leaving it to re(4) instead. Only re(4) has the PCI IDs tomatch the 8169/8169S/8110S gigE chips. if_re.c contains the samebasic code that was originally bolted onto if_rl.c, with thefollowing updates:- Added support for jumbo frames. Currently, there seems to be a limit of approximately 6200 bytes for jumbo frames on transmit. (This was determined via experimentation.) The 8169S/8110S chips apparently are limited to 7.5K frames on transmit. This may require some more work, though the framework to handle jumbo frames on RX is in place: the re_rxeof() routine will gather up frames than span multiple 2K clusters into a single mbuf list.- Fixed bug in re_txeof(): if we reap some of the TX buffers, but there are still some pending, re-arm the timer before exiting re_txeof() so that another timeout interrupt will be generated, just in case re_start() doesn't do it for us.- Handle the 'link state changed' interrupt- Fix a detach bug. If re(4) is loaded as a module, and you do tcpdump -i re0, then you do 'kldunload if_re,' the system will panic after a few seconds. This happens because ether_ifdetach() ends up calling the BPF detach code, which notices the interface is in promiscuous mode and tries to switch promisc mode off while detaching the BPF listner. This ultimately results in a call to re_ioctl() (due to SIOCSIFFLAGS), which in turn calls re_init() to handle the IFF_PROMISC flag change. Unfortunately, calling re_init() here turns the chip back on and restarts the 1-second timeout loop that drives re_tick(). By the time the timeout fires, if_re.ko has been unloaded, which results in a call to invalid code and blows up the system. To fix this, I cleared the IFF_UP flag before calling ether_ifdetach(), which stops the ioctl routine from trying to reset the chip.- Modified comments in re_rxeof() relating to the difference in RX descriptor status bit layout between the 8139C+ and the gigE chips. The layout is different because the frame length field was expanded from 12 bits to 13, and they got rid of one of the status bits to make room.- Add diagnostic code (re_diag()) to test for the case where a user has installed a broken 32-bit 8169 PCI NIC in a 64-bit slot. Some NICs have the REQ64# and ACK64# lines connected even though the board is 32-bit only (in this case, they should be pulled high). This fools the chip into doing 64-bit DMA transfers even though there is no 64-bit data path. To detect this, re_diag() puts the chip into digital loopback mode and sets the receiver to promiscuous mode, then initiates a single 64-byte packet transmission. The frame is echoed back to the host, and if the frame contents are intact, we know DMA is working correctly, otherwise we complain loudly on the console and abort the device attach. (At the moment, I don't know of any way to work around the problem other than physically modifying the board, so until/unless I can think of a software workaround, this will have do to.)- Created re(4) man page- Modified rlphy.c to allow re(4) to attach as well as rl(4).Note that this code works for the sample 8169/Marvell 88E1000 NICthat I have, but probably won't work for the 8169S/8110S chips.RealTek has sent me some sample NICs, but they haven't arrived yet.I will probably need to add an rlgphy driver to handle the on-boardPHY in the 8169S/8110S (it needs special DSP initialization). List of files: /freebsd/sys/modules/re/Makefile Mon, 08 Sep 2003 04:11:25 +0200 Bill Paul <wpaul@FreeBSD.org> http://kernelsources.org:8080/source/history/freebsd/sys/modules/re/Makefile#b6de9e91bd2c47efaeec72a08642f8fd99cc7b20 Remove bridge(4) from the tree. if_bridge(4) is a full functionalreplacement and has additional features which make it superior.Discussed on: -archReviewed by: thompsaX-MFC-after: never (RELENG_6 as transition period) List of files: /freebsd/sys/modules/re/Makefile Tue, 27 Sep 2005 20:10:43 +0200 Max Laier <mlaier@FreeBSD.org> http://kernelsources.org:8080/source/history/freebsd/sys/modules/re/Makefile#3ad525ef3c88e26f354fb6149970e848522b0235 Fix PATH: directive in sys/modules/re/Makefile, and add the re(4) driver todevd.conf.Pointed out by: Larry Rosenman List of files: /freebsd/sys/modules/re/Makefile Mon, 08 Sep 2003 05:24:29 +0200 Bill Paul <wpaul@FreeBSD.org> http://kernelsources.org:8080/source/history/freebsd/sys/modules/re/Makefile#a94100fa9b9ddccb74164cb9407e69fba557dbac Take the support for the 8139C+/8169/8169S/8110S chips out of therl(4) driver and put it in a new re(4) driver. The re(4) driver sharesthe if_rlreg.h file with rl(4) but is a separate module. (UltimatelyI may change this. For now, it's convenient.)rl(4) has been modified so that it will never attach to an 8139C+chip, leaving it to re(4) instead. Only re(4) has the PCI IDs tomatch the 8169/8169S/8110S gigE chips. if_re.c contains the samebasic code that was originally bolted onto if_rl.c, with thefollowing updates:- Added support for jumbo frames. Currently, there seems to be a limit of approximately 6200 bytes for jumbo frames on transmit. (This was determined via experimentation.) The 8169S/8110S chips apparently are limited to 7.5K frames on transmit. This may require some more work, though the framework to handle jumbo frames on RX is in place: the re_rxeof() routine will gather up frames than span multiple 2K clusters into a single mbuf list.- Fixed bug in re_txeof(): if we reap some of the TX buffers, but there are still some pending, re-arm the timer before exiting re_txeof() so that another timeout interrupt will be generated, just in case re_start() doesn't do it for us.- Handle the 'link state changed' interrupt- Fix a detach bug. If re(4) is loaded as a module, and you do tcpdump -i re0, then you do 'kldunload if_re,' the system will panic after a few seconds. This happens because ether_ifdetach() ends up calling the BPF detach code, which notices the interface is in promiscuous mode and tries to switch promisc mode off while detaching the BPF listner. This ultimately results in a call to re_ioctl() (due to SIOCSIFFLAGS), which in turn calls re_init() to handle the IFF_PROMISC flag change. Unfortunately, calling re_init() here turns the chip back on and restarts the 1-second timeout loop that drives re_tick(). By the time the timeout fires, if_re.ko has been unloaded, which results in a call to invalid code and blows up the system. To fix this, I cleared the IFF_UP flag before calling ether_ifdetach(), which stops the ioctl routine from trying to reset the chip.- Modified comments in re_rxeof() relating to the difference in RX descriptor status bit layout between the 8139C+ and the gigE chips. The layout is different because the frame length field was expanded from 12 bits to 13, and they got rid of one of the status bits to make room.- Add diagnostic code (re_diag()) to test for the case where a user has installed a broken 32-bit 8169 PCI NIC in a 64-bit slot. Some NICs have the REQ64# and ACK64# lines connected even though the board is 32-bit only (in this case, they should be pulled high). This fools the chip into doing 64-bit DMA transfers even though there is no 64-bit data path. To detect this, re_diag() puts the chip into digital loopback mode and sets the receiver to promiscuous mode, then initiates a single 64-byte packet transmission. The frame is echoed back to the host, and if the frame contents are intact, we know DMA is working correctly, otherwise we complain loudly on the console and abort the device attach. (At the moment, I don't know of any way to work around the problem other than physically modifying the board, so until/unless I can think of a software workaround, this will have do to.)- Created re(4) man page- Modified rlphy.c to allow re(4) to attach as well as rl(4).Note that this code works for the sample 8169/Marvell 88E1000 NICthat I have, but probably won't work for the 8169S/8110S chips.RealTek has sent me some sample NICs, but they haven't arrived yet.I will probably need to add an rlgphy driver to handle the on-boardPHY in the 8169S/8110S (it needs special DSP initialization). List of files: /freebsd/sys/modules/re/Makefile Mon, 08 Sep 2003 04:11:25 +0200 Bill Paul <wpaul@FreeBSD.org>