Re: should aarch64 cross-build work at amd64?

2016-09-23 Thread Glen Barber
On Sat, Sep 24, 2016 at 01:56:54AM +0300, Boris Samorodov wrote: > 24.09.2016 01:19, Glen Barber пишет: > > On Sat, Sep 24, 2016 at 12:54:05AM +0300, Boris Samorodov wrote: > >> 24.09.2016 00:44, Boris Samorodov пишет: > >>> 24.09.2016 00:39, Glen Barber пишет: > On Sat, Sep 24, 2016 at 12:35:

Re: should aarch64 cross-build work at amd64?

2016-09-23 Thread Boris Samorodov
24.09.2016 01:19, Glen Barber пишет: > On Sat, Sep 24, 2016 at 12:54:05AM +0300, Boris Samorodov wrote: >> 24.09.2016 00:44, Boris Samorodov пишет: >>> 24.09.2016 00:39, Glen Barber пишет: On Sat, Sep 24, 2016 at 12:35:30AM +0300, Boris Samorodov wrote: > make[1]: /poudriere/jails/HEAD-aar

Re: should aarch64 cross-build work at amd64?

2016-09-23 Thread Glen Barber
On Sat, Sep 24, 2016 at 12:54:05AM +0300, Boris Samorodov wrote: > 24.09.2016 00:44, Boris Samorodov пишет: > > 24.09.2016 00:39, Glen Barber пишет: > >> On Sat, Sep 24, 2016 at 12:35:30AM +0300, Boris Samorodov wrote: > >>> make[1]: /poudriere/jails/HEAD-aarch64/usr/src/Makefile.inc1 line 177: > >

Re: should aarch64 cross-build work at amd64?

2016-09-23 Thread Boris Samorodov
24.09.2016 00:44, Boris Samorodov пишет: > 24.09.2016 00:39, Glen Barber пишет: >> On Sat, Sep 24, 2016 at 12:35:30AM +0300, Boris Samorodov wrote: >>> make[1]: /poudriere/jails/HEAD-aarch64/usr/src/Makefile.inc1 line 177: >>> In-tree binutils does not support the aarch64 architecture. Install the

Re: should aarch64 cross-build work at amd64?

2016-09-23 Thread Boris Samorodov
24.09.2016 00:39, Glen Barber пишет: > On Sat, Sep 24, 2016 at 12:35:30AM +0300, Boris Samorodov wrote: >> make[1]: /poudriere/jails/HEAD-aarch64/usr/src/Makefile.inc1 line 177: >> In-tree binutils does not support the aarch64 architecture. Install the >> aarch64-binutils port or package or set CRO

Re: should aarch64 cross-build work at amd64?

2016-09-23 Thread Glen Barber
On Sat, Sep 24, 2016 at 12:35:30AM +0300, Boris Samorodov wrote: > make[1]: /poudriere/jails/HEAD-aarch64/usr/src/Makefile.inc1 line 177: > In-tree binutils does not support the aarch64 architecture. Install the > aarch64-binutils port or package or set CROSS_BINUTILS_PREFIX. These lines are relev

should aarch64 cross-build work at amd64?

2016-09-23 Thread Boris Samorodov
Hi All! I've just created an armv6 jail by poudriere at FreeBSD-current-amd64. It works fine: --- % poudriere jail -l JAILNAME VERSION ARCH METHOD TIMESTAMP PATH HEAD-armv6 12.0-CURRENT r306267 arm.armv6 svn+https2016-09-23 17:38:10 /poudriere/jails/HEAD-armv6 ---

Re: Question about wmb() and rmb() and task switching

2016-09-23 Thread Konstantin Belousov
On Fri, Sep 23, 2016 at 01:46:15PM +0200, Hans Petter Selasky wrote: > Hi, > > Does use of wmb() and rmb() for amd64 as defined in > sys/amd64/include/atomic.h required use of critical_enter()/critical_exit(). > > I was looking at the code in sys/amd64/amd64/cpu_switch.S which switches > betwee

Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing

2016-09-23 Thread Andriy Voskoboinyk
Fri, 23 Sep 2016 10:18:30 +0300 було написано Kevin Lo : Few more questions: 1) does it work with h/w encryption support? (enabled by default) (if 'yes' - I will remove 'hardware crypto enabled' warning). 2) is there rate control support? (wlandebug -i wlan0 rate ; then transmit something - if it

Question about wmb() and rmb() and task switching

2016-09-23 Thread Hans Petter Selasky
Hi, Does use of wmb() and rmb() for amd64 as defined in sys/amd64/include/atomic.h required use of critical_enter()/critical_exit(). I was looking at the code in sys/amd64/amd64/cpu_switch.S which switches between threads and I don't see any "sfence" instructions in there. Given the followi

Re: head@r305865: kernel panic after cuse4bsd load.

2016-09-23 Thread Sergey V. Dyatko
On Fri, 23 Sep 2016 09:47:52 +0200 Hans Petter Selasky wrote: > On 09/23/16 09:34, Hans Petter Selasky wrote: > > On 09/23/16 08:33, Sergey V. Dyatko wrote: > >> Hi, > >> > >> subj. > >> > >> WTR: > >> 1/ kldload cuse > >> 2/ kldload cuse4bsd > >> > >> expected (by me) behavior: 'Cuse4BSD: Pl

Re: head@r305865: kernel panic after cuse4bsd load.

2016-09-23 Thread Hans Petter Selasky
On 09/23/16 09:34, Hans Petter Selasky wrote: On 09/23/16 08:33, Sergey V. Dyatko wrote: Hi, subj. WTR: 1/ kldload cuse 2/ kldload cuse4bsd expected (by me) behavior: 'Cuse4BSD: Please exit all /dev/cuse instances and processes which have used this device.' message and exit, not kernel panic

Re: head@r305865: kernel panic after cuse4bsd load.

2016-09-23 Thread Hans Petter Selasky
On 09/23/16 08:33, Sergey V. Dyatko wrote: Hi, subj. WTR: 1/ kldload cuse 2/ kldload cuse4bsd expected (by me) behavior: 'Cuse4BSD: Please exit all /dev/cuse instances and processes which have used this device.' message and exit, not kernel panic HI, You should only load one of them. make

Re: urtwn(4) / rtwn(4) drivers are merged - call for review / testing

2016-09-23 Thread Kevin Lo
It works for me, thanks :) Kevin On Fri, Sep 23, 2016 at 09:08:15AM +0300, Andriy Voskoboinyk wrote: > > Fri, 23 Sep 2016 04:58:40 +0300 було написано Kevin Lo : > > Thanks for the log file, > > Tx 'device timeouts' should be fixed in > https://github.com/s3erios/rtwn/commit/f78d51b6ed