Re: [PULL] drm-intel-next

Hi, On Wed, Apr 17, 2024 at 09:38:55AM -0400, Rodrigo Vivi wrote: > Another thing that it is important to highlight is that we have 3 drm level > patches in this pull request where I didn't see any explicit recorded > ack from you (drm maintainers) nor from drm-misc maintainers. > The patches

Re: [PULL] drm-intel-next

On Wed, 07 Feb 2024, Jani Nikula wrote: > Hi Dave & Sima - > > drm-intel-next-2024-02-07: > drm/i915 feature pull for v6.9: Ping, this hasn't been merged yet. BR, Jani. -- Jani Nikula, Intel

Re: [PULL] drm-intel-next

On Thu, Nov 23, 2023 at 09:03:59PM +0200, Jani Nikula wrote: > > Hi Dave & Sima - > > The first i915 feature pull towards v6.8. > > The one thing to single out are the major DP MST, UHBR, and DSC > bandwidth management improvements from Imre. > > Alas, they also need to be singled out because

Re: [PULL] drm-intel-next-fixes

On Wed, Nov 08, 2023 at 04:04:14PM +0200, Jani Nikula wrote: > > Hi Dave & Daniel - > > I see Dave already sent the pull request for v6.7-rc1 fixes, but here's > some more. > > drm-intel-next-fixes-2023-11-08: > drm/i915 fixes for v6.7-rc1: > - Fix null dereference when perf interface is not

Re: [PULL] drm-intel-next-fixes

