[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-panel-devel
Subject: D9495: Properly detect Gallium drivers with newer Mesa
From: Fabian Vogt <noreply () phabricator ! kde ! org>
Date: 2017-12-25 11:08:36
Message-ID: 20171225110836.86142.109348E5F252D276 () phabricator ! kde ! org
[Download RAW message or body]
fvogt added a comment.
Restricted Application edited projects, added KWin; removed Plasma.
In https://phabricator.kde.org/D9495#182983, @graesslin wrote:
> In https://phabricator.kde.org/D9495#182931, @lbeltrame wrote:
>
> > > I consider detecting for newer driver a feature.
> >
> > That might make things more difficult for downstreams, however.
>
>
> Yes, of course. That's an issue which has created problems for me for years. KWin \
releases and mesa releases are not synced. This results in KWin not having a chance \
to be tested against latest Mesa. Distros combine these things. Like here openSUSE \
apparently combines a two year old KWin with a new Mesa.
Yes, it was decided that the latest Mesa for Leap is useful for newer hardware. Not \
uncommon, I suppose.
Note that I'm mostly asking for Plasma/5.11 here. When KWin 5.11 got released, Mesa \
already had this behaviour. So it has always been broken.
> Backporting is even more an issue. Because other distros might not have the new \
driver versions. And some changes in the past have been mutual exclusive.
This commit isn't.
> If such issues happen KWin master must be changed to require the newer Mesa \
version and explicitly break compatibility with older Mesa.
Well, you can get the mesa version at runtime, so this can't really happen. It's \
ugly, but solvable.
> In the end the problem here is not that KWin code needs to be adjusted, but that \
Mesa devs still don't get that their version and renderer information is considered \
by downstreams as part of an API.
Yes, but until that is the case, ignoring the problem isn't a workaround.
REPOSITORY
R108 KWin
BRANCH
Plasma/5.8
REVISION DETAIL
https://phabricator.kde.org/D9495
To: fvogt, #plasma, graesslin
Cc: lbeltrame, kwin, plasma-devel, #kwin, bwowk, ZrenBot, progwolff, lesliezhai, \
ali-mohamed, hardening, jensreuterberg, abetts, sebas, apol, mart
[Attachment #3 (unknown)]
<table><tr><td style="">fvogt added a comment.<br />Restricted Application edited \
projects, added KWin; removed Plasma. </td><a style="text-decoration: none; padding: \
4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; \
border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to \
bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" \
href="https://phabricator.kde.org/D9495" rel="noreferrer">View \
Revision</a></tr></table><br /><div><div><blockquote style="border-left: 3px solid \
#8C98B8; color: #6B748C;
font-style: italic;
margin: 4px 0 12px 0;
padding: 8px 12px;
background-color: #F8F9FC;">
<div style="font-style: normal;
padding-bottom: 4px;">In <a href="https://phabricator.kde.org/D9495#182983" \
style="background-color: #e7e7e7; border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;" rel="noreferrer">D9495#182983</a>, <a \
href="https://phabricator.kde.org/p/graesslin/" style=" border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;" rel="noreferrer">@graesslin</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><blockquote style="border-left: 3px solid \
#8C98B8; color: #6B748C;
font-style: italic;
margin: 4px 0 12px 0;
padding: 8px 12px;
background-color: #F8F9FC;">
<div style="font-style: normal;
padding-bottom: 4px;">In <a href="https://phabricator.kde.org/D9495#182931" \
style="background-color: #e7e7e7; border-color: #e7e7e7;
border-radius: 3px;
padding: 0 4px;
font-weight: bold;
color: black;text-decoration: none;" rel="noreferrer">D9495#182931</a>, <a \
href="https://phabricator.kde.org/p/lbeltrame/" style=" border-color: #f1f7ff;
color: #19558d;
background-color: #f1f7ff;
border: 1px solid transparent;
border-radius: 3px;
font-weight: bold;
padding: 0 4px;" rel="noreferrer">@lbeltrame</a> wrote:</div>
<div style="margin: 0;
padding: 0;
border: 0;
color: rgb(107, 116, 140);"><blockquote style="border-left: 3px solid \
#a7b5bf; color: #464c5c; font-style: italic; margin: 4px 0 12px 0; padding: 4px 12px; \
background-color: #f8f9fc;"><p>I consider detecting for newer driver a \
feature.</p></blockquote>
<p>That might make things more difficult for downstreams, however.</p></div>
</blockquote>
<p>Yes, of course. That's an issue which has created problems for me for years. \
KWin releases and mesa releases are not synced. This results in KWin not having a \
chance to be tested against latest Mesa. Distros combine these things. Like here \
openSUSE apparently combines a two year old KWin with a new Mesa.</p></div> \
</blockquote>
<p>Yes, it was decided that the latest Mesa for Leap is useful for newer hardware. \
Not uncommon, I suppose.</p>
<p>Note that I'm mostly asking for Plasma/5.11 here. When KWin 5.11 got \
released, Mesa already had this behaviour. So it has always been broken.</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: \
italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: \
#f8f9fc;"><p>Backporting is even more an issue. Because other distros might not have \
the new driver versions. And some changes in the past have been mutual \
exclusive.</p></blockquote>
<p>This commit isn't.</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: \
italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>If \
such issues happen KWin master must be changed to require the newer Mesa version and \
explicitly break compatibility with older Mesa.</p></blockquote>
<p>Well, you can get the mesa version at runtime, so this can't really happen. \
It's ugly, but solvable.</p>
<blockquote style="border-left: 3px solid #a7b5bf; color: #464c5c; font-style: \
italic; margin: 4px 0 12px 0; padding: 4px 12px; background-color: #f8f9fc;"><p>In \
the end the problem here is not that KWin code needs to be adjusted, but that Mesa \
devs still don't get that their version and renderer information is considered \
by downstreams as part of an API.</p></blockquote>
<p>Yes, but until that is the case, ignoring the problem isn't a \
workaround.</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R108 \
KWin</div></div></div><br \
/><div><strong>BRANCH</strong><div><div>Plasma/5.8</div></div></div><br \
/><div><strong>REVISION DETAIL</strong><div><a \
href="https://phabricator.kde.org/D9495" \
rel="noreferrer">https://phabricator.kde.org/D9495</a></div></div><br \
/><div><strong>To: </strong>fvogt, Plasma, graesslin<br /><strong>Cc: \
</strong>lbeltrame, kwin, plasma-devel, KWin, bwowk, ZrenBot, progwolff, lesliezhai, \
ali-mohamed, hardening, jensreuterberg, abetts, sebas, apol, mart<br /></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic