framebuffer not working

Open
#1,976 36 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
raspberry-pi
Domain
embedded-iot

Research direction

The issue mentions the framebuffer node in the start;s FDT, HDMI output, U-Boot, and possible VC4 involvement; begin by tracing how those components expose the framebuffer. Done means establishing whether the framebuffer can be tied to HDMI and used to write custom splash-screen data from U-Boot.

Written by the indexing model from the issue text.

Description

the framebuffer node in start;s fdt is not tied to the video output HDMI.
I can't do anything with it from u-boot. Guessing I need some vc4 magic to make it actually work ? The rainbow screen works, but I can't write my own data for a splash screen.
What can I do ?

Dominant language
No language data
Stars
5.6k
Forks
1.7k
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/firmware

All issues in raspberrypi/firmware

Similar issues

More Embedded & IoT issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.