IABSD.fr/src/sys/dev
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
e3508b1c | 2021-11-03 02:37:48 | drm/amdgpu: fix out of bounds write From Thelford Williams eb3b6805e3e9d98b2507201fd061a231988ce623 in linux 5.10.y/5.10.77 5afa7898ab7a0ec9c28556a91df714bf3c2f725e in mainline linux | |
|
56460339 | 2021-11-03 02:33:46 | drm/ttm: fix memleak in ttm_transfered_destroy From Christian Koenig c21b4002214c1c7e7b627b9b53375612f7aab6db in linux 5.10.y/5.10.77 0db55f9a1bafbe3dac750ea669de9134922389b5 in mainline linux | |
 |
ab93a547 | 2021-11-02 16:31:27 | Enable spleen16x32 and spleen32x64 on powerpc64 for GENERIC kernels. Pointed out by Brad, thanks! OK kettenis@, deraadt@ | |
 |
aec445ea | 2021-11-02 14:49:53 | Recognize BCM43436, as seen on the Raspberry Pi Zero 2 W. ok jsg@ | |
 |
0b89560c | 2021-11-02 09:52:40 | add handling for parity and character size config. i wanted to talk modbus to a thing using a uchcom rs485 adapter, but i needed even parity enabled to do that which the code didnt support. this pulls in the necessary changes from netbsd uchcom.c r1.26. it does not pull in the reset changes in 1.26 because netbsd r1.28 reverts the reset code back to what we have now. existing functionality tested by felix kronlage-dammers ok patrick@ | |
 |
c4d9c150 | 2021-11-02 02:17:56 | knf | |
|
065aa801 | 2021-11-01 18:43:04 | Enable spleen16x32 and spleen32x64 on riscv64 for GENERIC kernels. OK deraadt@ | |
 |
0ff00077 | 2021-11-01 12:08:46 | Restore some NULL checks lost in r1.132, add a couple more to deal with WEP key installation happening w/o a node, and don't attempt to set WEP keys that don't exist. Should fix the '(null node)' panics reported by James Hastings. ok stsp@ | |
|
e77e4c40 | 2021-11-01 03:29:53 | use hw_power to implement power_supply_is_system_supplied() | |
|
48860803 | 2021-10-31 15:25:10 | Disable both TCP/UDP checksum offloading and VLAN HW tag offloading for now, as we currently configure neither in the transmit code path. Found by sf@ | |
|
40350728 | 2021-10-31 15:22:40 | Implement transmit and transmit completion path. | |
 |
fe922775 | 2021-10-31 15:12:00 | Extend the SPI bus API a bit. The config structure gets an sc_cs_delay member to allow us to specify a delay between assert the CS# signal and starting the clock. And the transfer function gains a flags argument, which can be used to specify a new SPI_KEEP_CS flag to keep CS# asserted after the transfer. This allows us to do another transfer immediately afterwards without de-asserting CS# which is necessary for sending commands to the upcoming Apple M1 keyboard/touchpad driver. ok patrick@ | |
|
b88bced1 | 2021-10-31 15:02:25 | Move the fill and the tail pointer change to a later point, to make sure that the RDT is written, and that it is written not too early. Doing it before writing IGC_RXDCTL definitely doesn't work. The tail pointer needs to be set to the next empty slot, so it has to be "last desc filled + 1". Make sure sure that the rss mapping does not happen in the middle of the RX checksum block, and that it happens only if nqueues > 1. Also disable storing bad packets. With this, igc(4) receives packets just fine. ok kevlo@ | |
|
83306792 | 2021-10-31 14:52:57 | Add igc(4), a driver for the Intel 2.5Gb Ethernet controllers. Ported by kevlo@ ok jmatthew@ | |
|
12a48f82 | 2021-10-31 14:41:53 | regen | |
|
5fde8107 | 2021-10-31 14:41:00 | Add another PCI id for Intel 2.5Gb adapters. | |
 |
