Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KMSDRM video backend doesn't support multiple displays #3892

Closed
SDLBugzilla opened this issue Feb 11, 2021 · 5 comments
Closed

KMSDRM video backend doesn't support multiple displays #3892

SDLBugzilla opened this issue Feb 11, 2021 · 5 comments
Assignees
Milestone

Comments

@SDLBugzilla
Copy link
Collaborator

This bug report was migrated from our old Bugzilla tracker.

Reported in version: 2.0.12
Reported for operating system, platform: Linux, ARM

Comments on the original bug report:

On 2020-11-24 13:13:44 +0000, wrote:

Hi,

SDL (SDL_GetNumVideoDisplays) does not recognize the second display on a raspberry pi 4 when running with no X11(kmsdrm video driver). Higher level libraries,like pygame thus can not assign a display for particular output.

More information can be found here.

pygame/pygame#2356

Thanks

On 2020-11-24 13:31:49 +0000, Dan Lawrence wrote:

You can see that the kmsdrm driver is just assuming a single display here, in multiple lines like this one:

dispdata = (SDL_DisplayData *)SDL_GetDisplayDriverData(0); //viddata->devindex);

meanwhile other video drivers that do have multi_display support do things like:

SDL_DisplayData *pData =(SDL_DisplayData*)SDL_GetDisplayDriverData(displayIndex);

Looking back on this thread when the driver was first created:

https://discourse.libsdl.org/t/kms-drm-context-for-the-gl-gles-renderer/21813/11

it seems it was discussed and multiple displays being 'out of scope' was mentioned.

On 2020-11-24 15:37:16 +0000, Sam Lantinga wrote:

Multiple displays are no longer out of scope. I don't have a test setup for this, does anyone have a patch they'd like considered for inclusion that supports this?

@SDLBugzilla SDLBugzilla added bug waiting Waiting on user response labels Feb 11, 2021
@icculus icculus self-assigned this Feb 14, 2021
@icculus
Copy link
Collaborator

icculus commented Feb 14, 2021

Gonna assign this to myself but I don't know when I'll get to it quite yet, in case someone wants to steal it...but I do have a need for this in the relatively near future.

@icculus icculus removed the waiting Waiting on user response label Feb 14, 2021
@icculus icculus changed the title Raspberry pi 4 won't recognize the second display (kmsdrm video driver) KMSDRM video backend doesn't support multiple displays Feb 14, 2021
@icculus icculus added enhancement New feature or request and removed bug labels Feb 14, 2021
@MakerMatrix
Copy link

MakerMatrix commented Aug 6, 2021

I have a need for this as well. A simple touch UI on DSI, controlling an application displaying over one or more HDMI screens. X just adds unnecessary bloat and configuration to make it clean since there can be no desktop in this app. The purposely-limited touchscreen is the only HMI.

But, right now, I cannot get KMSDRM to work at all on Pi3b+ (2.0.16) for unknown reasons. Probably PEBKAC.

Edit: perhaps not PEBKAC?: pygame/pygame#2356

@slouken slouken added this to the 3.2.0 milestone Nov 7, 2023
@icculus icculus removed the enhancement New feature or request label Oct 6, 2024
@icculus
Copy link
Collaborator

icculus commented Oct 6, 2024

I think this is implemented now, but I'll try it on a RPi5 just to verify before we close this.

@slouken slouken modified the milestones: 3.2.0, 3.4.0, 2.32.0 Jan 16, 2025
@icculus icculus added the icculus-priority Things @icculus is looking at within a larger milestone. label Jan 16, 2025
@icculus
Copy link
Collaborator

icculus commented Jan 19, 2025

I got a second micro-HDMI connector, but I can't coerce this Pi5 to see both screens, SDL or otherwise.

Gonna try to drag a second actual TV over there tomorrow and see if it just doesn't like the random HDMI display from temu.com I threw at the one connector.

@icculus
Copy link
Collaborator

icculus commented Jan 19, 2025

trim.17365CAD-287C-41F3-8995-BD81D3B52957.MOV

@icculus icculus closed this as completed Jan 19, 2025
@icculus icculus removed the icculus-priority Things @icculus is looking at within a larger milestone. label Jan 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants