Re: FreeBSD_HEAD_amd64_gcc - Build #1144 - Failure

2016-04-04 Thread Li-Wen Hsu
On Mon, Apr 04, 2016 at 00:50:14 +0200, Baptiste Daroussin wrote: > On Mon, Apr 04, 2016 at 04:41:47AM +0800, Li-Wen Hsu wrote: > > I've checked this a little more, I found the return code of > > "installing a installed package" has been changed. > > > > For pkg 1.6.4_1, it returns 0, but 1.7.1 re

Re: FreeBSD_HEAD_amd64_gcc - Build #1144 - Failure

2016-04-04 Thread Baptiste Daroussin
On Mon, Apr 04, 2016 at 06:39:00PM +0800, Li-Wen Hsu wrote: > On Mon, Apr 04, 2016 at 00:50:14 +0200, Baptiste Daroussin wrote: > > On Mon, Apr 04, 2016 at 04:41:47AM +0800, Li-Wen Hsu wrote: > > > I've checked this a little more, I found the return code of > > > "installing a installed package" ha

Re: FreeBSD_HEAD_amd64_gcc - Build #1144 - Failure

2016-04-04 Thread Li-Wen Hsu
On Mon, Apr 04, 2016 at 12:53:16 +0200, Baptiste Daroussin wrote: > On Mon, Apr 04, 2016 at 06:39:00PM +0800, Li-Wen Hsu wrote: > > On Mon, Apr 04, 2016 at 00:50:14 +0200, Baptiste Daroussin wrote: > > > On Mon, Apr 04, 2016 at 04:41:47AM +0800, Li-Wen Hsu wrote: > > > > I've checked this a little

Re: FreeBSD_HEAD_amd64_gcc - Build #1144 - Failure

2016-04-04 Thread Baptiste Daroussin
On Mon, Apr 04, 2016 at 08:25:39PM +0800, Li-Wen Hsu wrote: > On Mon, Apr 04, 2016 at 12:53:16 +0200, Baptiste Daroussin wrote: > > On Mon, Apr 04, 2016 at 06:39:00PM +0800, Li-Wen Hsu wrote: > > > On Mon, Apr 04, 2016 at 00:50:14 +0200, Baptiste Daroussin wrote: > > > > On Mon, Apr 04, 2016 at 04:

Re: FreeBSD_HEAD_amd64_gcc - Build #1144 - Failure

2016-04-04 Thread Li-Wen Hsu
On Mon, Apr 04, 2016 at 14:32:35 +0200, Baptiste Daroussin wrote: > On Mon, Apr 04, 2016 at 08:25:39PM +0800, Li-Wen Hsu wrote: > > On Mon, Apr 04, 2016 at 12:53:16 +0200, Baptiste Daroussin wrote: > > > On Mon, Apr 04, 2016 at 06:39:00PM +0800, Li-Wen Hsu wrote: > > > > On Mon, Apr 04, 2016 at 00:

Re: FreeBSD_HEAD_amd64_gcc - Build #1144 - Failure

2016-04-04 Thread Baptiste Daroussin
On Mon, Apr 04, 2016 at 08:38:03PM +0800, Li-Wen Hsu wrote: > On Mon, Apr 04, 2016 at 14:32:35 +0200, Baptiste Daroussin wrote: > > On Mon, Apr 04, 2016 at 08:25:39PM +0800, Li-Wen Hsu wrote: > > > On Mon, Apr 04, 2016 at 12:53:16 +0200, Baptiste Daroussin wrote: > > > > On Mon, Apr 04, 2016 at 06:

Last call for 2016Q1 quarterly status report submissions

2016-04-04 Thread Benjamin Kaduk
Dear FreeBSD Community, There are just a few days left until the April 7 deadline for submitting entries for the next FreeBSD Quarterly Status Report. Please submit entries for work done in January, February, or March. Status report submissions do not have to be very long. They may be about any

[HEADSUP] new x86 smp topology detection code

2016-04-04 Thread Andriy Gapon
I've just committed new code for detecting SMP (processor and cache) topology on x86 systems. Please be aware. If you get any panics or crashes that look like they might be caused by this change please send a copy of a report to me. Another thing to watch is kern.sched.topology_spec. Please ch

