[PATCH 2/2] drm: make DRI1 drivers depend on BROKEN

Kevin Brace kevinbrace at gmx.com
Fri Aug 26 00:19:32 UTC 2016


Hi David,

> Lets move forward and hide the remaining DRI1 drivers behind a config
> option, so we have a central place to disable them all. Furthermore, we
> can provide a clear warning to anyone enabling them.
> 
> Signed-off-by: David Herrmann <dh.herrmann at gmail.com>
> ---
>  drivers/gpu/drm/Kconfig | 135 ++++++++++++++++++++++++++++--------------------
>  1 file changed, 78 insertions(+), 57 deletions(-)
> 
> diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig
> index fc35731..d8f6203 100644
> --- a/drivers/gpu/drm/Kconfig
> +++ b/drivers/gpu/drm/Kconfig
> @@ -108,24 +108,8 @@ config DRM_KMS_CMA_HELPER
>  
>  source "drivers/gpu/drm/i2c/Kconfig"

. . . 

> +
> +config DRM_VIA
> +	tristate "Via unichrome video cards"
> +	depends on DRM && PCI
> +	help
> +	  Choose this option if you have a Via unichrome or compatible video
> +	  chipset. If M is selected the module will be called via.
> +
. . .
> +endif # DRM_LEGACY
> -- 
> 2.9.2 

I am the sole developer of OpenChrome (VIA Technologies IGP), and I do still actively develop OpenChrome DDX every day.

https://cgit.freedesktop.org/openchrome/xf86-video-openchrome

I do not want to be seen as stopping progress, but there are still people who use less than current hardware (myself and countless others) or non Big 3 x86 graphics (NVIDIA, AMD, and Intel) for things like thin clients.
In fact, I just got DVI via (no pun intended) Silicon Image SiI 164 TMDS transmitter working for one thin client user with VIA IGP. (HP T5550 thin client)

https://bugs.freedesktop.org/show_bug.cgi?id=95059#c22
https://bugs.freedesktop.org/attachment.cgi?id=126035

He uses ThinStation OS.

http://thinstation.github.io/thinstation/

Anyway, regarding the move to DRI2 / KMS so that DRI1 can be discontinued, I am not personally against it in the long run, but the work on it has stalled.

https://cgit.freedesktop.org/openchrome/drm-openchrome/

Personally, I have had issues compiling the drm-openchrome code (the newer VIA IGP DRM) with a newer Linux kernel. (tried 4.2 with little success)
If someone knowledgeable about porting the current drm-openchrome code to the latest Linux kernel can assist me in doing it, that will certainly be helpful.
One box I have (HP Pavilion a800n; AMD Athlon XP + VIA Technologies KM400A chipset) has Lubuntu 14.04 installed with drm-openchrome (Linux 3.19-rc6) compiled for it, but due to a bug I have not been able to track down yet (I do not know how to get the Linux kernel to preserve a kernel panic dump.), it will kernel panic if I try to boot Lubuntu with drm-openchrome.
Lubuntu itself will boot fine with the latest OpenChrome DDX as long as I am using the stock Linux 3.13 kernel provided by Lubuntu or drm-openchrome with ATI Technologies RAGE 128 Pro AGP.
I must note that this kernel panic appears to be specific to UniChrome IGP (this is the very early VIA IGP model), and I have personally seen drm-openchrome successfully boot Linux 3.19-rc6 with the newer UniChrome Pro and Chrome9 IGPs.
    OpenChrome DDX itself is developed so that it can be DRI1 / DRI2 and UMS / KMS selectable.
With the current OpenChrome DDX, it will disable EXA and Xv acceleration.
At this point, this is a rather poor trade off for current VIA IGP users since 2D acceleration will go off.
As for myself, I am spending pretty much all of my personal time in fixing the existing DRI1 / UMS OpenChrome DDX code, and do not have the time resources to work on porting OpenChrome to support DRI2 / KMS.
That being said, if someone can assist me in getting drm-openchrome code ported to the latest Linux kernel, then maybe I can start spending more time in getting EXA to work with DRI2, and when that is achieved, DRI1 can be retired for good.

Sincerely,

Kevin Brace
OpenChrome Project Maintainer / Developer


More information about the dri-devel mailing list