wireguard-openbsd/sys/arch/arm/include/bus.h, branch jd/queueboostsWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/arm/include/bus.h?h=jd%2Fqueueboosts2020-04-29T15:25:07ZLet the armv7 bus_dma layer and simplebus(4) implementation deal with2020-04-29T15:25:07Zketteniskettenis@openbsd.org2020-04-29T15:25:07Zurn: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@
add a BUS_DMA_64BIT flag to bus_dma on all our archs.2017-05-08T00:27:45Zdlgdlg@openbsd.org2017-05-08T00:27:45Zurn:sha1:b0002153e68e19a4277a3f21e84cea855054f754
this is so drivers can advertise that they can handle 64 dma addresses
to the platform. it may choose to handle dmamaps differently based
on this flag.
tweaks and ok tom@
ok kettenis@
Some device trees use 64-bit intermediate virtual addresses. This2016-10-05T07:44:24Zpatrickpatrick@openbsd.org2016-10-05T07:44:24Zurn:sha1:ed541e3a3388d9d16c92bacf4e996fbd317100a0
means that even though the hardware in the end never leaves the 32-bit
address space, some addresses used solely in the device tree can be
bigger than 32-bit. As bus_space_map(9) takes addresses of size
bus_addr_t, which is 32-bit on ARMv7, we cannot pass those virtual
addresses to the parent bus, even though it will be mapped back into a
32-bit address in the end. To work around this, make bus_space_map(9)
take a 64-bit address. Since this is implemented as a macro and
function pointer we can safely do that without harming any other
architecture.
ok kettenis@ deraadt@
Implement bus dma support for loading raw mappings so that we can use2016-08-26T21:50:42Zpatrickpatrick@openbsd.org2016-08-26T21:50:42Zurn:sha1:fe41f3e965f7e1d764381606ed277831af4100f2
xhci(4) on ARM. The only way the load raw operation can get to know
about the coherent flag is via the segments. Store it there when the
memory is initially mapped. Also store the virtual address which we
need to know when we have to flush the caches on a non-coherent mapping.
ok kettenis@
Normalize sentinel. Use _MACHINE_*_H_ and _<ARCH>_*_H_ properly and consitently.2011-03-23T16:54:33Zpiroftipirofti@openbsd.org2011-03-23T16:54:33Zurn:sha1:2fa72412907ae78c4787a4a8f888c5f0486e225c
Discussed and okay drahn@. Okay deraadt@.
OpenBSD uses bus_space_copy_#, not bus_space_copy_region_#. Make sure only the2010-04-04T12:49:27Zmiodmiod@openbsd.org2010-04-04T12:49:27Zurn:sha1:0cda87aaf2d1dba3156afe1362b9e680d14fa20e
first name is used, and remove any #define foo_region foo compatibility
defines.
Also, on sparc64, do not provide a `raw' version of bus_space_copy.
Make sure all platforms understand the flags argument of bus_space_map() and2009-07-26T18:48:53Zmiodmiod@openbsd.org2009-07-26T18:48:53Zurn:sha1:2ab138fd07f9495743be1d801fa5f60c606ab698
bus_space_alloc() as a bitmask of flags, and not a boolean controlling
cacheability; and make sure the three MI BUS_SPACE_MAP_xxx values documented
in the manual page are defined on all platforms as well.
Add a BUS_DMA_ZERO flag for bus_dmamem_alloc() to return zeroed memory.2009-04-20T00:42:05Zogaoga@openbsd.org2009-04-20T00:42:05Zurn:sha1:471ccd185285af4568b3f0ff1eafabf82d4028ed
Saves every damned driver calling bzero(), and continues the M_ZERO,
PR_ZERO symmetry.
First pass at removing clauses 3 and 4 from NetBSD licenses.2008-06-26T05:42:03Zrayray@openbsd.org2008-06-26T05:42:03Zurn:sha1:d874cce4b1d9fe6b41c9e4f2117a77d8a4a37b92
Not sure what's more surprising: how long it took for NetBSD to
catch up to the rest of the BSDs (including UCB), or the amount of
code that NetBSD has claimed for itself without attributing to the
actual authors.
OK deraadt@
We will never use __BUS_SPACE_HAS_STREAM_METHODS so remove all the code2008-05-05T22:58:58Zclaudioclaudio@openbsd.org2008-05-05T22:58:58Zurn:sha1:a5b5fc5554211928414dd5f221abe7123efeb42f
behind it. OK miod@, drahn@