| created | 2019-10-15T20:35:22Z |
|---|---|
| begin | 2019-10-11T00:00:00Z |
| end | 2019-10-12T00:00:00Z |
| path | src/sys |
| commits | 2 |
| date | 2019-10-11T15:12:43Z | |||
|---|---|---|---|---|
| author | jsg | |||
| files | src/sys/arch/arm64/dev/bcm2835_dwctwo.c | log | diff | annotate |
| src/sys/arch/armv7/broadcom/bcm2835_dwctwo.c | log | diff | annotate | |
| message |
When available use "interrupt-names" to select the fdt idx for dwctwo interrupt. Required after the dts included with raspberry pi firmware changed from using idx 1 to idx 0 when introducing "interrupt-names". Fixes USB devices not probing reported by dtucker@ ok kettenis@ patrick@ deraadt@ |
|||
| date | 2019-10-11T15:20:36Z | |||
|---|---|---|---|---|
| author | patrick | |||
| files | src/sys/net80211/ieee80211_input.c | log | diff | annotate |
| message |
Probe responses are generally only seen after probe requests, which we only send if an SSID is already configured. Thus a scan only creates beacons. Especially on bwfm(4) only beacons frames are faked, there are no probe responses. When a node first is created, ni_rssi is 0, which is always smaller than rxi_rssi, and it wil never be set for nodes on 5 GHz. Thus we should always set ni_rssi if it is 0. Tested by jan@ tobhe@ ok stsp@ deraadt@ |
|||