From: Bakul Shah <bakul@iitbombay.org>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Raspberry Pi 4 stability dependent in RAM
Date: Sat, 14 Nov 2020 08:58:46 -0800 [thread overview]
Message-ID: <E1439B8B-A098-4645-A660-22EBB47E86FD@iitbombay.org> (raw)
In-Reply-To: <CAFSF3XP5JjfQkKbiq+7_5arSLERHr4VgegjKezR1YGzRAZ-m8A@mail.gmail.com>
There were reports of 2560x1440 res generating RF noise in the 2.4GHz band wifi channel 1. The proposed solution (by Eben Upton) was to use channel 4 or higher or use 5GHz wifi band at this res. And supposedly there is a firmware fix for this. No idea about the bluetooth issue. You should report these issues either on their forum or one of their github repos.
> On Nov 14, 2020, at 7:14 AM, hiro <23hiro@gmail.com> wrote:
>
> well, for me hdmi reliably stops working when i turn on the bluetooth
> keyboard and versa.
> clearly RF interference was none of their concern when they made this chip.
> if your monitor suggests a different pixel clock you might get lucky
> and it's just good enough, but your signal quality is gonna suffer no
> matter what
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Te91377223453b8c0-Mcf9b9e5189fa9b42b00a6193
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2020-11-14 16:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 0:30 a
2020-11-14 0:56 ` a
2020-11-14 9:35 ` Richard Miller
2020-11-14 11:14 ` Steve Simon
2020-11-14 11:24 ` Richard Miller
2020-11-14 14:48 ` hiro
2020-11-14 15:05 ` Richard Miller
2020-11-14 15:12 ` hiro
2020-11-14 16:58 ` Bakul Shah [this message]
2020-11-14 18:12 ` hiro
2020-11-22 10:48 ` hiro
2020-11-23 22:46 ` [9fans] node-red Bakul Shah
2020-11-14 15:29 ` [9fans] Raspberry Pi 4 stability dependent in RAM Richard Miller
2020-11-14 16:15 ` hiro
2020-11-14 11:24 ` Richard Miller
2020-11-18 23:13 ` Anthony Sorace
2020-11-19 0:15 ` Thaddeus Woskowiak
2020-11-19 7:37 ` Steve Simon
2020-11-19 8:27 ` Skip Tavakkolian
2020-11-20 23:05 ` Stuart Morrow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1439B8B-A098-4645-A660-22EBB47E86FD@iitbombay.org \
--to=bakul@iitbombay.org \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).