On Thu, Apr 13, 2023 at 03:12:19PM +0300, Joonas Lahtinen wrote: > Hi Dave & Daniel, > > Just one Cc:stable fix for indirect sampler state this week on > drm-intel-next-fixes. > > Regards, Joonas > > *** > > drm-intel-next-fixes-2023-04-13: > > Short summary of fixes pull (less than what git

Re: [PULL] drm-intel-next

On Thu, Apr 06, 2023 at 10:03:51AM -0400, Rodrigo Vivi wrote: > Hi Daniel, > > Here goes drm-intel-next-2023-04-06: > > - Fix DPT+shmem combo and add i915.enable_dpt modparam (Ville) > - i915.enable_sagv module parameter (Ville) > - Correction to QGV related register addresses (Vinod) > - IPS

Re: [PULL] drm-intel-next

On Thu, Mar 23, 2023 at 04:43:22PM -0400, Rodrigo Vivi wrote: > Hi Daniel, > > Here goes drm-intel-next-2023-03-23: > > Core Changes: > - drm: Add SDP Error Detection Configuration Register (Arun) > > Driver Changes: > - Meteor Lake enabling and fixes (RK, Jose, Madhumitha) > - Lock the fbdev

Re: [PULL] drm-intel-next

On Mon, 29 Aug 2022, Jani Nikula wrote: > Hi Dave & Daniel - > > drm-intel-next-2022-08-29: > drm/i915 feature pull for v6.1: Hey, I started making another pull request, but realized you haven't pulled this one yet. Anything the matter, or just fell between the cracks? BR, Jani. > > Features

Re: [PULL] drm-intel-next -> drm-intel-gt-next cross-merge sync

On 20/05/2022 12:02, Jani Nikula wrote: Hi all, This is for Tvrtko to pull to cross-merge sync drm-intel-next to drm-intel-gt-next. Dave, Daniel, IIUC this is what you prefer over having topic branches for all the small things that are needed between drm-intel branches. I don't think we've

Re: [PULL] drm-intel-next-fixes

On Thu, Jan 13, 2022 at 09:33:03AM +, Tvrtko Ursulin wrote: > > Hi Dave and Daniel, > > A few fixes for the merge window. > > One dealing with runtime PM handling on the PXP unbind path and a few > regarding the newly added TTM backend support. > > Regards, > > Tvrtko > > --- > >

Re: [PULL] drm-intel-next-fixes

On Wed, 30 Jun 2021, Rodrigo Vivi wrote: > On Wed, Jun 30, 2021 at 01:05:35PM +0300, Jani Nikula wrote: >> On Tue, 29 Jun 2021, Rodrigo Vivi wrote: >> > Hi Dave and Daniel, >> > >> > Here goes drm-intel-next-fixes-2021-06-29: >> > >> > The biggest fix is the restoration of mmap ioctl for gen12

Re: [PULL] drm-intel-next-fixes

On Wed, Jun 30, 2021 at 01:05:35PM +0300, Jani Nikula wrote: > On Tue, 29 Jun 2021, Rodrigo Vivi wrote: > > Hi Dave and Daniel, > > > > Here goes drm-intel-next-fixes-2021-06-29: > > > > The biggest fix is the restoration of mmap ioctl for gen12 integrated parts > > which lack was breaking ADL-P

Re: [PULL] drm-intel-next-fixes

On Tue, 29 Jun 2021, Rodrigo Vivi wrote: > Hi Dave and Daniel, > > Here goes drm-intel-next-fixes-2021-06-29: > > The biggest fix is the restoration of mmap ioctl for gen12 integrated parts > which lack was breaking ADL-P with media stack. > Besides that a small selftest fix and a theoretical

Re: [PULL] drm-intel-next

On Wed, Jan 27, 2021 at 09:08:22AM -0500, Rodrigo Vivi wrote: > Hi Dave and Daniel, > > Hopefully this is the last pull request towards 5.12. > > Please notice this contains a drm/framebuffer change needed for > supporting clear color support for TGL Render Decompression. > > Here goes

Re: [PULL] drm-intel-next

On Mon, Jan 04, 2021 at 01:10:18PM -0800, Rodrigo Vivi wrote: > Hi Dave and Daniel, > > Happy New Year. > > Here goes the first pull request targeting 5.12. > > drm-intel-next-2021-01-04: > - Display hotplug fix for gen2/gen3 (Chris) > - Remove trailing semicolon (Tom) > - Suppress display

Re: [PULL] drm-intel-next-fixes

On Fri, Dec 18, 2020 at 05:04:09PM +0200, Jani Nikula wrote: > > Hi Dave & Daniel - > > drm-intel-next-fixes-2020-12-18: > drm/i915 fixes for the merge window Pulled, thanks a lot. -Daniel > > > BR, > Jani. > > The following changes since commit efd3043790c6e92f0bbe1fe385db9b544131c59c: >

Re: [PULL] drm-intel-next-fixes

On Mon, 10 Aug 2020, Dave Airlie wrote: > Like this stuff has been getting past me for years but I'm not happy > about it anymore, I'm going to just be grumpy asshole going forward. > If we introduced scheduler races in linux-next, I want to see reverts, > and reverts only until we stopped

Re: [PULL] drm-intel-next-fixes

On Fri, 31 Jul 2020 at 02:26, Joonas Lahtinen wrote: > > Hi Dave & Daniel, > > (Covering for Jani here for drm-intel-next-fixes) > > 5 new commits over drm-intel-next here. > > Fix for KASAN detected race condition and linux-next scheduler > WARNs. Patch to avoid IRQ spinlock and Cc: stable PMU

Re: [PULL] drm-intel-next

On Wed, Jul 15, 2020 at 3:34 PM Jani Nikula wrote: > > > Argh, failed to mention: > > On Wed, 15 Jul 2020, Jani Nikula wrote: > > Lee Shawn C (1): > > drm/i915/mst: filter out the display mode exceed sink's capability > > The above depends on: > > > Lyude Paul (1): > >

Re: [PULL] drm-intel-next

Argh, failed to mention: On Wed, 15 Jul 2020, Jani Nikula wrote: > Lee Shawn C (1): > drm/i915/mst: filter out the display mode exceed sink's capability The above depends on: > Lyude Paul (1): > drm/probe_helper: Add drm_connector_helper_funcs.mode_valid_ctx Which has changes

Re: [PULL] drm-intel-next-fixes

Quoting Joonas Lahtinen (2020-06-10 12:37:00) > Hi Dave & Daniel, > > Sending this one early for it to hopefully make it in before -rc1. > > Two important fixes: OOPS fix that was missing "Fixes:" tag and > not picked up earlier. Also fix for a use-after-free in cmdparser. > > Additional fixup

Re: [PULL] drm-intel-next

Quoting Dave Airlie (2020-05-14 04:28:17) > On Thu, 14 May 2020 at 03:10, Joonas Lahtinen > wrote: > > > > Ping for merging this? If there are no issues, I'd prefer to pull in > > next gvt-next and tag the final pull sooner than later. > > Can you check that I'm correct and this isn;'t in

Re: [PULL] drm-intel-next

On Thu, 14 May 2020 at 03:10, Joonas Lahtinen wrote: > > Ping for merging this? If there are no issues, I'd prefer to pull in > next gvt-next and tag the final pull sooner than later. Can you check that I'm correct and this isn;'t in patchwork. I've checked both the dri-devel and intel-gfx

Re: [PULL] drm-intel-next

Ping for merging this? If there are no issues, I'd prefer to pull in next gvt-next and tag the final pull sooner than later. Regards, Joonas Quoting Joonas Lahtinen (2020-04-30 15:49:04) > Hi Dave & Daniel, > > Fix for performance regression GitLab #1698: Iris Plus 655 and > 4K screen. Missing

Re: [PULL] drm-intel-next

On Tue, 14 Jan 2020, Chris Wilson wrote: > Quoting Jani Nikula (2020-01-14 11:43:22) >> >> Hi Dave & Daniel - >> >> Last batch for v5.6, slightly delayed I'm afraid. > > I'd like to close https://gitlab.freedesktop.org/drm/intel/issues/738 > for 5.6, otherwise we'll have some more nasty emails

Re: [PULL] drm-intel-next

Quoting Jani Nikula (2020-01-14 11:43:22) > > Hi Dave & Daniel - > > Last batch for v5.6, slightly delayed I'm afraid. I'd like to close https://gitlab.freedesktop.org/drm/intel/issues/738 for 5.6, otherwise we'll have some more nasty emails from bewildered users/devs.

Re: [PULL] drm-intel-next-fixes

Quoting Joonas Lahtinen (2019-11-20 22:40:35) > Hi Dave & Daniel, > > NOTE: CI shard results are delayed, bu I'm sending this > already because I'll travel tomorrow. I'll let you know > if the results look OK or not. Or you can look up > CI_DINF_162 results check at: > >

Re: [PULL] drm-intel-next

On Fri, 23 Aug 2019 at 05:29, Rodrigo Vivi wrote: > > Hi Dave and Daniel, > > Here goes the final pull request targeting 5.4. For some reason patchwork hasn't picked this up. or if it has I can't see it. Not sure whether it was the earlier patch code in it or something else malformed. Dave.

Re: [PULL] drm-intel-next

On Thu, Apr 18, 2019 at 11:04:26AM +0300, Joonas Lahtinen wrote: > - Suppress spurious combo PHY B warning (Vile) That's putting it a bit strong :) -- Ville Syrjälä Intel ___ dri-devel mailing list dri-devel@lists.freedesktop.org

Re: [PULL] drm-intel-next

Quoting Dave Airlie (2019-03-28 04:09:56) > On Mon, 25 Mar 2019 at 22:49, Joonas Lahtinen > wrote: > > > > Hi Dave & Daniel, > > > > First batch of features for 5.2, tagged last week. > > I asked on irc, but got no answer I saw, >

Re: [PULL] drm-intel-next

On Mon, 25 Mar 2019 at 22:49, Joonas Lahtinen wrote: > > Hi Dave & Daniel, > > First batch of features for 5.2, tagged last week. I asked on irc, but got no answer I saw, /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/i915/i915_gem_context.c:698:12: warning: ‘context_barrier_task’ defined

Re: [PULL] drm-intel-next

On Mon, 04 Feb 2019, Daniel Vetter wrote: > On Mon, Feb 04, 2019 at 10:47:36AM +0200, Joonas Lahtinen wrote: >> Quoting Dave Airlie (2019-02-04 07:02:07) >> > On Sat, 2 Feb 2019 at 18:29, Rodrigo Vivi wrote: >> > > >> > > Hi Dave and Daniel, >> > > >> > > Here goes another pull request for 5.1.

Re: [PULL] drm-intel-next

On Mon, Feb 04, 2019 at 10:47:36AM +0200, Joonas Lahtinen wrote: > Quoting Dave Airlie (2019-02-04 07:02:07) > > On Sat, 2 Feb 2019 at 18:29, Rodrigo Vivi wrote: > > > > > > Hi Dave and Daniel, > > > > > > Here goes another pull request for 5.1. > > > > dim complained: > > > > Chris committed

Re: [PULL] drm-intel-next

Quoting Dave Airlie (2019-02-04 07:02:07) > On Sat, 2 Feb 2019 at 18:29, Rodrigo Vivi wrote: > > > > Hi Dave and Daniel, > > > > Here goes another pull request for 5.1. > > dim complained: > > Chris committed this without an S-O-B, now because it's all Intel this > probably doesn't matter, so

Re: [PULL] drm-intel-next

On Sat, 2 Feb 2019 at 18:29, Rodrigo Vivi wrote: > > Hi Dave and Daniel, > > Here goes another pull request for 5.1. dim complained: Chris committed this without an S-O-B, now because it's all Intel this probably doesn't matter, so I'll pull it, put please try and let it not happen again.

Re: [PULL] drm-intel-next for v4.21/v5.1

On Fri, 2 Nov 2018 at 20:21, Jani Nikula wrote: > > > Hi Dave - > > I just tagged this minutes ago, but I'm sending this now because I'll be > out for about a week. I don't expect you to pull this until some time > after -rc1 anyway. I'm asking Joonas and Rodrigo to tell you if this > one's a go

Re: [PULL] drm-intel-next-fixes

On Fri, Oct 19, 2018 at 12:38 PM Joonas Lahtinen wrote: > > Hi Dave, > > Here are the promised MST fixes that were missing due to being > in i915 tree, yet outside i915 directory. > > Further explanation in the previous PR's thread. fwiw, lgtm. Cheers, Daniel > > Regards, Joonas > > *** > >

Re: [PULL] drm-intel-next-fixes

Quoting Daniel Vetter (2018-10-19 10:05:32) > On Fri, Oct 19, 2018 at 8:59 AM Joonas Lahtinen > wrote: > > > > Quoting Daniel Vetter (2018-10-18 22:32:00) > > > On Thu, Oct 18, 2018 at 6:57 PM Joonas Lahtinen > > > wrote: > > > > > > > > Hi Dave, > > > > > > > > Here comes the final set of fixes

Re: [PULL] drm-intel-next-fixes

On Fri, Oct 19, 2018 at 8:59 AM Joonas Lahtinen wrote: > > Quoting Daniel Vetter (2018-10-18 22:32:00) > > On Thu, Oct 18, 2018 at 6:57 PM Joonas Lahtinen > > wrote: > > > > > > Hi Dave, > > > > > > Here comes the final set of fixes under -next-fixes umbrella. > > > Next one will be then from

Re: [PULL] drm-intel-next-fixes

Quoting Daniel Vetter (2018-10-18 22:32:00) > On Thu, Oct 18, 2018 at 6:57 PM Joonas Lahtinen > wrote: > > > > Hi Dave, > > > > Here comes the final set of fixes under -next-fixes umbrella. > > Next one will be then from -fixes, assuming a release next Sun. > > > > Fixes for bunch of display

Re: [PULL] drm-intel-next-fixes

On Thu, Oct 18, 2018 at 6:57 PM Joonas Lahtinen wrote: > > Hi Dave, > > Here comes the final set of fixes under -next-fixes umbrella. > Next one will be then from -fixes, assuming a release next Sun. > > Fixes for bunch of display related issues reported by users, then the > MST fixes that were

Re: [PULL] drm-intel-next

On Mon, Jun 18, 2018 at 09:12:55AM +0200, Daniel Vetter wrote: > On Tue, Jun 12, 2018 at 9:59 AM, Jani Nikula > wrote: > > On Tue, 12 Jun 2018, Dave Airlie wrote: > >> On 12 June 2018 at 02:27, Rodrigo Vivi wrote: > >>> Hi Dave, > >>> > >>> This is the first round targeting 4.19. > >>> > >>

Re: [PULL] drm-intel-next

On Tue, Jun 12, 2018 at 9:59 AM, Jani Nikula wrote: > On Tue, 12 Jun 2018, Dave Airlie wrote: >> On 12 June 2018 at 02:27, Rodrigo Vivi wrote: >>> Hi Dave, >>> >>> This is the first round targeting 4.19. >>> >> Does this tree feed into linux-next already? >> >> Since we shouldn't have new stuff

Re: [PULL] drm-intel-next

On Tue, Jun 12, 2018 at 9:59 AM, Jani Nikula wrote: > On Tue, 12 Jun 2018, Dave Airlie wrote: >> On 12 June 2018 at 02:27, Rodrigo Vivi wrote: >>> Hi Dave, >>> >>> This is the first round targeting 4.19. >>> >> Does this tree feed into linux-next already? >> >> Since we shouldn't have new stuff

Re: [PULL] drm-intel-next

On Tue, 12 Jun 2018, Dave Airlie wrote: > On 12 June 2018 at 02:27, Rodrigo Vivi wrote: >> Hi Dave, >> >> This is the first round targeting 4.19. >> > Does this tree feed into linux-next already? > > Since we shouldn't have new stuff for linux-next feeding into it until > after rc1. I think

Re: [PULL] drm-intel-next

On 12 June 2018 at 02:27, Rodrigo Vivi wrote: > Hi Dave, > > This is the first round targeting 4.19. > Does this tree feed into linux-next already? Since we shouldn't have new stuff for linux-next feeding into it until after rc1. I won't be pulling this until after rc1 anyways. Dave.

Re: [PULL] drm-intel-next

"... should _not_ take this as a personal failure ..." is what I meant of course. Worst possible oversight :-/ -Daniel On Tue, May 15, 2018 at 4:58 PM, Daniel Vetter wrote: > Imo we should take this as a personal failure of anyone, things > happen. Instead this is a good

Re: [PULL] drm-intel-next

Agreed. Zhi, don't worry about it. I think the main takeaways here are: 1) We need to improve the dim checks on git pulls. This is both for us pulling gvt, and now that Dave's experimenting with dim, for him pulling all the trees. 2) The GVT maintainers should consider using dim too. It would

