Searched hist:203422 (Results 1 - 7 of 7) sorted by relevance
| /freebsd-11-stable/sys/net80211/ | ||
| H A D | ieee80211_ioctl.h | diff 203556 Sat Feb 06 17:38:41 MST 2010 rpaulo Revert unwanted changes in revision 203422. Spotted by: sam diff 203422 Wed Feb 03 08:08:33 MST 2010 rpaulo When taking the AMPDU reorder fastpath, need_tap wasn't being initialized. Initialize on declaration to avoid this. Found with: clang static analyzer |
| H A D | ieee80211_adhoc.c | diff 203422 Wed Feb 03 08:08:33 MST 2010 rpaulo When taking the AMPDU reorder fastpath, need_tap wasn't being initialized. Initialize on declaration to avoid this. Found with: clang static analyzer |
| H A D | ieee80211_wds.c | diff 203422 Wed Feb 03 08:08:33 MST 2010 rpaulo When taking the AMPDU reorder fastpath, need_tap wasn't being initialized. Initialize on declaration to avoid this. Found with: clang static analyzer |
| H A D | ieee80211_hostap.c | diff 203422 Wed Feb 03 08:08:33 MST 2010 rpaulo When taking the AMPDU reorder fastpath, need_tap wasn't being initialized. Initialize on declaration to avoid this. Found with: clang static analyzer |
| H A D | ieee80211_sta.c | diff 203422 Wed Feb 03 08:08:33 MST 2010 rpaulo When taking the AMPDU reorder fastpath, need_tap wasn't being initialized. Initialize on declaration to avoid this. Found with: clang static analyzer |
| /freebsd-11-stable/sys/dev/rl/ | ||
| H A D | if_rlreg.h | diff 290566 Sun Nov 08 22:20:47 MST 2015 marius - Although it doesn't make a whole lot of sense to enable RX and TX before their initial configuration is done, it turns out that r281337 has the inverse effect on some older chips. Moreover, as with newer chips before, two chips seemingly identical according to their MAC revisions may behave differently in this regard, with most working but a few not, making changes extremely hard to test. Closer inspection of the corresponding Linux code suggests that RX and TX should only be enabled after their initial configuration with RTL8168G and later chips, i. e. RTL8106E{,US}, RTL8107E, as well as RTL8168{EP,G,GU,H}, so limit the new code path to these. [1] - Distinguish between RTL8168H and RTL8107E, with the latter being the 10/100-Mbit/s-only variant of the former. - For MAC variants that can only do Fast Ethernet at a maximum, ensure that we don't advertise Gigabit Ethernet speed. - In re_stop(), do the inverse of re_init_locked() and enable RXDV gate on RTL8168G and later chips again, matching what Linux does. PR: 203422 [1] MFC after: 1 week |
| /freebsd-11-stable/sys/dev/re/ | ||
| H A D | if_re.c | diff 290566 Sun Nov 08 22:20:47 MST 2015 marius - Although it doesn't make a whole lot of sense to enable RX and TX before their initial configuration is done, it turns out that r281337 has the inverse effect on some older chips. Moreover, as with newer chips before, two chips seemingly identical according to their MAC revisions may behave differently in this regard, with most working but a few not, making changes extremely hard to test. Closer inspection of the corresponding Linux code suggests that RX and TX should only be enabled after their initial configuration with RTL8168G and later chips, i. e. RTL8106E{,US}, RTL8107E, as well as RTL8168{EP,G,GU,H}, so limit the new code path to these. [1] - Distinguish between RTL8168H and RTL8107E, with the latter being the 10/100-Mbit/s-only variant of the former. - For MAC variants that can only do Fast Ethernet at a maximum, ensure that we don't advertise Gigabit Ethernet speed. - In re_stop(), do the inverse of re_init_locked() and enable RXDV gate on RTL8168G and later chips again, matching what Linux does. PR: 203422 [1] MFC after: 1 week |
Completed in 296 milliseconds