Re: ports.7: double distfile fetch size: 20 -> 40

On Wed, Dec 27, 2017 at 04:12:49AM +0100, Marc Espie wrote: > On Tue, Dec 26, 2017 at 05:51:51PM +0100, Jeremie Courreges-Anglas wrote: > > On Tue, Dec 26 2017, Scott Cheloha wrote: > > > Hey, > > > > > > I just did a full ports fetch and I pulled down at least 40GB: > > >

Re: ports.7: double distfile fetch size: 20 -> 40

On Tue, Dec 26, 2017 at 05:51:51PM +0100, Jeremie Courreges-Anglas wrote: > On Tue, Dec 26 2017, Scott Cheloha wrote: > > Hey, > > > > I just did a full ports fetch and I pulled down at least 40GB: > > > > $ du -h /usr/ports/distfiles | tail -n 1 > > 40.5G

Re: armv7 / A33 clock and pinctrl bindings

On Wed, Dec 27, 2017 at 09:37:12AM +0800, Kevin Lo wrote: > On Tue, Dec 26, 2017 at 06:20:59PM +0100, Mark Kettenis wrote: > > > > > Date: Tue, 26 Dec 2017 22:51:38 +0800 > > > From: Kevin Lo > > > > > > > Shouldn't be too difficult to add support for that one to axppmic(4).

Re: armv7 / A33 clock and pinctrl bindings

On Tue, Dec 26, 2017 at 06:20:59PM +0100, Mark Kettenis wrote: > > > Date: Tue, 26 Dec 2017 22:51:38 +0800 > > From: Kevin Lo > > > > > Shouldn't be too difficult to add support for that one to axppmic(4). > > > Do you want me to create a diff for you to test? > > > > That'd

Re: ports.7: double distfile fetch size: 20 -> 40

On 2017/12/26 08:18, Scott Cheloha wrote: > Hey, > > I just did a full ports fetch and I pulled down at least 40GB: > > $ du -h /usr/ports/distfiles | tail -n 1 > 40.5G /usr/ports/distfiles > > A future fetcher will probably appreciate an up-to-date quote. > > If anyone has recent numbers for

Unused variable in gomoku

Hi Everyone, I recently noticed that there is an unused variable in gomoku.h. I have included a diff that removes the unused variable, and have verified that gomoku compiles cleanly afterwards. I have performed a search for this header file within the source tree, and it looks like gomoku is the

pf state key linking

Hi, The functions to link the pf state keys always confused me a bit. I think the new naming and code of the functions is more consistent. ok? bluhm Index: kern/uipc_mbuf.c === RCS file:

Re: llvm: fix i386 floating point compiler bug

On Mon, Dec 25, 2017 at 12:52:56AM +0100, Patrick Wildt wrote: > Hi, > > gerhard@ found a bug in LLVM's i386 code. He noticed that some floating > point instructions were "optimized" and thus reordered between other FP > instructions that changed floating point modes, so that those reordered >

Re: Implement OF_getpropint64

On Tue, Dec 26, 2017 at 05:18:37PM +0100, Mark Kettenis wrote: > A function to easily extract properties that are represented as a > 64-bit integer. I'll be needing this in at least two little projects > that I'm working on. > > ok? ok patrick@ > > P.S. Those two little projects are EFI

Re: armv7 / A33 clock and pinctrl bindings

> Date: Tue, 26 Dec 2017 22:51:38 +0800 > From: Kevin Lo > > > Shouldn't be too difficult to add support for that one to axppmic(4). > > Do you want me to create a diff for you to test? > > That'd be great, thanks. Testing is easier than writing code :) Here's a diff.

Re: Implement OF_getpropint64

On Tue, Dec 26 2017, Mark Kettenis wrote: > A function to easily extract properties that are represented as a > 64-bit integer. I'll be needing this in at least two little projects > that I'm working on. > > ok? ok jca@ -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293

Re: ports.7: double distfile fetch size: 20 -> 40

On Tue, Dec 26 2017, Scott Cheloha wrote: > Hey, > > I just did a full ports fetch and I pulled down at least 40GB: > > $ du -h /usr/ports/distfiles | tail -n 1 > 40.5G /usr/ports/distfiles bulk(8) already documents "50GB for distfiles and 50GB for packages". -- jca |

Re: ksh: fix warnings produced by -Wshadow

On Tue, Dec 26 2017, "Todd C. Miller" wrote: > I was investigating what is needed to add WARNINGS=Yes to ksh's > Makefile. There are a lot of shadowed variable warnings. Some are > easy to fix, others are due to poorly chosen global variable names. > Specifically, "options"

Implement OF_getpropint64

A function to easily extract properties that are represented as a 64-bit integer. I'll be needing this in at least two little projects that I'm working on. ok? P.S. Those two little projects are EFI Runtime Services and DVFS support. Index: dev/ofw/fdt.c

Re: bug in inteldrm on braswell

On Tue, Dec 26, 2017 at 02:24:04PM +0100, Mark Kettenis wrote: > I've committed the first bit now. Let me know if you manage to > trigger the WARN_ON before the 2nd bit. I am running now since Thursday a kernel with only the first bit and had no Problems so far. (And I stressed this notebook a

Re: ksh: replace test_stat() with stat()

On Tue, Dec 26 2017, "Todd C. Miller" wrote: > We removed the hack for /dev/fd support on systems without it a > long time ago. Update the comments and replace test_stat() calls > with stat() since test_stat() now just calls stat() directly. Also > rename the "mode"

Re: llvm: fix i386 floating point compiler bug

> Date: Mon, 25 Dec 2017 00:52:56 +0100 > From: Patrick Wildt > > Hi, > > gerhard@ found a bug in LLVM's i386 code. He noticed that some floating > point instructions were "optimized" and thus reordered between other FP > instructions that changed floating point modes, so

Re: armv7 / A33 clock and pinctrl bindings

On Tue, Dec 26, 2017 at 03:30:17PM +0100, Mark Kettenis wrote: > > Date: Tue, 26 Dec 2017 17:16:47 +0800 > > From: Kevin Lo > > > > On Tue, Dec 26, 2017 at 09:52:36AM +0100, Mark Kettenis wrote: > > > > Date: Tue, 26 Dec 2017 15:59:12 +0800 > > > > From: Kevin Lo

Re: armv7 / A33 clock and pinctrl bindings

> Date: Tue, 26 Dec 2017 17:16:47 +0800 > From: Kevin Lo > > On Tue, Dec 26, 2017 at 09:52:36AM +0100, Mark Kettenis wrote: > > > Date: Tue, 26 Dec 2017 15:59:12 +0800 > > > From: Kevin Lo > > > > > > On Tue, Dec 26, 2017 at 05:12:39PM +1100, Jonathan Gray

ports.7: double distfile fetch size: 20 -> 40

Hey, I just did a full ports fetch and I pulled down at least 40GB: $ du -h /usr/ports/distfiles | tail -n 1 40.5G /usr/ports/distfiles A future fetcher will probably appreciate an up-to-date quote. If anyone has recent numbers for the total size of the package output and the size of the

Re: mktemp: Clarify error message

On Tue, Dec 26, 2017 at 12:31:02AM +0100, Klemens Nanni wrote: > On Mon, Dec 25, 2017 at 03:57:00PM -0700, Theo de Raadt wrote: > > I think this is a silly solution, and the documentation is clear > > enough. > The manual page certainly is clear enough but the current error message > is logically

ksh: fix warnings produced by -Wshadow

I was investigating what is needed to add WARNINGS=Yes to ksh's Makefile. There are a lot of shadowed variable warnings. Some are easy to fix, others are due to poorly chosen global variable names. Specifically, "options" and "path". I've renamed "options" to "sh_options" since it holds the

ksh: replace test_stat() with stat()

We removed the hack for /dev/fd support on systems without it a long time ago. Update the comments and replace test_stat() calls with stat() since test_stat() now just calls stat() directly. Also rename the "mode" parameter to "amode" in test_eaccess() to match access(2) and make it clear that

Re: bug in inteldrm on braswell

> Date: Thu, 21 Dec 2017 15:15:35 +0100 > From: Martin Ziemer > > > Sorry. I want to test this myself before I commit it, but I keep > > getting distracted with other stuff. > No Sorry. I think its cool, you find the time to test everything > yourself. (Everybody knows the

Re: mktemp: Clarify error message

On Tue, Dec 26, 2017 at 08:25:50AM +0100, Otto Moerbeek wrote: > > This reminds me of the old IRIX compiler, that would cite complete > parapgraphs of the C standard in error mesasges. Of course logically > it was all correct, but it lead to long and unreadable error messages > that filled up

Re: armv7 / A33 clock and pinctrl bindings

On Tue, Dec 26, 2017 at 09:52:36AM +0100, Mark Kettenis wrote: > > Date: Tue, 26 Dec 2017 15:59:12 +0800 > > From: Kevin Lo > > > > On Tue, Dec 26, 2017 at 05:12:39PM +1100, Jonathan Gray wrote: > > > > > > On Tue, Dec 26, 2017 at 01:15:35PM +0800, Kevin Lo wrote: > > > > The

Re: armv7 / A33 clock and pinctrl bindings

> Date: Tue, 26 Dec 2017 15:59:12 +0800 > From: Kevin Lo > > On Tue, Dec 26, 2017 at 05:12:39PM +1100, Jonathan Gray wrote: > > > > On Tue, Dec 26, 2017 at 01:15:35PM +0800, Kevin Lo wrote: > > > The diff below adds support for the "next-generation" clock and pinctrl > > >

Re: malloc cleanup and small optimizations

Been running a base linked against this on amd64 since the 24th. No new problems observed. If there's anything specific I can test do tell.

Re: armv7 / A33 clock and pinctrl bindings

On Tue, Dec 26, 2017 at 05:12:39PM +1100, Jonathan Gray wrote: > > On Tue, Dec 26, 2017 at 01:15:35PM +0800, Kevin Lo wrote: > > The diff below adds support for the "next-generation" clock and pinctrl > > bindings for the Allwinner A33. > > > > Tested on my Banana Pi M2 Magic. dmesg: