| created | 2023-09-04T09:42:44Z |
|---|---|
| begin | 2023-08-26T00:00:00Z |
| end | 2023-08-27T00:00:00Z |
| path | src/sys |
| commits | 5 |
| date | 2023-08-26T09:05:34Z | |||
|---|---|---|---|---|
| author | stsp | |||
| files | src/sys/dev/pci/if_iwx.c | log | diff | annotate |
| message |
fix iwx scan command such that the driver selects an SSID during bgscan The driver was asking firmware to send probe requests during background scans without having any SSID selected, which doesn't make sense. With that fixed I see faster background scans that no longer display every AP in range in debug logs, while relevant APs always show up. This is a possible fix for fatal firmware error 0x20002806 which is known to be related to bad scan commands and appeared with our upgrade to the -77 firmware API. Not yet confirmed because it is difficult to trigger this error on purpose. Apparently this change also repairs stability issues on AX210. I have never seen such issues first-hand and have no clue how they might relate to this change. One plausible theory is that our bogus bgscan command would trigger bad side-effects in firmware. Tested: ax200: jmc@, stsp@ ax210: Laurence Tratt, sf@ |
|||
| date | 2023-08-26T09:37:43Z | |||
|---|---|---|---|---|
| author | visa | |||
| files | src/sys/arch/loongson/dev/glxclk.c | log | diff | annotate |
| message |
Adapt glxclk(4) for clockintr Make glxclk(4) functional again. The MFGPT provides the CPU core an external clock interrupt. This interrupt enables a later change that reduces energy usage when the system is idle. Also, the use of the external clock fixes timekeeping when the core clock frequency is adjusted. |
|||
| date | 2023-08-26T11:33:46Z | |||
|---|---|---|---|---|
| author | dlg | |||
| files | src/sys/dev/usb/if_umb.c | log | diff | annotate |
| message |
umb can use p2p_input as an if_input handler. umb(4) is a hardware p2p driver, it just has ip coming in, so we can do the same thing we do for the address family and input processing as other p2p interfaces. the short packet check that umb_input does is already done by the ip stacks, so we're not losing anything. tested by gerhard@ mbuhl@ ok gerhard@ |
|||
| date | 2023-08-26T15:01:00Z | |||
|---|---|---|---|---|
| author | jmc | |||
| files | src/sys/dev/ic/pckbc.c | log | diff | annotate |
| message | word fix in comment; from crystal kolipe | |||
| date | 2023-08-26T22:21:00Z | |||
|---|---|---|---|---|
| author | cheloha | |||
| files | src/sys/kern/kern_clockintr.c | log | diff | annotate |
| message |
clockintr: add clockqueue_intrclock_install() At some point, clockintr_cpu_init() is going to go away. However, there will still need to be a way to add an intrclock to a struct clockintr_queue. Add a new internal interface, clockqueue_intrclock_install(). If the given clockintr_queue does not yet have an intrclock installed, it copies the contents of the given intrclock to the clockintr_queue's private intrclock (cq_intrclock) and sets CQ_INTRCLOCK in cq_flags. I'm using the verb "install" here instead of "attach" because an intrclock is really just a vtable that we copy into the clockintr_queue. The original intrclock is in no way "bound" or "affixed" to a particular clockintr_queue: it's more akin to a stamp that can be reused to initialize any number of individual clockintr_queue structs. |
|||