From what I understand, the TILER is a MMU trick. Data is shuffled as it read or written. Well, not the data but the address where the data is read/written.Still curious how TILER's gonna do that with 0 performance impact. I'm all in for miracles but it doesn't want to sound plausible to me. Wouldn't it at the very least either block framebuffer access during rotation or need it's own copy of it?
And how does it impact applications wanting to use TILER?
It'll probably just work out some way and no one will even think about it anymore once it runs, but I'm curious.
So the TILER can implement a zero-copy rotation. The program only writes the data to memory once. The display driver only reads the data from memory once. The rotation happens in between either by using the TILER during the read or write. In theory, zero-cost rotation. If it works that is.