<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Sure, I only collect informations how
the team thinks about it.<br>
Nvidia will adopt to 1.15 really fast. I don't know if AMD will do
it ever.<br>
There is a working solution for it to ship this second xorg-stack
just for catalyst, but I thought I don't have to anymore.<br>
Dropping Catalyst is lazy in my eyes. So I think we should move on
as it is now. Maybe update this stack if catalyst-legacy adopts
...<br>
<br>
Also SteamOS will speed up the process - so I hope ...<br>
<br>
On 11/05/2013 08:40 PM, Rob wrote:<br>
</div>
<blockquote
cite="mid:CAOunMDGvBANi3KBA+dYUtLsVM2RsfBwo6J_jnid2r6DhSMUTVw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>The thing is, it's not really a "Linux wide" issue, the
only people affected are the leading/bleeding edge rolling
releases, of which there aren't many and big companies like
AMD and nVidia care less about.<br>
<br>
</div>
Also, IMO any type "it'll also affect Arch" argument in regard
to catalyst driver is moot, because Arch does not officially
support catalyst (it got pulled from their main repos and
kicked to AUR years ago), but it is officially supported in
Manjaro .<br>
<br>
</div>
I don't deny my opinion is probably quite biased though,
considering my belief is that bleeding edge software and the
rolling release system is a bad choice for novice Linux users.<br>
<div>
<div>
<div>
<div class="gmail_extra">
<br>
<br>
<div class="gmail_quote">On Wed, Nov 6, 2013 at 4:33 AM,
J Fernyhough <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:j.fernyhough@gmail.com"
target="_blank">j.fernyhough@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
I personally don't see a problem with a solution
similar to Catalyst<br>
Legacy. If there is a Linux-wide issue with AMD
proprietary drivers<br>
and Xorg 1.15 then Manjaro won't be the only ones
affected (i.e. so<br>
will Arch). Given the leaps made by the OSS radeon
driver under Linux<br>
3.11 I'd personally be reticent to hold back other
packages because of<br>
one proprietary driver. For example, would you be
holding back Linux<br>
3.12 because ZFS/SPL hasn't yet been updated with
3.12 support? Once<br>
kernel 3.11 becomes default, I reckon the default
position should be<br>
to "try free first" (and in many cases people only
want Catalyst<br>
because they're used to needing it).<br>
<span class="HOEnZb"><font color="#888888"><br>
J<br>
</font></span>
<div class="HOEnZb">
<div class="h5"><br>
On 5 November 2013 09:34, Rob <<a
moz-do-not-send="true"
href="mailto:korrode@gmail.com">korrode@gmail.com</a>>
wrote:<br>
> Depends on if you want to always
arbitrarily roll Arch updates in or not. If<br>
> i was you I would have no problem holding
back the Xorg server for ages<br>
> after Arch has upgraded it, waiting for AMD
to release new drivers. Who is<br>
> going to feel a negative effect from a
slightly older X11? Certainly not the<br>
> average Manjaro user... unless there's
something i'm not considering?<br>
><br>
><br>
><br>
> On Tue, Nov 5, 2013 at 5:27 PM, Philip
Müller <<a moz-do-not-send="true"
href="mailto:philm@manjaro.org">philm@manjaro.org</a>>
wrote:<br>
>><br>
>> Some might not know it yet but Xorg
X-Server 1.15 RC1 got tagged. This<br>
>> means again a ABI bump which will break
Catalyst and Nvidia. I see no issues<br>
>> for Nvidia to release a working
proprietary blob but I see red for AMD once<br>
>> more. Sure, I already found a solution
to ship catalyst-server,<br>
>> catalyst-video and catalyst-input which
is simply an outdated xorg-stack you<br>
>> have to install to get this bollugs
working.<br>
>><br>
>> This means again to ship those extra
packages we only need for Catalyst<br>
>> and for x86_64 never reach a CD-size if
that matter. Also it means you'll<br>
>> never get the new features X-Server
1.15 series might offer.<br>
>><br>
>> I don't know if SteamOS will change
anything on this topic. The fact is,<br>
>> Arch will ship this new xorg-stack
series soon or later.<br>
>> Which leaves me to two options:<br>
>><br>
>> Keep Xorg-Stack 1.14 and maintain it on
our terms<br>
>> Keep up with Arch and use our
catalyst-stack solution<br>
>> Or ditch Catalyst once for all and
don't give a #$%&§ about it<br>
>><br>
>><br>
>> Thoughts, whishes<br>
>><br>
>> Phil<br>
>><br>
>>
_______________________________________________<br>
>> manjaro-dev mailing list<br>
>> <a moz-do-not-send="true"
href="mailto:manjaro-dev@manjaro.org">manjaro-dev@manjaro.org</a><br>
>> <a moz-do-not-send="true"
href="http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev"
target="_blank">http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev</a><br>
>><br>
><br>
><br>
>
_______________________________________________<br>
> manjaro-dev mailing list<br>
> <a moz-do-not-send="true"
href="mailto:manjaro-dev@manjaro.org">manjaro-dev@manjaro.org</a><br>
> <a moz-do-not-send="true"
href="http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev"
target="_blank">http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev</a><br>
><br>
_______________________________________________<br>
manjaro-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:manjaro-dev@manjaro.org">manjaro-dev@manjaro.org</a><br>
<a moz-do-not-send="true"
href="http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev"
target="_blank">http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
manjaro-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:manjaro-dev@manjaro.org">manjaro-dev@manjaro.org</a>
<a class="moz-txt-link-freetext" href="http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev">http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>