Re: [PULL] drm-intel-next

Imo we should take this as a personal failure of anyone, things happen. Instead this is a good opportunity to improve our scripts, to make sure we catch this in the future. Cheers, Daniel On Tue, May 15, 2018 at 3:16 PM, Wang, Zhi A wrote: > Hi: > > I am truly sorry for

RE: [PULL] drm-intel-next

Hi: I am truly sorry for the mess. It's actual my fault of solving a patch dependency by rebasing. Jani was trying to help me to catch the deadline, I am very appreciated for Jani's help and I am quite sorry for letting Jani experience this failure. He tried to help but I fail him. As a new

RE: [PULL] drm-intel-next

> -Original Message- > From: Nikula, Jani > Sent: Tuesday, May 15, 2018 3:26 PM > To: Dave Airlie > Cc: Daniel Vetter ; Jani Nikula > ; Joonas Lahtinen > ; Vivi, Rodrigo

Re: [PULL] drm-intel-next

On 4 May 2018 at 10:29, Dave Airlie wrote: > On 4 May 2018 at 10:19, Dave Airlie wrote: >> On 2 May 2018 at 17:03, Jani Nikula wrote: >>> >>> Hi Dave - >>> >>> drm-intel-next-2018-04-13: >>> First drm/i915 feature batch heading for

