[Openchrome-devel] Standardizing DRM / KMS development platform for drm-openchrome

[Mario Rugiero]

Can you clarify what your proposal is exactly?
Is it stadardizing in general, or is it standardizing to one of the
mentioned versions of Ubuntu?

I personally believe the ideal situation would be to try and make the
changes gradual and get them upstream ASAP, so drm-next is probably the
better option, assuming we do stay up to date.

You would probably need to use your own version of the Openchrome driver
anyway, and the rest of the stack should remain mostly compatible, as the
userspace interface should not break between kernel releases.

Cheers,
Mario.

2016-04-07 23:43 GMT-03:00 Kevin Brace <kevinbrace at gmx.com>:

> I was finally able to install Xubuntu 14.04.4 LTS in a satisfactory
> fashion on 2 computers.
> When I installed it, I noticed that Linux 4.2 kernel was installed,
> instead of Linux 3.13 or 3.14 kernel Ubuntu 14.04 based OSes installed in
> the past.
> Apparently Canonical now aggressively updates their Linux kernels.
> As I recall from 2 weeks or so ago, the original developer of VIA
> Technologies IGP DRM / KMS module, James Simmons, was using the latest TTM
> API, and as a result, it required the use of Linux 3.18 kernel to be able
> to compile his code without errors (I tried it with Linux 3.2 kernel source
> code, and I had a miserable 6 hours trying it . . .).
> It is just my proposal, and let me know if anyone likes it.
> I happened to use Xubuntu since it has a fairly light GUI that I prefer
> for software development purposes than straight Ubuntu.
> If there is anyone else wishing to express their opinion, please feel free
> to do so.
> _______________________________________________
> Openchrome-devel mailing list
> Openchrome-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/openchrome-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/openchrome-devel/attachments/20160408/d139e6f1/attachment-0001.html>