<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/sys/dev/i2c/i2c_exec.c, branch jd/histogram</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/sys/dev/i2c/i2c_exec.c?h=jd%2Fhistogram</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/sys/dev/i2c/i2c_exec.c?h=jd%2Fhistogram'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2015-03-14T03:38:46Z</updated>
<entry>
<title>Remove some includes include-what-you-use claims don't</title>
<updated>2015-03-14T03:38:46Z</updated>
<author>
<name>jsg</name>
<email>jsg@openbsd.org</email>
</author>
<published>2015-03-14T03:38:46Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=21dab745d772244ad59a415114e48be2888cfbc8'/>
<id>urn:sha1:21dab745d772244ad59a415114e48be2888cfbc8</id>
<content type='text'>
have any direct symbols used.  Tested for indirect use by compiling
amd64/i386/sparc64 kernels.

ok tedu@ deraadt@
</content>
</entry>
<entry>
<title>use sizeof(thing) instead of hard-coding it</title>
<updated>2008-04-17T16:48:40Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2008-04-17T16:48:40Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=7c8446f17a28144e7c819f943f203ed58e6f55e7'/>
<id>urn:sha1:7c8446f17a28144e7c819f943f203ed58e6f55e7</id>
<content type='text'>
</content>
</entry>
<entry>
<title>I2C framework originally written by Steve C. Woodford and Jason R. Thorpe</title>
<updated>2004-05-23T17:33:43Z</updated>
<author>
<name>grange</name>
<email>grange@openbsd.org</email>
</author>
<published>2004-05-23T17:33:43Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=1da3bef238384d7eb941464d04d7afdfead6f388'/>
<id>urn:sha1:1da3bef238384d7eb941464d04d7afdfead6f388</id>
<content type='text'>
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@
</content>
</entry>
</feed>