937de54f | 2021-10-31 12:24:02 | Make athn(4) attach to the Sony UWA-BR100. Patch by martingot@protonmail | |
|
4ee1c150 | 2021-10-31 12:23:17 | regen | |
|
4391a17a | 2021-10-31 12:22:48 | Add USB device ID for the Sony UWA-BR100. Patch by martingot@protonmail | |
|
ac5ee598 | 2021-10-31 12:17:54 | Raise SPL to IPL_NET in run_next_scan() to avoid splassert failures. Problem found and fix tested by krw@. ok krw@ | |
|
0294e0be | 2021-10-30 23:24:46 | Change hw.perfpolicy=auto by default, at startup. If the system has AC power connected (default is yes when no driver differentiates) then default to 100% performance. On battery, use the existing auto algorithm (which is admittedly somewhat unrefined). This change overrides the system/BIOS speed and puts OpenBSD in control. As this happens very early during boot, besides speedups in all usage usage patterns, some surprises: unhibernate and sysupgrade times are cut in half. note: on a few architectures, the setperf fn pointer is changed late, and thus the auto algorithm stops timeing out. kettenis and i will look for a solution. in snaps for more than a week. ok kettenis | |
 |
9a70ba8e | 2021-10-30 12:48:11 | Fix build break caused by accidental keystroke during last commit | |
|
501ade62 | 2021-10-30 12:40:55 | Disestablish softintrs upon detach (missed in last commit) During detach, we can't rely on softintrs to signal processes blocked in read, write or poll, so we need to explicitely call wakeup functions in the detach method, as other drivers do. | |
|
02e0ccc4 | 2021-10-30 12:26:26 | Defer selwakeup() calls to a softintr selwakeup() needs to be protected by KERNEL_LOCK, but we're not allowed to grab KERNEL_LOCK on interrupt context because midi runs at IPL_AUDIO with the audio_lock held. Furthermore, doing so is a locking order bug: syscall code-path grabs KERNEL_LOCK first while interrupt code-path does the opposite when calling selwakeup(). ok visa | |
|
671067d0 | 2021-10-30 11:56:19 | Revert previous commit as it's causing panic when devices are detached ok sthen, anton | |
|
61553a4e | 2021-10-30 03:27:35 | match on Intel 600 Series | |
|
ca3aa902 | 2021-10-30 03:24:59 | enable snooping on Intel 600 Series | |
|
eab40417 | 2021-10-30 03:22:44 | regen | |
|
6a8b08ee | 2021-10-30 03:22:08 | add Intel 600 Series and Alder Lake S ids described in 648364-001 Intel 600 Series Chipset Family Platform Controller Hub Datasheet 655258-001 12th Generation Intel Core Processors Datasheet | |
 |
57aafeb6 | 2021-10-29 15:43:55 | A USB HID report ID must be represented using a single byte ranging between 1-255 where 0 is reserved. The pseudo report ID UHIDEV_CLAIM_MULTIPLE_REPORTID is currently colliding with the valid report ID 255. Therefore crank it which gets rid of the collision and increase the related fields in order to cope with larger integers. Thanks to Damien Couderc <openbsd at petrocore dot eu> for reporting and testing. | |
|
2e8dbc7d | 2021-10-29 14:25:05 | match more Prolific HXN ids tested by robert@ on PL2303GT ok deraadt@ robert@ patrick@ | |
|
9a131efa | 2021-10-29 14:23:07 | regen | |
|
19cc58a0 | 2021-10-29 14:22:26 | more Prolific HXN ids ok deraadt@ robert@ patrick@ | |
|
ed1204be | 2021-10-29 13:24:50 | Don't grab audio_lock in filt_midi{read,write} if NOTE_SUBMIT is set. Fixes panics caused by attempts to grab audio_lock twice in the interrupt code path: once in the low-lever interrupt handler and once in selwakeup() This is exactly how audio(4) handles this problem. ok mpi | |
 |
42d1e0ec | 2021-10-28 08:47:40 | add proper declaration for addr in dt_prov_kprobe_hook | |
|
fc464cd9 | 2021-10-27 15:18:12 | use db_get_probe_addr() instead of handrolling the expression wrapped in ifdef ok mpi@ | |
|
c8ebe74c | 2021-10-27 09:09:55 | fix spello in comment | |
 |
