> 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
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 pr
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 just
> 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 just exposed an
> ether
On Wed, Oct 23, 2013, at 19:11, Adrian Chadd wrote:
> On 23 October 2013 15:31, Vincent Hoffman wrote:
>
> > On 23/10/2013 18:35, Eitan Adler wrote:
> >
> > On Mon, Oct 21, 2013 at 6:29 PM, Adrian Chadd
> > wrote:
> >
> > If there are drivers that people absolutely need fixed then they shoul
On 23 October 2013 15:31, Vincent Hoffman wrote:
> On 23/10/2013 18:35, Eitan Adler wrote:
>
> On Mon, Oct 21, 2013 at 6:29 PM, Adrian Chadd
> 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!" an
On 23/10/2013 18:35, Eitan Adler wrote:
> On Mon, Oct 21, 2013 at 6:29 PM, Adrian Chadd 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. Righ
Hi,
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 just exposed an
ethernet "device" wi
> > On 23 October 2013 13:10, claudiu vasadi 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 don't use wifi
Adrian Chadd wrote this message on Wed, Oct 23, 2013 at 11:11 -0700:
> On 23 October 2013 11:09, Alfred Perlstein 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 Broadco
And the link momentum is strong now. There's driver source.
Adrian
On Oct 23, 2013 2:41 PM, "John Baldwin" wrote:
> On Wednesday, October 23, 2013 2:11:29 pm Adrian Chadd wrote:
> > On 23 October 2013 11:09, Alfred Perlstein wrote:
> >
> >
> > > Eh, having taken a stab at porting the bwl blob a
On Wednesday, October 23, 2013 2:11:29 pm Adrian Chadd wrote:
> On 23 October 2013 11:09, Alfred Perlstein 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 pa
Because the Linux stuff is mostly very GPL.
Adrian
On Oct 23, 2013 2:15 PM, "Alfred Perlstein" wrote:
> On 10/23/13 11:11 AM, Adrian Chadd wrote:
>
>> On 23 October 2013 11:09, Alfred Perlstein wrote:
>>
>>
>> Eh, having taken a stab at porting the bwl blob already, I would strongly
>>>
o
On 10/23/13 11:11 AM, Adrian Chadd wrote:
On 23 October 2013 11:09, Alfred Perlstein 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
On 23 October 2013 11:09, Alfred Perlstein 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 change
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
On 23 October 2013 10:40, Allan Jude wrote:
> I think the point Adrian is trying to make, is that the NDISulator needs
> a maintainer, and rather than someone working on that hack, that person
> should spend their time on native drivers.
>
It's partially that.
It's also that a lot of the stuff
On 2013-10-23 13:35, Eitan Adler wrote:
> On Mon, Oct 21, 2013 at 6:29 PM, Adrian Chadd 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. Righ
On Mon, Oct 21, 2013 at 6:29 PM, Adrian Chadd 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 people work _arou
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
> release
> 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
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 dela
Is there any harm in marking it as deprecated in 10 so awareness begins
immediately? We can delay its removal beyond 11 if absolutely
necessary...
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To un
"Andrey V. Elsukov" 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 wrote:
> It's honestly about time that these were updated, fixed and/or ported to
>
On 21 October 2013 12:59, Andrey V. Elsukov 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 fallback.
>
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 fallback.
>
> There are still wifi adapters, Ethernet too, where there is
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
vend
> 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
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:
>>
>>
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
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:
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
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
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
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
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
36 matches
Mail list logo
