Commit 29f077e4 authored by Alessandro Rubini's avatar Alessandro Rubini

doc and header: portability docs and fix

Signed-off-by: Alessandro Rubini's avatarAlessandro Rubini <rubini@gnudd.com>
parent ece4856b
...@@ -1011,7 +1011,18 @@ checkout from when it is a submodule. ...@@ -1011,7 +1011,18 @@ checkout from when it is a submodule.
As the last bits are fixed I'll update this chapter, and I'll remove As the last bits are fixed I'll update this chapter, and I'll remove
this section when everything is verified by a larger user base. this section when everything is verified by a larger user base.
@c ##########################################################################
@node Portability
@chapter Portability
This package should be portable. However I didn't test it on a wide
variety of system. I used it on a 32-bit x86 host, running version 2.6.32
and 3.4 of the kernel.
I verified that it compiles without any warning from version 2.6.27 up
to 3.5, on a 32-bit x86 processor. On 2.6.26 it fails for changes in
the Linux device structures. On 2.6.25 and earlier it fails much more
badly.
@bye @bye
@c LocalWords: gnudd titlepage iftex texinfo CERN documentlanguage settitle @c LocalWords: gnudd titlepage iftex texinfo CERN documentlanguage settitle
......
...@@ -80,6 +80,14 @@ struct fmc_gpio { ...@@ -80,6 +80,14 @@ struct fmc_gpio {
#define FMC_GPIO_USER(x) ((x) + 0x1400) /* 256 of them */ #define FMC_GPIO_USER(x) ((x) + 0x1400) /* 256 of them */
/* We may add SCL and SDA, or other roles if the need arises */ /* We may add SCL and SDA, or other roles if the need arises */
/* GPIOF_DIR_IN etc are missing before 3.0. copy from <linux/gpio.h> */
#ifndef GPIOF_DIR_IN
# define GPIOF_DIR_OUT (0 << 0)
# define GPIOF_DIR_IN (1 << 0)
# define GPIOF_INIT_LOW (0 << 1)
# define GPIOF_INIT_HIGH (1 << 1)
#endif
/* /*
* The operations are offered by each carrier and should make driver * The operations are offered by each carrier and should make driver
* design completely independent of th carrier. Named GPIO pins may be * design completely independent of th carrier. Named GPIO pins may be
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment