linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bryan O'Donoghue" <pure.logic@nexus-software.ie>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: Peter Hurley <peter@hurleysoftware.com>,
	Maarten Lankhorst <maarten.lankhorst@canonical.com>,
	Ben Skeggs <bskeggs@redhat.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/nouveau/gem: tolerate a buffer specified multiple times
Date: Thu, 30 Jul 2015 16:14:46 +0100	[thread overview]
Message-ID: <55BA3F66.80906@nexus-software.ie> (raw)
In-Reply-To: <CAKb7UvhaKKzx3y15mpzFPpyFzCR4YMm2FneB9g54qYY8WDQN+g@mail.gmail.com>

On 30/07/15 16:02, Ilia Mirkin wrote:
>
> That's unfortunate. I know next to nothing about debian/ubuntu or how
> they do versions or how to even build packages for them. But they're
> big distros, presumably they have support teams of some sort, perhaps
> they can help you.
>
> Assuming that switching away does resolve the issue for you, perhaps
> you can also recommend that they avoid shipping that version, or
> include this nouveau fix in it:
>
> http://cgit.freedesktop.org/mesa/drm/commit/?id=812e8fe6ce46d733c30207ee26c788c61f546294
>
> This whole libdrm thing is a bit of a cluster%@#$ unfortunately --
> 2.4.60 is broken for nouveau, building even the latest released
> xf86-video-intel against 2.4.61+ causes it to not start ("fixed" in
> xf86-video-intel git), and newer mesa requires libdrm 2.4.60+.
>
>    -ilia
>

Matter of fact

apt-cache show libdrm2
sudo apt-get install libdrm2=2.4.56-1~ubuntu2
#sudo echo “package libdrm2” | sudo dpkg –set-selections

I'll give it a go at the end of the working day - should give enough 
time to recover if it all goes spectacularly wrong :)

  reply	other threads:[~2015-07-30 15:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-30 10:28 [PATCH] drm/nouveau/gem: tolerate a buffer specified multiple times Bryan O'Donoghue
2015-07-30 14:12 ` Ilia Mirkin
2015-07-30 14:48   ` Bryan O'Donoghue
2015-07-30 14:49   ` Peter Hurley
2015-07-30 14:52     ` Bryan O'Donoghue
2015-07-30 14:56       ` Bryan O'Donoghue
2015-07-30 15:02         ` Ilia Mirkin
2015-07-30 15:14           ` Bryan O'Donoghue [this message]
2015-07-30 15:26           ` Emil Velikov
2015-07-30 21:45             ` Peter Hurley
2015-07-31  0:03               ` Bryan O'Donoghue
2015-07-31  9:53                 ` Bryan O'Donoghue
2015-07-31  9:58                   ` Bryan O'Donoghue
2015-07-31 10:27                     ` Bryan O'Donoghue
2015-07-31 16:36                       ` Ilia Mirkin
2015-07-31 16:43                         ` Bryan O'Donoghue
2015-07-31 18:11                           ` Bryan O'Donoghue
2015-08-03  0:51                             ` Bryan O'Donoghue
2015-07-31 16:19               ` Bryan O'Donoghue

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=55BA3F66.80906@nexus-software.ie \
    --to=pure.logic@nexus-software.ie \
    --cc=bskeggs@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=imirkin@alum.mit.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@canonical.com \
    --cc=peter@hurleysoftware.com \
    /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;
as well as URLs for NNTP newsgroup(s).