wireguard-openbsd - WireGuard implementation for the OpenBSD kernel

	Commit message (Collapse)	Author	Age	Files	Lines
*	Unify the MD byteswapping code as much as possible across architectures.	naddy	2018-10-02	1	-22/+22
\| \| \| \| \| \| \|	Use inline functions instead of GNU C statement expressions, and make them available to userland. With clues from guenther@. ok guenther@ kettenis@
*	Tackle the endian.h mess. Make it so that:	guenther	2014-07-12	1	-5/+8
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* you can #include <sys/endian.h> instead of <machine/endian.h>, and ditto <endian.h> (fixes code that pulls in <sys/endian.h> first) * those will always export the symbols that POSIX specified for <endian.h>, including the new {be,le}{16,32,64}toh() set. c.f. http://austingroupbugs.net/view.php?id=162 if __BSD_VISIBLE then you also get the symbols that our <machine/endian.h> currently exports (ntohs, NTOHS, dlg's bemtoh, etc) when doing POSIX compiles (not __BSD_VISIBLE), then <netinet/in.h> and <arpa/inet.h> will stop exporting the extra symbols like BYTE_ORDER and betoh* ok deraadt@
*	Implement swap64 with the bswapq instruction. (Commit stolen from mikeb@)	guenther	2011-03-12	1	-9/+8
\| \| \| \| \| \|	Add missing __statement modifiers and correct %1 to %0 in the asm. ok mikeb@, pirofti@, drahn@
*	Use _MACHINE_ENDIAN_H_ for this is The Right Thing To Do.	pirofti	2011-03-11	1	-4/+4
\| \| \| \|	Okay guenther@, millert@.
*	First step in include files overhaul. Use __FOO_VISIBLE (as defined	millert	2005-12-13	1	-2/+2
\| \| \| \| \|	in sys/cdefs.h) instead of _FOO_SOURCE. Also fix several namespace pollution issues, including the byte order defines. OK deraadt@
*	Drop clause 3/4 as per i386 version this was based on.	jsg	2005-12-12	1	-6/+1
\| \| \| \|	ok niklas@ (Copyright holder).
*	an amd64 arch support.	mickey	2004-01-28	1	-0/+67
	hacked by art@ from netbsd sources and then later debugged by me into the shape where it can host itself. no bootloader yet as needs redoing from the recent advanced i386 sources (anyone? ;)