<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/sys/arch/powerpc64, branch master</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/powerpc64?h=master</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/powerpc64?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>Add uhidpp(4), a driver for Logitech HID++ devices. Currently limited to</title>
<updated>2021-02-04T16:25:38Z</updated>
<author>
<name>anton</name>
<email>anton@openbsd.org</email>
</author>
<published>2021-02-04T16:25:38Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=7acea25ddf6a2c2e0c9890ddb6c0a15e0dd82242'/>
<id>urn:sha1:7acea25ddf6a2c2e0c9890ddb6c0a15e0dd82242</id>
<content type='text'>
exposing battery sensors for HID++ 2.0 devices. Most of the code is
derived from the hid-logitech-hidpp Linux driver.

Thanks to Ville Valkonen &lt;weezeldinga at gmail dot com&gt; for testing.

ok mglocker@
</content>
</entry>
<entry>
<title>Again allow COPTS= to come from the environment again, and don't lose the</title>
<updated>2021-01-28T17:39:01Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2021-01-28T17:39:01Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=cae8b9cb0a13da6ca7aedfa2962b63c5aa8494c1'/>
<id>urn:sha1:cae8b9cb0a13da6ca7aedfa2962b63c5aa8494c1</id>
<content type='text'>
SMALL_KERNEL specific variations.
ok espie jsg
</content>
</entry>
<entry>
<title>OPAL implements firmware calls that abstract communicating with the BMC over</title>
<updated>2021-01-23T12:10:08Z</updated>
<author>
<name>kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2021-01-23T12:10:08Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=c5fc2d4914929c0917173549b6372d64cb18ba33'/>
<id>urn:sha1:c5fc2d4914929c0917173549b6372d64cb18ba33</id>
<content type='text'>
IPMI.  Use these calls to add support for impi(4) on PowerNV systems.

ok dlg@
</content>
</entry>
<entry>
<title>introduce ujoy(4), a restricted subset of uhid(4) for gamecontrollers.</title>
<updated>2021-01-23T05:08:33Z</updated>
<author>
<name>thfr</name>
<email>thfr@openbsd.org</email>
</author>
<published>2021-01-23T05:08:33Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=1d44892edf51d2b78a17901b1aa49c83bd9a69e0'/>
<id>urn:sha1:1d44892edf51d2b78a17901b1aa49c83bd9a69e0</id>
<content type='text'>
This includes ujoy_hid_is_collection() to work around limitations of
hid_is_collection() until this can be combined without fallout.

input, testing with 8bitdo controller, and ok brynet@
PS4 controller testing, fix for hid_is_collection, and ok mglocker@
</content>
</entry>
<entry>
<title>Enable support for floating-point exceptions.  We always run in "precise"</title>
<updated>2021-01-09T13:14:02Z</updated>
<author>
<name>kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2021-01-09T13:14:02Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=068793ccd4d9da0f69bf5536a9c727065f20b05d'/>
<id>urn:sha1:068793ccd4d9da0f69bf5536a9c727065f20b05d</id>
<content type='text'>
mode.  On modern processors (POWER8 and later) there is no performance
penalty for this as long as exceptions are disabled in the FPSCR (which
is the default).  This way we don't have to implement an
architecture-dependent system call to set the mode, as it can only be done
by the kernel.

With help from gkoehler@

ok gkoehler@
</content>
</entry>
<entry>
<title>Fix typo in comment.</title>
<updated>2021-01-07T19:02:45Z</updated>
<author>
<name>kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2021-01-07T19:02:45Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=9b7ac8413a7c0595727918f01f86e665f6791c98'/>
<id>urn:sha1:9b7ac8413a7c0595727918f01f86e665f6791c98</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Enter power-saving mode on POWER9 (ISA v3)</title>
<updated>2020-12-30T06:06:30Z</updated>
<author>
<name>gkoehler</name>
<email>gkoehler@openbsd.org</email>
</author>
<published>2020-12-30T06:06:30Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=196daab381bbbbcb721d4c428764249109b38970'/>
<id>urn:sha1:196daab381bbbbcb721d4c428764249109b38970</id>
<content type='text'>
When opal(4) attaches, look in the device tree for a psscr value.  In
cpu_idle_cycle(), use this psscr value and the stop instruction to
wait for the next interrupt.  In mp kernels, cpu_unidle() now sends an
interrupt.  In "sysctl hw.sensors", the power and temperature sensors
from opalsens(4) may show lower values.

The cpu may exit stop at the system reset vector after losing user
registers.  If so, restore some registers.  For now, ignore deeper
stop states that would lose hypervisor registers.

Our mp kernel uses only the first hardware thread of each core.  Take
the extra threads from the firmware and stop them forever; this may
switch the core from SMT4 to single-thread mode and increase
performance.

partly by kettenis@, ok kettenis@
</content>
</entry>
<entry>
<title>Use IPL_VM for the pmap pool like we do on amd64.</title>
<updated>2020-12-23T17:54:04Z</updated>
<author>
<name>kettenis</name>
<email>kettenis@openbsd.org</email>
</author>
<published>2020-12-23T17:54:04Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=a02f695c6a886c589dba0586557b6a20d78bebb1'/>
<id>urn:sha1:a02f695c6a886c589dba0586557b6a20d78bebb1</id>
<content type='text'>
</content>
</entry>
</feed>
