On Mon, 28 Jan 2013, Brad Smith wrote:
> Here is a diff to add support for the POSIX functions dprintf(3)
> and vdprintf(3).
Having poked at it a bit, I think the vdprintf.c below may be better. By
using its own write callback, it avoids the SHRT_MAX limit on the fd, and
it removes the fcntl()
The following changes mostly based on what has happened in
the upstream drm code seems to resolve problems with screen corruption
on power saving/dpms on ivy bridge with ums here. Testing on ironlake/
sandy bridge/ivy bridge (aka Core i*) to make sure this doesn't break
anything appreciated.
- re
Here is a diff to add support for the POSIX functions dprintf(3)
and vdprintf(3).
Index: lib/libc/shlib_version
===
RCS file: /cvs/src/lib/libc/shlib_version,v
retrieving revision 1.146
diff -u -p -r1.146 shlib_version
--- lib/libc/s
On Mon, Jan 28, 2013 at 10:54:33PM +, Stuart Henderson wrote:
> On 2013/01/28 14:20, Mike Larkin wrote:
> > On Mon, Jan 28, 2013 at 06:50:28PM -0200, Daniel Bolgheroni wrote:
> > > Hi tech@,
> > >
> > > anyone with a patch lurking around to work with a Rapoo V7 keyboard?
> > >
> > > Linux has
On 2013/01/28 14:20, Mike Larkin wrote:
> On Mon, Jan 28, 2013 at 06:50:28PM -0200, Daniel Bolgheroni wrote:
> > Hi tech@,
> >
> > anyone with a patch lurking around to work with a Rapoo V7 keyboard?
> >
> > Linux has a workaround, but don't know if works:
> >
> > https://github.com/Golevka/rapo
On Mon, Jan 28, 2013 at 06:50:28PM -0200, Daniel Bolgheroni wrote:
> Hi tech@,
>
> anyone with a patch lurking around to work with a Rapoo V7 keyboard?
>
> Linux has a workaround, but don't know if works:
>
> https://github.com/Golevka/rapoov7-keyboard-driver
>
> The dmesg for the kbd is:
>
>
Hi tech@,
anyone with a patch lurking around to work with a Rapoo V7 keyboard?
Linux has a workaround, but don't know if works:
https://github.com/Golevka/rapoov7-keyboard-driver
The dmesg for the kbd is:
uhidev1 at uhub5 port 1 configuration 1 interface 0 "Holtek USB Gaming
Keyboard" rev 1.1
On Mon, Jan 28, 2013 at 08:45:19PM +0100, Marc Espie wrote:
> > > Otoh this file is quite bad. It makes my vim light up all red.
> >
> > That's why you should stick to vi and not the emacs-in-a-vi-disguise
> > bloatware known as vim.
>
> Lol.
>
> Give me a vi with multiple windows, and with visu
> Give me a vi with multiple windows, and with visual, and I will consider
> changing editors.
If you need multiple windows, simply open several {rxvt,xterm,whatever}
windows and run vi in them.
On Mon, Jan 28, 2013 at 07:03:24PM +, Miod Vallat wrote:
> > Usually whitespace diffs are not that well liked, they make for
> > annoying differences, introduce noise and require more effort to review
> > for questionable gain.
> >
> > Otoh this file is quite bad. It makes my vim light up all
> Usually whitespace diffs are not that well liked, they make for
> annoying differences, introduce noise and require more effort to review
> for questionable gain.
>
> Otoh this file is quite bad. It makes my vim light up all red.
That's why you should stick to vi and not the emacs-in-a-vi-disgu
When working on the WPA-Enterprise stuff, I actually ran into an issue
with the rsu(4) I was using. It seems there is a problem with
submitting the "join BSS" command when an RSN information element is
included, which makes the command never complete. The crucial bit
seems to be that this changes
On Sun, 27 Jan 2013, Damien Miller wrote:
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
> Date: Mon, 28 Jan 2013 11:29:21 +0100 (CET)
> From: Mark Kettenis
>
> > Date: Sun, 27 Jan 2013 18:17:13 +
> > From: Stuart Henderson
> >
> > 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 h
On Mon, Jan 28, 2013 at 11:29:21AM +0100, Mark Kettenis wrote:
> [...]
> Looks like you and Gregor duplicated some effort. Anyway, this looks
> fine with to me. I'll submit my diff upstream later today.
> [...]
That's okay, my diff to the port only contains a version bump to 2.0 and
the WPA ente
On 2013/01/28 11:29, Mark Kettenis wrote:
> Looks like you and Gregor duplicated some effort.
Yes (I had already done the update to 2.0 and was waiting on an OK).
> Date: Sun, 27 Jan 2013 18:17:13 +
> From: Stuart Henderson
>
> 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
Have you checked if this is still necessary? libusb on OpenBSD is now able to
talk to devices claimed by drivers other than ugen.
Raphael Graf wrote:
>The diff below makes the jtag and serial interfaces of the beaglebone
>(FT2232H)
>work simultaneously.
>This is how the beaglebone shows up:
>
On Sun, Jan 27, 2013 at 06:17:13PM +, Stuart Henderson wrote:
> 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 (
On Mon, Jan 28, 2013 at 09:54:18AM +0100, Martin Pieuchot wrote:
> And I couldn't find a section on the FAQ about printers. Am I blind?
> Do you think it would be useful to at least document how to setup a
> printer like you did? Antoine what do you think?
Yes yes, it's on my todo.
Currently most
On 28/01/13(Mon) 00:44, Stefan Sperling wrote:
> 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 foo2
21 matches
Mail list logo