ec12b9df | 2021-10-26 16:49:12 | Add a new TEMPerHUM device id. style tweak deraadt@, ok mlarkin@ | |
|
27b5a9d5 | 2021-10-26 16:29:49 | Improve unhibernate performance (30% on some machines, another upcoming diff shows gains up to 50%) by skipping attach of irrelevant devices, which are tagged CD_SKIPHIBERNATE in the per-driver cfdriver. In particular, usb devices are not attached, so they don't need to detach during the suspend-unpack-resume. New bootblocks are required (which tell the kernel it's job is unhibernate before configure runs) tested by various | |
 |
7ac5eeb9 | 2021-10-25 19:51:12 | remove dtp_mtx which protected dtp_ref; the code is always called with KERNEL_LOCK() held | |
|
0ae68571 | 2021-10-25 17:15:29 | remove dtp_mtx which protected dtp_ref; the code is always called with KERNEL_LOCK() held discussed with and OK mpi@ | |
|
011d9570 | 2021-10-24 21:37:49 | For open/openat, if the flags parameter does not contain O_CREAT, the 3rd (variadic) mode_t parameter is irrelevant. Many developers in the past have passed mode_t (0, 044, 0644, or such), which might lead future people to copy this broken idiom, and perhaps even believe this parameter has some meaning or implication or application. Delete them all. This comes out of a conversation where tb@ noticed that a strange (but intentional) pledge behaviour is to always knock-out high-bits from mode_t on a number of system calls as a safety factor, and his bewilderment that this appeared to be happening against valid modes (at least visually), but no sorry, they are all irrelevant junk. They could all be 0xdeafbeef. ok millert | |
 |
9fdf0c62 | 2021-10-24 17:52:26 | Constify struct cfattach. ok visa@ a long time ago, ok patrick@ | |
 |
87edded1 | 2021-10-24 14:50:42 | Remove crp_etype and return errors directly from crypto_invoke() ok patrick@ | |
|
04c68813 | 2021-10-24 09:16:53 | pretty & normalize the cfdriver decl | |
 |
306068a2 | 2021-10-23 16:39:03 | tpm(4): add support for tpm2 CRB interface Some modern tpm2 devices require or prefer drivers communicate via the CRB interface and not the TIS/fifo interface. This change adds basic support for detecting CRB start mode and using CRB to issue commands required for proper S4 hibernation. As a result, this also defines a new struct definition for the TPM2 acpi table required for start mode detection. This fixes recent S4 regressions on the Surface Go 2 caused by a change in firmware from Microsoft. Other CRB start methods may need implementing in the future to support additional hardware. tested by deraadt@ and many others, ok kettenis@ | |
|
12758001 | 2021-10-23 15:42:34 | Retire asynchronous crypto API as it is no longer required by any driver and adds unnecessary complexity. Dedicated crypto offloading devices are not common anymore. Modern CPU crypto acceleration works synchronously, eliminating the need for callbacks. Replace all occurrences of crypto_dispatch() with crypto_invoke(), which is blocking and only returns after the operation has completed or an error occured. Invoke callback functions directly from the consumer (e.g. IPsec, softraid) instead of relying on the crypto driver to call crypto_done(). ok bluhm@ mvs@ patrick@ | |
|
db31205a | 2021-10-23 12:48:17 | Make sure we have enough space to add padding and final token to the nvram data. Also add the MAC address to the nvram data when there is a "local-mac-address" property in the device tree. This makes bwfm(4) work with the firmware/nvram/clm_blob files provided with MacOS on the Apple M1 Macs. ok patrick@ | |
|
cf35dfb8 | 2021-10-22 14:28:54 | Mask LPI interrupts. This fixes an interrupt storm on dwge(4) variants that support Energy Efficient Ethernet when connected to a switch that also supports Energy Effient Ethernet. For example on the odroid-hc4. ok patrick@ | |
|
75df5dbe | 2021-10-22 08:48:46 | regen | |
|
8b1845ed | 2021-10-22 08:48:08 | add Intel ADL-S and ADL-P graphics ids Mesa matches fix a GMA600 id while here | |
|
87f4b967 | 2021-10-22 05:06:37 | Remove last dangling usage of CRYPTO_F_NOQUEUE. ok tb@ | |
|
fd87b509 | 2021-10-22 04:59:31 | One could end up with the wrong encoding in xenocara while having a ucc keyboard attached and /etc/kbdtype being present. The advertised encoding of a wsmux is a bit fragile as the last attached device will dictate it. If this happens to be a ucc keyboard, KB_US will always be the advertised encoding as its encoding is immutable and /etc/kbdtype is ignored. Instead, do not advertise the encoding for ucc devices when the parent mux queries its attached devices. However, asking the device directly (i.e. bypassing the mux) still returns the encoding as wsconsctl(8) would otherwise report an error. Thanks to landry@ for the report and testing. | |
|
562a60fa | 2021-10-21 21:50:16 | regen | |
|
ffcb2d04 | 2021-10-21 21:47:41 | add Gemini Lake MEI; from fkr | |
 |