Re: [PULL] drm-intel-next

On 4 May 2018 at 10:19, Dave Airlie wrote: > On 2 May 2018 at 17:03, Jani Nikula wrote: >> >> Hi Dave - >> >> drm-intel-next-2018-04-13: >> First drm/i915 feature batch heading for v4.18: >> >> - drm-next backmerge to fix build (Rodrigo) >> - GPU

Re: [PULL] drm-intel-next

On 2 May 2018 at 17:03, Jani Nikula wrote: > > Hi Dave - > > drm-intel-next-2018-04-13: > First drm/i915 feature batch heading for v4.18: > > - drm-next backmerge to fix build (Rodrigo) > - GPU documentation improvements (Kevin) > - GuC and HuC refactoring, host/GuC

Re: [PULL] drm-intel-next

On Fri, 13 Oct 2017, Dave Airlie wrote: > On 13 October 2017 at 01:23, Jani Nikula wrote: >> On Wed, 11 Oct 2017, Jani Nikula wrote: >>> Hi Dave, more v4.15 features. >> >> Okay, so I suck and there's still one more batch to come

Re: [PULL] drm-intel-next

On 13 October 2017 at 01:23, Jani Nikula wrote: > On Wed, 11 Oct 2017, Jani Nikula wrote: >> Hi Dave, more v4.15 features. > > Okay, so I suck and there's still one more batch to come after this. I'm > a bit out of rhythm here. When do you want the

Re: [PULL] drm-intel-next

On Wed, 11 Oct 2017, Jani Nikula wrote: > Hi Dave, more v4.15 features. Okay, so I suck and there's still one more batch to come after this. I'm a bit out of rhythm here. When do you want the pull request for that at the latest? BR, Jani. > > Our tooling now supports

Re: [PULL] drm-intel-next^Wdrm-intel-fixes

Wrong subject, I need to fix my script ;-) -Daniel On Thu, Sep 26, 2013 at 10:48 AM, Daniel Vetter daniel.vet...@ffwll.ch wrote: Hi Dave, Just a few fixes for regressions and other serious stuff. Two fix state tracking mismatches, together with an additional patch that I've submitted to

Re: [PULL] drm-intel-next

On Wed, Aug 07, 2013 at 10:27:35AM +1000, Dave Airlie wrote: On Mon, Aug 5, 2013 at 5:35 AM, Daniel Vetter dan...@ffwll.ch wrote: Hi Dave, Okay since I missed this, then I merged patches from the list from David Herrmann fixing up drm_mm usage, then I merged this and it all fell to pieces.

Re: [pull] drm-intel-next

On Mon, Apr 15, 2013 at 09:56:29AM +0200, Daniel Vetter wrote: Hi Dave, Since I expect Linus to open the merge window in about a week I guess this is the last i915 feature pull for 3.10. Highlights: Updated testing tree for -next. Highlights: - Corner case fixes discovered with static

Re: [pull] drm-intel-next

-lkml On Sun, Mar 17, 2013 at 12:46 PM, Daniel Vetter dan...@ffwll.ch wrote: On Fri, Mar 15, 2013 at 3:11 AM, Stéphane Marchesin stephane.marche...@gmail.com wrote: drm/i915: read out the modeset hw state at load and resume time This commit regresses modeset on the samsung series 5

Re: [pull] drm-intel-next

On Mon, Mar 18, 2013 at 8:35 PM, Stéphane Marchesin stephane.marche...@gmail.com wrote: For starters I guess we need: - drm.debug=0xe dmesg from just before that commit - same for latest 3.9-rc kernels, presuming it's not broken there Latest upstream has a minor chance to work better I think

Re: [pull] drm-intel-next

On Fri, Mar 15, 2013 at 3:11 AM, Stéphane Marchesin stephane.marche...@gmail.com wrote: drm/i915: read out the modeset hw state at load and resume time This commit regresses modeset on the samsung series 5 chromebook (it is basically a pineview machine with an lvds panel). I don't seem to

Re: [pull] drm-intel-next

On Thu, Sep 13, 2012 at 7:18 AM, Daniel Vetter dan...@ffwll.ch wrote: Hi Dave, The big ticket item here is the new i915 modeset infrastructure. Shockingly it didn't not blow up all over the place (i.e. I've managed to fix the ugly issues before merging). 1-2 smaller corner cases broke, but

Re: [pull] drm-intel-next

On Fri, Nov 16, 2012 at 12:17 PM, Daniel Vetter dan...@ffwll.ch wrote: Hi Dave, Highlights of this -next round: - ivb fdi B/C fixes - hsw sprite/plane offset fixes from Damien - unified dp/hdmi encoder for hsw, finally external dp support on hsw (Paulo) - kill-agp and some other prep

