On Fri, 31 Jul 2020 at 23:32, Christian König <christian.koenig@xxxxxxx> wrote: > > Am 31.07.20 um 06:05 schrieb Dave Airlie: > > From: Dave Airlie <airlied@xxxxxxxxxx> > > > > This makes it easier to move these to a driver allocated system > > No, sorry that looks like going into the wrong direction to me. > > I already wanted to suggest to get rid of the size argument instead. I'm not sure how it should look then, I don't want the driver poking around inside the range manager code, the range manager should be a generic object that driver inits and leaves alone, I definitely don't want the driver to be poking caching and size values into the man objects for it, since it isn't a driver object. Do you have some other view on how the generic range manager should work? Dave. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
