On Tue, Apr 21, 2015 at 1:26 PM, Luis R. Rodriguez <mcgrof@xxxxxxxxxxxxxxxx> wrote: > As we phase out MTRR we need to also prepare for the flip of > the default ioremap() behaviour from UC- to strong UC. There > are a few remaining drivers which does not allow us to make > a smooth transition over and which do not allow us to remove > MTRR use. The atyfb is a good example driver and this series > addresses the work required to avoid such regressions and > cover MTRR size contraint use cases. > > This series also documents what we've learned along on the > way in order to address removal of MTRR use and its corner > cases. > > Luis R. Rodriguez (6): > x86: add ioremap_uc() - force strong UC, PCD=1, PWT=1 > x86: document WC MTRR effects on PAT / non-PAT pages > video: fbdev: atyfb: move framebuffer length fudging to helper > video: fbdev: atyfb: clarify ioremap() base and length used > video: fbdev: atyfb: replace MTRR UC hole with strong UC > video: fbdev: atyfb: use arch_phys_wc_add() and ioremap_wc() There was so far just one comment fix for this series. I'll repost the series with the fix but other than that folks seem to be OK with this. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
