From: "Michel Dänzer" <michel@daenzer.net>
To: Jerome Glisse <j.glisse@gmail.com>, Alex Deucher <alexdeucher@gmail.com>
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/radeon: tweak ACCEL_WORKING2 query for hawaii
Date: Wed, 30 Jul 2014 12:26:56 +0900 [thread overview]
Message-ID: <53D86600.2050902@daenzer.net> (raw)
In-Reply-To: <20140729171005.GB3103@gmail.com>
On 30.07.2014 02:10, Jerome Glisse wrote:
> On Tue, Jul 29, 2014 at 01:05:15PM -0400, Alex Deucher wrote:
>> On Tue, Jul 29, 2014 at 11:39 AM, Jerome Glisse <j.glisse@gmail.com> wrote:
>>> On Tue, Jul 29, 2014 at 10:33:18AM -0400, Alex Deucher wrote:
>>>> Return 2 so we can be sure the kernel has the necessary
>>>> changes for acceleration to work.
>>>
>>> I highly dislike that ? Why about just using nop2 in userspace ?
>>
>> How to we tell whether the version of mesa has that change or not?
>
> You do not need to know that in kernel, all that is needed is for userspace
> to test 3.16 kernel as it's all that is needed to get accel working.
What if the Hawaii fixes are backported to older kernels?
> So i would say enable accel on ddx now because truly if someone update its ddx
> then it must have updated mesa too.
There is no such guarantee.
This looks like a pretty good solution to me. Please add a check for
this in the Gallium winsys code as well for the benefit of non-X apps
such as Wayland compositors.
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
prev parent reply other threads:[~2014-07-30 3:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 14:33 [PATCH] drm/radeon: tweak ACCEL_WORKING2 query for hawaii Alex Deucher
2014-07-29 15:39 ` Jerome Glisse
2014-07-29 17:05 ` Alex Deucher
2014-07-29 17:10 ` Jerome Glisse
2014-07-29 17:22 ` Christian König
2014-07-29 17:31 ` Alex Deucher
2014-07-30 3:26 ` Michel Dänzer [this message]
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=53D86600.2050902@daenzer.net \
--to=michel@daenzer.net \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=j.glisse@gmail.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