yam1

  • Content Count

    64
  • Joined

  • Last visited

About yam1

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Just another data point, the following code initializes an ili9341 display on DRM, but there is something else wrong with SPI or driver (but tested driver and it works under H6). One could see the display initializes under X, but the mouse pointer is kind of messed up (1st pic), also X terminal is garbled (2nd pic) . X would then eventually shut down because of lack of input device or something else. 1_ili9341.dts Note: Same behavior with fbdev driver.
  2. This is using the second ili9341 tiny drm driver (the one not named ili9341) on kernel 5.9.14, running on OrangePi One Plus. Screen seems to be shifted, colors are also off. Seems somewhere in Panfrost it requires the screen to be at least 640 wide and the color depth to be at least 24 or it requires a different set of fonts??? If I disable Panfrost the screen gets back to normal so you can see the whole terminal and the texts are in black instead of yellow and brown. The following benchmark results are from glmark2 running in full screen mode: =========================
  3. Two things: The lines should be gpio_out, not in. The reset line should be 0 for DRM, and 1 for fbdev, just because.
  4. I always use a short barrel adapter cable to convert to a standard sized barrel plug (5.5mm x 2.1mm). I would throw these short cables away if when they wear out. It would also save wear and tear on the board connector.
  5. On another note, kernel 5.7 or later is somehow automatically switched to use DRM driver for ili9486 displays - this driver is not working. To work around this I made a copy of the fb ili9486 driver with a different name: 0001-fbtft-fb_ili9486o.patch update: DRM driver is working (slowly) on 5.9, so may be you don't need this patch any more... fbdev drivers seem to take precedence over DRM drivers, so if you leave this in it would still use the fbdev driver -- for drmfb the initialization string seemed not being honored may be the reason why it's so slow
  6. I made a copy of the driver with a different resolution, now it works with 240x240, 1.3", or 1.54", st7789 based tiny displays: 0001-fbtft-fb_st7789.patch The patch contains the brightness fix as mentioned earlier - the colors seem okay on this type of displays.
  7. Anything wrong with the spi driver for rock3328 or the rock64v2 hardware? My spi tft displays are way too slow when compared with h3 boards (5.7 kernel). Any ideas?
  8. The colors seem a bit off, I tried fixing it with the following changes. Its a better approximation/mapping and also makes screen brighter but the colors still a bit off. Any ideas? for (i = 0; i < to_copy; i++) { + u16 pixel = vmem16; + u16 b = pixel & 0x1f; + u16 g = (pixel & (0x3f << 5)) >> 5; + u16 r = (pixel & (0x1f << 11)) >> 11; + + u8 r8 = ((r & 0x1F)*4*63)/31 + 3; + u8 g8 = (g & 0x3F)*4 + 3; + u8 b8 = ((b & 0x1F)*4*63)/31 + 3; +
  9. Screen blanker only blanks the first screen :-(
  10. I finally had to chance to use this feature of debian, it gives me something like the snapshot capability of vmware. The tutorial is well written, all you have to do is to change the keywords required by the current mainline. Everything else works the same: setenv bootargs "boot=live live-media-path=/live union=overlay persistence persistence-media=removable ${consoleargs} consoleblank=0 loglevel=${verbosity} ubootpart=$... For persistence, create a USB partition named "persistence" and specify the directories you want to persist in persistence.conf. The USBs would contain all
  11. Picture from Neo Core with 3 ili9341 2.8 screens running at 48 mhz (horizontal splits seems to work better than vertical splits), with mpv playback configuration: vo=x11 autofit=720x320 geometry=100%x100% video-aspect=72:32 sws-scaler=fast-bilinear hwdec=vdpau hwdec-codecs=all fs=yes video-sync=audio
  12. Thought you might want to know :-)
  13. Here is another version :-)
  14. Finally, my very own :-)
  15. One noticeable difference is background and menu across both screens, but 20.04 is missing a lot of dependencies like libwebkit-dev which I have not been able to find a substitute.