From: Nicola Girardi <ng@0x80.stream>
To: 9front@9front.org
Subject: Re: [9front] Question re: RPI video performance
Date: Sat, 03 Dec 2022 09:48:59 +0000 [thread overview]
Message-ID: <6478B4AA38F595473D457BB5FF53FFBA@cirno> (raw)
In-Reply-To: <6A82C1CB-8E86-4872-9F6A-5C150B6AD773@ftrv.se>
Sigrid Solveig Haflínudóttir <sigrid@ftrv.se> wrote:
> Could be related to the framebuffer format. Check "aux/zerotrunc </dev/screen". Try to switch to a different format via config.txt(?), especially if your current mode is 16-bit.
Interesting. I had only configured the mode using hdmi_mode=82 in
config.txt and got r5g6b5 as output to your command. I now realize I
can additionally set vgasize in cmdline.txt to 1920x1080x32, then I
get
; read -c 60 /dev/screen
x8r8g8b8 0 0 1920 1080
Slow as before. Tried many other modes in the past month, and even
640x350 behaves in the same way I'd described earlier.
One thing I noticed in the config.txt provided by 9front is that
gpu_mem is set to 16, while the default is 64. As a total hunch I
tried to increase that value to 64 but then the RPI doesn't boot (or
boots, but screen is blank so I don't know :-)).
I can accept the behavior, it's just I'd like to understand more. I
tried to understand something from the git history but failed.
next prev parent reply other threads:[~2022-12-03 9:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 14:49 Nicola Girardi
2022-12-02 16:21 ` Sigrid Solveig Haflínudóttir
2022-12-03 9:48 ` Nicola Girardi [this message]
2022-12-03 10:02 ` Steve Simon
2022-12-03 11:12 ` Nicola Girardi
2022-12-03 11:53 ` Steve Simon
2022-12-03 16:13 ` Nicola Girardi
2022-12-05 17:00 ` Nicola Girardi
2022-12-03 16:13 ` Eckard Brauer
2022-12-04 18:53 ` Kristo
2022-12-04 20:11 ` Nicola Girardi
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=6478B4AA38F595473D457BB5FF53FFBA@cirno \
--to=ng@0x80.stream \
--cc=9front@9front.org \
/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).