wireguard-openbsd - WireGuard implementation for the OpenBSD kernel

	Commit message (Collapse)	Author	Age	Files	Lines
*	Remove some includes include-what-you-use claims don't	jsg	2015-03-14	1	-2/+1
\| \| \| \| \| \| \|	have any direct symbols used. Tested for indirect use by compiling amd64/i386/sparc64 kernels. ok tedu@ deraadt@
*	we have been knocking out i2c when ipmi exists on a machine (because	deraadt	2007-10-09	1	-12/+1
\| \| \| \| \| \| \| \|	there are ipmi bmc's that apparently violate i2c bus master locking). but those problems bite us only for sensors which we re-scan every few seconds, and then we hit the ipmi bmc's races. for non-sensor devices (like spdmem) it is probably ok to look once. let's try that method for a while and see if anyone sees breakage.
*	if ipmi is on the machine: instead of (confusingly) failing in match,	deraadt	2006-02-26	1	-8/+10
\| \| \| \|	bail out in attach, and also say why; ok marco
*	add a member to the i2c_attach args so that a controller can pass a	dlg	2006-02-08	1	-1/+2
\| \| \| \| \| \| \| \|	cookie down to the device. the most obvious use of this is to pass a device its ofw node on sparc64 and macppc so it can configure itself more appropriately. ok kettenis@ henning@ deraadt@
*	Disable iic whenever ipmi is enabled. This fixes boxes like Sun x4200 that	marco	2006-01-29	1	-1/+10
\| \| \| \| \| \| \|	freak out when more than one device driver touch the i2c devices. Reported by: Srebrenko Sehic <ssehic at gmail dot com> ok kettenis@
*	switch from macppc-specific maciic(4) driver to the generic iic(4),	deraadt	2006-01-01	1	-4/+6
\| \| \| \| \|	after teaching it to use a function pointer to get back to the OFW scan.. this will also help the sparc64 later; ok kettenis
*	no longer use ia_compat; tested by a few	deraadt	2005-12-27	1	-2/+1
\|
*	make direct mappings fail for now, since noone will test that for me	deraadt	2005-12-27	1	-3/+3
\|
*	the name belongs in "quotes"	deraadt	2005-12-27	1	-2/+2
\|
*	if probe falls, iic_print should print the name we attempted to match under	deraadt	2005-12-26	1	-1/+3
\|
*	upon startup, only scan-and-attach devices which specify an address	deraadt	2005-12-23	1	-9/+10
\| \| \| \| \|	attribute; if that is not set, then we hope something later will guess the address. this must be revisited later on, to avoid double-attachment
*	permit outsider to call iic_print	deraadt	2005-12-22	1	-2/+1
\|
*	Do bus scanning only if underlying controller asked for it.	grange	2005-12-20	1	-2/+3
\|
*	First attempt to have a table of known I2C slave devices that we	grange	2005-12-19	1	-1/+7
\| \| \| \| \| \| \| \|	have drivers for. iic(4) will scan the bus for them and try to attach an appropriate driver. For now iic(4) scans for all possible addresses for debugging purposes. ok deraadt@
*	instead of passing OF nodes down to the drivers, pass name/compat string	deraadt	2005-11-15	1	-1/+3
\| \| \| \| \| \|	pointers. This lets their match() functions actually make real decisions. OF-capable machines will pass name/compat pointers, but other machines will not. grudging ok kettenis
*	I2C framework originally written by Steve C. Woodford and Jason R. Thorpe	grange	2004-05-23	1	-0/+133
	for NetBSD (r). This framework supports various i2c master controllers: - dumb bit-bang controllers - a few styles of automated controllers that give you control over sending start/stop conditions on the i2c bus - automated controllers that are too smart for its own good, giving software no control over start/stop conditions - smbus controllers by emulating smbus protocol with i2c commands i2c slave devices need their addresses to be specified in the kernel config file, no device discovery presented. ok deraadt@