Linux drivers development - Revision history

WikiSysop: /* Adding your own drivers */

2013-09-04T15:55:52Z

‎Adding your own drivers

Salocin68 at 19:28, 1 August 2010

2010-08-01T19:28:07Z

JulienB: direct access to registers with Macro is deprecated

2009-08-05T16:48:35Z

direct access to registers with Macro is deprecated

JulienB: /* Adding your own drivers */

2009-08-05T16:46:15Z

‎Adding your own drivers

JulienB at 20:23, 11 February 2009

2009-02-11T20:23:23Z

JulienB: /* i.MX register access from driver */

2008-12-16T17:31:38Z

‎i.MX register access from driver

JulienB: /* Adding your own drivers */

2008-12-16T17:24:43Z

‎Adding your own drivers

NicolasC at 05:51, 27 July 2007

2007-07-27T05:51:06Z

JulienB: /* Driver compilation */

2007-03-24T16:15:20Z

‎Driver compilation

JulienB: /* Useful Links */

2007-03-24T16:13:41Z

‎Useful Links

@@ Line 10: / Line 10: @@
 You can select, in the linux "menuconfig / xconfig" tool, which Armadeus drivers you want to add on your target.
 <pre class="host">
-  $ make linux26-menuconfig
+  $ make linux-menuconfig
 </pre>
@@ Line 30: / Line 30: @@
 or
 <pre class="host">
-  $ make linux26
+  $ make linux
 </pre>
-Only ''make linux26'' will install the modules in the target rootfs image
+Only ''make linux'' will install the modules in the target rootfs image
 == i.MX register access from driver ==

← Older revision		Revision as of 19:28, 1 August 2010
Line 49:		Line 49:
	* http://old.kernelnewbies.org/documents/kdoc/kernel-api/linuxkernelapi.html		* http://old.kernelnewbies.org/documents/kdoc/kernel-api/linuxkernelapi.html
	* http://lwn.net/Articles/driver-porting/		* http://lwn.net/Articles/driver-porting/
−
−	~~{{LanguageBar\|Linux_drivers_development\|Développement de pilotes linux\|Linux Treiber Entwicklung}}~~

@@ Line 37: / Line 37: @@
 == i.MX register access from driver ==
-To access i.MX registers from your driver, please use the macros defined in:
+To access i.MX registers from your driver, please use the ''readw/readl/writew/writel'' helper functions.
-<source lang="c">
+Take a look at at ''arch/arm/mach-mx2/apf27.c'' or ''arch/arm/mach-imx/apf9328.c'' to have examples.
-#include <mach/imx-regs.h>
-</source>
-−
-<strike>For example (access to PWM control register):</strike>
-<source lang="c">
-/* enable the PWM */
-PWMC |= PWMC_EN;
-</source>
 ==Debug==

@@ Line 19: / Line 19: @@
 Here is the way to add custom drivers:
-* in ''armadeus/target/linux/modules/'', add a directory for your driver (ex ''toto/'')
+* change current dir to your armadeus view
-* put reference to this directory in the ''armadeus/target/linux/modules/Makefile'' and ''armadeus/target/linux/modules/Kconfig'' files
+* in ''target/linux/modules/'', add a directory for your driver (ex ''toto/'')
-* in ''toto/'' put your driver source code and create 2 files, ''Kconfig'' and ''Makefile''. (Use ''armadeus/target/linux/modules/gpio/Makefile'' & ''Kconfig'' as examples.)
+* put reference to this directory in the ''target/linux/modules/Makefile'' and ''target/linux/modules/Kconfig'' files
 To compile all the custom modules, either launch:
 <pre class="host">
-  $ make -C armadeus/target/linux/modules/
+  $ make -C target/linux/modules/
 </pre>
 or
@@ Line 32: / Line 33: @@
 </pre>
-only ''make linux26'' will install the modules in the target rootfs image
+Only ''make linux26'' will install the modules in the target rootfs image
 == i.MX register access from driver ==

@@ Line 9: / Line 9: @@
 Our custom drivers build is integrated to the Linux build system (kbuild).
 You can select, in the linux "menuconfig / xconfig" tool, which Armadeus drivers you want to add on your target.
   $ make linux26-menuconfig
 Here is the way to add custom drivers:
-* in ''armadeus/target/linux/modules/'', add a directory for you driver (ex ''toto/'')
+* in ''armadeus/target/linux/modules/'', add a directory for your driver (ex ''toto/'')
 * put reference to this directory in the ''armadeus/target/linux/modules/Makefile'' and ''armadeus/target/linux/modules/Kconfig'' files
 * in ''toto/'' put your driver source code and create 2 files, ''Kconfig'' and ''Makefile''. (Use ''armadeus/target/linux/modules/gpio/Makefile'' & ''Kconfig'' as examples.)
 To compile all the custom modules, either launch:
   $ make -C armadeus/target/linux/modules/
 or
   $ make linux26
-only ''make linux26'' will install the modules in target rootfs image
+only ''make linux26'' will install the modules in the target rootfs image
 == i.MX register access from driver ==
@@ Line 30: / Line 41: @@
 </source>
-For example (access to PWM control register):
+<strike>For example (access to PWM control register):</strike>
 <source lang="c">
 /* enable the PWM */
@@ Line 37: / Line 48: @@
 ==Debug==
-Activate debug messages (from pr_debug() function) on console:
+* Activate debug messages (from pr_debug() function) on console:
   # echo 8 > /proc/sys/kernel/printk
 == Useful Links ==
@@ Line 44: / Line 57: @@
 * http://lwn.net/Articles/driver-porting/
-<br>[[Image:FrenchFlag.png]][[Fr:Développement de pilotes linux | Cette page en Français]]
+{{LanguageBar|Linux_drivers_development|Développement de pilotes linux|Linux Treiber Entwicklung}}

← Older revision		Revision as of 05:51, 27 July 2007
Line 40:		Line 40:
	* http://old.kernelnewbies.org/documents/kdoc/kernel-api/linuxkernelapi.html		* http://old.kernelnewbies.org/documents/kdoc/kernel-api/linuxkernelapi.html
	* http://lwn.net/Articles/driver-porting/		* http://lwn.net/Articles/driver-porting/
		+
		+	<br>[[Image:FrenchFlag.png]][[Fr:Développement de pilotes linux \| Cette page en Français]]

@@ Line 5: / Line 5: @@
 * Linux Device Drivers (3rd edition) book: http://lwn.net/Kernel/LDD3/
-== Driver compilation ==
+== Adding your own drivers ==
 Our custom drivers build is integrated to the Linux build system (kbuild).