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
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
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
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
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 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
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
Hi,
Please try this:
http://people.freebsd.org/~adrian/ath/20131023-net80211-txmgt-locking-2.diff
It implements what I think is the mostly-right fix:
* remove the node reference in the callout, it's actually not freaking
needed!
* grab the ic lock when doing the timeout callout, ensuring
Hi,
Still getting the Cannot reset interface wlan0 - exit status 1 in wifimgr
but no crash yet. Will keep trying :D
On Wed, Oct 23, 2013 at 9:51 PM, Adrian Chadd adr...@freebsd.org wrote:
Hi,
Please try this:
http://people.freebsd.org/~adrian/ath/20131023-net80211-txmgt-locking-2.diff
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 don't use wifimgr so I
Understood. Will do so.
On Wed, Oct 23, 2013 at 10:12 PM, Adrian Chadd adr...@freebsd.org wrote:
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
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
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
What is the best way to restart a wireless stack?
A command ifconfig wlan0 create wlandev ath0 starts the wpa_supplicant
by itself. It means that the netif script runs the wpa_supplicant twice,
always. Is it ok?
There is my debug during booting:
[netif.network_common()] START:
.. that needs to be fixed. It definitely shouldn't be started twice!
-adrian
On 23 October 2013 16:56, clutton clut...@zoho.com wrote:
What is the best way to restart a wireless stack?
A command ifconfig wlan0 create wlandev ath0 starts the wpa_supplicant
by itself. It means that the
Hi,
Ok. I've reviewed this stuff in more depth.
Split-6 is still way too big to commit as one commit.
I was also hoping that we could get the updated hardware support into this
without necessarily adding the PAN support. But, you're the one driving
this, so it's up to you. :)
* There's
.. and I've just done the if_iwn_debug.h stuff, so you should update your
patchset to include that.
Thanks,
-adrian
On 23 October 2013 17:43, Adrian Chadd adr...@freebsd.org wrote:
Hi,
Ok. I've reviewed this stuff in more depth.
Split-6 is still way too big to commit as one commit.
IT's not. It's devd doing something dumb.
-a
On 23 October 2013 21:30, clutton clut...@zoho.com wrote:
Indeed.
I have looked at a sys/net80211 and at a sys/dev/ath.
But I still have no idea which one triggers rc script and how on the
earth it can be done.
On Wed, 2013-10-23 at 16:57
18 matches
Mail list logo
