wireguard-openbsd - WireGuard implementation for the OpenBSD kernel

	Commit message (Collapse)	Author	Age	Files	Lines
*	If you use sys/param.h, you don't need sys/types.h	deraadt	2017-09-08	1	-2/+1
\|
*	Don't include <mips64/archtype.h> unless you really need it.	miod	2012-10-03	1	-2/+1
\|
*	Don't forget to print the frame buffer name obtained from ARCS, as all other	miod	2012-05-12	1	-2/+6
\| \| \| \|	GIO frame buffer drivers do.
*	GIO devices with a 32-bit device identifier actually do not like halfword and	miod	2012-05-10	1	-4/+5
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	byte accesses to the ID register; instead of interpreting this is as a lack of hardware, reconize this as a valid GIO device (if the `has a 32-bit ID' bit is set, that is). This allows GIO Impact boards, which use a 32-bit ID, to be recognized correctly, and to work as a console device. Commited from an Indigo2 with glass console on the single-board Impact (MG10) board which arrived in the mail today. Would have been done even earlier, had I not forgotten to connect the extra power supply cable to the Impact GIO backplane...
*	Be more strict in the `are we the console device' logic at device attachment	miod	2012-05-10	1	-2/+7
\| \| \| \| \|	time; not only do we need to match the graphics console address, but cn_tab needs to point to wsdisplay, too.
*	Pour even more smarts into the GIO device identification code, to the point	miod	2012-04-24	1	-15/+1
\| \| \| \| \| \| \| \|	that it can now tell ID-less framebuffers apart correctly. Therefore, we can use direct configuration instead of ugly games. Frame buffer drivers match routines now only need to check for the fake ID they receive. Tested on various newport and grtwo setups (including multihead configurations)
*	Split the existing impact@xbow attachment into generic impact routines, and	miod	2012-04-18	1	-0/+142
	bus-specific attachment; impactreg.h and impactvar.h move from sgi/xbow/ to sgi/dev/. Teach the generic impact code how to code with pre-ImpactSR boards, which have a slightly different register layout (information obtained from Peter Fuerst's Linux IP28 patches). Add an impact@gio attachment (unfortunately untested, no Impact GIO boards here). All Indigo 2 graphics options should be supported now (assuming the Extreme/Ultra will actually work with grtwo(4) out of the box). Tested not to disturb operation on IP30. ATTENTION! If you are building IP27 or IP30 kernels, be sure to rm impact.d before building a new kernel.