On Thu, Jul 25, 2013 at 09:34:05AM +0100, Chris Wilson wrote: > On Thu, Jul 25, 2013 at 09:41:49AM +0200, Daniel Vetter wrote: > > On Wed, Jul 24, 2013 at 05:04:43PM -0700, Jesse Barnes wrote: > > Two bikesheds: > > - Can't we give the thing a better name like "Intel Graphics Stolen"? > > Using a custom type and name seems simple enough and naturally leads it > to ending up in iomem_resource. > > > - Can't we store the iomem region somewhere so that intel-gtt.ko and > > i915.ko can get at it and we could drop the duplicated stolen detection > > code? > > The choice is then walking the resource list looking for our named > region or reading a couple of registers. Certainly walking the iomem makes > everything much clearer. Oh, I like this ;-) -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
