wireguard-openbsd/sys/arch/alpha/include/bus.h, branch jd/simplify-queueing WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/alpha/include/bus.h?h=jd%2Fsimplify-queueing 2019-05-13T21:27:59Z free(9) sizes. 2019-05-13T21:27:59Z mpi mpi@openbsd.org 2019-05-13T21:27:59Z urn:sha1:5be190757ae4fdbd85f768bf239e80e316cb615b From miod@ add a BUS_DMA_64BIT flag to bus_dma on all our archs. 2017-05-08T00:27:45Z dlg dlg@openbsd.org 2017-05-08T00:27:45Z urn: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@ alias bus_space_{read,write}_raw to the non-raw counterparts 2016-05-03T11:22:08Z dlg dlg@openbsd.org 2016-05-03T11:22:08Z urn:sha1:a847dbdaf336dff60f2eafdae43a0d79aa90542c busses are little endian, so the non-raw ops are raw anyway. fixes the kernel build after xge grew the use of the raw ops. Normalize sentinel. Use _MACHINE_*_H_ and _<ARCH>_*_H_ properly and consitently. 2011-03-23T16:54:33Z pirofti pirofti@openbsd.org 2011-03-23T16:54:33Z urn:sha1:2fa72412907ae78c4787a4a8f888c5f0486e225c Discussed and okay drahn@. Okay deraadt@. Add bus_space_vaddr() when applicable; from NetBSD. 2009-12-25T20:52:32Z miod miod@openbsd.org 2009-12-25T20:52:32Z urn:sha1:f8ac741cd63ec3e39f041509b573960998dcdbda Get rid of the obsolet BUS_BARRIER_xxx constants for bus_space_barrier(), only 2009-07-30T21:39:13Z miod miod@openbsd.org 2009-07-30T21:39:13Z urn:sha1:7107682f8cd66f3de37a5950811a419ae4fc4202 provide and use BUS_SPACE_BARRIER_xxx. Add a BUS_DMA_ZERO flag for bus_dmamem_alloc() to return zeroed memory. 2009-04-20T00:42:05Z oga oga@openbsd.org 2009-04-20T00:42:05Z urn:sha1:471ccd185285af4568b3f0ff1eafabf82d4028ed Saves every damned driver calling bzero(), and continues the M_ZERO, PR_ZERO symmetry. Remove unused _pfthresh member from struct alpha_bus_dma_tag. 2009-02-01T14:33:58Z miod miod@openbsd.org 2009-02-01T14:33:58Z urn:sha1:2fce6f7588a334a996e097db6d469bbed787d5fc Keep track of which DMA window was actually used to map the 2006-05-12T20:48:19Z brad brad@openbsd.org 2006-05-12T20:48:19Z urn:sha1:53312540147f71445709af697103d5d4de6d9921 request (not always the passed in DMA tag if we try direct-map and then fall back to sgmap-mapped). Use the actual window when performing dmamap_sync and dmamap_unload operations. From NetBSD ok martin@ from PAE work: 2006-04-27T15:17:07Z mickey mickey@openbsd.org 2006-04-27T15:17:07Z urn:sha1:ecc650db3f73d225259c771fb8ebbf291dce6986 add a BUS_DMA_24BIT flag to signify that dmamap being created is for the isadma use (thus already backed up by the bounce buffers). later also to be used for dmamem allocation.