Linux - Revision history

Tectu: /* Touchscreen / Mouse */

2016-08-23T22:35:41Z

‎Touchscreen / Mouse

Tectu: /* Touchscreen / Mouse */

2016-08-23T22:29:32Z

‎Touchscreen / Mouse

Tectu at 22:27, 23 August 2016

2016-08-23T22:27:50Z

Tectu: /* Framebuffer */

2016-08-23T22:27:39Z

‎Framebuffer

Tectu: /* Makefile */

2016-08-23T22:00:40Z

‎Makefile

Tectu: Undo revision 1756 by Tectu (talk)

2016-08-23T21:55:46Z

Undo revision 1756 by Tectu (talk)

Tectu at 21:54, 23 August 2016

2016-08-23T21:54:41Z

Tectu: /* Example */

2016-08-21T16:52:49Z

‎Example

Tectu: /* Example */

2016-08-21T16:52:34Z

‎Example

Tectu: /* Framebuffer */

2016-08-21T16:52:24Z

‎Framebuffer

@@ Line 45: / Line 45: @@
 #define GMOUSE_LINUX_EVENT_DEVICE "/dev/input/event0"
 </source>
 === Example ===

@@ Line 38: / Line 38: @@
 === Touchscreen / Mouse ===
-When the touchscreen/mouse device is already accessible through the Linux event input system ''(eg. <code>/dev/input/event0</code> or similar)'' the </code>Linux-Event</code> GINPUT driver can be used to interface the device.
+When the touchscreen/mouse device is already accessible through the Linux event input system ''(eg. <code>/dev/input/event0</code> or similar)'' the <code>Linux-Event</code> GINPUT driver can be used to interface the device.
 To simplify handling of systems that use the [[Linux#Framebuffer|framebuffer]] and a touchscreen or mouse via the event input system, the <code>Linux-Framebuffer-Touch</code> board files can be used.
 === Example ===

@@ Line 40: / Line 40: @@
 When the touchscreen/mouse device is already accessible through the Linux event input system ''(eg. <code>/dev/input/event0</code> or similar)'' the </code>Linux-Event</code> GINPUT driver can be used to interface the device.
 To simplify handling of systems that use the [[Linux#Framebuffer|framebuffer]] and a touchscreen or mouse via the event input system, the <code>Linux-Framebuffer-Touch</code> board files can be used.
 === Example ===
@@ Line 59: / Line 58: @@
 === Makefile ===
 A ready-to-use Makefile to compile a native µGFX Linux application can be found under ''/boards/base/Linux-X/example/''.

← Older revision		Revision as of 22:27, 23 August 2016
Line 36:		Line 36:

	The pixel format can be set using <code>GDISP_LLD_PIXELFORMAT</code>. By default <code>GDISP_PIXELFORMAT_RGB888</code> is used. Note that the Linux framebuffer only supports RGB mode (no BGR modes).		The pixel format can be set using <code>GDISP_LLD_PIXELFORMAT</code>. By default <code>GDISP_PIXELFORMAT_RGB888</code> is used. Note that the Linux framebuffer only supports RGB mode (no BGR modes).
		+
		+	=== Touchscreen / Mouse ===
		+	When the touchscreen/mouse device is already accessible through the Linux event input system ''(eg. <code>/dev/input/event0</code> or similar)'' the </code>Linux-Event</code> GINPUT driver can be used to interface the device.
		+	To simplify handling of systems that use the [[Linux#Framebuffer\|framebuffer]] and a touchscreen or mouse via the event input system, the <code>Linux-Framebuffer-Touch</code> board files can be used.
		+

	=== Example ===		=== Example ===

← Older revision		Revision as of 22:00, 23 August 2016
Line 54:		Line 54:
	=== Makefile ===		=== Makefile ===
	A ready-to-use Makefile to compile a native µGFX Linux application can be found under ''/boards/base/Linux-X/example/''.		A ready-to-use Makefile to compile a native µGFX Linux application can be found under ''/boards/base/Linux-X/example/''.
		+
		+	== Touchscreen / Mouse ==
		+	When the touchscreen/mouse device is already accessible through the Linux event input system ''(eg. <code>/dev/input/event0</code> or similar)'' the </code>Linux-Event</code> GINPUT driver can be used to interface the device.
		+
		+	To simplify handling of systems that use the [[Linux#Framebuffer\|framebuffer]] and a touchscreen or mouse via the event input system, the <code>Linux-Framebuffer-Touch</code> board files can be used.

@@ Line 1: / Line 1: @@
 µGFX runs natively on any Linux system. The SDL driver can be used to compile a native Linux desktop application. This is especially useful during the development process as the entire µGFX application can be developed and tested without flashing the target microcontroller every time. The Framebuffer driver is useful to use µGFX on embedded Linux systems that don't run X or a full Desktop environment.
-== Display ==
+== SDL ==
-=== SDL ===
 Using the SDL driver is the '''recommended way''' of running µGFX inside a Linux system with a desktop environment. The SDL driver also supports mouse and keyboard input.
-==== Dependencies ====
+=== Dependencies ===
 [https://www.libsdl.org/ SDL2] is required to use the µGFX SDL driver. As we are compiling an SDL application ourselves, the development version of the SDL2 library used. On most common Linux distributions these can be installed by the <code>libsdl2-dev</code> package. However, note that µGFX applications get compiled as 32-bit applications. Therefore, you have to install the 32-bit variation of that package if you are running a 64-Bit Linux.
@@ Line 13: / Line 12: @@
 </source>
-==== Makefile ====
+=== Makefile ===
 A ready-to-use Makefile to compile a native µGFX Linux application can be found under ''/boards/base/Linux-SDL/example/''.
@@ Line 21: / Line 20: @@
 </syntaxhighlight>
-=== Framebuffer ===
+== Framebuffer ==
 The framebuffer driver can be used to run µGFX on embedded Linux systems that don't run X or a desktop environment.
 <syntaxhighlight lang=make>
@@ Line 27: / Line 26: @@
 </syntaxhighlight>
-==== Dependencies ====
+=== Dependencies ===
 There are no dependencies to use the Linux framebuffer driver. However, the Linux kernel must have been compiled with framebuffer support enabled.
-==== Makefile ====
+=== Makefile ===
 A ready-to-use Makefile to compile a native µGFX Linux application can be found under ''/boards/base/Linux-Framebuffer/example/''.
-==== Framebuffer device ====
+=== Framebuffer device ===
 By default, the framebuffer driver looks for the framebuffer device under <code>/dev/fb0</code> and <code>/dev/fb/0</code>. If your system links the framebuffer under a different path, please modify the <code>FBDEV_PATH1</code> macro in the <code>/boards/base/Linux-Framebuffer/board_framebuffer.h</code> file.
 The pixel format can be set using <code>GDISP_LLD_PIXELFORMAT</code>. By default <code>GDISP_PIXELFORMAT_RGB888</code> is used. Note that the Linux framebuffer only supports RGB mode (no BGR modes).
-==== Example ====
+=== Example ===
 Please have a look at the [[Raspberry_Pi|Raspberry Pi guide]] for an extensive step-by-step tutorial on how-to getting µGFX running on an embedded Linux system using the framebuffer.
-=== X ===
+== X ==
 Using the X driver is '''not recommended'''. It's deprecated and an old relic that is kept in the µGFX library as a reference for examples and for systems that are incapable of running SDL. It is '''STRONGLY''' recommended to use the SDL driver instead (see above).
 The performance of the resulting program is very bad because the X driver just uses <code>setPixel()</code> and doesn't take any advantage of area blitting or double buffering.
-==== Dependencies ====
+=== Dependencies ===
 The X11 development libraries are required to run the µGFX X driver.
@@ Line 53: / Line 52: @@
 </source>
-==== Makefile ====
+=== Makefile ===
 A ready-to-use Makefile to compile a native µGFX Linux application can be found under ''/boards/base/Linux-X/example/''.

← Older revision		Revision as of 16:52, 21 August 2016
Line 36:		Line 36:

	The pixel format can be set using <code>GDISP_LLD_PIXELFORMAT</code>. By default <code>GDISP_PIXELFORMAT_RGB888</code> is used. Note that the Linux framebuffer only supports RGB mode (no BGR modes).		The pixel format can be set using <code>GDISP_LLD_PIXELFORMAT</code>. By default <code>GDISP_PIXELFORMAT_RGB888</code> is used. Note that the Linux framebuffer only supports RGB mode (no BGR modes).
		+
		+	== Example ==
		+	Please have a look at the [[Raspberry_Pi]] guide for an extensive step-by-step tutorial on how-to getting µGFX running on an embedded Linux system using the framebuffer.

	== X ==		== X ==