[Openchrome-devel] [Bug 95524] Ditching xf86-video-openchrome in favor of xf86-video-modesetting?

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=95524

--- Comment #4 from Kevin Brace <kevinbrace at gmx.com> ---
(In reply to nw9165-3201 from comment #3)
> 
> 
> No, it is not.

Okay, I can accept you explanation for now.

> 
> But since Phoronix.com has always reported about this topic in the past, I
> have Cc'ed Michael Larabel here.
> 
> Regards

At this point, there is nothing newsworthy to write about OpenChrome.
Whether you or other people like it or not, OpenChrome development lags other
more developed graphics device driver stacks by a huge margin.
Effectively, I am the only person working on OpenChrome at this point (Frank is
taking a break from the development.), and since the code itself has many
problems, it takes tremendous amount of time to figure out why stuff goes
wrong.
In terms of the development roadmap, it is something like this.

1. Stablize OpenChrome UMS code

  - Fix screen resolution change bug (a regression that happened between
Version 0.3.2 and 0.3.3)
  - Add external TMDS transmitter (VT1632A) support for DVI
  - Add dynamic IGA1 / IGA2 allocation within OpenChrome
  - Fix TV out support
  - Fix ACPI S3 State resume bug with several devices

2. Port OpenChrome UMS code to the newer DRM that supports KMS

3. Add DisplayPort and HDMI support to OpenChrome UMS code

4. Add 2D and video acceleration support when the newer DRM is used

5. Work on developing the 3D device driver stack


Some of these items in the roadmap can be done in parallel with other items
(i.e., 3D stack), but since I am the only one actively working on developing
OpenChrome, inevitably, they will be done sequentially.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/openchrome-devel/attachments/20160526/fc7586c3/attachment.html>