Status of OpenChrome DRM (February 2018)

Since XDC2017 where I presented about the state of OpenChrome Project, I have made big strides towards getting OpenChrome DRM mainlined within the Linux kernel. I will go over the progress I have made since then, in addition to discussing the remaining issues that need to be resolved.

The biggest I have been able to resolve is standby resume support. This was the original reason why I started to work on OpenChrome DDX back in Year 2015. One thing I have noticed about sub-par Linux / BSD graphics device drivers, in general, is the lack of standby resume support. After spending so much time on this issue, I was able to figure out why it was not working, and was able to fix it.

There were several reasons why standby resume was not working. The biggest reason why it was not working was due to DRM not asking for a mode setting after resuming from standby. Basically, the previous developer who worked on OpenChrome DRM did not put the necessary code for a mode setting to get retriggered after standby resume. I finally put in the code to do this after analyzing Radeon DRM’s standby resume code.

Another related issue I observed after I got standby resume working on most models was with setting display FIFO. Again, the previous developer who worked on OpenChrome DRM did not put in the code to do this for CLE266 and KM400 chipsets. This is related to the fact that OpenChrome DRM did not originally contain PLL settings code for CLE266 and KM400 chipsets back in September 2016. Both of these chipsets have UniChrome (not UniChrome Pro) IGP. Due to the necessity to support rather bandwidth limited DDR200 (PC1600) DDR SDRAM, they do require fairly complicated display FIFO settings code. I did not have the actual hardware with me for several weeks, so I did not catch the regression prior to the code commit, but as of OpenChrome DRM Version 3.0.71, the issues are resolved.

Also, due to lacking access to K8M800 chipset based hardware, I caused similar display FIFO issues (i.e., wrong IGA1 display FIFO parameters), but this was fixed as of OpenChrome DRM Version 3.0.75 since I regained access to the actual hardware for testing.

Today, standby resume is working with VGA (analog) and most FPs (Flat Panel); starting with CLE266 chipset and all the way to VX900 chipset. Yes, there are some hardware out there where the standby resume is not working, but this appears to be issues unrelated to OpenChrome DRM. If I were to cite one example, I will say Averatec 3250 laptop (KN400 chipset). Regarding this troubled laptop, it also has issues with OpenChrome DDX’s mode setting code when it comes to standby resume.

Regarding the outstanding issues, I still have issues with runtime change of screen resolution. Changing the screen resolution during runtime I will talk about this in the next post, but this is the biggest outstanding issue OpenChrome has. OpenChrome DRM still lacks external DVI (TMDS) transmitter support, but this will get worked on probably in the next few months. There are still issues with FP recognition some times, and I am aware of the issue, but it will not get worked on until I fix the runtime change of screen resolution issue.

One white elephant I have not talked about is the rendering performance of OpenChrome DDX along with OpenChrome DRM. It appears to vary by the chipset, but in general, the current OpenChrome DDX along with OpenChrome DRM is way below of that of existing OpenChrome DDX running DRM free or with DRI1 based VIA DRM (only older UniChrome and UniChrome Pro devices are supported). For my main development computer (HP 2133 mini-note; VN896 chipset), the rendering performance is at an acceptable level for the OpenChrome DDX along with OpenChrome DRM, but I have noticed severe performance issues with CLE266 and VX900 chipsets. Note that this is particularly noticeable when moving a window around on the desktop screen (it is painfully slow . . .). The reason for this is really simple; OpenChrome DDX along with OpenChrome DRM does not utilize 2D acceleration hardware currently. I expect to fix this issue after OpenChrome DRM is mainlined. The previous developer appeared to be working on some code for 2D acceleration, but for the purpose of mainlining, I expect to remove the 2D acceleration support code for now (obviously, it will come back eventually).

That’s it for now.

3 thoughts on “Status of OpenChrome DRM (February 2018)

  1. hi, thanks for your work on openchrome.
    For the 2d acceleration, do you plan to use glamor like james as suggested or use exa ?
    (sorry for y bad english)

    Like

  2. Hi s3boun3t,

    At least for the purpose of Linux kernel tree maintaining, OpenChrome DRM code will not support any rendering acceleration initially.
    This is because OpenChrome DRM code was in a bad shape when I inherited the code, and getting such feature incomplete and buggy code to reliable and general release quality is in of itself a huge undertaking.
    As a result, acceleration support will be added later after mainlining.
    As for Glamor or EXA support, I will take the EXA route first since OpenChrome DDX itself contains reliable 2D acceleration code that I hope to make it work with OpenChrome DRM.
    I am open to working with Gallium 3D in order to support Glamor after that.

    Like

  3. Hi, so glad I found your blog and your presentation from last year.

    I’ve got an ongoing effort to improve the open source experience and, since I have a very old notebook with the VIA S3 chipset, it’d be important for me to have proper Linux support on it.

    Already tried many kernels and official VIA drivers for it but nothing really works, but now that I’ve seen your development I’m quite pleased. You are on the right track. Please keep it up.

    I’ve read your slides, and some points caught my attention because I’m a bit like you, mostly self-taught, with background in Electrical Engineering (though in fact I haven’t joined yet).

    Have a look at my initiative if you’d like (https://gitlab.com/ranolfi/opensource-todo-list/issues). You are mentioned in issue #81.

    Btw, I’d very much like to know how you’re able to work most of your time on this endeavor without ever getting paid for it. (I’ve yet to find a way to begin tackling on those issues in my list.)

    Please reach me by email if you feel it’s more appropriate.

    Thanks and good luck.

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s