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

2016-10-13 Thread Kevin Lo
On Fri, Oct 14, 2016 at 03:03:41AM +0300, Andriy Voskoboinyk wrote: > > Wed, 12 Oct 2016 07:34:15 +0300 було написано Kevin Lo : > > Thanks for testing! (I have got another one to simplify the process) > Can you approve that current tree (master) works without any (new) > problems? Sure. For

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

2016-10-13 Thread Andriy Voskoboinyk
Wed, 12 Oct 2016 07:34:15 +0300 було написано Kevin Lo : Thanks for testing! (I have got another one to simplify the process) Can you approve that current tree (master) works without any (new) problems? P.S. Known issue (present in the current driver too): - the card ACKs only some frames th

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

2016-10-11 Thread Kevin Lo
I tried to use https://github.com/s3erios/rtwn/tree/pci_modified, still no luck. BTW, there's a compilation error: http://pastebin.com/hCFfYVSj To ensure that the adapter is not faulty, I tested with the snapshots image (FreeBSD-12.0-CURRENT-amd64-20160829-r305028-memstick.img), rtwn(4) works fi

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

2016-10-11 Thread Adrian Chadd
Hiya, So uhm - normal rtwn works fine, but andriy's merged version doesn't? -a ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebs

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

2016-10-11 Thread Andriy Voskoboinyk
Tue, 11 Oct 2016 04:27:02 +0300 було написано Kevin Lo : I have created 'pci_modified' branch to speed-up the process (RTL881*AU will not work with it for now); right now it contains (mostly) unmodified initialization path from rtwn(4) driver. If this version will work, I will revert some 'RT

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

2016-10-10 Thread Kevin Lo
On Sat, Oct 08, 2016 at 02:18:54AM +0300, Andriy Voskoboinyk wrote: > > Mon, 03 Oct 2016 03:55:23 +0300 було написано Kevin Lo : > > Hi! Hi Andriy, > Can you refresh the tree and retest it (dev.rtwn.0.debug=0x829f) ? I refreshed the tree and retested it, unfortunately it's still the same. He

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

2016-10-07 Thread Andriy Voskoboinyk
Mon, 03 Oct 2016 03:55:23 +0300 було написано Kevin Lo : Hi! Can you refresh the tree and retest it (dev.rtwn.0.debug=0x829f) ? P.S. If Rx is still broken (status is always 0) try to execute 'ifconfig wlan0 promisc' On Sun, Oct 02, 2016 at 10:15:49AM -0700, Adrian Chadd wrote: hi, Hi Adri

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

2016-10-02 Thread Kevin Lo
On Sun, Oct 02, 2016 at 10:15:49AM -0700, Adrian Chadd wrote: > > hi, Hi Adrian, > can you turn on debugging? Do you see RX frames? No Rx frames. The log is pretty much the same one I sent on the list: https://lists.freebsd.org/pipermail/freebsd-wireless/2016-September/007093.html > -a Thank

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

2016-10-02 Thread Adrian Chadd
hi, can you turn on debugging? Do you see RX frames? -a On 1 October 2016 at 08:09, Kevin Lo wrote: > Strange, rtwn(4) stops working. I tried to scan for the available network, > but it just returns empty results. > > On Fri, Sep 23, 2016 at 02:44:13PM +0300, Andriy Voskoboinyk wrote: >> >>

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

2016-10-01 Thread Kevin Lo
Strange, rtwn(4) stops working. I tried to scan for the available network, but it just returns empty results. On Fri, Sep 23, 2016 at 02:44:13PM +0300, Andriy Voskoboinyk wrote: > > Fri, 23 Sep 2016 10:18:30 +0300 було написано Kevin Lo : > > Few more questions: > 1) does it work with h/w encry

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

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

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

2016-09-22 Thread Andriy Voskoboinyk
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/f78d51b6ed8590e3aeb65fbf616aa767034a89f5 (currently I'm reviewing PCI-specific code to see if there are any additional issues - e.g.

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

2016-09-22 Thread Kevin Lo
On Thu, Sep 22, 2016 at 01:54:21PM +0300, Andriy Voskoboinyk wrote: > > Thu, 22 Sep 2016 12:24:42 +0300 було написано Kevin Lo : > > Hi, > > So, the driver was fully tested. Thanks! > Can you set dev.rtwn.0.debug=0x829f for RTL8188CE to see how big > the problem is? Sure. Here you go https://p

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

2016-09-22 Thread Andriy Voskoboinyk
Thu, 22 Sep 2016 12:24:42 +0300 було написано Kevin Lo : Hi, So, the driver was fully tested. Thanks! Can you set dev.rtwn.0.debug=0x829f for RTL8188CE to see how big the problem is? Hi Andriy, First of all, THANK YOU! You're doing amazing work! Second, I've done some testing on the followin

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

2016-09-22 Thread Kevin Lo
Hi Andriy, First of all, THANK YOU! You're doing amazing work! Second, I've done some testing on the following devices, downloading FreeBSD-12.0-CURRENT-amd64-20160809-r303880-disc1.iso from ftp.freebsd.org: - ASUS USB-N10 NANO (RTL8188CUS): rtwn0: on usbus0 rtwn0: MAC/BB RTL8188CUS, RF 60

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

2016-09-19 Thread Andriy Voskoboinyk
hi, I'll try it out tonight! Is the rtwn repo still "ok" to try as a standalone thing? Yes, sys/{dev/rtwn,modules} subtree is the same. The usbdevs patch is fine standalone - would you like to just commit this in advance? Done in r305991. -adrian On 19 September 2016 at 06:26, Andr

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

2016-09-19 Thread Andriy Voskoboinyk
Mon, 19 Sep 2016 20:51:16 +0300 було написано Hans Petter Selasky : On 09/19/16 19:43, Adrian Chadd wrote: hi, I'll try it out tonight! Is the rtwn repo still "ok" to try as a standalone thing? The usbdevs patch is fine standalone - would you like to just commit this in advance? Possibly

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

2016-09-19 Thread Hans Petter Selasky
On 09/19/16 19:43, Adrian Chadd wrote: hi, I'll try it out tonight! Is the rtwn repo still "ok" to try as a standalone thing? The usbdevs patch is fine standalone - would you like to just commit this in advance? Possibly you should also rebuild /etc/devd/usb.conf to automatically load the c

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

2016-09-19 Thread Adrian Chadd
hi, I'll try it out tonight! Is the rtwn repo still "ok" to try as a standalone thing? The usbdevs patch is fine standalone - would you like to just commit this in advance? -adrian On 19 September 2016 at 06:26, Andriy Voskoboinyk wrote: > Thu, 01 Sep 2016 19:29:03 +0300 було написано Andr

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

2016-09-19 Thread Andriy Voskoboinyk
Thu, 01 Sep 2016 19:29:03 +0300 було написано Andriy Voskoboinyk : Now it resides on https://github.com/s3erios/freebsd-rtwn (integrated into src tree, so it can be built with 'make buildkernel' / 'make buildworld'). This the last stage; once all reported issues will be resolved, I'm going