<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/sys/dev/usb, branch master</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/sys/dev/usb?h=master</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/sys/dev/usb?h=master'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2021-04-01T08:39:52Z</updated>
<entry>
<title>Push kernel lock down to umb_rtrequest().</title>
<updated>2021-04-01T08:39:52Z</updated>
<author>
<name>mvs</name>
<email>mvs@openbsd.org</email>
</author>
<published>2021-04-01T08:39:52Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=99ae0d529b6d032ce4069677ab2067bf7b453da4'/>
<id>urn:sha1:99ae0d529b6d032ce4069677ab2067bf7b453da4</id>
<content type='text'>
We are going to unlock PF_ROUTE sockets. This means `if_rtrequest'
handler will be performed without kernel lock.

umb_rtrequest() calls umb_send_inet_proposal() which touches kernel lock
protected `ipv{4,6}dns' array. Also umb_rtrequest() is the only handler
which requires kernel lock to be held. So push the lock down to
umb_rtrequest() instead of grab it around `if_rtrequest' call.

This hunk was commited separately for decreases PF_ROUTE sockets
unlocking diff.

ok gerhard@ deraadt@
</content>
</entry>
<entry>
<title>sync</title>
<updated>2021-03-31T09:59:32Z</updated>
<author>
<name>sthen</name>
<email>sthen@openbsd.org</email>
</author>
<published>2021-03-31T09:59:32Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=f1b57233183230e170f617e4e288ea95dd91842d'/>
<id>urn:sha1:f1b57233183230e170f617e4e288ea95dd91842d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Remove redundant "HUAWEI Mobile" in usbdevs strings, mention radio</title>
<updated>2021-03-31T09:59:21Z</updated>
<author>
<name>sthen</name>
<email>sthen@openbsd.org</email>
</author>
<published>2021-03-31T09:59:21Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=ab95e3fef0852dc8bde2750459a5ad77d0e77dce'/>
<id>urn:sha1:ab95e3fef0852dc8bde2750459a5ad77d0e77dce</id>
<content type='text'>
technology where known.  ok deraadt
</content>
</entry>
<entry>
<title>fix typos in comments</title>
<updated>2021-03-30T20:58:19Z</updated>
<author>
<name>sthen</name>
<email>sthen@openbsd.org</email>
</author>
<published>2021-03-30T20:58:19Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=cb6aabf8dec4728ac72ed1cf84cb63183544292c'/>
<id>urn:sha1:cb6aabf8dec4728ac72ed1cf84cb63183544292c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Some cards announce support for the NTB16 format, but that support does not</title>
<updated>2021-03-30T15:59:04Z</updated>
<author>
<name>patrick</name>
<email>patrick@openbsd.org</email>
</author>
<published>2021-03-30T15:59:04Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=83adad259f528e17beecae7257fe85f0f0a9dfa9'/>
<id>urn:sha1:83adad259f528e17beecae7257fe85f0f0a9dfa9</id>
<content type='text'>
work.  Hence, add support for NTB32 in the transmit path.  We already have
support for NTB32 in the receive path.  We detect the supported format on
boot and can then decide on transmit which format to use.

From ehrhardt@ with gerhard@
Tested by jan@
ok sthen@
</content>
</entry>
<entry>
<title>Some umb(4) devices require the NDP pointer behind the NDP datagram.</title>
<updated>2021-03-30T15:48:36Z</updated>
<author>
<name>patrick</name>
<email>patrick@openbsd.org</email>
</author>
<published>2021-03-30T15:48:36Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=e77540ad9329c6dc6b4c4193eb1ad52c6b2d2ee5'/>
<id>urn:sha1:e77540ad9329c6dc6b4c4193eb1ad52c6b2d2ee5</id>
<content type='text'>
From gerhard@
"broadly OK" sthen@
</content>
</entry>
<entry>
<title>combine umb_products and umb_fccauth_devs into one umb_quirks table</title>
<updated>2021-03-29T13:38:01Z</updated>
<author>
<name>sthen</name>
<email>sthen@openbsd.org</email>
</author>
<published>2021-03-29T13:38:01Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=af33e5c81c7ed26da48f5fe9192db998adf7fecb'/>
<id>urn:sha1:af33e5c81c7ed26da48f5fe9192db998adf7fecb</id>
<content type='text'>
ok gerhard@
</content>
</entry>
<entry>
<title>Add vid/pid table to umb(4) allowing matching to alternate config</title>
<updated>2021-03-28T12:08:58Z</updated>
<author>
<name>sthen</name>
<email>sthen@openbsd.org</email>
</author>
<published>2021-03-28T12:08:58Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=c2fcfdc9e070a8fd2d17b3b1529fc687de7585cb'/>
<id>urn:sha1:c2fcfdc9e070a8fd2d17b3b1529fc687de7585cb</id>
<content type='text'>
Some devices present multiple configurations and the one chosen by default
is not always usable - for example, some have an CDC ECM config that does
not work with our cdce(4) - allow overriding to a specific config in those
cases.

From gerhard@ with tweaks to comments by me, ok patrick@
</content>
</entry>
<entry>
<title>sync</title>
<updated>2021-03-28T12:06:46Z</updated>
<author>
<name>sthen</name>
<email>sthen@openbsd.org</email>
</author>
<published>2021-03-28T12:06:46Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=0b088910f3b803fcf5d0e660f54040b508f989b1'/>
<id>urn:sha1:0b088910f3b803fcf5d0e660f54040b508f989b1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>add pid for Dell DW5821e and HUAWEI ME906s LTE, ok patrick@</title>
<updated>2021-03-28T12:06:35Z</updated>
<author>
<name>sthen</name>
<email>sthen@openbsd.org</email>
</author>
<published>2021-03-28T12:06:35Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=8cc3a8654c847780af6ffd4ce4b19057503128b2'/>
<id>urn:sha1:8cc3a8654c847780af6ffd4ce4b19057503128b2</id>
<content type='text'>
</content>
</entry>
</feed>
