On Wed, Apr 20, 2016 at 01:17:30PM +0200, Daniel Vetter wrote: > On Wed, Apr 20, 2016 at 11:10:54AM +0200, Luis R. Rodriguez wrote: > > Reason I ask is since I noticed a while ago a lot of drivers > > were using info->fix.smem_start and info->fix.smem_len consistently > > for their ioremap'd areas it might make sense instead to let the > > internal framebuffer (register_framebuffer()) optionally manage the > > ioremap_wc() for drivers, given that this is pretty generic stuff. > > All that legacy fbdev stuff is just for legacy support, and I prefer to > have that as dumb as possible. There's been some discussion even around > lifting the "kick out firmware fb driver" out of fbdev, since we'd need it > to have a simple drm driver for e.g. uefi. > > But I definitely don't want a legacy horror show like fbdev to > automagically take care of device mappings for drivers. Makes sense, it also still begs the question if more modern APIs could manage the ioremap for you. Evidence shows people get sloppy and if things were done internally with helpers it may be easier to later make adjustments. Luis _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