Re: [pull] drm-intel-next

On Fri, Nov 16, 2012 at 6:47 PM, Alex Deucher alexdeuc...@gmail.com wrote: Hey, I don't see the drm HPD fixes. Are you planning to put them in another pull request? It would be nice to get them upstream for 3.8 Since they only refine the drm helpers in the core, I've figured there's no need

Re: [pull] drm-intel-next

On Thu, Sep 13, 2012 at 04:18:41PM +0200, Daniel Vetter wrote: Hi Dave, The big ticket item here is the new i915 modeset infrastructure. Shockingly it didn't not blow up all over the place (i.e. I've managed to fix the ugly issues before merging). 1-2 smaller corner cases broke, but we have

Re: [PULL] drm-intel-next

On Thu, Jun 28, 2012 at 02:05:16PM +0200, Daniel Vetter wrote: Hi Dave, New -next pull request. Highlights: - Remaining vlv patches from Jesse et al. - Some hw workarounds from Jesse - hw context support from Ben - full uncore sharing on ivb - prep work to move the gtt code from

Re: [PULL] drm-intel-next

On Wed, Jan 04, 2012 at 07:35:41PM -0800, Keith Packard wrote: Here are the rest of the 3.3 pending changes. This has a bunch of small bug fixes and overlay plane support for i915. The following changes since commit 7a7e8734ac3235efafd34819b27fbdf5417e6d60: Merge branch

Re: [PULL] drm-intel-next

On 08/03/2011 11:14 PM, Keith Packard wrote: Here's a pile of fixes on top of the stuff already in drm-core-next. * Pile of mode setting fixes which eliminate a selection of bugs and other annoyances. Eliminates the 'stripey' effect when going from two to one monitor, makes hot-plug

Re: [PULL] drm-intel-next

On Wed, 10 Aug 2011 12:20:14 -0400, Andy Lutomirski l...@mit.edu wrote: Can you ack at least this one: Revert and fix drm/i915/dp: remove DPMS mode tracking from DP (i.e. d2b996ac698aebb28557355857927b8b934bb4f9) for -stable? It fixes an annoying regression in 3.0. I'm working

Re: [PULL] drm-intel-next

On Wed, Jul 13, 2011 at 09:39:41AM -0700, Keith Packard wrote: Here's most of the patches I'm hoping to land after 3.0: Is this one intentionally not in or did it slip through? drm/i915: gracefully bail out when init_clock_gating-pointer is not set [1] [1]

Re: [PULL] drm-intel-next

On Wed, 13 Jul 2011 19:22:14 +0200, Wolfram Sang w.s...@pengutronix.de wrote: Is this one intentionally not in or did it slip through? I thought I had replied to that -- it doesn't apply to either -fixes or -next at this point. I can try to fix it, but I'd prefer it if you'd figure out how

Re: [PULL] drm-intel-next

Sorry for not pinging you when I didn't hear back. No problem! Will fix it. Thanks, Wolfram -- Pengutronix e.K. | Wolfram Sang| Industrial Linux Solutions | http://www.pengutronix.de/ | signature.asc Description: Digital

Re: [PULL] drm-intel-next

This fixes a simple typo in the Ivybridge code -- an extra semicolon. The following changes since commit 9e3c256d7d56a12a324945ce8e6347f93fa0: drm/i915: initialize gen6 rps work queue on Sandy Bridge and Ivy Bridge (2011-05-18 15:14:39 -0700) are available in the git repository at:

Re: [PULL] drm-intel-next

I've pushed four more patches to this branch for your merging pleasure. * Disabling FBC on Ironlake to enable RC6 instead Two patches for this are included. The following changes since commit 645c62a5e95a5f9a8e0d0627446bbda4ee042024: drm/i915: split PCH clock gating init (2011-05-13

Re: [PULL] drm-intel-next

On Tue, 17 May 2011 15:00:01 -0700, Keith Packard kei...@keithp.com wrote: I've pushed four more patches to this branch for your merging pleasure. And, one more which fixes non-eDP displays on Ironlake systems after the Ivybridge merge. Sorry for not catching that in our testing... The