wireguard-openbsd/sys/dev/sdmmc, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/sys/dev/sdmmc?h=jd%2Fqueueboosts 2020-06-19T20:56:23Z Add support for BCM4359 SDIO variants such as the AP6359SA module found 2020-06-19T20:56:23Z kettenis kettenis@openbsd.org 2020-06-19T20:56:23Z urn:sha1:0d580645848505bdd39faad26e8b744b415b76b9 on the RockPro64 WiFi module. Note that there is no fiirmware for this chip in the bwfm-firmware package at the moment. ok patrick@ Make sure SDHC_HOST_CTL2 is consistently controlled using 2-byte accesses, 2020-06-14T18:37:16Z patrick patrick@openbsd.org 2020-06-14T18:37:16Z urn:sha1:679ad45b47ec8c8380dd85e5a877a046013fc6ec otherwise it would lead to unaligned memory access. Fixes a panic on my MACCHIATObin. ok kettenis@ Add pre/post hooks for bus clock changes to sdhc(4). These will be 2020-05-22T10:23:14Z patrick patrick@openbsd.org 2020-05-22T10:23:14Z urn:sha1:fa1cdcb1c73cfe1af50c3dfe1dea168aeb0e97c6 used by sdhc(4) attachment drivers to do additional MD initialization. ok kettenis@ Some newer bwfm(4) chips from Cypress hold their regulatory 2020-05-15T14:09:14Z patrick patrick@openbsd.org 2020-05-15T14:09:14Z urn:sha1:6c2f85e4fc18b21bb516a765c6bbb75b5c56d1ce constraints in a separate blob, instead of in the firmware. This .clm_blob needs to be loaded as well. sdhc(4), sdmmc(4): tsleep(9) -> tsleep_nsec(9); ok patrick@ 2020-05-13T17:31:16Z cheloha cheloha@openbsd.org 2020-05-13T17:31:16Z urn:sha1:3f3abf148c8be9ce4a8fb7d3c8360ee62cd204d3 According to the SDIO Simplified Specification 3.0, a tuple length 2020-04-29T09:44:49Z patrick patrick@openbsd.org 2020-04-29T09:44:49Z urn:sha1:4372d0df8945018256d1f237db36d452225718e1 (aka link field) of 0 specifies an empty tuple body. This implies that a tuple length of 0 is actually allowed, so we don't need to error out if we encounter one. Seen on an SDIO-connected ath10k. ok kettenis@ fix SDHC_DEBUG build, remove procname printf's 2020-04-27T11:37:23Z ians ians@openbsd.org 2020-04-27T11:37:23Z urn:sha1:1dd2d335d54084ab0e086076a9471fcbbdf26fa2 ok kettenis@ Add comments to clarify the hex IDs of some bwfm(4) devices on SD bus. 2020-04-19T21:40:21Z stsp stsp@openbsd.org 2020-04-19T21:40:21Z urn:sha1:b102dfaa5268e5c70438e84c7c38c0216fbdd5e6 ok jmc@ deraadt@ kettenis@ "thanks and don't wait for me" patrick@ Add support for hardware where an SDHC controller lives on a bus that 2020-04-19T16:25:33Z kettenis kettenis@openbsd.org 2020-04-19T16:25:33Z urn:sha1:37d458161c55492f23dd0f2d1450bf14b7bc4ddf only supports 32-bit access (hello Raspberry Pi). ok tobhe@ Add support for hardware where an SDHC controller lives on a bus that 2020-04-19T16:15:20Z kettenis kettenis@openbsd.org 2020-04-19T16:15:20Z urn:sha1:04b7fce9f408c9612415599024741fa07f0f187e only supports 32-bit access (hello Raspberry Pi). ok tobhe@