wireguard-openbsd - WireGuard implementation for the OpenBSD kernel

	Commit message (Collapse)	Author	Age	Files	Lines
*	add a size argument to free. will be used soon, but for now default to 0.	tedu	2014-07-12	1	-3/+3
\| \| \| \|	after discussions with beck deraadt kettenis.
*	Standardize xfer byte counts to ssize_t rather than a mix of size_t and int	miod	2014-06-27	1	-51/+71
\| \| \| \| \| \| \| \| \|	(we need to make them signed to spot controller overruns), and fix format strings accordingly. While there, make sure every runtime printf is prefixed by either the complete target information, if available, or at least the driver name with the proper instance number - supported systems with > 1 wdsc are quite common.
*	move away from XS_NO_CCB to iopools. all instances of this driver share a	dlg	2014-01-18	1	-26/+22
\| \| \| \| \| \| \|	single pool, which we now layer iopools on top of and share in the same way. tweaks and testing by miod@
*	Backout premature optimization and actually commit the diff which had been	miod	2012-07-02	1	-3/+8
\| \| \| \|	tested to boot multiuser.
*	Report immediate deselection from a target upon selection as a `selection	miod	2012-07-02	1	-5/+6
\| \| \| \| \| \| \| \| \|	timeout', instead of being stuck with a non-progressing request. This lets the nonexistent LUNs of the Insite Floptical probe (as non-existing) correctly. Step two of Floptical support, now if only the loading mechanism would unjam I could try some real I/O with it...
*	If running on the original 33C93, reject commands not in groups 0, 1 or 5	miod	2012-04-09	1	-58/+87
\| \| \| \| \| \| \| \| \| \| \| \|	if their size is not exactly six bytes, as the chip can't cope with this situation. Another situation all 33C93 do not cope with very well, is sending stop commands to targets (such as all sd(4) devices when halting with poweroff) - it takes a very long time to recover once all targets on the bus have been powered down, so we need to raise timeouts to unholy values (one test case has required more than 20 seconds to recover). Not surprising, as this command is not documented as supported in the chip documentation.
*	Work in progress support for the SGI Indigo, Indigo 2 and Indy systems	miod	2012-03-28	1	-0/+2337
	(IP20, IP22, IP24) in 64-bit mode, adapated from NetBSD. Currently limited to headless operation, input and video drivers will get ported soon. Should work on all R4000, R4440 and R5000 based systems. L2 cache on R5000SC Indy not supported yet (coming soon), R4600 not supported yet either (coming soon as well). Tested to boot multiuser on: Indigo2 R4000SC, Indy R4000PC, Indy R4000SC, Indy R5000SC, Indigo2 R4400SC. There are still glitches in the Ethernet driver which are being looked at. Expansion support is limited to the GIO E++ board; GIO boards with PCI-GIO bridges not ported yet due to the lack of hardware, and this kind of driver does not port blindly. Most of this work comes from NetBSD, polishing and integration work, as well as putting as many ``R4x00 in 64-bit mode'' erratas as necessary, by yours truly. More work is coming, as well as trying to get some easy way to boot install kernels (as older PROM can only boot ECOFF binaries, which won't do for the kernel).