Re: urtwn(4) / rtwn(4) drivers are merged - call for testing (Was: RTL8812AU / RTL8821AU driver)

Hi! > On -current rtwn has been attached to same chip. I've rebuild to FreeBSD udog.opsec.eu 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r307767: Sat Oct 22 15:31:03 CEST 2016 p...@udog.opsec.eu:/usr/obj/usr/src/sys/GENERIC amd64 and still: none2@pci0:3:0:0: class=0x028000

Re: urtwn(4) / rtwn(4) drivers are merged - call for testing (Was: RTL8812AU / RTL8821AU driver)

Hi! > > rtwn(4), urtwn(4) and urtwm (from previous emails) drivers were merged > > into a > > single rtwn driver (plus rtwn_usb / rtwn_pci device glue); the code is > > available on https://github.com/s3erios/rtwn repository. Among bugfixes / > > code deduplication, there some new features too: >

Re: urtwn(4) / rtwn(4) drivers are merged - call for testing (Was: RTL8812AU / RTL8821AU driver)

On, Thu Sep 01, 2016, Andriy Voskoboinyk wrote: > Hi everyone, > > rtwn(4), urtwn(4) and urtwm (from previous emails) drivers were merged > into a > single rtwn driver (plus rtwn_usb / rtwn_pci device glue); the code is > available on https://github.com/s3erios/rtwn repository. Among bugfixes / >

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

On Fri, Oct 14, 2016 at 03:03:41AM +0300, Andriy Voskoboinyk wrote: > > Wed, 12 Oct 2016 07:34:15 +0300 було написано Kevin Lo <ke...@freebsd.org>: > > Thanks for testing! (I have got another one to simplify the process) > Can you approve that current tree (master) w

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

Wed, 12 Oct 2016 07:34:15 +0300 було написано Kevin Lo <ke...@freebsd.org>: 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 car

Re: [request for testing] isl, cyapa on chromebooks

On 12/10/2016 09:21, Andriy Gapon wrote: > On 12/10/2016 07:03, Warner Losh wrote: >> I think I can do the device table mechanism if Andriy isn't up for it. > > That would be great, thank you! > Meanwhile, I've added a "stop-gap" version of 'chromebook_platform' driver here:

Re: [request for testing] isl, cyapa on chromebooks

On 12/10/2016 07:03, Warner Losh wrote: > I think I can do the device table mechanism if Andriy isn't up for it. That would be great, thank you! -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list

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

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

Re: [request for testing] isl, cyapa on chromebooks

On Mon, Oct 10, 2016 at 12:45 PM, Michael Gmelin wrote: > > >> On 10 Oct 2016, at 20:27, Matthias Apitz wrote: >> >>> El día Monday, October 10, 2016 a las 09:26:26AM -0600, Warner Losh >>> escribió: >>> >>> I see no reason not to start the table right away

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

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

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

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

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

>> >> (currently I'm reviewing PCI-specific code to see if there are any > >> >> >> additional > >> >> >> issues - e.g., there are no Rx events in the log file). > >> >> >> > >> >> >> > On Thu, Sep 22, 2016 at 01:54:21PM +0300,

Re: [request for testing] isl, cyapa on chromebooks

On 10/10/2016 21:45, Michael Gmelin wrote: > I see three tasks here: - Andriy finishes his change, moving things from > smbus to iicbus, adding some workaround to keep the user experience like it > is - Someone else implements the device table mechanism for auto detection - > Someone else ports

Re: [request for testing] isl, cyapa on chromebooks

> On 10 Oct 2016, at 20:27, Matthias Apitz wrote: > >> El día Monday, October 10, 2016 a las 09:26:26AM -0600, Warner Losh escribió: >> >> I see no reason not to start the table right away based on >> smbios.sys.product and other criteria. I don't think we need all the >>

Re: [request for testing] isl, cyapa on chromebooks

El día Monday, October 10, 2016 a las 09:26:26AM -0600, Warner Losh escribió: > I see no reason not to start the table right away based on > smbios.sys.product and other criteria. I don't think we need all the > matches that Linux uses, but we can expand the table if we find it so. > Why have a

Re: [request for testing] isl, cyapa on chromebooks

On 10/10/2016 18:26, Warner Losh wrote: > I see no reason not to start the table right away based on > smbios.sys.product and other criteria. I don't think we need all the > matches that Linux uses, but we can expand the table if we find it so. > Why have a stop gap that's a table that we kludge

Re: [request for testing] isl, cyapa on chromebooks

I see no reason not to start the table right away based on smbios.sys.product and other criteria. I don't think we need all the matches that Linux uses, but we can expand the table if we find it so. Why have a stop gap that's a table that we kludge together when the real table is of comparable

Re: [request for testing] isl, cyapa on chromebooks

On Mon, 10 Oct 2016 14:35:22 +0300 Andriy Gapon wrote: > On 09/10/2016 23:22, Warner Losh wrote: > > There seems to be enough information present in the smbios data to > > know what devices are at what addresses. Perhaps we should use it as > > much as possible in well

Re: [request for testing] isl, cyapa on chromebooks

On 09/10/2016 23:22, Warner Losh wrote: > There seems to be enough information present in the smbios data to > know what devices are at what addresses. Perhaps we should use it as > much as possible in well controlled situations to move this knowledge > into the OS. So, I was thinking about maybe

Re: [request for testing] isl, cyapa on chromebooks

On Sun, Oct 9, 2016 at 12:54 AM, Matthias Apitz wrote: > El día Sunday, October 09, 2016 a las 01:53:24AM +0200, Michael Gmelin > escribió: > >> Would I maybe make sense to have man pages for specific laptops (instead >> of the "FreeBSD Laptop" page, blogs on the internet and

Re: [request for testing] isl, cyapa on chromebooks

Thanks. Changing device.hints to iicbus14 iicbus15 makes cyapa(4) attaching and moused working fine. I will later install xorg into this memstick. matthias -- Sent from my Ubuntu phone http://www.unixarea.de/ ___ freebsd-current@freebsd.org

Re: [request for testing] isl, cyapa on chromebooks

El día Sunday, October 09, 2016 a las 01:53:24AM +0200, Michael Gmelin escribió: > Would I maybe make sense to have man pages for specific laptops (instead > of the "FreeBSD Laptop" page, blogs on the internet and Wiki pages). > > Just thinking that after this change, people will need to know

Re: [request for testing] isl, cyapa on chromebooks

On 09/10/2016 09:36, Matthias Apitz wrote: > El día Saturday, October 08, 2016 a las 10:17:07PM +0300, Andriy Gapon > escribió: > >> On 08/10/2016 21:07, Matthias Apitz wrote: >>> I have now produced a memstick with (unpatched) r306769 of October 6. It >>> boots >>> fine in my Acer C720

Re: [request for testing] isl, cyapa on chromebooks

El día Saturday, October 08, 2016 a las 10:17:07PM +0300, Andriy Gapon escribió: > On 08/10/2016 21:07, Matthias Apitz wrote: > > I have now produced a memstick with (unpatched) r306769 of October 6. It > > boots > > fine in my Acer C720 Chromebook and the moused is working fine with the > >

Re: [request for testing] isl, cyapa on chromebooks

On Sat, 8 Oct 2016 15:54:27 -0600 Warner Losh wrote: > Speaking of Chromebooks, what's the best way to put FreeBSD onto one? > > Warner > > Depends on the Chromebook in question, when porting the drivers for the c720, I wrote a blog post about it (quite a while ago):

Re: [request for testing] isl, cyapa on chromebooks

On Saturday, 8 October 2016 23:54:27 CEST, Warner Losh wrote: Speaking of Chromebooks, what's the best way to put FreeBSD onto one? Set it to developer mode or Legacy boot, boot and install 11-C or 12-C from USB. matthias -- Sent from my Ubuntu phone

Re: [request for testing] isl, cyapa on chromebooks

Speaking of Chromebooks, what's the best way to put FreeBSD onto one? Warner On Sat, Oct 8, 2016 at 1:17 PM, Andriy Gapon wrote: > On 08/10/2016 21:07, Matthias Apitz wrote: >> I have now produced a memstick with (unpatched) r306769 of October 6. It >> boots >> fine in my

Re: [request for testing] isl, cyapa on chromebooks

On 08/10/2016 21:07, Matthias Apitz wrote: > I have now produced a memstick with (unpatched) r306769 of October 6. It boots > fine in my Acer C720 Chromebook and the moused is working fine with the > cyapa(4) driver. I will apply tomorrow the above v4 patch or is there > anything newer? And will

Re: [request for testing] isl, cyapa on chromebooks

El día Thursday, October 06, 2016 a las 11:12:27AM +0300, Andriy Gapon escribió: > On 06/10/2016 11:10, Michael Gmelin wrote: > > > > > >> On 06 Oct 2016, at 09:48, Andriy Gapon <a...@freebsd.org> wrote: > >> > >>> On 06/10/2016 08:37, An

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

16 12:24:42 +0300 було написано Kevin Lo >> >> >> <ke...@freebsd.org>: >> >> >> >> >> >> Hi, >> >> >> >> >> >> So, the driver was fully tested. Thanks! >> >> >> Can you set dev.rtwn.0.d

Re: [request for testing] isl, cyapa on chromebooks

On Thu, 6 Oct 2016 11:12:27 +0300 Andriy Gapon <a...@freebsd.org> wrote: > On 06/10/2016 11:10, Michael Gmelin wrote: > > > > > >> On 06 Oct 2016, at 09:48, Andriy Gapon <a...@freebsd.org> wrote: > >> > >>> On 06/10/2016 08:

Re: [request for testing] isl, cyapa on chromebooks

On 06/10/2016 11:10, Michael Gmelin wrote: > > >> On 06 Oct 2016, at 09:48, Andriy Gapon <a...@freebsd.org> wrote: >> >>> On 06/10/2016 08:37, Andriy Gapon wrote: >>> The more testing the better! >> >> Based on Michael's results I've uploaded

Re: [request for testing] isl, cyapa on chromebooks

> On 06 Oct 2016, at 09:48, Andriy Gapon <a...@freebsd.org> wrote: > >> On 06/10/2016 08:37, Andriy Gapon wrote: >> The more testing the better! > > Based on Michael's results I've uploaded a new version: > https://people.freebsd.org/~avg/ig4-i2c.v4.diff >

Re: [request for testing] isl, cyapa on chromebooks

On 06/10/2016 08:37, Andriy Gapon wrote: > The more testing the better! Based on Michael's results I've uploaded a new version: https://people.freebsd.org/~avg/ig4-i2c.v4.diff -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list ht

Re: [request for testing] isl, cyapa on chromebooks

On 06/10/2016 10:25, Andriy Gapon wrote: > On 06/10/2016 10:08, Michael Gmelin wrote: >> >> >>> On 05 Oct 2016, at 15:01, Andriy Gapon wrote: >>> On 05/10/2016 14:19, Michael Gmelin wrote: ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe

Re: [request for testing] isl, cyapa on chromebooks

on top of the previous patch. >> > > Isl attaches cleanly on iicbus1 now, but it doesn't appear to function (all > inputs, like dev.isl.ir etc, are stuck at 0). At least some progress... Anything interesting in logs? Oh! and I've just spotted a typo in isl.c: the last c

Re: [request for testing] isl, cyapa on chromebooks

> On 05 Oct 2016, at 15:01, Andriy Gapon wrote: > >> On 05/10/2016 14:19, Michael Gmelin wrote: >> >> ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe and >> iicbus_attach are not. > > Thank you! > Now I think I see where I made a silly mistake. >

Re: [request for testing] isl, cyapa on chromebooks

fore to a more recent CURRENT? I think that the patch should apply. But if it doesn't... > I have a second C720 > where I could do such test/update more easy, but this is current not in > my hands and has, after a repair at Acer, a Elan touch pad. > But I could prepare an USB key with 12-CU

Re: [request for testing] isl, cyapa on chromebooks

El día Wednesday, October 05, 2016 a las 04:01:25PM +0300, Andriy Gapon escribió: > On 05/10/2016 14:19, Michael Gmelin wrote: > > > > ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe and > > iicbus_attach are not. > > Thank you! > Now I think I see where I made a silly

Re: [request for testing] isl, cyapa on chromebooks

On 05/10/2016 14:19, Michael Gmelin wrote: > > ig4iic_start is called, but iicbus_hinted_child, isl_probe, iicbus_probe and > iicbus_attach are not. Thank you! Now I think I see where I made a silly mistake. Please try an updated version of the patch from here

Re: [request for testing] isl, cyapa on chromebooks

Nice! I'd love to follow along in development and learn whatever can. I've never worked at device driver level before. Do you have a suggested time I can start harassing you more about testing? Den 5 okt. 2016 13:48 skrev "Michael Gmelin" <gre...@freebsd.org>: > > >

Re: [request for testing] isl, cyapa on chromebooks

Den 5 okt. 2016 13:19 skrev "Michael Gmelin" : > > > > > On 05 Oct 2016, at 07:48, Andriy Gapon wrote: > > > >> On 05/10/2016 01:48, Michael Gmelin wrote: > >> Double-checked the hints, it's all ok. > >> > >> Please find a more verbose log file of loading the

Re: [request for testing] isl, cyapa on chromebooks

bsd-mobile > > To unsubscribe, send any mail to "freebsd-mobile-unsubscr...@freebsd.org" > > I'm running a laptop that uses an Elantech touch pad over i2c. I think I get > Elantech is quite close to cyapa, would this patch be a good place to start > for trying to get the touc

Re: [request for testing] isl, cyapa on chromebooks

> On 05 Oct 2016, at 07:48, Andriy Gapon wrote: > >> On 05/10/2016 01:48, Michael Gmelin wrote: >> Double-checked the hints, it's all ok. >> >> Please find a more verbose log file of loading the kernel modules here: >> >> https://people.freebsd.org/~grembo/c720-20161105.log

Re: [request for testing] isl, cyapa on chromebooks

On 05/10/2016 01:48, Michael Gmelin wrote: > Double-checked the hints, it's all ok. > > Please find a more verbose log file of loading the kernel modules here: > > https://people.freebsd.org/~grembo/c720-20161105.log Unfortunately this doesn't provide any new insights. Could you please add

Re: [request for testing] isl, cyapa on chromebooks

On Tue, 4 Oct 2016 13:07:28 +0300 Andriy Gapon wrote: > On 04/10/2016 12:46, Michael Gmelin wrote: > > iicbus(0|1) actually show up in devinfo -v, but nothing else works. > > > > You can find a log file and various outputs (dmesg, devinfo etc) > > here: > > > >

Re: [request for testing] isl, cyapa on chromebooks

On 04/10/2016 12:46, Michael Gmelin wrote: > iicbus(0|1) actually show up in devinfo -v, but nothing else works. > > You can find a log file and various outputs (dmesg, devinfo etc) here: > > https://people.freebsd.org/~grembo/c720-20161104.log Thank you. Could you please double-check that

Re: [request for testing] isl, cyapa on chromebooks

On Tue, 4 Oct 2016 01:04:10 +0300 Andriy Gapon wrote: > On 03/10/2016 23:25, Michael Gmelin wrote: > > On Mon, 3 Oct 2016 19:41:17 +0300 > > Andriy Gapon wrote: > > > >> On 03/10/2016 19:07, Michael Gmelin wrote: > >>> I upgraded the latter the r306641,

Re: [request for testing] isl, cyapa on chromebooks

On 03/10/2016 23:25, Michael Gmelin wrote: > On Mon, 3 Oct 2016 19:41:17 +0300 > Andriy Gapon wrote: > >> On 03/10/2016 19:07, Michael Gmelin wrote: >>> I upgraded the latter the r306641, applied your patches (cleanly) >>> and ran "make kernel" (GENERIC kernel), added the

Re: [request for testing] isl, cyapa on chromebooks

On Mon, 3 Oct 2016 19:41:17 +0300 Andriy Gapon wrote: > On 03/10/2016 19:07, Michael Gmelin wrote: > > I upgraded the latter the r306641, applied your patches (cleanly) > > and ran "make kernel" (GENERIC kernel), added the entries to > > device.hints and rebooted. Unfortunately

Re: [request for testing] isl, cyapa on chromebooks

On 03/10/2016 19:07, Michael Gmelin wrote: > I upgraded the latter the r306641, applied your patches (cleanly) and > ran "make kernel" (GENERIC kernel), added the entries to device.hints > and rebooted. Unfortunately ig4 won't load: > > # kldload ig4 > link_elf_obj: symbol iicbus_transfer_desc

Re: [request for testing] isl, cyapa on chromebooks

bose dmesg would be of great help. That could > be obtained by booting in a verbose mode if the drivers are > auto-loaded or by setting debug.bootverbose=1 before loading the > drivers if that's done manually. > > Please also note that ig4 driver is changed, so it too has to be > reb

[request for testing] isl, cyapa on chromebooks

hat ig4 driver is changed, so it too has to be rebuilt if you are going to build individual modules rather than do a kernel + modules build. I will appreciate your testing and feedback. Thank you! -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list ht

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

ke...@freebsd.org>: > >> >> >> > >> >> >> Hi, > >> >> >> > >> >> >> So, the driver was fully tested. Thanks! > >> >> >> Can you set dev.rtwn.0.debug=0x829f for RTL8188CE to see how big

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

, Andriy Voskoboinyk wrote: >> >> >> >> >> >> Thu, 22 Sep 2016 12:24:42 +0300 було написано Kevin Lo >> >> >> <ke...@freebsd.org>: >> >> >> >> >> >> Hi, >> >> >> >> >> >> So, th

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

ver 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://people.freebsd.org/~kevlo/rtl8188ce-debug.t

Re: urtwn(4) / rtwn(4) drivers are merged - call for testing (Was: RTL8812AU / RTL8821AU driver)

> On 26 Sep 2016, at 17:10, Andriy Voskoboinyk wrote: > > Mon, 26 Sep 2016 23:02:15 +0300 було написано Renato Botelho > : > > No, warnings are for 'untested' parts (although I think they are not the > reason...) > > Can you send messages.log when >

Re: urtwn(4) / rtwn(4) drivers are merged - call for testing (Was: RTL8812AU / RTL8821AU driver)

Mon, 26 Sep 2016 23:02:15 +0300 було написано Renato Botelho : No, warnings are for 'untested' parts (although I think they are not the reason...) Can you send messages.log when dev.rtwn.0.debug=0x829f is set? I’ve built and loaded it and the error is gone. But ‘list scan’

Re: urtwn(4) / rtwn(4) drivers are merged - call for testing (Was: RTL8812AU / RTL8821AU driver)

> On 26 Sep 2016, at 16:53, Andriy Voskoboinyk wrote: > > Mon, 26 Sep 2016 22:46:58 +0300 було написано Renato Botelho > >: > > AFAIK, it is not critical (at least for USB devices). > > If it won't work without firmware try to

Re: urtwn(4) / rtwn(4) drivers are merged - call for testing (Was: RTL8812AU / RTL8821AU driver)

ects current 'rate control' algorithm (currently only 'none' and 'net80211' are supported; RTL8192CE needs testing with the last). 3) (incomplete) power management support for RTL8188EU (requires firmware). 4) Short Guard Interval support. It's known to work with RTL8188CUS, RTL8188EU a

Re: urtwn(4) / rtwn(4) drivers are merged - call for testing (Was: RTL8812AU / RTL8821AU driver)

use hardware crypto acceleration > * dev.rtwn.#.ratectl_selected > * dev.rtwn.#.ratectl - selects current 'rate control' algorithm > (currently only 'none' and 'net80211' are supported; RTL8192CE needs testing > with the last). > 3) (incomplete) power management support for RTL8

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

;> > 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: >> &

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

8188CE to see how big > >> the problem is? > > > > Sure. Here you go https://people.freebsd.org/~kevlo/rtl8188ce-debug.txt > > > > Thanks, > > Kevin > > > >> > Hi Andriy, > >> > > >> > First of all, THANK YOU! You're do

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

debug=0x829f for RTL8188CE to see how big the problem is? Sure. Here you go https://people.freebsd.org/~kevlo/rtl8188ce-debug.txt Thanks, Kevin > Hi Andriy, > > First of all, THANK YOU! You're doing amazing work! > Second, I've done some testing on the following devices, downloadin

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

big > the problem is? Sure. Here you go https://people.freebsd.org/~kevlo/rtl8188ce-debug.txt Thanks, Kevin > > Hi Andriy, > > > > First of all, THANK YOU! You're doing amazing work! > > Second, I've done some testing on the following devices, downloading > >

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

