Re: Info

2019-03-08 Thread Adrian Chadd
Hi! We're working on it in github.com/erikarn/athp/ . I'm fixing up the
transmit path in the driver right now to work around firmware behaviour and
Geramy is wrapping his head around DMA / busdma issues.


-adrian


On Fri, 8 Mar 2019 at 03:45, Domenico Panella  wrote:

> Hi guys,
>
> I am a programmer and I have a good knowledge of the C / C ++ language. In
> a few weeks a new machine should arrive with the Killer 1435 wifi card. I
> would like to run FreeBSD on this machine but I read that this card is not
> supported.
> At what point are you with the development of the driver?
>
> The technical specifications of this card are as follows:
>
>  Single-chip, 2.4 / 5 GHz, 2 stream 802.11a / b / g / n / ac and BT 4.2
>  11ac 2X2 WLAN standards with low power PCIe (with L1 sub-state)
> interfaces + BT 4.2 with USB1.1 interface.
>  Module specifications: Next generation form factor, M.2, module size =
> 22mm x 30mm, Key (A-E)
>  Chipset: QCA6174A
>
> I would like to collaborate with you for the development and testing of
> these drivers or other, obviously documenting me first well.
> Can you give me some guidelines to get started?
>
> with regard
> BSDUser
> ___
> freebsd-wireless@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org
> "
>
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"


Info

2019-03-08 Thread Domenico Panella
Hi guys,

I am a programmer and I have a good knowledge of the C / C ++ language. In
a few weeks a new machine should arrive with the Killer 1435 wifi card. I
would like to run FreeBSD on this machine but I read that this card is not
supported.
At what point are you with the development of the driver?

The technical specifications of this card are as follows:

 Single-chip, 2.4 / 5 GHz, 2 stream 802.11a / b / g / n / ac and BT 4.2
 11ac 2X2 WLAN standards with low power PCIe (with L1 sub-state)
interfaces + BT 4.2 with USB1.1 interface.
 Module specifications: Next generation form factor, M.2, module size =
22mm x 30mm, Key (A-E)
 Chipset: QCA6174A

I would like to collaborate with you for the development and testing of
these drivers or other, obviously documenting me first well.
Can you give me some guidelines to get started?

with regard
BSDUser
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"


Re: How to get the info from ioctl to iwinfo

2013-12-08 Thread Adrian Chadd
.. Luci? OpenWrt? FreeBSD?
On Dec 8, 2013 5:33 AM, Tek Wiz tx2...@gmail.com wrote:

 How to get the info from ioctl to iwinfo?

 I want to transfer the info of the interference scan results (e.g. RSSI and
 noise floor for each channel) to the OpenWrt LuCI web page.

 Thanks
 ___
 freebsd-wireless@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
 To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
 

___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org


Re: How to get the info from ioctl to iwinfo

2013-12-08 Thread Tek Wiz
Actually I'm working on Luci and OpenWrt. I was wondering if FreeBSD has a
similar feature.

Thanks


On Mon, Dec 9, 2013 at 10:14 AM, Adrian Chadd adrian.ch...@gmail.comwrote:

 .. Luci? OpenWrt? FreeBSD?
 On Dec 8, 2013 5:33 AM, Tek Wiz tx2...@gmail.com wrote:

 How to get the info from ioctl to iwinfo?

 I want to transfer the info of the interference scan results (e.g. RSSI
 and
 noise floor for each channel) to the OpenWrt LuCI web page.

 Thanks
 ___
 freebsd-wireless@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
 To unsubscribe, send any mail to 
 freebsd-wireless-unsubscr...@freebsd.org


___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org


Re: How to get the info from ioctl to iwinfo

2013-12-08 Thread Adrian Chadd
Yes, there's a scan results ioctl in net80211 somewhere. It's how you
extract out the scan table.

You can also use wpa_cli to query wpa_supplicant about its copy of the
scan table.


-a


