<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/sys/dev/hil/hilid.c, branch jd/simplify-queueing</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/sys/dev/hil/hilid.c?h=jd%2Fsimplify-queueing</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/sys/dev/hil/hilid.c?h=jd%2Fsimplify-queueing'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2005-01-09T23:49:35Z</updated>
<entry>
<title>Allow send_hil{,dev}_cmd to return failure, and handle this where</title>
<updated>2005-01-09T23:49:35Z</updated>
<author>
<name>miod</name>
<email>miod@openbsd.org</email>
</author>
<published>2005-01-09T23:49:35Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=705b644aecf61563d30824cd205d3586be3ec81b'/>
<id>urn:sha1:705b644aecf61563d30824cd205d3586be3ec81b</id>
<content type='text'>
applicable.

During device probe, if a device does not answer commands, display a warning
message. This apparently happens on hp300 when the console is configured
as remote (i.e. serial console). Unplugging and replugging the device works
fine afterwards...
</content>
</entry>
<entry>
<title>Relax a redundant printf format specifier.</title>
<updated>2003-12-20T22:53:56Z</updated>
<author>
<name>miod</name>
<email>miod@openbsd.org</email>
</author>
<published>2003-12-20T22:53:56Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=46d7e1889d3c0ce6ba03c74d2614891d5e4ea3d5'/>
<id>urn:sha1:46d7e1889d3c0ce6ba03c74d2614891d5e4ea3d5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>New hil child devices attachment framework, that allow them to be detached</title>
<updated>2003-02-26T20:22:03Z</updated>
<author>
<name>miod</name>
<email>miod@openbsd.org</email>
</author>
<published>2003-02-26T20:22:03Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=60a8f706295043489d6f389dbed5ba05edf84e44'/>
<id>urn:sha1:60a8f706295043489d6f389dbed5ba05edf84e44</id>
<content type='text'>
at runtime.

Handle reconfiguration notices from the loop, and do the necessary
detach/attach work so that our vision of the loop is in sync with reality.

Adapt all hil child devices to the above changes.

"This is not as plug'n'play as usb, but you get the same feeling anyways..."
</content>
</entry>
<entry>
<title>A simple and crude driver to play with the hil so-called ``ID module''</title>
<updated>2003-02-15T23:50:00Z</updated>
<author>
<name>miod</name>
<email>miod@openbsd.org</email>
</author>
<published>2003-02-15T23:50:00Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=bda3b6898da3ac6022127199ba22fd730b7ff5e0'/>
<id>urn:sha1:bda3b6898da3ac6022127199ba22fd730b7ff5e0</id>
<content type='text'>
devices.

The ID module only purpose is to provide a small, unique, bitstring, which
was used for some copy-protection or licensing scheme under HP-UX.

Right now this driver is useless, as it provides no way to communicate
this information to userland, and only displays it while attaching, as such:
hilid0 at hil0 code 2: ID module
hilid0: security code 10 04 b4 41 ac 77 14 0f 41 00 00 00 00 00 00 00
hilid1 at hil0 code 3: ID module
hilid1: security code 10 04 b4 41 e3 b8 13 0f 41 00 00 00 00 00 00 00

Too bad it's not even good enough to feed the kernel random generator...
</content>
</entry>
</feed>
