Mercurialcrosstool-ng / file revision
summary | shortlog | changelog | graph | tags | branches | files | changeset | file | latest | revisions | annotate | diff | raw | help
patches/linux/2.6.11.3/160-linux-2.6.11-allow-gcc-4.0-i2c.patch
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Fri Apr 18 22:16:28 2008 +0000 (2008-04-18)
changeset 451 8a72f9bcf675
permissions -rw-r--r--
Using SOCKS 4/5 proxy is no easy task:
- a machine may well be able to reach the proxy, even if it is not on the same sub-net(s) as the machine itself (absolutely legitimate)
- tsocks.conf needs a list of so-called 'local' networks that can be reached without the need for a SOCKS connection
- SOCKS proxies are expected to be in 'local' networks
- there is absolutely NO way to tell what networks are local, besides the sub-net(s) the machine is in

Therefore, appropriate configuration of SOCKS 4/5 configuration is really complex, and attempts to correctly overcome this issue are doomed.

/trunk/scripts/crosstool.sh | 52 46 6 0 ++++++++++++++++++++++++++++++++++----
/trunk/config/global/download_extract.in | 39 31 8 0 +++++++++++++++++++++++------
2 files changed, 77 insertions(+), 14 deletions(-) 
     1 Fixes

     2 

     3 In file included from fs/compat_ioctl.c:69,

     4                  from arch/ppc64/kernel/ioctl32.c:24:

     5 include/linux/i2c.h:58: error: array type has incomplete element type

     6 include/linux/i2c.h:197: error: array type has incomplete element type

     7 

     8 when compiling with gcc-4.0.

     9 

    10 --- linux-2.6.11.3/include/linux/i2c.h.old	2005-03-19 10:59:09.000000000 -0800

    11 +++ linux-2.6.11.3/include/linux/i2c.h	2005-03-19 11:01:37.000000000 -0800

    12 @@ -36,7 +36,22 @@

    13  

    14  /* --- General options ------------------------------------------------	*/

    15  

    16 -struct i2c_msg;

    17 +/*

    18 + * I2C Message - used for pure i2c transaction, also from /dev interface

    19 + */

    20 +struct i2c_msg {

    21 +	__u16 addr;	/* slave address			*/

    22 + 	__u16 flags;		

    23 +#define I2C_M_TEN	0x10	/* we have a ten bit chip address	*/

    24 +#define I2C_M_RD	0x01

    25 +#define I2C_M_NOSTART	0x4000

    26 +#define I2C_M_REV_DIR_ADDR	0x2000

    27 +#define I2C_M_IGNORE_NAK	0x1000

    28 +#define I2C_M_NO_RD_ACK		0x0800

    29 + 	__u16 len;		/* msg length				*/

    30 + 	__u8 *buf;		/* pointer to msg data			*/

    31 +};

    32 +

    33  struct i2c_algorithm;

    34  struct i2c_adapter;

    35  struct i2c_client;

    36 @@ -379,22 +394,6 @@

    37  /* Return 1 if adapter supports everything we need, 0 if not. */

    38  extern int i2c_check_functionality (struct i2c_adapter *adap, u32 func);

    39  

    40 -/*

    41 - * I2C Message - used for pure i2c transaction, also from /dev interface

    42 - */

    43 -struct i2c_msg {

    44 -	__u16 addr;	/* slave address			*/

    45 - 	__u16 flags;		

    46 -#define I2C_M_TEN	0x10	/* we have a ten bit chip address	*/

    47 -#define I2C_M_RD	0x01

    48 -#define I2C_M_NOSTART	0x4000

    49 -#define I2C_M_REV_DIR_ADDR	0x2000

    50 -#define I2C_M_IGNORE_NAK	0x1000

    51 -#define I2C_M_NO_RD_ACK		0x0800

    52 - 	__u16 len;		/* msg length				*/

    53 - 	__u8 *buf;		/* pointer to msg data			*/

    54 -};

    55 -

    56  /* To determine what functionality is present */

    57  

    58  #define I2C_FUNC_I2C			0x00000001
crosstool-ng