wireguard-openbsd - WireGuard implementation for the OpenBSD kernel

	Commit message (Collapse)	Author	Age	Files	Lines
*	Add support for RT3290 chipset by James Hastings.	kevlo	2018-10-02	1	-2/+378
\| \| \| \|	Tested by me and James Hastings.
*	Update ral(4) firmware for RT2860 family devices.	stsp	2016-08-17	1	-348/+348
\| \| \| \| \| \| \| \|	Required for upcoming RT5390 and RT5392 chipset support. Tested by procter@ on RT2860 and by me on RT2790 and RT3090. Ported from FreeBSD by James Hastings. kevlo confirmed this version of the firmware is still ISC licensed.
*	Initial bits for >=RT3090 support.	damien	2010-04-05	1	-391/+391
\| \| \| \| \| \| \|	Probably not functionnal yet (but test reports are welcome). Update microcode for RT2860 while I'm here (remember to run make && make install under sys/dev/microcode/ral/).
*	fix a comment. no binary change.	damien	2008-04-15	1	-2/+2
\|
*	Adjust a date correctly; spotted by jsg	deraadt	2008-03-06	1	-2/+2
\|
*	New license from Paul Lin at Ralink; same terms, but now also	deraadt	2008-03-06	1	-1/+749
\| \| \| \|	including the firmware for the rt2860!
*	Separate rum(4) firmware from ral(4) ones.	damien	2006-08-17	1	-191/+1
\| \| \| \| \| \| \| \| \|	ral(4) firmwares are built on PCI-capable architectures only while rum(4) firmware is built on USB-capable architectures only. Rename ral-rt2573 into rum-rt2573 and build rum-rt2573 on the zaurus too (pointed out by Patrick Heim). ok deraadt@
*	- add rt2573 microcode. mostly from jolan@.	niallo	2006-06-16	1	-1/+191
\|
*	- add preliminary support for Ralink Technology RT2561, RT2561S and RT2661	damien	2006-01-09	1	-0/+2267
	chipsets in ral(4). - restructure the code a bit; split ic/ral.c into ic/rt2560.c and ic/rt2661.c - import the 8051 microcode files required by these chipsets. - more to come; there is currently no automatic rate control and some features are untested (hostap and ibss modes for instance). most of the pre-802.11n capabilities of the RT2661 chipset are not supported (like frame aggregation, piggy-back). MIMO should work though the performance/range gain has not been measured.