0a828ff4 | 2021-10-21 18:36:41 | Remove hifn(4), safe(4), and ubsec(4) crypto drivers. They require the asynchronous crypto API which makes progress in MP difficult. The hardware is rarely available. They support only obsolete crypto algorithms. Scheduling crypto tasks via PCI is probably slower than the CPU, especailly as modern CPUs have their own accelerators. | |
|
9b8211f6 | 2021-10-20 23:50:20 | drm/edid: In connector_bad_edid() cap num_of_ext by num_blocks read From Douglas Anderson a7b45024f66f9ec769e8dbb1a51ae83cd05929c7 in linux 5.10.y/5.10.75 97794170b696856483f74b47bfb6049780d2d3a0 in mainline linux | |
|
3dfc65b6 | 2021-10-17 10:59:45 | drm/amdgpu: fix gart.bo pin_count leak From Leslie Shi 621ddffb70db824eabd63d18ac635180fe9500f9 in linux 5.10.y/5.10.74 66805763a97f8f7bdf742fc0851d85c02ed9411f in mainline linux | |
|
054189b2 | 2021-10-16 17:14:41 | Bail out early if the PCIe controller hasn't been initialized by the firmware. ok jsg@ | |
|
b4d5bb03 | 2021-10-15 13:38:10 | Add initial 40MHz support to the iwx(4) driver. Tested: ax200: jmc, phessler, kevlo, hrvoje, sdk, fkr, stsp, Mark Patruck ax201: jcs, stsp, Fredrik Engberg, Eric Auge | |
|
b092f79b | 2021-10-13 22:43:44 | The function crypto_dispatch() never returns an error. Make it void and remove error handling in the callers. OK patrick@ mvs@ | |
|
3877526a | 2021-10-13 13:08:58 | The kernel crypto framework sometimes returned an error, sometimes the callback was called, and sometimes both. So the caller of that API could not release resources correctly. A bunch of errors can or should not happen, replace them with an assert. Remove redundant checks. crypto_invoke() should not return the error, but pass it via callback. Some old hardware drivers keep part of their inconsistency as I cannot test them. OK mpi@ | |
|
5543f5ef | 2021-10-12 18:22:04 | Remove misleading uvm reference counting that isn't actually used. Make sure uvm_obj_init() is only called once. Call uvm_obj_destroy() when we release the GEM object that wraps an uvm object for which we called uvm_obj_init(). ok mpi@, jsg@ | |
 |
