Re: [rfc] removing the NDISulator

2013-10-25 Thread Thomas Mueller
On 24.10.2013 05:46, Thomas Mueller wrote: I have motherboard (MSI Z77 MPOWER) with Realtek 8111E Ethernet that fails to connect in FreeBSD or OpenBSD, OK with NetBSD-current and Linux, and Atheros AR9271 onboard wifi: device athn is included in NetBSD (current only) and OpenBSD.

Re: [rfc] removing the NDISulator

2013-10-24 Thread Kevin Lo
Thomas Mueller wrote: The later driver model isn't supported by ndisulator. We'd have to implement all the newer NDIS stuff for wifi and ethernet. In the later NDIS layer the Microsoft Wireless Services implement a bunch of stuff that used to be up to the driver. Ie, the driver

Re: [rfc] removing the NDISulator

2013-10-24 Thread Maciej Milewski
On 24.10.2013 05:46, Thomas Mueller wrote: I have motherboard (MSI Z77 MPOWER) with Realtek 8111E Ethernet that fails to connect in FreeBSD or OpenBSD, OK with NetBSD-current and Linux, and Atheros AR9271 onboard wifi: device athn is included in NetBSD (current only) and OpenBSD. Tom For your

Re: [rfc] removing the NDISulator

2013-10-23 Thread John Baldwin
On Monday, October 21, 2013 6:29:24 pm Adrian Chadd wrote: The NDISulator is a crutch from a time when there wasn't _any_ real alternative. There are plenty of alternatives now. What's lacking is desire and person-power. But the datasheets are there, or the vendor code has been released, or

Re: [rfc] removing the NDISulator

2013-10-23 Thread Eitan Adler
On Mon, Oct 21, 2013 at 6:29 PM, Adrian Chadd adr...@freebsd.org wrote: If there are drivers that people absolutely need fixed then they should stand up and say hey, I really would like X to work better! and then follow it up with some encouraging incentives. Right now the NDISulator lets

Re: [rfc] removing the NDISulator

2013-10-23 Thread Adrian Chadd
On 23 October 2013 11:09, Alfred Perlstein bri...@mu.org wrote: Eh, having taken a stab at porting the bwl blob already, I would strongly oppose removing NDIS. If you do that I will just stop using my netbook with a Broadcom part altogether as I wouldn't be able to use it to try to test bwl

Re: [rfc] removing the NDISulator

2013-10-23 Thread Alfred Perlstein
On 10/23/13 11:11 AM, Adrian Chadd wrote: On 23 October 2013 11:09, Alfred Perlstein bri...@mu.org wrote: Eh, having taken a stab at porting the bwl blob already, I would strongly oppose removing NDIS. If you do that I will just stop using my netbook with a Broadcom part altogether as I

Re: [rfc] removing the NDISulator

2013-10-23 Thread Alfred Perlstein
On 10/23/13 7:23 AM, John Baldwin wrote: On Monday, October 21, 2013 6:29:24 pm Adrian Chadd wrote: The NDISulator is a crutch from a time when there wasn't _any_ real alternative. There are plenty of alternatives now. What's lacking is desire and person-power. But the datasheets are there, or

Re: [rfc] removing the NDISulator

2013-10-23 Thread Adrian Chadd
Because the Linux stuff is mostly very GPL. Adrian On Oct 23, 2013 2:15 PM, Alfred Perlstein bri...@mu.org wrote: On 10/23/13 11:11 AM, Adrian Chadd wrote: On 23 October 2013 11:09, Alfred Perlstein bri...@mu.org wrote: Eh, having taken a stab at porting the bwl blob already, I would

Re: [rfc] removing the NDISulator

2013-10-23 Thread John Baldwin
On Wednesday, October 23, 2013 2:11:29 pm Adrian Chadd wrote: On 23 October 2013 11:09, Alfred Perlstein bri...@mu.org wrote: Eh, having taken a stab at porting the bwl blob already, I would strongly oppose removing NDIS. If you do that I will just stop using my netbook with a Broadcom

Re: [rfc] removing the NDISulator

2013-10-23 Thread Adrian Chadd
And the link momentum is strong now. There's driver source. Adrian On Oct 23, 2013 2:41 PM, John Baldwin j...@freebsd.org wrote: On Wednesday, October 23, 2013 2:11:29 pm Adrian Chadd wrote: On 23 October 2013 11:09, Alfred Perlstein bri...@mu.org wrote: Eh, having taken a stab at

Re: [rfc] removing the NDISulator

2013-10-23 Thread Thomas Mueller
On 23 October 2013 13:10, claudiu vasadi claudiu.vas...@gmail.com wrote: Hi, Still getting the Cannot reset interface wlan0 - exit status 1 in wifimgr but no crash yet. Will keep trying :D I have no idea about that. It's likely there's some net80211/iwn bug(s) but I

Re: [rfc] removing the NDISulator

2013-10-23 Thread Vincent Hoffman
On 23/10/2013 18:35, Eitan Adler wrote: On Mon, Oct 21, 2013 at 6:29 PM, Adrian Chadd adr...@freebsd.org wrote: If there are drivers that people absolutely need fixed then they should stand up and say hey, I really would like X to work better! and then follow it up with some encouraging

Re: [rfc] removing the NDISulator

2013-10-22 Thread Thomas Mueller
The NDISulator is a crutch from a time when there wasn't _any_ real alternative. There are plenty of alternatives now. What's lacking is desire and person-power. But the datasheets are there, or the vendor code has been released, or there's linux/otherbsd drivers. Leaving it in there is

Re: [rfc] removing the NDISulator

2013-10-21 Thread Adrian Chadd
On 21 October 2013 12:59, Andrey V. Elsukov bu7c...@yandex.ru wrote: On 19.10.2013 10:01, Thomas Mueller wrote: I too would like to see more effort writing new Ethernet and wifi drivers and porting from other operating systems. But I would like to keep the NDISulator/NDISwrapper as a

Re: [rfc] removing the NDISulator

2013-10-21 Thread Julian H. Stacey
Andrey V. Elsukov bu7c...@yandex.ru wrote: I'm agree. While there are still some devices without native drivers, but that work via NDISulator, we should keep it. Yes, best keep it while it helps some people. Adrian Chadd adr...@freebsd.org wrote: It's honestly about time that these were

Re: [rfc] removing the NDISulator

2013-10-21 Thread Adrian Chadd
The NDISulator is a crutch from a time when there wasn't _any_ real alternative. There are plenty of alternatives now. What's lacking is desire and person-power. But the datasheets are there, or the vendor code has been released, or there's linux/otherbsd drivers. Leaving it in there is just

Re: [rfc] removing the NDISulator

2013-10-19 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 Linux

Re: [rfc] removing the NDISulator

2013-10-19 Thread m
On 01:51 19-Oct 2013 Adrian Chadd wrote: 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. In brcsmac (driver that

Re: [rfc] removing the NDISulator

2013-10-19 Thread Matthias Apitz
El día Friday, October 18, 2013 a las 02:19:42PM -0700, Adrian Chadd escribió: I'd really like to see bwi/bwn maintained and have support added for the later hardware. Hi Adrian, $ pciconf -vl ndis0@pci0:1:0:0: class=0x028000 card=0xe01b105b chip=0x431514e4 rev=0x01 hdr=0x00

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

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 Adrian Chadd
Hi, On 18 October 2013 13:53, Steve Wills swi...@freebsd.org 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

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 =

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

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
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 bri...@mu.org wrote: On 10/18/13 2:04 PM, Nathan Whitehorn wrote: On 10/18/13 16:01, Steve Kargl wrote: