Hi Christian,
On Mon, Apr 08, 2013 at 08:56:03AM +0200, Christian Gmeiner wrote:
> Using the new mail address of wolfram sang - got the following error:
>
>
> Delivery to the following recipient failed permanently:
>
> w.s...@pengutronix.de
>
> Technical details of permanent failure:
>
Using the new mail address of wolfram sang - got the following error:
Delivery to the following recipient failed permanently:
w.s...@pengutronix.de
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the
server for the recipient
Using the new mail address of wolfram sang - got the following error:
Delivery to the following recipient failed permanently:
w.s...@pengutronix.de
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the
server for the recipient
Hi Christian,
On Mon, Apr 08, 2013 at 08:56:03AM +0200, Christian Gmeiner wrote:
Using the new mail address of wolfram sang - got the following error:
Delivery to the following recipient failed permanently:
w.s...@pengutronix.de
Technical details of permanent failure:
Google
2013/1/24 Wolfram Sang :
> On Wed, Dec 19, 2012 at 05:07:09PM +0100, Christian Gmeiner wrote:
>> I have a at24 EEPROM connected via i2c bus provided by ISCH i2c
>> bus driver. This bus driver does not support
>> I2C_FUNC_SMBUS_WRITE_I2C_BLOCK and so I was looking for a way
>> to be able to write
2013/1/24 Wolfram Sang w.s...@pengutronix.de:
On Wed, Dec 19, 2012 at 05:07:09PM +0100, Christian Gmeiner wrote:
I have a at24 EEPROM connected via i2c bus provided by ISCH i2c
bus driver. This bus driver does not support
I2C_FUNC_SMBUS_WRITE_I2C_BLOCK and so I was looking for a way
to be
On Wed, Dec 19, 2012 at 05:07:09PM +0100, Christian Gmeiner wrote:
> I have a at24 EEPROM connected via i2c bus provided by ISCH i2c
> bus driver. This bus driver does not support
> I2C_FUNC_SMBUS_WRITE_I2C_BLOCK and so I was looking for a way
> to be able to write the eeprom. This patch adds
On Wed, Dec 19, 2012 at 05:07:09PM +0100, Christian Gmeiner wrote:
I have a at24 EEPROM connected via i2c bus provided by ISCH i2c
bus driver. This bus driver does not support
I2C_FUNC_SMBUS_WRITE_I2C_BLOCK and so I was looking for a way
to be able to write the eeprom. This patch adds support
ping
--
Christian Gmeiner, MSc
2012/12/19 Christian Gmeiner :
> I have a at24 EEPROM connected via i2c bus provided by ISCH i2c
> bus driver. This bus driver does not support
> I2C_FUNC_SMBUS_WRITE_I2C_BLOCK and so I was looking for a way
> to be able to write the eeprom. This patch adds support
ping
--
Christian Gmeiner, MSc
2012/12/19 Christian Gmeiner christian.gmei...@gmail.com:
I have a at24 EEPROM connected via i2c bus provided by ISCH i2c
bus driver. This bus driver does not support
I2C_FUNC_SMBUS_WRITE_I2C_BLOCK and so I was looking for a way
to be able to write the eeprom.
I have a at24 EEPROM connected via i2c bus provided by ISCH i2c
bus driver. This bus driver does not support
I2C_FUNC_SMBUS_WRITE_I2C_BLOCK and so I was looking for a way
to be able to write the eeprom. This patch adds support for
I2C_SMBUS_BYTE_DATA writing via i2c_smbus_write_byte_data.
It is
I have a at24 EEPROM connected via i2c bus provided by ISCH i2c
bus driver. This bus driver does not support
I2C_FUNC_SMBUS_WRITE_I2C_BLOCK and so I was looking for a way
to be able to write the eeprom. This patch adds support for
I2C_SMBUS_BYTE_DATA writing via i2c_smbus_write_byte_data.
It is
12 matches
Mail list logo