RE: [iwn]Review Split 6

2013-08-13 Thread Cedric GROSS
 
  I guess '_u1' here is 'PAN VAP'. We'll eventually rename this stuff
  and maybe shift it into a separate source file so all the PAN stuff
  clearly lives elsewhere.
 
 Ok I'll do that.
 

Here is new version of split 6 with new files and new function renamed.

Cedric


pan2.patch
Description: Binary data
___
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]Review Split 6

2013-08-12 Thread Cedric GROSS

 De : adrian.ch...@gmail.com [mailto:adrian.ch...@gmail.com] De la part
 de Adrian Chadd
 Envoyé : dimanche 11 août 2013 19:09
 À : Cedric GROSS
 Cc : freebsd-wireless@freebsd.org
 Objet : Re: [iwn]Review Split 6
 
 On 11 August 2013 10:06, Cedric GROSS c...@cgross.info wrote:
 
  U1 stand for unit 1.
  As you see, all function with this prefix will be call when unit==1
  within iwn_vap_create.
 
  As previously, I haven't investigate a lot this side. I plan to do so
  when standard run will be ok.
 
 Right. But what's going on, per se? Is it two separate NICs that show
 up as separate PCI devices? Or is this a hack so the firmware can
 present two virtual NICs via the firmware API?
 
Not a separate PCI device but yes ability to create 2 wlan NIC :

iwn0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 2290
ether 60:36:dd:93:34:56
nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL
media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng
status: associated
wlan0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0
mtu 1500
ether 60:36:dd:93:34:56
inet 192.168.1.20 netmask 0xff00 broadcast 192.168.1.255
nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL
media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
status: associated
ssid WLenine channel 5 (2432 MHz 11g ht/20) bssid 00:24:d4:97:80:20
country US authmode WPA2/802.11i privacy ON deftxkey UNDEF
AES-CCM 2:128-bit txpower 15 bmiss 10 scanvalid 450 bgscan
bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 64 protmode CTS
ampdulimit 64k -amsdutx amsdurx shortgi wme roaming MANUAL bintval
96
wlan1: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 1500
ether 60:36:dd:93:34:57
nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL
media: IEEE 802.11 Wireless Ethernet autoselect (autoselect)
status: no carrier
ssid  channel 5 (2432 MHz 11g ht/20)
country US authmode OPEN privacy OFF txpower 15 bmiss 10 scanvalid
60
bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 64
protmode CTS ampdulimit 8k -amsdutx amsdurx shortgi wme bintval 0

___
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]Review Split 6

2013-08-12 Thread Adrian Chadd
On 12 August 2013 10:41, Cedric GROSS c...@cgross.info wrote:

 But again, as current version is not stable in normal operation, I haven't
 test it further.

 What could be interest of this ?
 Wifi relay, bridge or whatever usage of 2 wireless but only with 1 card.

It's likely for STA on one VAP and P2P-GO on the other VAP.



-adrian
___
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]Review Split 6

2013-08-12 Thread Adrian Chadd
Ok, so this PAN support is .. pretty terrifying. We'll have to tidy it
up once the rest of this work is debugged.

I guess '_u1' here is 'PAN VAP'. We'll eventually rename this stuff
and maybe shift it into a separate source file so all the PAN stuff
clearly lives elsewhere.

I wonder which NICs support PAN - ie, how I would even begin going
about testing it out. Unfortunately our net80211 stack doesn't yet
have P2P support - it would be nice if someone wrote up the basic
infrastructure for that.

Anyway. I'll test this out on the iwn(4) NICs I now have and I'll get
back to you with any regressions that my light testing finds. As
always, thanks!



-adrian
___
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]Review Split 6

2013-08-12 Thread Cedric GROSS

 -Message d'origine-
 De : adrian.ch...@gmail.com [mailto:adrian.ch...@gmail.com] De la part
 de Adrian Chadd
 Envoyé : lundi 12 août 2013 20:25
 À : Cedric GROSS
 Cc : freebsd-wireless@freebsd.org
 Objet : Re: [iwn]Review Split 6
 
 Ok, so this PAN support is .. pretty terrifying. We'll have to tidy it
 up once the rest of this work is debugged.
 
 I guess '_u1' here is 'PAN VAP'. We'll eventually rename this stuff and
 maybe shift it into a separate source file so all the PAN stuff clearly
 lives elsewhere.

Ok I'll do that. 

 
 I wonder which NICs support PAN - ie, how I would even begin going
 about testing it out. Unfortunately our net80211 stack doesn't yet have
 P2P support - it would be nice if someone wrote up the basic
 infrastructure for that.

PAN support is found within firmware: IWN_FW_TLV_PAN

 
 Anyway. I'll test this out on the iwn(4) NICs I now have and I'll get
 back to you with any regressions that my light testing finds. As
 always, thanks!
 

Should be none I guess ;)

 
 
 -adrian

___
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]Review Split 6

2013-08-11 Thread Adrian Chadd
Hi!

What's 'u1' as a prefix supposed to represent?



-adrian

On 11 August 2013 06:09, Cedric GROSS c...@cgross.info wrote:
 Hello,



 Here is patch split 6.



 It's follow split 5 as it implement PAN context.

 This patch is purely based on work done by Sean Bruno.



 Cedric


 ___
 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: [iwn]Review Split 6

2013-08-11 Thread Cedric GROSS


 -Message d'origine-
 De : adrian.ch...@gmail.com [mailto:adrian.ch...@gmail.com] De la part
 de Adrian Chadd
 Envoyé : dimanche 11 août 2013 18:34
 À : Cedric GROSS
 Cc : freebsd-wireless@freebsd.org
 Objet : Re: [iwn]Review Split 6
 
 Hi!
 
 What's 'u1' as a prefix supposed to represent?
 

U1 stand for unit 1. 
As you see, all function with this prefix will be call when unit==1 within
iwn_vap_create.

As previously, I haven't investigate a lot this side. I plan to do so when
standard run will be ok.

 
 
 -adrian
 
  It's follow split 5 as it implement PAN context.
 
  This patch is purely based on work done by Sean Bruno.
 
  Cedric

___
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]Review Split 6

2013-08-11 Thread Adrian Chadd
On 11 August 2013 10:06, Cedric GROSS c...@cgross.info wrote:

 U1 stand for unit 1.
 As you see, all function with this prefix will be call when unit==1 within
 iwn_vap_create.

 As previously, I haven't investigate a lot this side. I plan to do so when
 standard run will be ok.

Right. But what's going on, per se? Is it two separate NICs that show
up as separate PCI devices? Or is this a hack so the firmware can
present two virtual NICs via the firmware API?



-adrian
___
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