Re: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [PULL] drm-intel-next

On Tue, Mar 07, 2023 at 05:00:01PM -0500, Rodrigo Vivi wrote: > Hi Dave and Daniel, > > Here goes our first pull request towards 6.3. You know, I meant 6.4. :) Thank you Joonas for noticing that. > > drm-intel-next-2023-03-07: > > Cross-subsystem Changes: > - MEI patches to fix

Re: [Intel-gfx] [PULL] drm-intel-next

On Tue, Nov 01, 2022 at 10:29:24PM +, Vivi, Rodrigo wrote: > On Sat, 2022-10-29 at 02:41 +0300, Ville Syrjälä wrote: > > On Fri, Oct 28, 2022 at 02:22:33PM -0400, Rodrigo Vivi wrote: > > > Hi Dave and Daniel, > > > > > > Here goes the first chunk of drm-intel-next targeting 6.2 > > > > > >

Re: [Intel-gfx] [PULL] drm-intel-next

On Sat, 2022-10-29 at 02:41 +0300, Ville Syrjälä wrote: > On Fri, Oct 28, 2022 at 02:22:33PM -0400, Rodrigo Vivi wrote: > > Hi Dave and Daniel, > > > > Here goes the first chunk of drm-intel-next targeting 6.2 > > > > The highlight goes to Ville with many display related clean-up > > and

Re: [Intel-gfx] [PULL] drm-intel-next

On Fri, Oct 28, 2022 at 02:22:33PM -0400, Rodrigo Vivi wrote: > Hi Dave and Daniel, > > Here goes the first chunk of drm-intel-next targeting 6.2 > > The highlight goes to Ville with many display related clean-up > and improvement, some other MTL enabling work and many other > fixes and small

