Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <CGME20190314114511epcas2p2a9669714177b00989bd3195300f7d3a6@epcas2p2.samsung.com>
 <20190314114500.8336-1-kraxel@redhat.com> <33cf37dc-8456-0316-0b48-fca7c92caa28@samsung.com>
 <CAKMK7uEs+OaoiEmd9Dp6K_v5Pz4pf197DP8KFkvhNMYXv9tYxA@mail.gmail.com>
 <20190402204325.cqu7fobzekd3ccls@sirius.home.kraxel.org> <CAKMK7uHLY1RKUGbqDeHTNnx98y-FLhGWKGcG-o9KDH54=BObAg@mail.gmail.com>
 <20190403072238.76gwp6rfumgqiely@sirius.home.kraxel.org>
In-Reply-To: <20190403072238.76gwp6rfumgqiely@sirius.home.kraxel.org>
From:   Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Wed, 3 Apr 2019 09:25:35 +0200
Message-ID: <CAKMK7uFGv_oFWHqnWLNz56BkTGk8mXwsEmAXy52Yo9tbMQu+qg@mail.gmail.com>
Subject: Re: [PATCH] fbdev: list all pci memory bars as conflicting apertures
To:     Gerd Hoffmann <kraxel@redhat.com>
Cc:     Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
        dri-devel <dri-devel@lists.freedesktop.org>,
        "open list:FRAMEBUFFER LAYER" <linux-fbdev@vger.kernel.org>,
        open list <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, Apr 3, 2019 at 9:22 AM Gerd Hoffmann <kraxel@redhat.com> wrote:
>
> On Wed, Apr 03, 2019 at 08:48:16AM +0200, Daniel Vetter wrote:
> > On Tue, Apr 2, 2019 at 10:43 PM Gerd Hoffmann <kraxel@redhat.com> wrote:
> > >
> > > On Tue, Apr 02, 2019 at 02:09:45PM +0200, Daniel Vetter wrote:
> > > > On Mon, Apr 1, 2019 at 4:00 PM Bartlomiej Zolnierkiewicz
> > > > <b.zolnierkie@samsung.com> wrote:
> > > > >
> > > > >
> > > > > On 03/14/2019 12:45 PM, Gerd Hoffmann wrote:
> > > > > > Simply add all pci memory bars to struct apertures_struct in
> > > > > > remove_conflicting_pci_framebuffers(), without depending on the
> > > > > > res_id parameter.
> > > > > >
> > > > > > The plan is to drop the res_id parameter later on.  For now keep the
> > > > > > parameter, use it for sanity-checking and warn on inconsistencies.
> > > > > >
> > > > > > Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> > > > > > Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> > > > >
> > > > > Patch queued for v5.2, thanks.
> > > >
> > > > Might be good to also stuff this into drm (double merge or topic
> > > > branch, whatever you prefer), since that's where all the users are.
> > > > Gerd also has some follow-up patches to apply on top of this one iirc.
> > >
> > > No follow-up patches yet.  Plan is to wait a bit, see if the
> > > sanity-checks trigger, and if all goes well go drop the res_id
> > > parameter in 5.3 ...
> >
> > Hm I thought you had a patch to convert i915 over. Or did that land already?
>
> Ah, *that* one.  Yep, that is still sitting in a branch here.  Didn't
> rebase it yet.  But I suspect it will be easier to first drop res_id
> and then rebase the i915 patch on top of *that*, so I don't have to
> figure which i915 revision needs which res_id ...

Ok, sounds like a plan for 5.3 somewhen.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch