From: Heiko Stuebner <heiko@sntech.de>
To: Randy Li <randy.li@rock-chips.com>
Cc: dri-devel@lists.freedesktop.org, tfiga@chromium.org
Subject: Re: About the Xserver for rockchip
Date: Mon, 17 Oct 2016 09:12:51 +0200 [thread overview]
Message-ID: <2490297.1T3pOKgAFM@phil> (raw)
In-Reply-To: <53687eb1-2d6b-9589-6407-5b682cd9124d@rock-chips.com>
Am Montag, 17. Oktober 2016, 14:45:30 CEST schrieb Randy Li:
> Hello Tomasz:
> Heiko told me you are in charge of the graphics part of chromium, I
> think I had better told you the developing status of the xorg xserver in
> rockchip.
What I actually said was that Tomasz did the original VPU driver used on
veyron chromebooks, so may be interested in your current work on that :-) .
Also ChromeOS moved from X11 to use Freon instead, so I'm not sure if ChromeOS
cares about that anymore.
> Currently the graphics department released a modification
> version of xserver which would support the libMali, but the way to
> support it is some kind of hacker which disabled the original mesa gl
> support.
> https://github.com/rockchip-linux/xserver/commit/bae12718e76d50d7388a93a251e
> f6777f6ca4850#diff-92a9ba7d51895d2d69c5c893fa0f658dL792
>
> Since the code base of that is really a mess, I rebase the branch
> rockchip with the xserver branch 1.18 from upstream, it is there
> https://github.com/rockchip-linux/xserver/tree/rockchip-1.18
> But the version I made would omit some pixels when it is drawing, I have
> not found out why.
Didn't Mark do a lot of changes on your xserver, so maybe he knows what might
be going wrong?
Heiko
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-10-17 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 6:45 About the Xserver for rockchip Randy Li
2016-10-17 7:12 ` Heiko Stuebner [this message]
2016-10-17 8:02 ` Mark yao
2016-10-17 8:34 ` Randy Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2490297.1T3pOKgAFM@phil \
--to=heiko@sntech.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=randy.li@rock-chips.com \
--cc=tfiga@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox