dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: "Ilia Mirkin" <imirkin@alum.mit.edu>,
	"Tom St Denis" <tom.stdenis@amd.com>,
	"Michel Dänzer" <michel@daenzer.net>,
	"Maling list - DRI developers" <dri-devel@lists.freedesktop.org>
Subject: Hardware 3D acceleration doesn't work anymore with the latest git kernel
Date: Fri, 24 Nov 2017 21:58:14 +0100	[thread overview]
Message-ID: <3e7b3e54-ecb9-b760-7aa7-fed85c2c26c3@xenosoft.de> (raw)
In-Reply-To: <CAKb7UvgfjHbRHbhiNVdm==Hq3jfjaYSmWuKaA7AHRHva8dUe7A@mail.gmail.com>

On 24.11.2017 20:14, Ilia Mirkin wrote:
>
> Do you have SWIOTLB disabled in your .config? Try enabling it to see
> if that's the issue.
>
> Looking at your bisect log, you might have incorrectly marked some
> revisions. E.g. you had a compile failure, which while isn't "good",
> it's also not "bad" -- good and bad are only in reference to the
> specific issue you're seeing. In such cases you can run "git bisect
> skip" which will mark the commit as "unknown" and pick a different one
> to try.
>
>    -ilia
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

Hi All,

Success!!!!!!!!!! I enabled SWIOTLB and the hardware 3D acceleration 
works again! Fantastic. Thank you very much! And thank you for the hint 
with "git bisect skip".

Cheers,
Christian

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-11-24 20:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 18:08 Hardware 3D acceleration doesn't work anymore with the latest git kernel Christian Zigotzky
2017-11-21  4:38 ` Alex Deucher
2017-11-21 11:32   ` Christian Zigotzky
2017-11-22 13:20   ` Christian Zigotzky
2017-11-22 13:27     ` Ilia Mirkin
2017-11-22 13:40       ` Christian Zigotzky
2017-11-22 13:45         ` Ilia Mirkin
2017-11-22 14:53           ` Christian Zigotzky
2017-11-24 14:29           ` Christian Zigotzky
2017-11-24 16:09             ` Michel Dänzer
2017-11-24 19:08               ` Christian Zigotzky
2017-11-24 19:13                 ` Christian Zigotzky
2017-11-24 19:14                 ` Ilia Mirkin
2017-11-24 20:58                   ` Christian Zigotzky [this message]
2017-11-27 11:02               ` Michel Dänzer
2017-11-27 11:50                 ` Christian König
2017-11-27 12:02                   ` Michel Dänzer
2017-11-27 12:17                     ` Tom St Denis
2017-11-27 14:53                       ` Michel Dänzer
2017-11-28  5:43                         ` Christian Zigotzky
2017-11-28  9:40                           ` Michel Dänzer
2017-11-28 23:48                             ` Christian Zigotzky
2017-11-27 12:20                     ` Christian König
2017-11-29  8:50                       ` Michel Dänzer

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=3e7b3e54-ecb9-b760-7aa7-fed85c2c26c3@xenosoft.de \
    --to=chzigotzky@xenosoft.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=imirkin@alum.mit.edu \
    --cc=michel@daenzer.net \
    --cc=tom.stdenis@amd.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).