Re: AR934x initial support is now in the tree

2013-10-16 Thread Thomas Mueller
> The initial AR934x support is now in the tree. Is there any relation between AR934x chip and AR9271? MSI M77 MPOWER motherboard has this chip (quasi-USB wireless) as well as Realtek 8111E Ethernet which doesn't work with FreeBSD or OpenBSD but good with NetBSD-current and Linux. I'd like to

RE: [IWN] Review

2013-10-16 Thread Cedric GROSS
Hello Adrian, It’s up to you. If you wish to continue commit small part review split_6, split_7 and split_8. Or directly test and commit split_8. >From split_8, it’s remaining Sean’s work : - Led management - Power supply management After that, freebsd repo will be

Re: AR934x initial support is now in the tree

2013-10-16 Thread Adrian Chadd
The AR9271 is a USB-connected AR9285, for all intents and purposes. So it would use ath(4), if ath(4) had the required USB glue. Sorry. -adrian On 16 October 2013 00:32, Thomas Mueller wrote: > > The initial AR934x support is now in the tree. > > Is there any relation between AR934x chip

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

2013-10-16 Thread Ulrich Spörlein
Hey, I'm running this small -CURRENT box as router/AP and it has a miniPCI ath(4) card that typically works fine, it only reports the occasional ath0: stuck beacon; resetting (bmiss count 4) not sure if that is problematic, the wifi used to work fine. If that message is harmless, maybe it should

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

2013-10-16 Thread John Nielsen
On Oct 16, 2013, at 11:29 AM, Ulrich Spörlein wrote: > Hey, I'm running this small -CURRENT box as router/AP and it has a > miniPCI ath(4) card that typically works fine, it only reports the > occasional > > ath0: stuck beacon; resetting (bmiss count 4) > > not sure if that is problematic, the

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

2013-10-16 Thread Adrian Chadd
Right. There's different Mac addresses. Then him.. Wonder whether I should make staggered beacons optional. Burst beacons work better but I will need to do surgery... Adrian On Oct 16, 2013 2:03 PM, "John Nielsen" wrote: > On Oct 16, 2013, at 11:29 AM, Ulrich Spörlein > wrote: > > > Hey, I'm ru

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

2013-10-16 Thread Adrian Chadd
.. and there aren't currently any USB fobs that work rock solid in AP mode in 5GHz. Sorry. -adrian ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireles

Re: AR934x initial support is now in the tree

2013-10-16 Thread Thomas Mueller
> The AR9271 is a USB-connected AR9285, for all intents and purposes. > So it would use ath(4), if ath(4) had the required USB glue. > Sorry. > -adrian NetBSD-current seems to support AR9271, so maybe the required USB glue is not too far away? I haven't set it up yet, so can't see if

Re: AR934x initial support is now in the tree

2013-10-16 Thread Adrian Chadd
Where in their repo is the AR9271 support? -adrian On 16 October 2013 14:18, Thomas Mueller wrote: > > The AR9271 is a USB-connected AR9285, for all intents and purposes. > > > So it would use ath(4), if ath(4) had the required USB glue. > > > Sorry. > > > > -adrian > > NetBSD-current seems

Re: AR934x initial support is now in the tree

2013-10-16 Thread Adrian Chadd
oh, it's the athn port from openbsd. Sure, if someone ports the USB glue from that over, but glues it into our ath driver and ath_hal code, I'll commit it. The only bits are: * usb probe/attach * usb command send/receive * basic register read/write ops * HTC commands (new station, del station, ra

Re: AR934x initial support is now in the tree

2013-10-16 Thread Thomas Mueller
> Where in their repo is the AR9271 support? > -adrian AR9271 support in NetBSD-current is in the kernel source. In $SRCDIR/sys/dev/usb I see, among many other source-code files, if_athn_usb.c if_athn_usb.h Device falls under athn. You can do man athn. NetBSD man pages are