b889aa9d | 2021-10-12 11:20:32 | iwm(4): revert to use firmware v17 on Intel AC 7265. fixes instability issues seen on X1 carbon gen3 (hw rev 0x210) by anton@, mpi@ and myself. diff from stsp@ ok mpi@ stsp@ | |
|
8e2545be | 2021-10-12 10:46:57 | Make our old BSSID available to iwx_newstate_task() when roaming. ic_bss->ni_bssid has already been overwritten once we enter iwx_newstate_task() to perform the state transitions necessary for roaming to our new access point (RUN->AUTH->ASSOC->RUN). We do however use the BSSID in commands sent to firmware. Cache our BSSID in struct iwx_node such that firmware commands keep using the old BSSID while we are still tearing things down. Switch to the new BSSID only once we start back up in iwx_auth(). This should be consistent from the firmware's point of view. Same fix as committed for iwm(4) recently. | |
|
42c96387 | 2021-10-12 10:45:21 | Explicitly stop iwx(4) Rx block ack when roaming between access points. This is similar to a recent fix committed to iwm(4). Unlike iwm(4) we do not need to disable Tx aggregation queues in iwx(4). Attempting to do so would cause fatal firmware errors. Tested by jmc@ and myself. | |
|
e8480993 | 2021-10-12 10:44:33 | Remove code which was needed to support old firmware images from iwx(4). Tested with cc-a0-63 and QuZ-a0-hr-b0-63 firmware by myself. Tested with Qu-c0-hr-b0-63 firmware by Fredrik Engberg. | |
|
880afff8 | 2021-10-11 09:03:22 | Add support for 802.11n 40MHz channels to the iwm(4) driver. According to 11n MCS index tables our maximum data rate is now 300 Mbit/s at MCS 15, excluding protocol overhead. I have measured up to 200Mbit/s of effective throughput on clean 5GHz channels. The driver enables use of 40MHz channels automatically as long as the access point announces support for such channels in its beacons. In case 40MHz transmissions fail we ask firmware to retry with a 20MHz transmission. There is no integration with ifconfig yet, so use of 40MHz is not yet displayed there. In the meantime, tcpdump(8) can be used to check if the current access point supports 40MHz: tcpdump -n -i iwm0 -v -y IEEE802_11_RADIO -s 4096 type mgt and subtype beacon Channel width is displayed in the HT operation information element, where a 40MHz channels looks like this: htop=<40MHz chan X:Y ...> Tested: 7260: florian, bcallah 7265: landry 8260: bket 8265: stsp, abieber, Matthias Schmidt, Josh Rickmar, empee on mastodon 9560: stsp | |
|
ca785ca0 | 2021-10-11 09:01:05 | Add support for 40MHz channels to net80211 RA. For the moment we use either the 40MHz rate set or the 20 MHz one, depending on whether our peer supports 40MHz channels. If this turns out to be suboptimal we could probe the 40MHz and 20MHz rate sets separately to detect which one works better. The same applies to use of the short guard interval (SGI), which is either always on or off at the moment. Again, probing for this could be added later if needed. | |
|
fb4391c8 | 2021-10-10 16:20:37 | Apparently it is possible for firmware to indicate that SMCCC_VERSION is implemented but have that call return NOT_SUPPORTED. Makes no sense, but the SMCCC standard documents this and tells us to treat this as v1.0. Change the code accordingly. Turn a few checks that should always be true into KASSERTs to keep the control flow simple. ok patrick@ | |
|
3af8c687 | 2021-10-09 14:47:02 | placing the same vnd underneath a vnd (with VNDIOCSET) is a lock violation, but other circumstances are also bad, so let's block all vnd on top of vnd. While here, fix some toctou multiple-copyin of the path, and restructure the ioctl defer all softc updates to the end. ok mpi | |
 |
a97e1fbf | 2021-10-09 08:38:13 | No need to enable bus mastering, it's already done for us. from Brad | |
 |
