Re: [rfc] removing the NDISulator

2013-10-18 Thread Thomas Mueller
> I'd like to remove the NDISulator. I've had many requests to update it to > the latest NDIS version and support more of the 64 bit wifi drivers. But, > to be perfectly honest, I have no desire to keep hacking at this. The world > has changed quite a bit - we can port/reimplement drivers from Linu

Re: [rfc] removing the NDISulator

2013-10-18 Thread Adrian Chadd
I don't know how many times i can say "it needs a maintainer" and "it needs updating." So yeah, it needs (a) a maintainer, (b) updating. -adrian On 18 October 2013 15:47, Alfred Perlstein wrote: > On 10/18/13 2:04 PM, Nathan Whitehorn wrote: > >> On 10/18/13 16:01, Steve Kargl wrote: >> >>

Re: [rfc] removing the NDISulator

2013-10-18 Thread Alfred Perlstein
On 10/18/13 2:04 PM, Nathan Whitehorn wrote: On 10/18/13 16:01, Steve Kargl wrote: On Fri, Oct 18, 2013 at 08:53:54PM +, Steve Wills wrote: I would love to have a native driver for this: none2@pci0:2:0:0: class=0x028000 card=0x00101028 chip=0x472714e4 rev=0x01 hdr=0x00 vendor

Re: [rfc] removing the NDISulator

2013-10-18 Thread Adrian Chadd
bwn(4) requires a lot more than just an additional PCI ID. The driver is somewhat architected for all the different RF and PHY modules that plug into the internal bus (the whole SIBA thing) but it does sorely need updating. Thanks, -adrian On 18 October 2013 14:04, Nathan Whitehorn wrote:

Re: [rfc] removing the NDISulator

2013-10-18 Thread Nathan Whitehorn
On 10/18/13 16:01, Steve Kargl wrote: On Fri, Oct 18, 2013 at 08:53:54PM +, Steve Wills wrote: I would love to have a native driver for this: none2@pci0:2:0:0: class=0x028000 card=0x00101028 chip=0x472714e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'B

Re: [rfc] removing the NDISulator

2013-10-18 Thread Adrian Chadd
Hi, On 18 October 2013 13:53, Steve Wills wrote: > I would love to have a native driver for this: > > none2@pci0:2:0:0: class=0x028000 card=0x00101028 chip=0x472714e4 > rev=0x01 hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'BCM4313 802.11b/g/n Wireless LAN Control

Re: [rfc] removing the NDISulator

2013-10-18 Thread Steve Kargl
On Fri, Oct 18, 2013 at 08:53:54PM +, Steve Wills wrote: > I would love to have a native driver for this: > > none2@pci0:2:0:0: > class=0x028000 card=0x00101028 chip=0x472714e4 rev=0x01 hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'BCM4313 802.11b/g/n Wireless LAN

Re: [rfc] removing the NDISulator

2013-10-18 Thread Steve Wills
I would love to have a native driver for this: none2@pci0:2:0:0: class=0x028000 card=0x00101028 chip=0x472714e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM4313 802.11b/g/n Wireless LAN Controller' class = network Are there docs or other drivers

[rfc] removing the NDISulator

2013-10-18 Thread Adrian Chadd
Hi all, I'd like to remove the NDISulator. I've had many requests to update it to the latest NDIS version and support more of the 64 bit wifi drivers. But, to be perfectly honest, I have no desire to keep hacking at this. The world has changed quite a bit - we can port/reimplement drivers from Lin

Re: Why does ath(4) suck, and what else to buy?

2013-10-18 Thread Adrian Chadd
Hi, No. I have infinite hardware. I just don't have time/drive to hack on other wireless hardware at the moment. I'd appreciate it if someone else stepped up with decent interest in a USB device or two, but the interest seems .. ephemeral. -adrian On 18 October 2013 10:43, Ulrich Spörlein

Re: Why does ath(4) suck, and what else to buy?

2013-10-18 Thread Ulrich Spörlein
Well, the VAP support is not a hard requirement, as I can just buy one USB fob per AP that I need (I have plenty of USB ports on this little thing). So no USB wireless device with working AP mode? :( What are other people using? Would hardware donations speed things up? Anyone? Sad, Uli 2013/10/