Skip to content

Conversation

@W-Mai
Copy link
Contributor

@W-Mai W-Mai commented Feb 4, 2026

Note: Please adhere to Contributing Guidelines.

Summary

Enhance fbdev mmap handling to support both consecutive and
non-consecutive
memory layouts. The implementation now correctly calculates memory
offsets
and performs mmap operations for the second framebuffer plane based on
the
physical memory addresses returned by the driver.

Key changes:

  • Retrieve physical memory addresses for both display planes
  • Detect consecutive vs non-consecutive memory layouts
  • Calculate proper offset for mmap operations
  • Adjust framebuffer length based on memory layout
  • Improve error handling and resource cleanup

Impact

N/A

Testing

N/A

Copy link
Contributor

@cederom cederom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @W-Mai :-)

  • Please update PR description according to Contributing Guide (you can see that in the PR template).
  • Please update git commit title examples/fb: ...
  • Please remember to provide runtime logs.
  • Build error.. a glitch?

Enhance fbdev mmap handling to support both consecutive and
non-consecutive
memory layouts. The implementation now correctly calculates memory
offsets
and performs mmap operations for the second framebuffer plane based on
the
physical memory addresses returned by the driver.

Key changes:
- Retrieve physical memory addresses for both display planes
- Detect consecutive vs non-consecutive memory layouts
- Calculate proper offset for mmap operations
- Adjust framebuffer length based on memory layout
- Improve error handling and resource cleanup

Signed-off-by: xinbingnan <xinbingnan@xiaomi.com>
@W-Mai W-Mai changed the title fb: support for complete non-/consecutive fbdev mmap processing examples/fb: support for complete non-/consecutive fbdev mmap processing Feb 4, 2026
@W-Mai W-Mai marked this pull request as draft February 4, 2026 08:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants