On Wed, Feb 13, 2013 at 1:46 PM, Dmitry Torokhov
wrote:
> On Fri, Feb 01, 2013 at 04:11:46PM +0800, Daniel Kurtz wrote:
>> In some cases it is possible for a device to be in its bootloader at
>> driver probe time. This is detected by the driver when probe() is called
>> with an i2c_client which
On Fri, Feb 01, 2013 at 04:11:46PM +0800, Daniel Kurtz wrote:
> In some cases it is possible for a device to be in its bootloader at
> driver probe time. This is detected by the driver when probe() is called
> with an i2c_client which has one of the Atmel Bootloader i2c addresses.
>
> In this
On Fri, Feb 01, 2013 at 04:11:46PM +0800, Daniel Kurtz wrote:
In some cases it is possible for a device to be in its bootloader at
driver probe time. This is detected by the driver when probe() is called
with an i2c_client which has one of the Atmel Bootloader i2c addresses.
In this case,
On Wed, Feb 13, 2013 at 1:46 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Fri, Feb 01, 2013 at 04:11:46PM +0800, Daniel Kurtz wrote:
In some cases it is possible for a device to be in its bootloader at
driver probe time. This is detected by the driver when probe() is called
with an
In some cases it is possible for a device to be in its bootloader at
driver probe time. This is detected by the driver when probe() is called
with an i2c_client which has one of the Atmel Bootloader i2c addresses.
In this case, we should load enough driver functionality to still loading
new
In some cases it is possible for a device to be in its bootloader at
driver probe time. This is detected by the driver when probe() is called
with an i2c_client which has one of the Atmel Bootloader i2c addresses.
In this case, we should load enough driver functionality to still loading
new
6 matches
Mail list logo