Re: [Intel-gfx] [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: [Intel-gfx] [PULL] drm-intel-next-fixes

On Fri, Aug 05, 2022 at 05:25:43PM +0200, Mauro Carvalho Chehab wrote: > On Fri, 5 Aug 2022 10:39:44 -0400 > Rodrigo Vivi wrote: > > > On Fri, Aug 05, 2022 at 10:46:57AM +0200, Mauro Carvalho Chehab wrote: > > > Hi Rodrigo, > > > > > > On Thu, 4 Aug 2022 13:33:06 -0400 > > > Rodrigo Vivi

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

On Fri, 5 Aug 2022 10:39:44 -0400 Rodrigo Vivi wrote: > On Fri, Aug 05, 2022 at 10:46:57AM +0200, Mauro Carvalho Chehab wrote: > > Hi Rodrigo, > > > > On Thu, 4 Aug 2022 13:33:06 -0400 > > Rodrigo Vivi wrote: > > > > > Hi Dave and Daniel, > > > > > > Here goes

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

On Fri, Aug 05, 2022 at 10:46:57AM +0200, Mauro Carvalho Chehab wrote: > Hi Rodrigo, > > On Thu, 4 Aug 2022 13:33:06 -0400 > Rodrigo Vivi wrote: > > > Hi Dave and Daniel, > > > > Here goes drm-intel-next-fixes-2022-08-04: > > > > - disable pci resize on 32-bit systems (Nirmoy) > > - don't

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

Hi Rodrigo, On Thu, 4 Aug 2022 13:33:06 -0400 Rodrigo Vivi wrote: > Hi Dave and Daniel, > > Here goes drm-intel-next-fixes-2022-08-04: > > - disable pci resize on 32-bit systems (Nirmoy) > - don't leak the ccs state (Matt) > - TLB invalidation fixes (Chris) > > Thanks, > Rodrigo. > > The

Re: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [PULL] drm-intel-next-fixes

On Thu, Jul 01, 2021 at 11:57:53AM +0300, Jani Nikula wrote: > 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

Re: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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 ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org

Re: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [PULL] drm-intel-next

On Mon, Oct 24, 2016 at 9:25 AM, Daniel Vetter wrote: > Hi Dave, > > drm-intel-next-2016-10-24: > - first slice of the gvt device model (Zhenyu et al) > - compression support for gpu error states (Chris) > - sunset clause on gpu errors resulting in dmesg noise telling

Re: [Intel-gfx] [PULL] drm-intel-next

On Wed, Jun 22, 2016 at 11:24:57AM +0200, Daniel Vetter wrote: > Hi Dave, > > drm-intel-next-2016-06-20: > - Infrastructure for GVT-g (paravirtualized gpu on gen8+), from Zhi Wang > - another attemp at nonblocking atomic plane updates > - bugfixes and refactoring for GuC doorbell code (Dave

Re: [Intel-gfx] [PULL] drm-intel-next

On Thu, Apr 21, 2016 at 11:26:49AM +0200, Daniel Vetter wrote: > Hi Dave, > > drm-intel-next-2016-04-11: > - make modeset hw state checker atomic aware (Maarten) > - close races in gpu stuck detection/seqno reading (Chris) > - tons of small improvements from Chris Wilson all over the gem code > -

Re: [Intel-gfx] [PULL] drm-intel-next

On Tue, Dec 22, 2015 at 04:31:22PM +, Tvrtko Ursulin wrote: > > On 22/12/15 14:31, Chris Wilson wrote: > >On Tue, Dec 22, 2015 at 03:05:14PM +0100, Daniel Vetter wrote: > >>On Tue, Dec 22, 2015 at 11:37:18AM +0100, Daniel Vetter wrote: > >>>Hi Dave, > >>> > >>>Final 4.5 feature pull for

Re: [Intel-gfx] [PULL] drm-intel-next

On 22/12/15 14:31, Chris Wilson wrote: On Tue, Dec 22, 2015 at 03:05:14PM +0100, Daniel Vetter wrote: On Tue, Dec 22, 2015 at 11:37:18AM +0100, Daniel Vetter wrote: Hi Dave, Final 4.5 feature pull for drm/i915! drm-intel-next-2015-12-18: - fix atomic watermark recomputation logic (Maarten)

Re: [Intel-gfx] [PULL] drm-intel-next

On Tue, Dec 22, 2015 at 11:37:18AM +0100, Daniel Vetter wrote: > Hi Dave, > > Final 4.5 feature pull for drm/i915! > > drm-intel-next-2015-12-18: > - fix atomic watermark recomputation logic (Maarten) > - modeset sequence fixes for LPT (Ville) > - more kbl enabling work (Rodrigo, Wayne) > -

Re: [Intel-gfx] [PULL] drm-intel-next

On Tue, Dec 22, 2015 at 03:05:14PM +0100, Daniel Vetter wrote: > On Tue, Dec 22, 2015 at 11:37:18AM +0100, Daniel Vetter wrote: > > Hi Dave, > > > > Final 4.5 feature pull for drm/i915! > > > > drm-intel-next-2015-12-18: > > - fix atomic watermark recomputation logic (Maarten) > > - modeset

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

On 22 June 2015 at 18:12, Jani Nikula jani.nik...@intel.com wrote: On Mon, 22 Jun 2015, Ander Conselvan De Oliveira conselv...@gmail.com wrote: There is commit bd4b4827acdc00bf9e71f939d160102021d10d4f Author: Ander Conselvan de Oliveira ander.conselvan.de.olive...@intel.com Date: Fri May

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

There is commit bd4b4827acdc00bf9e71f939d160102021d10d4f Author: Ander Conselvan de Oliveira ander.conselvan.de.olive...@intel.com Date: Fri May 29 14:28:09 2015 +0300 drm/i915: Silence compiler warning in -nightly to fix that same issue. I didn't realize this was also needed in

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

On Mon, 22 Jun 2015, Ander Conselvan De Oliveira conselv...@gmail.com wrote: There is commit bd4b4827acdc00bf9e71f939d160102021d10d4f Author: Ander Conselvan de Oliveira ander.conselvan.de.olive...@intel.com Date: Fri May 29 14:28:09 2015 +0300 drm/i915: Silence compiler warning in

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

On Fri, Jun 19, 2015 at 01:48:13PM +1000, Dave Airlie wrote: On 18 June 2015 at 16:04, Jani Nikula jani.nik...@intel.com wrote: Hi Dave, i915 fixes for drm-next/v4.2. BR, Jani. And my gcc says: /home/airlied/devel/kernel/drm-next/drivers/gpu/drm/i915/intel_display.c: In function

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

On 18 June 2015 at 16:04, Jani Nikula jani.nik...@intel.com wrote: Hi Dave, i915 fixes for drm-next/v4.2. BR, Jani. And my gcc says: /home/airlied/devel/kernel/drm-next/drivers/gpu/drm/i915/intel_display.c: In function ‘__intel_set_mode’:

Re: [Intel-gfx] [PULL] drm-intel-next

On 1 April 2015 at 00:31, Daniel Vetter daniel.vet...@ffwll.ch wrote: Hi Dave, Final i915 pull for 4.1, except maybe I'll throw in a bxt stage1 enabling patch if it's ready in time - all the core changes have landed already so impact would be minimal, as usual. You should mentioned when you

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

On Wed, Feb 11, 2015 at 01:09:51PM +0200, Jani Nikula wrote: Hi Dave - Here's a batch of i915 fixes for drm-next, with more cc: stable material than fixes specific to drm-next. BR, Jani. The following changes since commit 1293eaa3ebf92f146f366d9b678a07b8b3200ea1: drm/i915:

Re: [Intel-gfx] [PULL] drm-intel-next

On Fri, Dec 19, 2014 at 10:44:34AM +0100, Daniel Vetter wrote: Hi Dave, drm-intel-next-2014-12-05: - dual-dsi enabling from Gaurav with prep work from Jani - reshuffling the ring init code to move towards a clean sw/hw state setup split - ring free space refactoring from Dave Gordon -

Re: [Intel-gfx] [PULL] drm-intel-next

On 29 November 2014 at 00:22, Daniel Vetter dan...@ffwll.ch wrote: On Fri, Nov 28, 2014 at 02:30:45PM +0100, Daniel Vetter wrote: Hi Dave, As discussed on irc here's the slightly late (because our QA cycle was a bit misaligned) final feature pull request for 3.19. I have a few fixes to sort

Re: [Intel-gfx] [PULL] drm-intel-next

On Tue, Dec 02, 2014 at 11:02:59AM +1000, Dave Airlie wrote: On 29 November 2014 at 00:22, Daniel Vetter dan...@ffwll.ch wrote: On Fri, Nov 28, 2014 at 02:30:45PM +0100, Daniel Vetter wrote: Hi Dave, As discussed on irc here's the slightly late (because our QA cycle was a bit

Re: [Intel-gfx] [PULL] drm-intel-next

On Fri, Nov 28, 2014 at 02:30:45PM +0100, Daniel Vetter wrote: Hi Dave, As discussed on irc here's the slightly late (because our QA cycle was a bit misaligned) final feature pull request for 3.19. I have a few fixes to sort out in my 3.20 queue, so will send you one more pull request next

Re: [Intel-gfx] [PULL] drm-intel-next

On Wed, Oct 22, 2014 at 09:09:43AM +1000, Dave Airlie wrote: On 21 October 2014 23:38, Daniel Vetter daniel.vet...@ffwll.ch wrote: Hi Dave, drm-intel-next-2014-10-03: - first batch of skl stage 1 enabling - fixes from Rodrigo to the PSR, fbc and sink crc code - kerneldoc for the

Re: [Intel-gfx] [PULL] drm-intel-next

On 22 October 2014 17:05, Chris Wilson ch...@chris-wilson.co.uk wrote: On Wed, Oct 22, 2014 at 09:09:43AM +1000, Dave Airlie wrote: On 21 October 2014 23:38, Daniel Vetter daniel.vet...@ffwll.ch wrote: Hi Dave, drm-intel-next-2014-10-03: - first batch of skl stage 1 enabling - fixes

Re: [Intel-gfx] [PULL] drm-intel-next

On Tue, Oct 21, 2014 at 2:27 PM, Daniel Vetter daniel.vet...@ffwll.ch wrote: There's some simple merge conflicts with current upstream but nothing serious really, I can push out a merge point if you want to. As usual -nightly has the solution for you to peek at. Sorrry I've lied, there's an

Re: [Intel-gfx] [PULL] drm-intel-next

On 21 October 2014 23:38, Daniel Vetter daniel.vet...@ffwll.ch wrote: Hi Dave, drm-intel-next-2014-10-03: - first batch of skl stage 1 enabling - fixes from Rodrigo to the PSR, fbc and sink crc code - kerneldoc for the frontbuffer tracking code, runtime pm code and the basic interrupt

Re: [Intel-gfx] [PULL] drm-intel-next

On 4 August 2014 17:10, Daniel Vetter daniel.vet...@ffwll.ch wrote: Hi Dave, Final feature pull for 3.17. drm-intel-next-2014-07-25: - Ditch UMS support (well just the config option for now) - Prep work for future platforms (Sonika Jindal, Damien) - runtime pm/soix fixes (Paulo, Jesse) -

Re: [Intel-gfx] [PULL] drm-intel-next

On Tue, Jul 1, 2014 at 10:24 AM, Jani Nikula jani.nik...@intel.com wrote: As discussed, it contains acpi-next as a dependency for Jesse's S0ix work through these merges (should not conflict, fingers crossed): Aside: This is acpi-next for 3.16, so _really_ shouldn't conflict. It's only in there

Re: [Intel-gfx] [PULL] drm-intel-next

On Tue, 06 May 2014, Daniel Vetter dan...@ffwll.ch wrote: On Tue, May 06, 2014 at 10:04:17PM +0200, Knut Petersen wrote: On 06.05.2014 20:59, Daniel Vetter wrote: On Tue, May 06, 2014 at 04:30:45PM +0300, Jani Nikula wrote: On Tue, 06 May 2014, Knut Petersen knut_peter...@t-online.de wrote:

Re: [Intel-gfx] [PULL] drm-intel-next

On 28.04.2014 15:26, Daniel Vetter wrote: Hi Dave, drm-intel-next-2014-04-16: - vlv infoframe fixes from Jesse - dsi/mipi fixes from Shobhit - gen8 pageflip fixes for LRI/SRM from Damien - cmd parser fixes from Brad Volkin - some prep patches for CHV, DRRS, ... - and tons of little things all

Re: [Intel-gfx] [PULL] drm-intel-next

On Tue, 06 May 2014, Knut Petersen knut_peter...@t-online.de wrote: On 28.04.2014 15:26, Daniel Vetter wrote: The patch below is a clear candidate for 3.15 as it fixes a regression introduced after 3.14 Egbert Eich (1): drm/i915/SDVO: For sysfs link put directory and target in correct

Re: [Intel-gfx] [PULL] drm-intel-next

On Tue, May 06, 2014 at 04:30:45PM +0300, Jani Nikula wrote: On Tue, 06 May 2014, Knut Petersen knut_peter...@t-online.de wrote: On 28.04.2014 15:26, Daniel Vetter wrote: The patch below is a clear candidate for 3.15 as it fixes a regression introduced after 3.14 Egbert Eich (1):

Re: [Intel-gfx] [PULL] drm-intel-next

On Tue, May 06, 2014 at 10:04:17PM +0200, Knut Petersen wrote: On 06.05.2014 20:59, Daniel Vetter wrote: On Tue, May 06, 2014 at 04:30:45PM +0300, Jani Nikula wrote: On Tue, 06 May 2014, Knut Petersen knut_peter...@t-online.de wrote: On 28.04.2014 15:26, Daniel Vetter wrote: The patch below

Re: [Intel-gfx] [PULL] drm-intel-next

On Thu, May 1, 2014 at 1:26 AM, Dave Airlie airl...@gmail.com wrote: Merged, but 32-bit still a thing, CC [M] drivers/gpu/drm/i915/i915_cmd_parser.o /ssd/git/drm-next/drivers/gpu/drm/i915/i915_cmd_parser.c: In function ‘i915_parse_cmds’:

Re: [Intel-gfx] [PULL] drm-intel-next

As discussed on irc this contains a (not yet fully tuned and also not yet in granting mode) cmd parser for gen7. Performance is still a bit rough, but not quite as bad as originally feared (Ken later on discovered that he also changed something in his glamour setup which made things worse). If

Re: [Intel-gfx] [PULL] drm-intel-next

On Fri, Dec 20, 2013 at 10:42:34PM +0100, Daniel Vetter wrote: Hi Dave, We're back to the regular -next updates. Somehow still not too much going on really, I guess everyone was thinking about vacation already ;-) On that topic: I'll be offline for 2 weeks now. I don't really expect much

Re: [Intel-gfx] [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: [Intel-gfx] [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: [Intel-gfx] [PULL] drm-intel-next-queued

On Sat, Aug 3, 2013 at 5:47 AM, Ben Widawsky b...@bwidawsk.net wrote: Hi Daniel. Jesse and Chris get egging me on to merge some patches. Dave has already merged the one patch for -fixes, so I have nothing but patches for -next-queued. It should be a straight fast-forward. QA has been running

Re: [Intel-gfx] [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

  1   2   >