Action Item #128
Add support for hardware accelerated X.org
|Status:||Closed||Start date:||07 Nov 2012|
|Category:||04 - Root File System|
|Severity:||02 - High
Not sure if this support already exists. If not, fallback to software enabled or perhaps frame buffer driver.
RM #128: Added hardware accelerated X.org driver to build. Driver is not stable so it's not being used yet.
RM #128: fbturbo seems to work better with the new 3.10.y kernel than it did with 3.2.27 so I've made it the default.
- Priority changed from Immediate to Normal
- % Done changed from 0 to 50
- Severity changed from High to Medium
There is no hardware accelerated X for Raspberry Pi at this time.
I updated the xorg.conf file and switched the xinitrc to blackbox. X now starts correctly using the fbdev driver.
I'll leave this one open until a hardware accelerated driver arrives.
- Severity changed from Medium to 03 - Medium
- Target version changed from 0.3.0 to 1.0 - Atreides
- Target version changed from 1.0 - Atreides to 2.0 - Harkonnen
- Priority changed from Normal to Urgent
- Target version changed from 2.0 - Harkonnen to 0.8.0
- Status changed from New to In Progress
- % Done changed from 50 to 70
Built a buildroot package for it and did a test build. Builds okay with mods for buildroot xorg config (xf86driproto).
Tested on hardware and it comes up fine. Verified it was working in Xorg.log.0. Not sure if 3D is working but 2D acceleration should be there. Don't see great difference in starting surf, however. It still runs slow.
Need to verify complete and current buildroot build works with new package. Then I can check in updates for the new driver, including updating the xorg.conf to use it.
Left the driver running overnight and found that the display was partially unrefreshed. Hitting a keystroke (shift key) refreshed it.
- Target version changed from 0.8.0 to 1.0 - Atreides
Pushing this to later release to give driver time to become more stable.
- Target version changed from 1.0 - Atreides to 0.9.0
Moving to 0.9 to test updates to the driver with newer kernel/gcc/glibc and rootfs.
- Priority changed from Urgent to Immediate
- Severity changed from 03 - Medium to 02 - High
Building for 3.10.y - there are currently no updates to the project so this is the same code that was less stable than the standard fbdev with the 3.2.27 kernel.
Also, there is an alternative X.org driver with additional information on using it at eLinux.org.
Doh - the driver was already enabled and built. It just wasn't used in the xorg.conf. I've switched to it and will let it sit for a while to see what happens.
After one screen blanking, a keypress brought it back without problem. I'm going to reboot and test if the keyboard is available on first boot (instead of requiring an Xorg restart) and then let it sit overnight and see if its still okay in the morning.
Xorg still requires a restart on first boot with fbturbo and 3.10.31+.
Leaving overnight to see if driver is okay after long time unattended.
- Status changed from In Progress to Closed
- % Done changed from 70 to 100
Seems to still be working just fine. I've made it the default for now.
Closing issue. If the driver causes problems I can reopen it.
Also available in: Atom