From: "Christian König" <christian.koenig@amd.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [pull] radeon drm-fixes-3.15
Date: Mon, 5 May 2014 11:04:25 +0200 [thread overview]
Message-ID: <53675419.8070406@amd.com> (raw)
In-Reply-To: <CAPM=9txzT9F=ehD53Taut78mV8Z12bx=MHQe3H0xKs25x-qhmw@mail.gmail.com>
Hi Dave,
> To keep Linus happier, I'd like to split this into two pull requests,
> one with the
> fixes, and one with the new hardware support, so I can send one as part of my
> regular fixes pull without fear of it upsetting the other, and vice-versa.
Sure, no problem.
I've just removed mullins support from my drm-fixes-3.15 branch and
forcefully pushed the result to fdo. The old branch is now available as
"mullins" on fdo as well.
The only patch I'm not 100% sure about is "drm/radeon: dpm updates for
KV/KB". This one came from the Mullins branch as well, but I need to
check with Alex if we shouldn't include that in fixes even without
Mullins support.
I have a couple of more patches for drm-fixes in the queue, so I wanted
to send out a new pull request tomorrow anyway. You can pull my
drm-fixes-3.15 branch now or you could just ignore this one and get a
new clean pull request tomorrow. Just let me know what you prefer.
Regards,
Christian.
Am 05.05.2014 02:51, schrieb Dave Airlie:
> On 1 May 2014 23:47, Christian König <christian.koenig@amd.com> wrote:
>> Hi Dave,
>>
> To keep Linus happier, I'd like to split this into two pull requests,
> one with the
> fixes, and one with the new hardware support, so I can send one as part of my
> regular fixes pull without fear of it upsetting the other, and vice-versa.
>
> Dave.
>
>> this is the next pull quested for stashed up radeon fixes for 3.15.
>> Highlights this time are:
>> 1. Support for Mullins. Handled like Kabini, so only PCI-IDs and a new enum
>> that needs to be added on various locations.
>> 2. DPM updates for Kabini.
>> 3. One more patch to better handle PLL limits.
>> 4. Making use of the PFLIP additional to the VBLANK interrupt, otherwise we
>> sometimes miss page flip events.
>> 5. Fix for the UVD command stream parser.
>> 6. Fix for bootup UVD clocks on RV7xx systems.
>>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-05-05 9:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 13:47 [pull] radeon drm-fixes-3.15 Christian König
2014-05-05 0:51 ` Dave Airlie
2014-05-05 9:04 ` Christian König [this message]
2014-05-05 12:48 ` Deucher, Alexander
-- strict thread matches above, loose matches on Subject: below --
2014-06-02 13:17 Christian König
2014-05-30 12:23 Christian König
2014-05-20 13:14 Christian König
2014-05-26 7:12 ` Malte Schröder
2014-05-26 7:39 ` Christian König
2014-05-16 13:54 Christian König
2014-05-18 23:04 ` Dave Airlie
2014-05-19 8:49 ` Christian König
2014-05-19 14:01 ` Deucher, Alexander
2014-05-06 10:32 Christian König
2014-04-22 16:49 Christian König
2014-04-17 12:40 Christian König
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=53675419.8070406@amd.com \
--to=christian.koenig@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--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.