<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/sys/arch/sparc64/dev, branch master</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/sparc64/dev?h=master</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/sparc64/dev?h=master'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2021-03-11T11:16:54Z</updated>
<entry>
<title>spelling</title>
<updated>2021-03-11T11:16:54Z</updated>
<author>
<name>jsg</name>
<email>jsg@openbsd.org</email>
</author>
<published>2021-03-11T11:16:54Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=36fd90dcf1acf2ddb4ef5dbabe5313b3a8d46ee2'/>
<id>urn:sha1:36fd90dcf1acf2ddb4ef5dbabe5313b3a8d46ee2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>timecounting: use C99-style initialization for all timecounter structs</title>
<updated>2021-02-23T04:44:30Z</updated>
<author>
<name>cheloha</name>
<email>cheloha@openbsd.org</email>
</author>
<published>2021-02-23T04:44:30Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=8611d3cdb295683ad47c33036b86b471b2d09741'/>
<id>urn:sha1:8611d3cdb295683ad47c33036b86b471b2d09741</id>
<content type='text'>
The timecounter struct is large and I think it may change in the
future.  Changing it later will be easier if we use C99-style
initialization for all timecounter structs.  It also makes reading the
code a bit easier.

For reasons I cannot explain, switching to C99-style initialization
sometimes changes the hash of the resulting object file, even though
the resulting struct should be the same.  So there is a binary change
here, but only sometimes.  No behavior should change in either case.

I can't compile-test this everywhere but I have been staring at the
diff for days now and I'm relatively confident this will not break
compilation.  Fingers crossed.

ok gnezdo@
</content>
</entry>
<entry>
<title>blacklist com on m3000s. our com code causes faults somehow.</title>
<updated>2021-01-19T21:52:59Z</updated>
<author>
<name>dlg</name>
<email>dlg@openbsd.org</email>
</author>
<published>2021-01-19T21:52:59Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=c317fba5c295aa6b03fb700374cc80a25dbabd29'/>
<id>urn:sha1:c317fba5c295aa6b03fb700374cc80a25dbabd29</id>
<content type='text'>
console i/o still happens using ofw routines, which is Good Enough(tm)
for now. having a working machine means i can better test changes
now though.

ok deraadt@
</content>
</entry>
<entry>
<title>Refactor klist insertion and removal</title>
<updated>2020-12-25T12:59:51Z</updated>
<author>
<name>visa</name>
<email>visa@openbsd.org</email>
</author>
<published>2020-12-25T12:59:51Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=9b0cf67b268a857fffa6a742ad6be57acdc35301'/>
<id>urn:sha1:9b0cf67b268a857fffa6a742ad6be57acdc35301</id>
<content type='text'>
Rename klist_{insert,remove}() to klist_{insert,remove}_locked().
These functions assume that the caller has locked the klist. The current
state of locking remains intact because the kernel lock is still used
with all klists.

Add new functions klist_insert() and klist_remove() that lock the klist
internally. This allows some code simplification.

OK mpi@
</content>
</entry>
<entry>
<title>Rename the macro MCLGETI to MCLGETL and removes the dead parameter ifp.</title>
<updated>2020-12-12T11:48:52Z</updated>
<author>
<name>jan</name>
<email>jan@openbsd.org</email>
</author>
<published>2020-12-12T11:48:52Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=471f2571dbcecd0ac12f9020fb846fcac790084a'/>
<id>urn:sha1:471f2571dbcecd0ac12f9020fb846fcac790084a</id>
<content type='text'>
OK dlg@, bluhm@
No Opinion mpi@
Not against it claudio@
</content>
</entry>
<entry>
<title>If Open Firmware doesn't provide an interrupt mapping, use the swizzled</title>
<updated>2020-10-27T21:01:33Z</updated>
<author>
<name>kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2020-10-27T21:01:33Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=ce94d5d8e6a56207ace314d2caca54d7916fd88a'/>
<id>urn:sha1:ce94d5d8e6a56207ace314d2caca54d7916fd88a</id>
<content type='text'>
interrupt pin as the devino.  Fixes ohci(4) and ehci(4) interrupts on the
Fujitsu M10-1.
</content>
</entry>
<entry>
<title>If the #msi-eqs property says there are no event queues, don't try to set</title>
<updated>2020-10-24T05:07:47Z</updated>
<author>
<name>jmatthew</name>
<email>jmatthew@openbsd.org</email>
</author>
<published>2020-10-24T05:07:47Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=abff9b49e15f11028cf336ccdf6c688532590a3c'/>
<id>urn:sha1:abff9b49e15f11028cf336ccdf6c688532590a3c</id>
<content type='text'>
up MSI support.

stsp@ and bluhm@ ran into this on T5220s
ok stsp@ kettenis@ patrick@
</content>
</entry>
<entry>
<title>unbreak build</title>
<updated>2020-10-16T03:59:24Z</updated>
<author>
<name>jsg</name>
<email>jsg@openbsd.org</email>
</author>
<published>2020-10-16T03:59:24Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=a1adfca221f7772ddcb5d4c9283735c30ccd6fbe'/>
<id>urn:sha1:a1adfca221f7772ddcb5d4c9283735c30ccd6fbe</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Replace simple one-line bcopy()/memcpy() of faked data into scsi_xfer with call</title>
<updated>2020-10-15T13:22:12Z</updated>
<author>
<name>krw</name>
<email>krw@openbsd.org</email>
</author>
<published>2020-10-15T13:22:12Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=a83ec2865aeaeb867719080e00ad0ac9752d01cc'/>
<id>urn:sha1:a83ec2865aeaeb867719080e00ad0ac9752d01cc</id>
<content type='text'>
to scsi_copy_internal_data(). Thus getting xs-&gt;resid properly set and adding the
usual uio/size sanity checks.
</content>
</entry>
<entry>
<title>fix indentation</title>
<updated>2020-10-01T05:14:10Z</updated>
<author>
<name>jsg</name>
<email>jsg@openbsd.org</email>
</author>
<published>2020-10-01T05:14:10Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=16dc50068fe999300032a0a8a678a0c980c921a4'/>
<id>urn:sha1:16dc50068fe999300032a0a8a678a0c980c921a4</id>
<content type='text'>
</content>
</entry>
</feed>
