3 ms·

You need support from the chip manufacturers to get that done. Intel and Broadcomm hand you a binary firmware blob and tell you to go screw yourself for the mo

You need support from the chip manufacturers to get that done. Intel and Broadcomm hand you a binary firmware blob and tell you to go screw yourself for the most part. Atheros is one of the few helpful ones. The wifi support that we have now is the result of painstaking hard work. And to be honest, I use the wifi on OpenBSD fine without 802.11ac support

brynet 4y ago
> I use the wifi on OpenBSD fine without 802.11ac support But OpenBSD does have 802.11ac support*, since 7.1. :-) * On iwm(4)/iwx(4) only for now. https://www.openbsd.org/71.html https://www.openbsd.org/71.html
- busterarm 4y ago
  I'm still on 6.something sorry but that is my hardware. I should update. :-)
  - brynet 4y ago
    Yes you should, buster.
  - snvzz 4y ago
    Being one release behind is fine (and supported). 6.x is not...
    - busterarm 4y ago
      I've been moving around a lot for two years and talking about unpowered hardware.
loeg 4y ago
It's partly the driver, partly the stack, at least on FreeBSD. My understanding is the newer high-speed wifi modes use multiple channels or pairs of channels or something like that, and the 80211 stack in FreeBSD was just not built with that in mind. So retrofitting it is some work. I think there are other things like that missing still, in addition to driver support.
ksec 4y ago
>You need support from the chip manufacturers to get that done. Not speaking as an Open Source everything advocate. But I wonder how much would it cost to develop a fully open WiFi 7 and Bluetooth 5.3 Chip.
- Sirened 4y ago
  I know of at least one open implementation of a wifi and BTLE modem made by a small university research team (though I can't find it online so it may not be published yet, won't say who it is unless I can find public details). It's definitely possible but it did take a team of grad students a little over a year to tapeout, and so it'd likely be very expensive
- greyhair 4y ago
  The RF side of WiFi is hell. The modem side is work, yes, but getting the air interface to work, and then dealing with all the interference management side is a nightmare. I am not certain, but I think part of the 'blob' thing on WiFi internal implementations is to prevent someone breaking certification, particularly for the interference mitigation for things like DFS.

brynet 4y ago

> I use the wifi on OpenBSD fine without 802.11ac support But OpenBSD does have 802.11ac support*, since 7.1. :-) * On iwm(4)/iwx(4) only for now. https://www.openbsd.org/71.html https://www.openbsd.org/71.html

busterarm 4y ago
I'm still on 6.something sorry but that is my hardware. I should update. :-)
- brynet 4y ago
  Yes you should, buster.
- snvzz 4y ago
  Being one release behind is fine (and supported). 6.x is not...
  - busterarm 4y ago
    I've been moving around a lot for two years and talking about unpowered hardware.

loeg 4y ago

It's partly the driver, partly the stack, at least on FreeBSD. My understanding is the newer high-speed wifi modes use multiple channels or pairs of channels or something like that, and the 80211 stack in FreeBSD was just not built with that in mind. So retrofitting it is some work. I think there are other things like that missing still, in addition to driver support.

ksec 4y ago

>You need support from the chip manufacturers to get that done. Not speaking as an Open Source everything advocate. But I wonder how much would it cost to develop a fully open WiFi 7 and Bluetooth 5.3 Chip.

Sirened 4y ago
I know of at least one open implementation of a wifi and BTLE modem made by a small university research team (though I can't find it online so it may not be published yet, won't say who it is unless I can find public details). It's definitely possible but it did take a team of grad students a little over a year to tapeout, and so it'd likely be very expensive
greyhair 4y ago
The RF side of WiFi is hell. The modem side is work, yes, but getting the air interface to work, and then dealing with all the interference management side is a nightmare. I am not certain, but I think part of the 'blob' thing on WiFi internal implementations is to prevent someone breaking certification, particularly for the interference mitigation for things like DFS.