master/sys/dev/rtwn/pci/rtwn_pci_attach.h
However, since 8192CE is supported, perhaps adding 8192EE is not so
difficult (however, I am not very familiar with rtwn.)
-waddlesplash
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/ma
; if we had a way to
specifically earmark funding for WiFi, and only WiFi (or at least, WiFi
plus less-maintained ethernet drivers), I could petition our Inc. to
donate, and the community at large, too. It wouldn't be a lot, but if you
are only part-time anyway, perh
.
You're a little late to the party:
https://github.com/freebsd/freebsd/commit/57f16e900dfc21dc7ed636d71e4e19b0a43da1d0
:)
-waddlesplash
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To uns
ed by iwm, yes. 802.11ac is definitely not
implemented and I don't think anyone's working on it either.
-waddlesplash
___
freebsd-wireless@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscr
FlyBSD changes (ivadasz' work,
not mine) which refactor quite a bit of iwm's firmware and device
state tracking code, and bring a lot of it closer to Linux's behavior.
This might be relevant to your work?
-waddlesplash
___
freebsd-wireles
p;status=new&status=reopened&type=bug&component=%5EDrivers%2FNetwork&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&desc=1&order=id
-waddlesplash
___
freebsd-wireless@freebsd.org mailing
a while and a good amount
of assistance to figure out.)
Anyway, thanks for the help so far, and thanks for a (mostly) portable
net80211 stack!
-waddlesplash
[1]: https://www.haiku-os.org/
[2]:
https://git.haiku-os.org/haiku/commit/?id=af8988cdb6664339b2958b32863554c70d2fe76f