Even after 20 years, the Matrox G200 series is still an excellent 2d graphics card. Unfortunately, there's only an fbdev driver and a user-space driver. Both are obsolete, as modern Linux uses the DRM framework for managing graphics cards. There already is a DRM driver for the G200 server series. This driver is under-maintained and doesn't work with desktop chips.

I intend to work on a DRM driver for the G200 during the hackweek. Let's see how far one can get within a few days. :)

Looking for hackers with the skills:

kernel graphics

This project is part of:

Hack Week 17

Activity

  • almost 2 years ago: ptesarik added keyword "kernel" to Create a DRM driver for Matrox G200
  • almost 2 years ago: ptesarik added keyword "graphics" to Create a DRM driver for Matrox G200
  • almost 2 years ago: ptesarik joined Create a DRM driver for Matrox G200
  • almost 2 years ago: ptesarik liked Create a DRM driver for Matrox G200
  • almost 2 years ago: tdz started Create a DRM driver for Matrox G200
  • almost 2 years ago: mbrugger liked Create a DRM driver for Matrox G200
  • almost 2 years ago: mwilck liked Create a DRM driver for Matrox G200
  • almost 2 years ago: tdz originated Create a DRM driver for Matrox G200

  • Comments

    • ptesarik
      almost 2 years ago by ptesarik | Reply

      G200 is also found in Fujitsu Primergy. Anyway, having a DRM driver sounds like a good step towards a unified graphics stack.

    • tdz
      almost 2 years ago by tdz | Reply

      Oh, interresting! I found this: http://www.fujitsu.com/de/products/computing/servers/primergy/os/linux/suse/ and it specifically mentions Primergy. Do we have one of these devices around for testing?

      My plan is to start with desktop cards (because I can do that locally) and at some point merge support for the server. The differences are minor. I mentioned this earlier, the current server-chipset driver is under-maintained and not up to today's DRM. Having desktop support should also help to keep this maintained for the longer term.

    • tdz
      almost 2 years ago by tdz | Reply

      From some earlier spare-time work, I already have the power-up code and the DDC code. Next is memory mgmt and modesetting.

    • tdz
      almost 2 years ago by tdz | Reply

      Here's what's there so far, not cleaned up:

      https://gitlab.suse.de/tdz/linux/tree/mga-kms

    • tdz
      over 1 year ago by tdz | Reply

      Here's the state after day 1; not cleaned up:

      https://gitlab.suse.de/tdz/linux/tree/mga-kms-day1

      It can do DDC and power-up the device if the BIOS didn't already do so. The fbdev tries to initialize a video mode, but the actual modesetting code is not yet present.

    • tdz
      over 1 year ago by tdz | Reply

      The state of the driver after day 2 is at

      https://gitlab.suse.de/tdz/linux/tree/mga-kms-day2

      I've added code for computing a mode's required memory bandwidth and VCLK (actually Pixel PLL config). This is part of the check-phase of applying a mode. The commit phase is next. Once that works, a lot of clean-up will have to be done.

    • tdz
      over 1 year ago by tdz | Reply

      The state of the driver after day 3 is at

      https://gitlab.suse.de/tdz/linux/tree/mga-kms-day3

      I didn't make much visible progress today, as I was busy with debugging and reading code in the DRM framework.

    Similar Projects

    Mainline Sunplus Plus1 SP7021 kernel for Banana Pi F2S by a_faerber

    The recent Banana Pi BPI-F2S board features a n...


    openSUSE/SLE/Mainline U-boot for some not-yet-supported ARM64 boards by ldevulder

    The Khadas VIM (http://khadas.com/vim/) is an a...


    netlink interface for ethtool by mkubecek

    There seems to be an overall consensus that the...


    ethtool ops for netdevsim by mkubecek

    This can be seen as a subproject of [ethtool ne...


    Support for DRM platform drivers by tdz

    This project could get us rid of the last fbdev...


    Support for DRM platform drivers by tdz

    This project could get us rid of the last fbdev...