Jump to content

lentinj

Members
  • Posts

    4
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. Excellent. I can now build and run modules/gwin/widgets without any modifications with GFXBOAD=Linux-Framebuffer-Touch Thanks for your help.
  2. mxsfb.c expects bits_per_pixel set to either 16 or 32 (i.e. RGBA, even though the "A" is completely ignored): http://lxr.free-electrons.com/source/drivers/video/fbdev/mxsfb.c#L449 ...but ugfx requests a video mode of 24 bits-per-pixel (i.e. RGB) when using GDISP_PIXELFORMAT_RGB888. I've not dug around enough to decide where the bug really is. However, one terrible bodge later: Index: git/src/gdisp/gdisp_driver.h =================================================================== --- git.orig/src/gdisp/gdisp_driver.h +++ git/src/gdisp/gdisp_driver.h @@ -820,7 +820,7 @@ typedef struct GDISPVMT { #define LLDCOLOR_BITS_R ((GDISP_LLD_PIXELFORMAT>>8) & 0x0F) #define LLDCOLOR_BITS_G ((GDISP_LLD_PIXELFORMAT>>4) & 0x0F) #define LLDCOLOR_BITS_B ((GDISP_LLD_PIXELFORMAT>>0) & 0x0F) - #define LLDCOLOR_BITS (LLDCOLOR_BITS_R + LLDCOLOR_BITS_G + LLDCOLOR_BITS_B) + #define LLDCOLOR_BITS (LLDCOLOR_BITS_R + LLDCOLOR_BITS_G + LLDCOLOR_BITS_B + LLDCOLOR_BITS_B) // From the number of bits determine COLOR_TYPE, COLOR_TYPE_BITS and masking #if LLDCOLOR_BITS <= 8 ...and I was on my way. uGFX seems to work fine, but this obviously isn't production-quality code
  3. You're right, copied the files into drivers/ginput/touch/LINUX_EVENT/ and boards/base/Linux-Framebuffer-Event respectively and was able to build and run the modules/gwin/widgets demo fine. Didn't need to modify any code. Shouldn't have heeded the not-complete warnings in that thread! I think it'd be a very useful addition if you could include it.
  4. Hello, I'm looking at using uGFX to an i.MX233 board. The MXS framebuffer works fine once I hack LLDCOLOR_BITS to include an extra dummy byte for an (unused) alpha channel. The touchscreen is available via. /dev/input/event0, but I can't see any driver to use. This thread talks about an unfinished input subsystem driver, is there a complete version somewhere now, or is this something we'd have to develop?
×
×
  • Create New...