wireguard-openbsd/sys/arch/armv7/broadcom, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/armv7/broadcom?h=jd%2Fqueueboosts 2020-05-14T15:44:07Z The dwctwo(4) FDT glue is now identical on armv7 and arm64. Move it to 2020-05-14T15:44:07Z kettenis kettenis@openbsd.org 2020-05-14T15:44:07Z urn:sha1:bae339d43690903557f1801672ecbcf7f22a4f0e /dev/fdt. ok patrick@, visa@ Let the armv7 bus_dma layer and simplebus(4) implementation deal with 2020-04-29T15:25:07Z kettenis kettenis@openbsd.org 2020-04-29T15:25:07Z urn:sha1:37084e1e34e6eafe959b14d27c905d6c5ddf0888 DMA remapping in the same way as arm64. This relies on the dma-ranges property in the device tree and allows us to get rid of the hack for the Raspberry Pi in the dwctwo(4) driver. Note that this does not include the hack in simplebus(4) that we have on arm64 since firmware that has the dma-ranges is in widespread use now. ok patrick@ When available use "interrupt-names" to select the fdt idx for dwctwo 2019-10-11T15:12:43Z jsg jsg@openbsd.org 2019-10-11T15:12:43Z urn:sha1:353d046454df5d7b649dc6729b092c57e142de8d 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@ Use mask to extract IPL; should have been part of the earlier diff that 2019-10-05T15:44:57Z kettenis kettenis@openbsd.org 2019-10-05T15:44:57Z urn:sha1:72784ddadfb4bc05c57d73d2a4f860f3f0e4931a added IPI support on armv7. Remove bcmmuart since it has already replaced with com(4). 2017-10-23T08:06:30Z kevlo kevlo@openbsd.org 2017-10-23T08:06:30Z urn:sha1:085c1ee2b9ea661d1760d98cb8aedb895965e2d6 ok patrick@ Rename Debugger() into db_enter(). 2017-04-30T16:45:45Z mpi mpi@openbsd.org 2017-04-30T16:45:45Z urn:sha1:e97088d66c8eee044cad550a3fd9fad00889544f Using a name with the 'db_' prefix makes it invisible from the dynamic profiler. ok deraadt@, kettenis@, visa@ Set sc_vendor in bcm2835_dwctwo before calling dwc2_init(). 2017-02-22T04:39:30Z jsg jsg@openbsd.org 2017-02-22T04:39:30Z urn:sha1:0ee5d61cd98189a5f9b64dd36298008af93ad070 This changes the root hub dmesg output from "vendor 0x0000 DWC2 root hub" to "Broadcom DWC2 root hub". ok kettenis@ Replace bcmmuart(4) with com(4). 2016-08-20T15:44:04Z kettenis kettenis@openbsd.org 2016-08-20T15:44:04Z urn:sha1:a41b6ebba9765b38ea9e6b9737c6f7d056ad29c9 ok patrick@ Use the device tree to lookup the address of the ARM control logic and remove 2016-08-07T18:43:17Z kettenis kettenis@openbsd.org 2016-08-07T18:43:17Z urn:sha1:997621bae470bfd7309e11c04f49b997bfbd29af some debug crap that I accidentally committed. Initial support for Raspberry Pi 2/3. All the hard work done by patrick@, I 2016-08-07T17:46:36Z kettenis kettenis@openbsd.org 2016-08-07T17:46:36Z urn:sha1:367aba55752639a62e3e889e9837fec1c3b168c1 just cleaned things up a bit. Any bugs introduced in that process are entirely mine. This doesn't work yet. But when it does, you'll need recent firmware from the Raspberry Pi Foundation git repository at https://github.com/raspberrypi/firmware The device tree for the Raspberry Pi is somewhat in flux as bits and pieces to support the Raspberry Pi 2 and 3 are committed to the mainline Linux kernel.