-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
configs: arm64/bcm2711: Enable V3D #3063
Conversation
drivers/gpu/drm/v3d/Kconfig
Outdated
@@ -1,6 +1,6 @@ | |||
config DRM_V3D | |||
tristate "Broadcom V3D 3.x and newer" | |||
depends on ARCH_BCM || ARCH_BCMSTB || COMPILE_TEST | |||
depends on ARCH_BCM || ARCH_BCMSTB || ARCH_BCM2835 || COMPILE_TEST |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The arm64 bcm2711_defconfig should defiine ARCH_BCM=y, like the 32-bit version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ARCH_BCM wasn't defined at all for arm64, so I added it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please keep your original change by adding ARCH_BCM2835.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you still want ARCH_BCM to be defined?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is necessary.
This allows for 3d acceleration with a 64bit kernel on the Pi 4. ARCH_BCM wasn't defined at all for arm64, so I copied it over from arm. The PM driver is now default for BCM2835
Seems to work well! I have added this PR to my bcm2711-kernel-bis weekly autobuild pro tem, until it is merged upstream. A prebuilt release tarball may be downloaded here. Screenshot (64-bit Gentoo userland, also has #3144 applied for bounce buffers / 4GiB RAM): Thanks, sakaki |
@lategoodbye requested the use of ARCH_BCM2835 instead rather than ARCH_BCM, which makes for a smaller commit, but the end result is the same. |
@sakaki- Hi, could you please help me with the problem here? I cannot figure it out. |
What problem? |
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Thanks, @phire - I've merged the simpler (ARCH_BCM2835) version of your patch. |
With a typo in the commit title. Ho hum. |
@pelwell, I think, looking at the screenshot, what @yrzr means that he isn't getting Well, a little OT ^-^, but the issue here is userland, not kernel: The line you need to add to your hth, sakaki |
@sakaki- Thanks for your replay. I have already used the ebuild from your overlay and enabled video_cards_vc4. Still wondering what I have missed.
|
@yrzr, |
Superseded by fc5826f, but thanks for submitting. |
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: raspberrypi#3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: raspberrypi#3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: raspberrypi#3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: raspberrypi#3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
BugLink: https://bugs.launchpad.net/bugs/1958146 Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: raspberrypi/linux#3063 Signed-off-by: Phil Elwell <[email protected]> (cherry picked from commit 8e4686368d52cc2faf82923e71d9e29ce5850403 rpi-5.15.y) Signed-off-by: Juerg Haefliger <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: raspberrypi#3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: raspberrypi#3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: raspberrypi#3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: #3063 Signed-off-by: Phil Elwell <[email protected]>
Enable the V3D driver, which depends on BCM2835_POWER. Originally submitted by GitHub user 'phire' in a slightly different form. See: raspberrypi/linux#3063 Signed-off-by: Phil Elwell <[email protected]>
This allows for 3d acceleration with a 64bit kernel on the Pi 4.
I tested with the existing 32bit raspbian run time. I assume it will work with a 64bit run time once you recompile mesa.
Relates to #3032