On 8 December 2013 18:37, Tek Wiz tx2...@gmail.com wrote:
 Actually I'm working on Luci and OpenWrt. I was wondering if FreeBSD has a
 similar feature.

 Thanks


 On Mon, Dec 9, 2013 at 10:14 AM, Adrian Chadd adrian.ch...@gmail.com
 wrote:

 .. Luci? OpenWrt? FreeBSD?

 On Dec 8, 2013 5:33 AM, Tek Wiz tx2...@gmail.com wrote:

 How to get the info from ioctl to iwinfo?

 I want to transfer the info of the interference scan results (e.g. RSSI
 and
 noise floor for each channel) to the OpenWrt LuCI web page.

 Thanks
 ___
 freebsd-wireless@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
 To unsubscribe, send any mail to
 freebsd-wireless-unsubscr...@freebsd.org


___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org


iwn transmit debug info

2013-11-08 Thread Eitan Adler
Per Adrian's request:

iwn_notif_intr: scanning channel 5 status 1
iwn_notif_intr: scanning channel 8 status 1
iwn_notif_intr: scanning channel 9 status 1
iwn_notif_intr: scanning channel 10 status 1
iwn_notif_intr: scanning channel 12 status 1
iwn_tx_data_raw: qid 3 idx 0 len 6 nsegs 1
iwn5000_tx_done: qid 3 idx 0 retries 1 nkill 0 rate 420a duration 1242
status 201
iwn_tx_data_raw: qid 3 idx 1 len 83 nsegs 1
iwn5000_tx_done: qid 3 idx 1 retries 0 nkill 0 rate 420a duration 1394
status 201
wlan1: link state changed to UP
iwn_tx_data: qid 3 idx 2 len 24 nsegs 2
iwn5000_tx_done: qid 3 idx 2 retries 0 nkill 0 rate 6100 duration 158 status 201
iwn_tx_data: qid 3 idx 3 len 241 nsegs 2
iwn5000_tx_done: qid 3 idx 3 retries 0 nkill 0 rate 6100 duration 399 status 201
iwn_tx_data: qid 3 idx 4 len 18 nsegs 2
iwn5000_tx_done: qid 3 idx 4 retries 0 nkill 0 rate 6100 duration 150 status 201
iwn_tx_data: qid 3 idx 5 len 18 nsegs 2
iwn5000_tx_done: qid 3 idx 5 retries 0 nkill 0 rate 6100 duration 150 status 201
iwn_tx_data: qid 3 idx 6 len 18 nsegs 2
iwn5000_tx_done: qid 3 idx 6 retries 0 nkill 0 rate 6100 duration 150 status 201
iwn_tx_data: qid 3 idx 7 len 18 nsegs 2
iwn5000_tx_done: qid 3 idx 7 retries 1 nkill 0 rate 6100 duration 240 status 201
iwn_tx_data: qid 3 idx 8 len 344 nsegs 2
iwn5000_tx_done: qid 3 idx 8 retries 0 nkill 0 rate 6100 duration 514 status 201
iwn_tx_data: qid 3 idx 9 len 18 nsegs 2
iwn5000_tx_done: qid 3 idx 9 retries 0 nkill 0 rate 6100 duration 150 status 201
iwn_tx_data: qid 3 idx 10 len 108 nsegs 2
iwn5000_tx_done: qid 3 idx 10 retries 0 nkill 0 rate 6100 duration 251
status 201
iwn_tx_data: qid 3 idx 11 len 156 nsegs 2
iwn5000_tx_done: qid 3 idx 11 retries 0 nkill 0 rate 6100 duration 305
status 201
iwn_tx_data: qid 3 idx 12 len 92 nsegs 2
iwn5000_tx_done: qid 3 idx 12 retries 0 nkill 0 rate 6100 duration 233
status 201
iwn_tx_data: qid 3 idx 13 len 18 nsegs 2
iwn5000_tx_done: qid 3 idx 13 retries 0 nkill 0 rate 6100 duration 150
status 201
iwn_tx_data: qid 3 idx 14 len 129 nsegs 2
iwn5000_tx_done: qid 3 idx 14 retries 0 nkill 0 rate 6100 duration 276
status 201
iwn_tx_data: qid 3 idx 15 len 107 nsegs 2
iwn5000_tx_done: qid 3 idx 15 retries 0 nkill 0 rate 6100 duration 251
status 201


-- 
Eitan Adler
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org


Re: iwn transmit debug info

2013-11-08 Thread Adrian Chadd
Yeah, but those frames are successfully transmitting.

Are pings making it through?


-adrian


On 8 November 2013 21:38, Eitan Adler li...@eitanadler.com wrote:
 Per Adrian's request:

 iwn_notif_intr: scanning channel 5 status 1
 iwn_notif_intr: scanning channel 8 status 1
 iwn_notif_intr: scanning channel 9 status 1
 iwn_notif_intr: scanning channel 10 status 1
 iwn_notif_intr: scanning channel 12 status 1
 iwn_tx_data_raw: qid 3 idx 0 len 6 nsegs 1
 iwn5000_tx_done: qid 3 idx 0 retries 1 nkill 0 rate 420a duration 1242
 status 201
 iwn_tx_data_raw: qid 3 idx 1 len 83 nsegs 1
 iwn5000_tx_done: qid 3 idx 1 retries 0 nkill 0 rate 420a duration 1394
 status 201
 wlan1: link state changed to UP
 iwn_tx_data: qid 3 idx 2 len 24 nsegs 2
 iwn5000_tx_done: qid 3 idx 2 retries 0 nkill 0 rate 6100 duration 158 status 
 201
 iwn_tx_data: qid 3 idx 3 len 241 nsegs 2
 iwn5000_tx_done: qid 3 idx 3 retries 0 nkill 0 rate 6100 duration 399 status 
 201
 iwn_tx_data: qid 3 idx 4 len 18 nsegs 2
 iwn5000_tx_done: qid 3 idx 4 retries 0 nkill 0 rate 6100 duration 150 status 
 201
 iwn_tx_data: qid 3 idx 5 len 18 nsegs 2
 iwn5000_tx_done: qid 3 idx 5 retries 0 nkill 0 rate 6100 duration 150 status 
 201
 iwn_tx_data: qid 3 idx 6 len 18 nsegs 2
 iwn5000_tx_done: qid 3 idx 6 retries 0 nkill 0 rate 6100 duration 150 status 
 201
 iwn_tx_data: qid 3 idx 7 len 18 nsegs 2
 iwn5000_tx_done: qid 3 idx 7 retries 1 nkill 0 rate 6100 duration 240 status 
 201
 iwn_tx_data: qid 3 idx 8 len 344 nsegs 2
 iwn5000_tx_done: qid 3 idx 8 retries 0 nkill 0 rate 6100 duration 514 status 
 201
 iwn_tx_data: qid 3 idx 9 len 18 nsegs 2
 iwn5000_tx_done: qid 3 idx 9 retries 0 nkill 0 rate 6100 duration 150 status 
 201
 iwn_tx_data: qid 3 idx 10 len 108 nsegs 2
 iwn5000_tx_done: qid 3 idx 10 retries 0 nkill 0 rate 6100 duration 251
 status 201
 iwn_tx_data: qid 3 idx 11 len 156 nsegs 2
 iwn5000_tx_done: qid 3 idx 11 retries 0 nkill 0 rate 6100 duration 305
 status 201
 iwn_tx_data: qid 3 idx 12 len 92 nsegs 2
 iwn5000_tx_done: qid 3 idx 12 retries 0 nkill 0 rate 6100 duration 233
 status 201
 iwn_tx_data: qid 3 idx 13 len 18 nsegs 2
 iwn5000_tx_done: qid 3 idx 13 retries 0 nkill 0 rate 6100 duration 150
 status 201
 iwn_tx_data: qid 3 idx 14 len 129 nsegs 2
 iwn5000_tx_done: qid 3 idx 14 retries 0 nkill 0 rate 6100 duration 276
 status 201
 iwn_tx_data: qid 3 idx 15 len 107 nsegs 2
 iwn5000_tx_done: qid 3 idx 15 retries 0 nkill 0 rate 6100 duration 251
 status 201


 --
 Eitan Adler
 ___
 freebsd-wireless@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
 To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org