Yes, many LCDs will not support this functionality. In that case, putrun() should test for npixels > row size and return ERROR if this happens. Right now many LCD drivers should be updated if this change in semantics is performed, since they all assume npixels < row size. If a separate putrows() function is added instead, putrun() semantics can stay as is. What would be preferable?
On Tue, Apr 21, 2020, at 12:07, Gregory Nutt wrote: > > > That would indeed work as well. I did not suggest it to avoid modifying > > semantics of an existing call. > > It should work on most but not all LCDs. It should work on LCDs where > the run is simply writing pixels into a graphics memory. But there are > other LCDs that have to do other, incompatible operations. Those are, I > think, all very low end LCD controllers. > > >
