I like this *MUCH* better than the way acpithinkpad volume buttons
currently work. these buttons should be affecting the mixer, if
at all possible, instead of doing things behind the audio system's
back, which causes confusion.
On Sun, Mar 13, 2011 at 10:11:54PM +0300, Alexander Polakov wrote:
On Sun, Mar 13, 2011 at 8:49 AM, Stefan Sperling s...@openbsd.org wrote:
The vfwprintf.c innards are based on a mix of OpenBSD's vfprintf.c
and NetBSD's vfwprintf.c. In NetBSD, both narrow and wide character
versions are generated from the same file using tons of macro spaghetti.
I didn't find
On Mon 2011.03.14 at 11:05 +0800, Kevin Lo wrote:
This diff fixes uninitialized variable warnings emitted by gcc 4.2.1
on i386/amd64.
How's this instead (lifted from mksh)?
Index: eval.c
===
RCS file:
2011/3/11 Anton Maksimenkov anton...@gmail.com:
If some process can catch COM port in a way that noone can use the
port and noone can kill that process - it is wrong situation.
I think this would be a little bit better:
--- /usr/origsrc/sys/kern/tty.c Mon Oct 11 22:20:15 2010
+++
On Mon, Mar 14, 2011 at 05:52:41AM +, Jacob Meuser wrote:
I like this *MUCH* better than the way acpithinkpad volume buttons
currently work. these buttons should be affecting the mixer, if
at all possible, instead of doing things behind the audio system's
back, which causes confusion.
This device:
udav0 at uhub5 port 2 ShanTou DM9601 rev 1.10/1.01 addr 2
udav0: address 00:60:6e:00:6e:20
amphy0 at udav0 phy 0: DM9601 10/100 PHY, rev. 0
causes a kernel crash with the following messages:
memcpy() at memcpy+0x16
usb_transfer_complete() at usb_transfer_complete+0x256
Zima je konaD
no prošla... Vreme je za proleDno D
išDenje!
Neka vaš dom zablista uz najbolje Top Shop proizvode za D
išDenje, a vi
uEivajte u više slobodnog vremena!
Kliknite ovde i odaberite najbolje za blistav dom. Završite kuDne
poslove za kraDe vreme - neka drugi rade umesto vas!
On Sun, Mar 13, 2011 at 8:22 PM, Philip Guenther guent...@gmail.com wrote:
Hmm, any test programs that are smaller and preferably not need X11?
My little V100 takes forever with a build as is...
I don't know of any at the moment. I'll try to look for something.
You should be using
On Tue, Mar 8, 2011 at 11:50 AM, Matthew Dempsky matt...@dempsky.org wrote:
Currently, the diff only supports amd64, i386, and sparc64 (the only
arches that NetBSD supports fenv.h on),
I'd also appreciate help on adding support for the other platforms.
Thanks!
On Mon, Mar 14, 2011 at 12:29 AM, Amit Kulkarni amitk...@gmail.com wrote:
I understand these need to be done right after lock. Might be you guys
have better stuff planned than this stuff.
Right after is a relative term. If adding wprintf goes smoothly, then
there's plenty of time for wscanf.
the following diff make mfi(4) use 64-bit frames, and support 64-bit
dma addresses. these changes are based on freebsd's mfi(4). however,
freebsd only uses 64-bit frames 'if (sizeof(bus_addr_t)) == 8',
whereas this patch uses 64-bit frames unconditionally, for both 32-bit
and 64-bit platforms.
remove unused SILLY game of life.
no binary change.
ok?
Index: config.h
===
RCS file: /home/okan/hack/open/cvs/src/bin/ksh/config.h,v
retrieving revision 1.13
diff -u -p -r1.13 config.h
--- config.h18 Dec 2004 22:42:26 -
pull out the never enabled fp support.
no binary change.
ok?
Index: ksh_limval.h
===
RCS file: /home/okan/hack/open/cvs/src/bin/ksh/ksh_limval.h,v
retrieving revision 1.2
diff -u -p -r1.2 ksh_limval.h
--- ksh_limval.h18 Dec
On Mon, Mar 14, 2011 at 4:29 PM, Jacob Meuser jake...@sdf.lonestar.org
wrote:
i386
32-bit mfi frames (current code)
32m23.04s 33m50.57s 10m49.27s
32m31.09s 33m48.24s 10m51.21s
64-bit mfi frames (with patch)
32m29.76s 33m36.95s
Hi,
The following adds legacy MDNS lookups to libc.
It adds the keyword 'mdns' to 'lookup' in /etc/resolv.conf, only names in the
.local (MDNS domain) are looked up.
A legacy lookup is how MDNS calls a simple unicast lookup sent to the mcast addr
224.0.0.251, the MDNS responder is responsible
15 matches
Mail list logo
