<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/sys/dev/ic, branch master</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/sys/dev/ic?h=master</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/sys/dev/ic?h=master'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2021-03-07T06:21:38Z</updated>
<entry>
<title>ansi</title>
<updated>2021-03-07T06:21:38Z</updated>
<author>
<name>jsg</name>
<email>jsg@openbsd.org</email>
</author>
<published>2021-03-07T06:21:38Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=5c074aa0e62ba7e1d8a33f27483c11ed48c5d450'/>
<id>urn:sha1:5c074aa0e62ba7e1d8a33f27483c11ed48c5d450</id>
<content type='text'>
</content>
</entry>
<entry>
<title>off by one</title>
<updated>2021-03-03T23:58:28Z</updated>
<author>
<name>jsg</name>
<email>jsg@openbsd.org</email>
</author>
<published>2021-03-03T23:58:28Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=f662719dc20132ce7579d13e09ec7d2fb5f5c18b'/>
<id>urn:sha1:f662719dc20132ce7579d13e09ec7d2fb5f5c18b</id>
<content type='text'>
ok claudio@ deraadt@
</content>
</entry>
<entry>
<title>Read and parse OTP on the BCM4378.  There are quite a few firmware and</title>
<updated>2021-02-26T12:33:59Z</updated>
<author>
<name>patrick</name>
<email>patrick@openbsd.org</email>
</author>
<published>2021-02-26T12:33:59Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=ed6d4272d7266bb8145ca2309077cd2b21e76d74'/>
<id>urn:sha1:ed6d4272d7266bb8145ca2309077cd2b21e76d74</id>
<content type='text'>
nvram files used for the different Apple devices.  The device tree and
the OTP hold the information which of those we will have to use.  For
now this information will simply be printed, but depending on how we
choose to do the firmare distribution we could use it for loadfirmware().
</content>
</entry>
<entry>
<title>Refactor bwfm(4) firmware loading.  The PCIe backend will need to be able</title>
<updated>2021-02-26T00:07:41Z</updated>
<author>
<name>patrick</name>
<email>patrick@openbsd.org</email>
</author>
<published>2021-02-26T00:07:41Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=94e4747cf8507bfa25f5391c2d82bc52c1f571c7'/>
<id>urn:sha1:94e4747cf8507bfa25f5391c2d82bc52c1f571c7</id>
<content type='text'>
to load the CLM blob like the SDIO backend already does.  Additionally it
is also helpful for the PCIe backend to try a file named after the device
tree compatible.  Thus refactor the SDIO code and make it available for
both SDIO and PCIe.
</content>
</entry>
<entry>
<title>Some newer chips have two D11/802.11 cores, and we need to reset both at</title>
<updated>2021-02-25T23:55:41Z</updated>
<author>
<name>patrick</name>
<email>patrick@openbsd.org</email>
</author>
<published>2021-02-25T23:55:41Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=3c53ddef6de1ba5c41255da644773727fffe34cc'/>
<id>urn:sha1:3c53ddef6de1ba5c41255da644773727fffe34cc</id>
<content type='text'>
the same time.
</content>
</entry>
<entry>
<title>Prevent zero size devices from attaching</title>
<updated>2021-02-25T07:30:36Z</updated>
<author>
<name>jan</name>
<email>jan@openbsd.org</email>
</author>
<published>2021-02-25T07:30:36Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=badf3925680491859cc47586d6b39ed57e0aa3e4'/>
<id>urn:sha1:badf3925680491859cc47586d6b39ed57e0aa3e4</id>
<content type='text'>
This also fixes two NULL ptr derefs in later code path.

OK patick@, krw@
</content>
</entry>
<entry>
<title>we don't have to cast to caddr_t when calling m_copydata anymore.</title>
<updated>2021-02-25T02:48:19Z</updated>
<author>
<name>dlg</name>
<email>dlg@openbsd.org</email>
</author>
<published>2021-02-25T02:48:19Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=5c7fed39bd376c774afa6b5ea3c41fd50de48416'/>
<id>urn:sha1:5c7fed39bd376c774afa6b5ea3c41fd50de48416</id>
<content type='text'>
the first cut of this diff was made with coccinelle using this spatch:

@rule@
type caddr_t;
expression m, off, len, cp;
@@
-m_copydata(m, off, len, (caddr_t)cp)
+m_copydata(m, off, len, cp)

i had fix it's opinionated idea of formatting by hand though, so
i'm not sure it was worth it.

ok deraadt@ bluhm@
</content>
</entry>
<entry>
<title>Enumerate GCI core, which seems to contain the OTP on the Apple M1.</title>
<updated>2021-02-24T10:13:08Z</updated>
<author>
<name>patrick</name>
<email>patrick@openbsd.org</email>
</author>
<published>2021-02-24T10:13:08Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=9d277f821f2e88239ca1ec293a27df700b62db0c'/>
<id>urn:sha1:9d277f821f2e88239ca1ec293a27df700b62db0c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>remove some unused includes</title>
<updated>2021-02-23T10:20:10Z</updated>
<author>
<name>jsg</name>
<email>jsg@openbsd.org</email>
</author>
<published>2021-02-23T10:20:10Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=2e4f0d95aeae5f7c52ca7e76b88e9df56a856c15'/>
<id>urn:sha1:2e4f0d95aeae5f7c52ca7e76b88e9df56a856c15</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add a barrier between reading the cqe flags and the command ID, which</title>
<updated>2021-02-09T01:50:10Z</updated>
<author>
<name>jmatthew</name>
<email>jmatthew@openbsd.org</email>
</author>
<published>2021-02-09T01:50:10Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=ee570821402ebda8e6230e9e2035c8409933bfc1'/>
<id>urn:sha1:ee570821402ebda8e6230e9e2035c8409933bfc1</id>
<content type='text'>
should ensure that we don't read a stale command ID and complete the
wrong scsi io.  powerpc64 base builds were crashing like this fairly
regularly.

ok deraadt@ dlg@
</content>
</entry>
</feed>
