On Fri, Jan 25, 2013 at 04:00:51PM +0100, Martin Pieuchot wrote:
> What about modifying ulpt(4) to upload the correct firmware like
> uvideo(4) does?
I've done this, and the printer now works out of the box with lpd(8),
as long as the foo2zjs port is used as a filter:
$ cat /etc/printcap
On Thu, Jan 24, 2013 at 09:37:33PM +0200, Ville Valkonen wrote:
> Hi,
>
> save a few precious bytes by removing unnecessary white spaces from
> libc/merge.c.
Please send diffs inline, it's a lot easier to review.
Usually whitespace diffs are not that well liked, they make for
annoying difference
On 2013/01/27 17:33, Stuart Henderson wrote:
> I will merge this with my port diff to update to 2.0 and send out a diff soon.
I haven't tested WPA enterprise, but I have tested wired authentication
with this version (TP-Link switch / MD5 / freeradius).
I made a start at enabling the privilege sep
I will merge this with my port diff to update to 2.0 and send out a diff soon.
Mark Kettenis wrote:
>The recent rantings on misc@ made me look at getting this to work once
>more. And this time I got it to work, sortof. The approach uses
>wpa_supplicant, but since the OpenBSD net80211 stack tak
I just rolled an update to the wpa_supplicant port that updates it to
2.0 and includes your patch. I'm trying it out right now but it seems to
work flawlessly. Thanks a lot for the work :)
--
Gregor Best
The diff below makes the jtag and serial interfaces of the beaglebone (FT2232H)
work simultaneously.
This is how the beaglebone shows up:
uhub8 at uhub0 port 1 "Standard Microsystems product 0x2412" rev 2.00/b.b2 addr
3
uftdi0 at uhub8 port 1 configuration 1 interface 1 "FTDI BeagleBone/XDS100V2"
The recent rantings on misc@ made me look at getting this to work once
more. And this time I got it to work, sortof. The approach uses
wpa_supplicant, but since the OpenBSD net80211 stack takes care of
most of the key management (including the so-called 4-way handshake)
we only really need it to
On Fri, 25 Jan 2013, Stefan Fritsch wrote:
> Hi,
>
> qemu 1.3 has added a virtio entropy device. Here is a driver for it.
> Comments?
> OKs?
>
> As the entropy reserve of the host may not be unlimited, the OpenBSD guest
> should only ask for entropy when it actually needs it. Would it make sense
