vrmay23 commented on PR #18301: URL: https://github.com/apache/nuttx/pull/18301#issuecomment-3892081131
Well, I kind of understand what you mean. Basically is up to the user to decides either to use a FB or a LCD driver. This is clear. However, please, don't get me wrong, but if we think carefully: The "RAM" argument is self-defeating (or my understanding can be wrong, for sure and if it is the case, correct me). But let's see what I thought: 1 - Small display means small framebuffer that fits in small MCU RAM. 2 - Large display already requires a capable MCU by nature (SPI bandwidth, processing power, peripheral complexity). So, any one pairing a 320x480 display with a 20KB MCU (without external ram) would face bigger problems than the framebuffer size the system simply wouldn't work for any meaningful use case. 3 - The lcd_dev_s line-by-line approach on a small MCU with a large display is technically possible but practically useless, because you cannot render anything meaningful on 320x480 without a proper buffer. Therefore, the "low RAM" advantage of lcd_dev_s only applies to small displays, where the framebuffer is also small and fits in RAM anyway. Hence, the argument defeats itself. I can for sure improve it, that's the idea in the end. Work as much as possible to support NuttX to grow, but not only grow (become better). I just need more time and knowledge :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
