Bukie Mabayoje wrote:
I will be glad to work with on this, I have some exposure to the BMC.
See text below in blue.
bukie
Corey Minyard wrote:
Mark Studebaker wrote:
> is there a way to do this solely in i2c-core without having to
> add support to all the drivers?
Yes and no. In order to
Bukie Mabayoje wrote:
I will be glad to work with on this, I have some exposure to the BMC.
See text below in blue.
bukie
Corey Minyard wrote:
Mark Studebaker wrote:
is there a way to do this solely in i2c-core without having to
add support to all the drivers?
Yes and no. In order to support
> I will be glad to work with on this, I have some exposure to the BMC. See
> text below in blue.
>
> bukie
>
> Corey Minyard wrote:
>
>> Mark Studebaker wrote:
>>
>> > is there a way to do this solely in i2c-core without having to
>> > add support to all the drivers?
>>
>> Yes and no. In order
Mark Studebaker wrote:
is there a way to do this solely in i2c-core without having to
add support to all the drivers?
Yes and no. In order to support this async operation, the driver cannot
block and do things like msleep() or schedule(). It has to start the
operation, return, and either let
is there a way to do this solely in i2c-core without having to
add support to all the drivers?
Corey Minyard wrote:
I have an IPMI interface driver that sits on top of the I2C code. I'd
like to get it into the mainstream kernel, but I have a few problems
to solve first before I can do that. The
is there a way to do this solely in i2c-core without having to
add support to all the drivers?
Corey Minyard wrote:
I have an IPMI interface driver that sits on top of the I2C code. I'd
like to get it into the mainstream kernel, but I have a few problems
to solve first before I can do that. The
Mark Studebaker wrote:
is there a way to do this solely in i2c-core without having to
add support to all the drivers?
Yes and no. In order to support this async operation, the driver cannot
block and do things like msleep() or schedule(). It has to start the
operation, return, and either let
I will be glad to work with on this, I have some exposure to the BMC. See
text below in blue.
bukie
Corey Minyard wrote:
Mark Studebaker wrote:
is there a way to do this solely in i2c-core without having to
add support to all the drivers?
Yes and no. In order to support this
Quoth Corey Minyard:
> I would really like add asynchronous interface to the I2C bus drivers.
Applause! This is IMO overdue, but maybe sensor systems don't need it
as much as other I2C applications do. For example, see the isp1301_omap
driver, which could have been hugely simpler if there were
I have an IPMI interface driver that sits on top of the I2C code. I'd
like to get it into the mainstream kernel, but I have a few problems
to solve first before I can do that. The I2C code is synchronous and
must run from a task context. The IPMI driver has certain
operations that occur at
I have an IPMI interface driver that sits on top of the I2C code. I'd
like to get it into the mainstream kernel, but I have a few problems
to solve first before I can do that. The I2C code is synchronous and
must run from a task context. The IPMI driver has certain
operations that occur at
Quoth Corey Minyard:
I would really like add asynchronous interface to the I2C bus drivers.
Applause! This is IMO overdue, but maybe sensor systems don't need it
as much as other I2C applications do. For example, see the isp1301_omap
driver, which could have been hugely simpler if there were
12 matches
Mail list logo
