2560x1440@60Hz has a pixel clock of 241.5 MHz, TMDS clock of 2.415 GHz, and suddenly your Raspberry Pi 4 can't use 2.4GHz WiFi and 1440p at the same time, because EMI is hard. I guess the RPi foundation *still* can't design hardware. https://www.enricozini.org/blog/2019/himblick/raspberry-pi-4-loses-wifi-at-2560x1440-screen-resolution/ …
-
This is if course the basic flaw of ISM band communication being widely adopted
This has nothing to do with wide adoption of the band. HDMI isn't a wireless protocol. It could've happened with any other band at the corresponding pixel clock.
-
-
Sorry, licensed bands come with their own restrictions but mostly not the hard EI tolerance/emission ones that restrict WiFi to an EIRP of +35dbm (4 watts) which means a 6dbi dipole is limited to 1W & an 18dbi dipole to 63mW Many unintentional emitters can easily overpower that
-
You wouldn't want to be pumping out more power anyway. The RPi barely gets 10W to run the whole thing, best case. Never mind battery-powered devices!
- Show replies
New conversation -
-
-
Isn't there a similar problem with USB3 ports and 2.4GHz WiFi and mouse/keyboard dongles?
-
Intel has an app note IIRC detailing how some USB3 ports may cause spurious 2.4 interference when operating as a SuperSpeed port
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.