Starbane

I might be new to GitHub customs but this issue was a "Device support request" and #549 was a feature request so why close them? how would you differentiate between...

> I've done a bit of digging to see what it would take to support these modules, and the main piece missing right now is support for Quad SPI buses....

@FeralAI you wanna collaborate on the QSPI integration into LovyanGFX?

I got my T4-S3 in the mail today and it broke my Bus/Driver but it should not since it is command compatible. I got a set pixel function working on...

> @Starbane Here's an example for the 1.91" using just raw pushColors() - no GFX library: [Lilygo_amoled_191_raw_push.zip](https://github.com/lovyan03/LovyanGFX/files/14893523/Lilygo_amoled_191_raw_push.zip) > > Tested with ESP_Arduino Alpha 3. > > Notes: > > GPIO...

I do that as part of the initialization: ```C++ if (_config.pmicen != -1) { if(digitalPinCanOutput(_config.pmicen)) { pinMode(_config.pmicen, OUTPUT); digitalWrite(_config.pmicen, HIGH); } else { logError("QSPI - Failed to initialize bus, PMICEn...

Yes it works. So something is off in my code. I suspect my QSPI bus driver is not working. but the thing is that it is working on the 1.91...

If I include TFT_eSPI into you example it stops working just like mine code. So the line ```C++ #include ``` breaks your example for me

It seems that it is the order of the including that is the problem. As well as if I do tft.begin() on the TFT_eSPI. I managed to get it to...

I experience the same thing, it will not boot. I try to mount the boot image and get an error stating that there is some thing wrong with /dev/loop