I'm trying to compile that in the kernel for some reasons related to startup optimization.
The kernel sees them, and compiles them, and it WORKS with other things requiring a firmware like i915 with the HuC and the GuC, but not for regulatory.db
> you could probably send a weaker signal from mobile devices and drown the air with signal from anything plugged into a wall socket.
How exactly is your mobile device going to ACK those received packets? The mobile device needs to transmit as loudly as the AP for its ack to be received.
Boosting the transmit power higher than your receiving device can transmit leads to very bad wifi links, where the mobile device is receiving a good signal but it's own messages are not received back.
You can use different modulation rates to/from a device (this commonly happens). Lower modulation rates give you better SNR, letting your quiet client do slow weak ACKs to loud large chunks of data from the router.
> I'm not sure what hardware capabilities you think are poorly supported by OpenWRT or the open-source drivers for the known-good hardware choices from the QCA lineage or Mediatek's mt76 family. Can you provide any specifics?
I can't speak for them, but I've used OpenWRT on routers with Broadcom chipsets, so I think they were saying that OpenWRT support isn't a good litmus test for drivers that support the full functionality of the hardware they're for.
I specifically said "well-supported by OpenWRT", because even the most cursory investigation of what hardware works well with OpenWRT will warn you away from buying Broadcom.
Thanks! Apologies. Thanks thanks thanks. I edited the post after your posting. Thanks thanks thanks.
I also didn't know at the time this was limited to AP mode. Still, it being bad for so long is ultra-embarassing. I sincerely appreciate the correction. My bad.
12 comments
[ 7.7 ms ] story [ 38.1 ms ] threadThe kernel sees them, and compiles them, and it WORKS with other things requiring a firmware like i915 with the HuC and the GuC, but not for regulatory.db
How exactly is your mobile device going to ACK those received packets? The mobile device needs to transmit as loudly as the AP for its ack to be received.
Boosting the transmit power higher than your receiving device can transmit leads to very bad wifi links, where the mobile device is receiving a good signal but it's own messages are not received back.
I can't speak for them, but I've used OpenWRT on routers with Broadcom chipsets, so I think they were saying that OpenWRT support isn't a good litmus test for drivers that support the full functionality of the hardware they're for.
I also didn't know at the time this was limited to AP mode. Still, it being bad for so long is ultra-embarassing. I sincerely appreciate the correction. My bad.