EGL driver for vt?

2016-04-04 Thread Lundberg, Johannes
Hi Would anyone be interested in an Mesa/EGL driver for vt? If we had this we could run wayland/egl-based compositors with llvmpipe on platforms without GPU support similar to X+scfb driver. (if my understanding of the graphics stack if correct..) If similar to the (now deprecated) Linux framebu

Re: accessing a PCIe register from userspace through kmem or other ways ?

2016-04-04 Thread John Baldwin
On Friday, April 01, 2016 08:04:58 PM Konstantin Belousov wrote: > On Fri, Apr 01, 2016 at 12:48:24PM -0400, Ryan Stone wrote: > > That is actually a really good question. I know that with some recent > > BIOSes if I enabled allocating 64-bit addresses to BARs, the BAR would > > actually be mapped

Re: accessing a PCIe register from userspace through kmem or other ways ?

2016-04-04 Thread Ryan Stone
On Mon, Apr 4, 2016 at 6:45 PM, John Baldwin wrote: > I suspect Ryan might be referring to BARs outside of the DMAP which we > only populate to Maxmem IIRC. /dev/mem should work for those. > Unfortunately I no longer have access to the systems so I can't really confirm. I had a debug tool that

Re: accessing a PCIe register from userspace through kmem or other ways ?

2016-04-04 Thread John Baldwin
On Monday, April 04, 2016 08:58:47 PM Ryan Stone wrote: > On Mon, Apr 4, 2016 at 6:45 PM, John Baldwin wrote: > > > I suspect Ryan might be referring to BARs outside of the DMAP which we > > only populate to Maxmem IIRC. /dev/mem should work for those. > > > > Unfortunately I no longer have acc

D3702: add support for Bluetooth Magic Mouse

2016-04-04 Thread Warren Block
Is anyone working on Bluetooth stuff? https://reviews.freebsd.org/D3702 adds support for the Apple Magic Mouse, and has been tested and reported working: https://lists.freebsd.org/pipermail/freebsd-bluetooth/2016-April/002053.html Could someone please review and commit this? Thanks!

Re: accessing a PCIe register from userspace through kmem or other ways ?

2016-04-04 Thread Konstantin Belousov
On Mon, Apr 04, 2016 at 09:02:49PM -0700, John Baldwin wrote: > kib@ fixed /dev/mem to handle addresses beyond the direct map limit to use > temporary mappings instead of failing with EFAULT in 277051 which was only > committed to HEAD last January, so well after 8.2. The mmap(2) interface to /dev

Re: accessing a PCIe register from userspace through kmem or other ways ?

2016-04-04 Thread Konstantin Belousov
On Mon, Apr 04, 2016 at 03:45:07PM -0700, John Baldwin wrote: > However, another question is how to deal with systems that do bus address > translation (like the arm64 ThunderX boxes) where the values in the PCI > BAR are not CPU physical addresses. To do this properly we may need some > sort of b

Re: CURRENT slow and shaky network stability

2016-04-04 Thread O. Hartmann
On Sat, 02 Apr 2016 16:14:57 -0700 Cy Schubert wrote: > In message <20160402231955.41b05526.ohart...@zedat.fu-berlin.de>, "O. > Hartmann" > writes: > > --Sig_/eJJPtbrEuK1nN2zIpc7BmVr > > Content-Type: text/plain; charset=US-ASCII > > Content-Transfer-Encoding: quoted-printable > > > > Am Sat,

Re: CURRENT slow and shaky network stability

2016-04-04 Thread Cy Schubert
In message <20160405082047.670d7...@freyja.zeit4.iv.bundesimmobilien.de>, "O. H artmann" writes: > On Sat, 02 Apr 2016 16:14:57 -0700 > Cy Schubert wrote: > > > In message <20160402231955.41b05526.ohart...@zedat.fu-berlin.de>, "O. > > Hartmann" > > writes: > > > --Sig_/eJJPtbrEuK1nN2zIpc7BmVr