e 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: 3> on usbus0 rtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R - TP-Link TL-WN725N v2 (RTL8188EU): rtwn0: on usbus0 rtwn

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

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

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

leration * dev.rtwn.#.ratectl_selected * dev.rtwn.#.ratectl - selects current 'rate control' algorithm (currently only 'none' and 'net80211' are supported; RTL8192CE needs testing with the last). 3) (incomplete) power management support for RTL8188EU (requires firmware). 4) Short Guard Interval suppor

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

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

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

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

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

* dev.rtwn.#.crypto - controls how to use hardware crypto acceleration >> * dev.rtwn.#.ratectl_selected >> * dev.rtwn.#.ratectl - selects current 'rate control' algorithm >> (currently only 'none' and 'net80211' are supported; RTL8192CE needs >> testing >> with

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

atectl - selects current 'rate control' algorithm (currently only 'none' and 'net80211' are supported; RTL8192CE needs testing with the last). 3) (incomplete) power management support for RTL8188EU (requires firmware). 4) Short Guard Interval support. It's known to work with RTL8188CUS, RTL

Re: Call for Testing: Switching back to our BSD licensed dtc(1)

On 24 Jul 2016, at 12:42, David Chisnall wrote: > > I’ve now fixed both of these in the version here: > > https://github.com/davidchisnall/dtc Andy filed a number of issues on GitHub, which are now all fixed. In particular, /include/ should now work everywhere and

Re: urtwn(4) / rtwn(4) drivers are merged - call for testing (Was: RTL8812AU / RTL8821AU driver)

ypto - controls how to use hardware crypto acceleration * dev.rtwn.#.ratectl_selected * dev.rtwn.#.ratectl - selects current 'rate control' algorithm (currently only 'none' and 'net80211' are supported; RTL8192CE needs testing with the last). I got a RTL8192CE - what should I look for, wh

Re: urtwn(4) / rtwn(4) drivers are merged - call for testing (Was: RTL8812AU / RTL8821AU driver)

on > * dev.rtwn.#.ratectl_selected > * dev.rtwn.#.ratectl - selects current 'rate control' algorithm > (currently only 'none' and 'net80211' are supported; RTL8192CE needs > testing > with the last). I got a RTL8192CE - what should I look for, when using net80211? Cheers Marcus signature.asc Description: PGP signature

urtwn(4) / rtwn(4) drivers are merged - call for testing (Was: RTL8812AU / RTL8821AU driver)

(currently only 'none' and 'net80211' are supported; RTL8192CE needs testing with the last). 3) (incomplete) power management support for RTL8188EU (requires firmware). 4) Short Guard Interval support. It's known to work with RTL8188CUS, RTL8188EU and RTL8821AU; however, it was never tested

Re: [CFT] ypldap testing against OpenLDAP and Microsoft Active Directory

apd to cache or replicate the > data locally without resorting to the broken nscd. Hello, I was curious, so I made a patcheset which adds NSSOV config option to net/openldap24-server. Unfortunately I'm not getting results :( I decided to compile nssov.la with -DNSLCD_SOCKET=/var/run/nscld.ctl – the s

Re: Call for testing on vagrant-bhyve

Hello, Thanks for your reply. One of my mentor, Steve Wills, has started working on adding support to vagrant-mutate. https://github.com/swills/vagrant-mutate/tree/bhyve But now it's limited to FreeBSD boxes, Linux boxes are more complicated, we are trying to find better ways. Now we have to

Re: Call for testing on vagrant-bhyve

Hi, thanks for your work! Regarding the conversion process described in the README, you might also want to look into / patch vagrant-mutate: https://github.com/sciurus/vagrant-mutate People use it to convert from VirtualBox to libvirt on Linux. -- Christian Schwarz

Call for testing on vagrant-bhyve

l ones and prioritize their implementation. So, please help us. I have documented a step by step guide on how to test vagrant-bhyve, you can follow that. When you find some problems or need some new features, feel free to open an issue. All your testing and feedback will be much appreciated. :) Here is a

Re: Call for Testing: Switching back to our BSD licensed dtc(1)

Thanks, On 19 Jul 2016, at 20:49, Emmanuel Vadot wrote: > > > Hello, > > I've just tried bsd dtc on all arm dts that we have. > It doesn't seems to handle multiple include directories. > Here is how to reproduce : > > $ export SRCROOT=/path/to/fbsd/src > $ export

Re: Call for Testing: Switching back to our BSD licensed dtc(1)

On Fri, 22 Jul 2016 22:16:41 -0600 Warner Losh wrote: > On Fri, Jul 22, 2016 at 1:03 AM, David Chisnall wrote: > > On 22 Jul 2016, at 03:40, Warner Losh wrote: > >> > >> On Wed, Jul 20, 2016 at 9:51 AM, David Chisnall

Re: Call for Testing: Switching back to our BSD licensed dtc(1)

On 23 Jul 2016, at 05:16, Warner Losh wrote: > > On Fri, Jul 22, 2016 at 1:03 AM, David Chisnall wrote: >> On 22 Jul 2016, at 03:40, Warner Losh wrote: >>> >>> On Wed, Jul 20, 2016 at 9:51 AM, David Chisnall >>>

Re: Call for Testing: Switching back to our BSD licensed dtc(1)

On Fri, Jul 22, 2016 at 1:03 AM, David Chisnall wrote: > On 22 Jul 2016, at 03:40, Warner Losh wrote: >> >> On Wed, Jul 20, 2016 at 9:51 AM, David Chisnall wrote: >>> On 20 Jul 2016, at 16:46, Warner Losh wrote:

Re: Call for Testing: Switching back to our BSD licensed dtc(1)

On 22 Jul 2016, at 03:40, Warner Losh wrote: > > On Wed, Jul 20, 2016 at 9:51 AM, David Chisnall wrote: >> On 20 Jul 2016, at 16:46, Warner Losh wrote: >>> >>> I've been trying to get the final spec for it. Right now it's a >>>

Re: Call for Testing: Switching back to our BSD licensed dtc(1)

On Wed, Jul 20, 2016 at 9:51 AM, David Chisnall wrote: > On 20 Jul 2016, at 16:46, Warner Losh wrote: >> >> I've been trying to get the final spec for it. Right now it's a >> disorganized series >> of patches, some of which have been merge some that

Re: Call for Testing: Switching back to our BSD licensed dtc(1)

On 20 Jul 2016, at 16:46, Warner Losh wrote: > > I've been trying to get the final spec for it. Right now it's a > disorganized series > of patches, some of which have been merge some that haven't. I'll send you a > copy when I can find something better than "here's the code."

Re: Call for Testing: Switching back to our BSD licensed dtc(1)

On Wed, Jul 20, 2016 at 3:05 AM, David Chisnall wrote: > On 20 Jul 2016, at 05:48, Warner Losh wrote: >> >> My concern with this is overlay support. Overlay support for "shields" or >> "badges" is going into upstream GPL dtc shortly. The patches have been

Re: Call for Testing: Switching back to our BSD licensed dtc(1)

On Wed, Jul 20, 2016 at 9:45 AM, Warner Losh wrote: > On Wed, Jul 20, 2016 at 3:05 AM, David Chisnall wrote: >> On 20 Jul 2016, at 05:48, Warner Losh wrote: >>> >>> My concern with this is overlay support. Overlay support for "shields" or

Re: Call for Testing: Switching back to our BSD licensed dtc(1)

On 20 Jul 2016, at 05:48, Warner Losh wrote: > > My concern with this is overlay support. Overlay support for "shields" or > "badges" is going into upstream GPL dtc shortly. The patches have been > kicking around for a while and are almost ready to go in. We need this feature >

Re: Call for Testing: Switching back to our BSD licensed dtc(1)

