Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 Jan 2019 11:22:51 -0800
From:      Adrian Chadd <adrian.chadd@gmail.com>
To:        waddlesplash <waddlesplash@gmail.com>
Cc:        "freebsd-wireless@freebsd.org" <wireless@freebsd.org>
Subject:   Re: wireless coordination and who's working on what?
Message-ID:  <CAJ-VmokgrYSqhrsW5%2B_Uy8Pu8P=a2TUBgjLUYYC_5KXKvtMPSg@mail.gmail.com>
In-Reply-To: <CAEesM75f111pms2MMiZZQ=hRZ1p2QAOwrSvzwHEVhSAgOXPabg@mail.gmail.com>
References:  <BDD2289A-D362-48C3-8635-FBD4B0711C22@FreeBSD.org> <CAEesM75f111pms2MMiZZQ=hRZ1p2QAOwrSvzwHEVhSAgOXPabg@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
>
> Hi,
>

I'm .. mostly trying to help people. Geramy has been helping out hugely on
the ath10k port and I'm updating my laptops (again!) to the latest head so
I can continue rolling with that.

I'd like to get ath10k ready to put into the tree but there are a couple of
net80211 and driver holes that need patching for these newer firmware NICs.
(Around node creation/deletion, crypto key updates, sending frames, etc -
net80211 assumes they're all non-blocking operations but that's definitely
not true for the majority of hardware now shipping.)



-a



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokgrYSqhrsW5%2B_Uy8Pu8P=a2TUBgjLUYYC_5KXKvtMPSg>