e3238c4d | 2021-10-07 14:11:32 | remove quirks for ALC887 because they were only causing trouble on my machine at least; let's see how others are; ok ratchov@ | |
|
80a9ea70 | 2021-10-07 08:15:04 | Make our old BSSID available to iwm_newstate() when roaming. ic_bss->ni_bssid has already been overwritten once we enter iwm_newstate() to perform the state transitions necessary for roaming to our new access point (RUN->AUTH->ASSOC->RUN). We do however use the BSSID in commands sent to firmware. Cache our BSSID in struct iwm_node such that firmware commands keep using the old BSSID while we are still tearing things down. Switch to the new BSSID only once we start back up in iwm_auth(). This should be consistent from the firmware's point of view. ok mpi@ | |
|
0a9c143c | 2021-10-07 03:44:00 | drm/i915/request: fix early tracepoints From Matthew Auld d35d95e8b9da638d27bce9552262e0c486138343 in linux 5.10.y/5.10.71 c83ff0186401169eb27ce5057d820b7a863455c3 in mainline linux | |
|
2bdcbea8 | 2021-10-07 03:42:00 | drm/amdgpu: correct initial cp_hqd_quantum for gfx9 From Hawking Zhang 9f382e1edf90ae03be43dbd4976c2a332cd7ce2d in linux 5.10.y/5.10.71 9f52c25f59b504a29dda42d83ac1e24d2af535d4 in mainline linux | |
|
deb5723a | 2021-10-07 03:39:35 | drm/amd/display: Pass PCI deviceid into DC From Charlene Liu c331fad63b6d527193ae8b7c056b2f10fef53c81 in linux 5.10.y/5.10.71 d942856865c733ff60450de9691af796ad71d7bc in mainline linux | |
|
4ccda297 | 2021-10-06 13:36:47 | Allow AUTH->AUTH state transitions in the iwm(4) and iwx(4) drivers again. AUTH->AUTH state transitions happen if the access point uses band-steering. This was originally implemented to fix interop with some Aruba APs, and was probably broken by my recent CVS commit XeKkqPoaUCklmgtC ("prevent attempts to transition towards the same state"). ok mpi@ | |
|
6df20340 | 2021-10-06 13:35:55 | Make sure iwm(4) uses the HT frame format only for data frames. Non-data frames are not supposed to use HT. This change is for code correctness and does not fix any known issue. And it applies only if the Tx rate has been fixed for testing purposes with a command such as 'ifconfig iwm0 media HT-MCS13 mode 11n'. ok mpi@ | |
|
e95c7e16 | 2021-10-05 10:34:36 | Fix iwm(4) performance drop after roaming between APs in 11n mode. Stop BA sessions directly in iwm_run_stop() and disable Tx agg queues when leaving RUN state. Otherwise Tx agg queues do not work properly after switching APs and Tx performance drops to about 2 Mbit/s with excessive retries being reported to RA. Tested: 7260: florian 8260: bket 8265: stsp 9260: florian 9560: stsp | |
|
cdaceaad | 2021-10-04 19:04:12 | Allegedly a "Marvell Armada 3700 Functional Errata, Guidelines, and Restrictions" document exists that discusses an errata #251 in section "3.12 PCIe Completion Timeout" and suggests that setting the DIS_ORD_CHK flag in the Debug Mux Control register is necessary as a workaround: https://lore.kernel.org/linux-pci/20210624222621.4776-6-pali@kernel.org This workaround is still being discussed by the Linux developers, but it does fix an issue I am seeing with athn(4), where an external abort happens under load. So apply this workaround since its potential side effects seem to be significantly less severe than provoking an external abort that hangs the machine. ok patrick@ | |
 |
1e1b982a | 2021-10-04 01:33:42 | Build firmware for rsu(4), rtwn(4), and urtwn(4). We have to install the files with new filenames (removal of "fw" from each of the filenames) and change the driver to use the new filenames, such that the package becomes irrelevant. Discussed with deraadt@ and sthen@ ok deraadt@ | |
|
2f22c038 | 2021-10-04 01:29:57 | Permission from Realtek to include wireless firmwares After deraadt@ explained why the Realtek firmware cannot be put into our tree, I reached out to Realtek to explain the situation. According to the LICENCE.rtlwifi_firmware.txt [1], the rules permitted adding their non-open-source firmware into open source operating systems but such an addition (ironically) makes that open source operating system not entirely open source. Realtek understood the irony, and change the license. Thanks to Realtek for this change which lets us put the firmware .h file into our tree, this means Realtek wireless will work without requiring a firmware download (which is difficult over a non-working Realtek network :) [1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/LICENCE.rtlwifi_firmware.txt?id=0f863ff1b388ad5b0f7d25decdbb642#n22 ok deraadt@ | |
|
6dc21066 | 2021-10-03 20:19:55 | Apparently some athn(4) variants are buggy and may hand us corrupt frames that are marked "ok". Linux has some workarounds for this and checks whether the status word has error bits set in it regardless of the bit that marks the frame as "ok". Adapt this workaround to our driver and drop the frame after setting input errors. This doesn't filter out all corrupted frames, but it does keep things down to a level where it doesn't fill up the node cache anymore when athn(4) is used in hostap mode. Seen with: athn0 at pci1 dev 0 function 0 "Atheros AR9281" rev 0x01: intx athn0: AR9280 rev 2 (2T2R), ROM rev 16, address xx:xx:xx:xx:xx:xx ok stsp@ | |
|
43a70795 | 2021-10-03 00:48:45 | un.ifdef USB and PCI, since all our architectures (minus one) have models which can have these busses, might as well make these distributable firmwares available in case the drivers find devices. ok kettenis | |
|
d8c6c2e5 | 2021-10-02 14:26:05 | Extend workaround for reset on context closure from gen 7-8 to gen 4-8 as asavvycomputist@disroot.org reported this occurs on gm45 (gen 4). | |
|
b44e4dce | 2021-10-02 07:48:20 | Remove iwx_assoc() and iwx_disassoc(). Not needed because they duplicate work that is already handled by state transitions involving AUTH or RUN. | |
|
b072c62e | 2021-10-02 07:47:54 | Remove iwm_assoc() and iwm_disassoc(). Not needed because they duplicate work that is already handled by state transitions involving AUTH or RUN. | |
|
042c85e1 | 2021-10-02 07:39:52 | Fix panic when iwx(4) firmware is not present at boot time. Uncomfortable bug found the hard way by deraadt@ | |
|
77f42572 | 2021-10-01 04:41:10 | amd/display: downgrade validation failure log level From Simon Ser 526261c1b706fec0ea80ce9f14c8fe8468bee34d in linux 5.10.y/5.10.70 7bbee36d71502ab9a341505da89a017c7ae2e6b2 in mainline linux | |
|
6dafb210 | 2021-10-01 04:36:38 | treewide: Change list_sort to use const pointers From Sami Tolvanen 55e6f8b3c0f5cc600df12ddd0371d2703b910fd7 in linux 5.10.y/5.10.70 4f0f586bf0c898233d8f316f471a21db2abd522d in mainline linux | |
|
d6342323 | 2021-10-01 04:25:17 | drm/amd/pm: Update intermediate power state for SI From Lijo Lazar 68d4fbe6220cd1f3d07cab0a4901e62f8c12cc68 in linux 5.10.y/5.10.70 ab39d3cef526ba09c4c6923b4cd7e6ec1c5d4faa in mainline linux | |
|
c99d53f1 | 2021-09-30 09:27:47 | In iwm(4) and iwx(4), prevent attemps to transition towards the same state in cases where this would result in a redundant or illegal state transition. jmc@ observed ASSOC -> ASSOC transitions which would result in a hang. Such transitions are invalid and never intentionally triggered by net80211. They imply a race between the Rx interrupt handler and the newstate task. Tested by jmc@ on AX200 for a week and several known issues seem to be fixed. | |
|
607dd7f8 | 2021-09-29 22:03:33 | Add support for Cannon Lake H and Tiger Lake H platforms. ok jcs@ | |
|
d23c6173 | 2021-09-29 13:03:47 | sync | |
|
52ec2841 | 2021-09-29 13:02:29 | drm/amdgpu: add some additional RDNA2 PCI IDs From Alex Deucher 8f0c93f454bd7ab04eaec1d3c436c4c7c2378f07 in mainline linux | |
|
b82307fb | 2021-09-29 12:18:40 | regen | |
|
3137721d | 2021-09-29 12:18:08 | intel 0x5915 is a kaby lake graphics id not imaging unit fix strings in some other graphics devices as well | |
|
915335c8 | 2021-09-29 10:28:07 | regen | |
|
27a47fe4 | 2021-09-29 10:27:21 | add amdgpu and inteldrm devices matched by 5.15 drm without force probe includes amd codenames for codenames so subject to change |