On Tue, Jul 19, 2016 at 1:12 PM, Ed Maste wrote: > dtc(1) is the Device Tree Compiler, used for embedded builds. We have > two versions of dtc(1) in the FreeBSD tree: a GPLv2 one from > https://git.kernel.org/cgit/utils/dtc/dtc.git and a BSD licensed one > in

Re: Call for Testing: Switching back to our BSD licensed dtc(1)

Hello, I've just tried bsd dtc on all arm dts that we have. It doesn't seems to handle multiple include directories. Here is how to reproduce : $ export SRCROOT=/path/to/fbsd/src $ export MACHINE=arm $ cd $SRCROOT/sys/boot/fdt/dts/arm $ $SRCROOT/sys/tools/fdt/make_dtb.sh $SRCROOT/sys

Call for Testing: Switching back to our BSD licensed dtc(1)

dtc(1) is the Device Tree Compiler, used for embedded builds. We have two versions of dtc(1) in the FreeBSD tree: a GPLv2 one from https://git.kernel.org/cgit/utils/dtc/dtc.git and a BSD licensed one in https://svn.freebsd.org/base/head/usr.bin/dtc. We switched back to the GPL one since device

Request for VIMAGE testing in 11.0-ALPHA6 and later

interface. I have done some testing and stress testing but it's impossible to catch all combinations and setups or even options. So once 11.0-ALPHA6 is out please do test (or if you want to do so now r302302 or later). These changes are only and will only be in FreeBSD 11 for the time being. You

Re: RTL8812AU / RTL8821AU driver - call for testing

Some updates: - 11n (A-MPDU & A-MSDU) now is supported (hw.usb.urtwm.enable_11n option was removed); - Atheros Fast-Frames support was added in https://github.com/s3erios/urtwm/commit/e835e556a0533d0adf81008dd4330241a7a5fbab . Hi all! The driver is in https://github.com/s3erios/urtwm ;

Re: [CFT] ypldap testing against OpenLDAP and Microsoft Active Directory

On Tue, Jun 21, 2016 at 9:55 AM, Jan Bramkamp wrote: > On 18/06/16 17:15, Alan Somers wrote: >> >> On Thu, Jun 16, 2016 at 7:20 AM, Chris H wrote: >>> >>> On Wed, 15 Jun 2016 08:03:55 -0400 Nikolai Lifanov >>> >>> wrote >>>

Re: [CFT] ypldap testing against OpenLDAP and Microsoft Active Directory

On 18/06/16 17:15, Alan Somers wrote: On Thu, Jun 16, 2016 at 7:20 AM, Chris H wrote: On Wed, 15 Jun 2016 08:03:55 -0400 Nikolai Lifanov wrote On 06/14/2016 21:05, Marcelo Araujo wrote: 2016-06-15 8:17 GMT+08:00 Chris H

Re: [CFT] ypldap testing against OpenLDAP and Microsoft Active Directory

On Thu, Jun 16, 2016 at 7:20 AM, Chris H wrote: > On Wed, 15 Jun 2016 08:03:55 -0400 Nikolai Lifanov > wrote > >> On 06/14/2016 21:05, Marcelo Araujo wrote: >> > 2016-06-15 8:17 GMT+08:00 Chris H : >> > >> >> On Thu, 9 Jun

Re: [CFT] ypldap testing against OpenLDAP and Microsoft Active Directory

On Wed, 15 Jun 2016 08:03:55 -0400 Nikolai Lifanov wrote > On 06/14/2016 21:05, Marcelo Araujo wrote: > > 2016-06-15 8:17 GMT+08:00 Chris H : > > > >> On Thu, 9 Jun 2016 17:55:58 +0800 Marcelo Araujo > >> wrote > >> >

Re: [CFT] ypldap testing against OpenLDAP and Microsoft Active Directory

I hear too!!! And that is why we are having this talk here around ypldap. Best, 2016-06-16 10:50 GMT+08:00 Outback Dingo : > > > On Wed, Jun 15, 2016 at 10:15 PM, Marcelo Araujo > wrote: > >> No worries Nikolai! If one day I will do it, will be

<    1   2   3   4   5   6   7   8   9   10   >