ugfx/drivers/gdisp/VMT
Andrew Hannam 8275c8820f Ginput and structure changes
GINPUT Touch including drivers
GTIMER fixes
GEVENT fixes
GWIN button completion
Structure changes to better seperate sections of a sub-system
2012-11-26 18:45:26 +10:00
..
gdisp_lld.c Ginput and structure changes 2012-11-26 18:45:26 +10:00
gdisp_lld.mk Makefile LCD replaced with GFX 2012-10-04 09:09:03 +02:00
gdisp_lld_config.h docs 2012-11-03 02:23:34 +01:00
gdisp_lld_driver1.c big doxygen update - now it works as it should 2012-11-07 01:47:53 +01:00
gdisp_lld_driver2.c big doxygen update - now it works as it should 2012-11-07 01:47:53 +01:00
readme.txt renamed macros 2012-10-21 01:47:11 +02:00

readme.txt

This file contains invisible Unicode characters!

This file contains invisible Unicode characters that may be processed differently from what appears below. If your use case is intentional and legitimate, you can safely ignore this warning. Use the Escape button to reveal hidden characters.

This driver enables you to have two underlying drivers handling different hardware.
A choice is made at run-time of which driver to call based on which driver succeeds
to initialise first (init returns TRUE).

To use this driver:

1. Add in your halconf.h:
	a) #define GFX_USE_GDISP	TRUE
	b) Any optional high level driver defines (see gdisp.h) eg: GDISP_NEED_MULTITHREAD
	c) Define these:
		#define GDISP_VMT_NAME1(x)	x##YourDriver1
		#define GDISP_VMT_NAME2(x)	x##YourDriver2
		Note YourDriver1 & 2 are the basenames of the directories containing the driver.
		Note that both drivers must be the same pixel format which is
			GDISP_PIXELFORMAT_RGB565 by default. Alter gdispVMT/gdisp_lld_config.h if your
			pixel format is different on both drivers.
	d) Any driver specific defines. If both drivers use the same defines then they must
		accept the same values for the define.

2. To your makefile add the following lines:
	include $(CHIBIOS)/os/halext/halext.mk
	include $(CHIBIOS)/os/halext/drivers/gdispVMT/gdisp_lld.mk