From: Jerome Glisse <j.glisse@gmail.com>
To: "Christian König" <deathsimple@vodafone.de>
Cc: "Deucher, Alexander" <Alexander.Deucher@amd.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [pull] radeon drm-next-3.17
Date: Tue, 5 Aug 2014 13:41:05 -0400 [thread overview]
Message-ID: <20140805174103.GA2863@gmail.com> (raw)
In-Reply-To: <53E11539.10500@vodafone.de>
On Tue, Aug 05, 2014 at 07:32:41PM +0200, Christian König wrote:
> Am 05.08.2014 um 19:22 schrieb Daniel Vetter:
> >On Tue, Aug 5, 2014 at 7:15 PM, Deucher, Alexander
> ><Alexander.Deucher@amd.com> wrote:
> >>>-----Original Message-----
> >>>From: Daniel Vetter [mailto:daniel.vetter@ffwll.ch] On Behalf Of Daniel
> >>>Vetter
> >>>Sent: Tuesday, August 05, 2014 1:09 PM
> >>>To: Alex Deucher
> >>>Cc: dri-devel@lists.freedesktop.org; airlied@gmail.com; Deucher, Alexander
> >>>Subject: Re: [pull] radeon drm-next-3.17
> >>>
> >>>On Tue, Aug 05, 2014 at 12:22:06PM -0400, Alex Deucher wrote:
> >>>>Hi Dave,
> >>>>
> >>>>This is the radeon pull request for 3.17. Highlights:
> >>>>- Additional Hawaii fixes
> >>>>- Support for using the display scaler on non-fixed mode displays
> >>>>- Support for new firmware format that makes it easier to update
> >>>>- Enable dpm by default on additional asics
> >>>>- GPUVM improvements
> >>>>- Support for uncached and write combined gtt buffers
> >>>>- Userptr support
> >>>Aside: Where's the libdrm/mesa/whatever patches for this? I didn't see
> >>>them fly by anywhere, so I guess I've missed them on some m-l I don't
> >>>subscribe to.
> >>Christian wrote some patches to validate the interfaces, but I'm not sure he ever sent them out. We haven't yet done a full implementation in the usermode drivers to take advantage of this yet.
> >Well right now I've consistently rejected all patches that don't yet
> >come with the full thing (libdrm, usermode drivers and tests for it
> >all as not ready). And I do that at least once per week since we have
> >blob userspace separate from mesa, too. So if we toss that rule
> >overboard (and my understanding is that Dave's been fairly strict
> >here) I'll look rather bad. As in really, really bad.
> >
> >I strongly prefer that userptr gets postponed until it's ready. Dave?
>
> That's just my fault. Wanted to wait with the mesa patches till we have the
> kernel interface accepted.
>
> I've just send them out,
> Christian.
Well i am still not agreeing with the anonymous thingy. It should restrict
to anonymous vma period and not require a flag for that.
Cheers,
Jérôme
>
> >-Daniel
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-08-05 17:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 16:22 [pull] radeon drm-next-3.17 Alex Deucher
2014-08-05 17:09 ` Daniel Vetter
2014-08-05 17:15 ` Deucher, Alexander
2014-08-05 17:22 ` Daniel Vetter
2014-08-05 17:32 ` Christian König
2014-08-05 17:41 ` Jerome Glisse [this message]
2014-08-06 6:35 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2014-08-05 22:16 Alex Deucher
2014-08-06 9:45 Alex Deucher
2014-08-07 22:08 Alex Deucher
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=20140805174103.GA2863@gmail.com \
--to=j.glisse@gmail.com \
--cc=Alexander.Deucher@amd.com \
--cc=deathsimple@vodafone.de \
--cc=dri-devel@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.