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()
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, incompatibl
-Original Message-
> From: Matias N.
> Sent: Tuesday, April 21, 2020 1:55 AM
> To: dev@nuttx.apache.org
> Subject: Re: sending multiple rows to LCD in one go
>
> I understand your interest in supporting the NX graphics system. No
> intention to have any effect on that. To be cle
fer, size_t npixels);
#endif
Can we extend npixels longer than one line to represent the multiple row?
-Original Message-
From: Matias N.
Sent: Tuesday, April 21, 2020 1:55 AM
To: dev@nuttx.apache.org
Subject: Re: sending multiple rows to LCD in one go
I understand your interest
I understand your interest in supporting the NX graphics system. No intention
to have any effect on that. To be clear: absolutely no change to NX is needed
here, so there is no API dictation from LCD driver towards NX.
I think LCD devices, as any other hardware device, need a driver for NuttX,
Didn't quite understood what you mean by "crappy" driver interface.
My object is to support the core NuttX graphics system. Not user
kludges to get low level access to drivers. That is unimportant because
it is not on the OS roadmap. It was a mistake to create those userspace
drivers in t
Hi Greg,
sorry, I didn't quite understood your response. You mentioned NX functions
which, when using an LCD driver backend, will ultimately always call info
putrun(). To draw a rectangle, for example, you would need one putrun per line.
This means multiple SPI/I2C transfers and all communicatio
On 4/20/2020 8:45 AM, Gregory Nutt wrote:
when working with some LCDs (such as SSD1306 or Sharp Memory LCD) via
the LCD driver interface, the putrun() method greatly limits the
speed at which you can update the screen, since it imposes one
I2C/SPI transfer per putrun(). This type of graphical
when working with some LCDs (such as SSD1306 or Sharp Memory LCD) via the LCD
driver interface, the putrun() method greatly limits the speed at which you can
update the screen, since it imposes one I2C/SPI transfer per putrun(). This
type of graphical LCDs typically support sending a transfe
