Re: run(4) firmware update; please test

2014-05-17 Thread Stefan Sperling
On Fri, May 16, 2014 at 02:38:49PM +, Alexey Suslikov wrote: Please take a look at my (unfinished) attempt to bring MediaTek/Ralink RT5370/RT5372 support to run(4). http://marc.info/?l=openbsd-techm=138903287819764w=2 I did take a look at this some time ago. After looking at FreeBSD's

Re: support for newer run(4) devices

2014-05-17 Thread Stefan Sperling
On Sat, May 17, 2014 at 03:50:46PM +0200, Stefan Sperling wrote: I still have to run this through make release to ensure it won't break the floppies on i386/amd64/sgi. So please don't put into release builds unless you're willing to help with that. If you can run an sgi release build, please

crypto/stack.c reallocarray

2014-05-17 Thread Ted Unangst
Should be a straigtforward conversion. Index: stack.c === RCS file: /cvs/src/lib/libssl/src/crypto/stack/stack.c,v retrieving revision 1.10 diff -u -p -r1.10 stack.c --- stack.c 20 Apr 2014 13:54:10 - 1.10 +++ stack.c

PATCH: ACPI_DEBUG - format fixes

2014-05-17 Thread Fabian Raetz
Hi, the following diff fixes kernel builds with ACPI_DEBUG defined. Not sure if these are the right ones, but at least it compiles again. Cheers, Fabian Index: acpi.c === RCS file: /cvs/src/sys/dev/acpi/acpi.c,v retrieving

PATCH: acpibat - expose capacity as sensor

2014-05-17 Thread Fabian Raetz
Hi, i want to expose capacity (full capacity design) as a sensor like the rest. This sensor will be used in an upcoming diff to upower to expose energy-full-design and capacity properties if this patch gets merged. Both patches together will fix wrong notifications about broken batteries in

Re: run(4) firmware update; please test

2014-05-17 Thread Matthieu Herrb
On Sat, May 17, 2014 at 02:15:46PM +0200, Stefan Sperling wrote: On Fri, May 16, 2014 at 01:30:58PM +0200, Gerhard Roth wrote: He's using a model that requires a firmware-blob different from the one of all other testers (run-rt2870 vs. run-rt3071). That might explain, why he's the only one

Re: support for newer run(4) devices

2014-05-17 Thread Matthieu Herrb
On Sat, May 17, 2014 at 03:50:46PM +0200, Stefan Sperling wrote: This ports many of kevlo's changes in FreeBSD to support newer run(4) devices. Requires the firmware update at http://marc.info/?l=openbsd-techm=140032898325109w=2 I'm posting this version of the diff now for anyone who'd

stack memmove

2014-05-17 Thread Ted Unangst
sunos doesn't have memmove? I guess sunos won't have libressl. Index: stack.c === RCS file: /cvs/src/lib/libssl/src/crypto/stack/stack.c,v retrieving revision 1.11 diff -u -p -r1.11 stack.c --- stack.c 17 May 2014 17:35:04 -

s/REGRESS_DEPENDS/TEST_DEPENDS/ in packages-specs.7

2014-05-17 Thread Fabian Raetz
Index: infrastructure/mk/README.internals === RCS file: /cvs/ports/infrastructure/mk/README.internals,v retrieving revision 1.11 diff -u -p -r1.11 README.internals --- infrastructure/mk/README.internals 11 Feb 2014 10:34:34 -

Re: s/REGRESS_DEPENDS/TEST_DEPENDS/ in packages-specs.7

2014-05-17 Thread Fabian Raetz
On Sat, May 17, 2014 at 07:51:25PM +0200, Fabian Raetz wrote: Index: infrastructure/mk/README.internals === RCS file: /cvs/ports/infrastructure/mk/README.internals,v retrieving revision 1.11 diff -u -p -r1.11 README.internals

Re: Proposal for changes to the event(3) documentation

2014-05-17 Thread Jason McIntyre
On Sat, May 17, 2014 at 12:10:36PM -0600, Ted Bullock wrote: On Sat, May 17, 2014 at 12:08 PM, Ted Bullock tbull...@comlore.com wrote: On Sat, May 17, 2014 at 3:33 AM, Jason McIntyre j...@kerhand.co.uk wrote: On Sat, May 17, 2014 at 03:09:03AM -0600, Ted Bullock wrote: On Fri, May 16, 2014

Re: Proposal for changes to the event(3) documentation

2014-05-17 Thread Ted Bullock
On Sat, May 17, 2014 at 12:08 PM, Ted Bullock tbull...@comlore.com wrote: On Sat, May 17, 2014 at 3:33 AM, Jason McIntyre j...@kerhand.co.uk wrote: On Sat, May 17, 2014 at 03:09:03AM -0600, Ted Bullock wrote: On Fri, May 16, 2014 at 1:10 AM, Nicholas Marriott nicholas.marri...@gmail.com wrote:

Re: buffer overflow in inet_ntop4

2014-05-17 Thread Ted Unangst
On Sat, May 17, 2014 at 11:00, enh wrote: inet_ntop4 incorrectly mixes a user-supplied size with a self-supplied buffer: inet_ntop4(const u_char *src, char *dst, size_t size) ... char tmp[sizeof 255.255.255.255]; ... l = snprintf(tmp, size, fmt, src[0], src[1], src[2], src[3]);

Re: buffer overflow in inet_ntop4

2014-05-17 Thread Stefan Sperling
On Sat, May 17, 2014 at 02:18:22PM -0400, Ted Unangst wrote: On Sat, May 17, 2014 at 11:00, enh wrote: inet_ntop4 incorrectly mixes a user-supplied size with a self-supplied buffer: inet_ntop4(const u_char *src, char *dst, size_t size) ... char tmp[sizeof 255.255.255.255];