Hello ksi,
k...@koi8.net wrote:
On Wed, 28 Jan 2009, Heiko Schocher wrote:
Hello ksi,
k...@koi8.net schrieb:
On Tue, 27 Jan 2009, Heiko Schocher wrote:
k...@koi8.net wrote:
[...]
OK,. But if I look in your patch you delete the i2c bus command, and
this breaks at least 2 boards.
Yep. As
Hello ksi,
k...@koi8.net schrieb:
On Tue, 27 Jan 2009, Heiko Schocher wrote:
k...@koi8.net wrote:
Hi everyone,
Here is the first draft of major I2C subsystem rework. This is not a
patch
[...]
the new code. It is a big job and I don't want to spend a lot of time
doing
something that
On Wed, 28 Jan 2009, Heiko Schocher wrote:
Hello ksi,
k...@koi8.net schrieb:
On Tue, 27 Jan 2009, Heiko Schocher wrote:
k...@koi8.net wrote:
Hi everyone,
Here is the first draft of major I2C subsystem rework. This is not a
patch
[...]
the new code. It is a big job and I don't want to
Hello ksi,
k...@koi8.net wrote:
Hi everyone,
Here is the first draft of major I2C subsystem rework. This is not a patch
that should be applied to the tree--it will break systems with I2C busses
over multiplexers and probably something else--but rather a Request For
Comments. I would like to
On Tue, 27 Jan 2009, Heiko Schocher wrote:
Hello ksi,
k...@koi8.net wrote:
Hi everyone,
Here is the first draft of major I2C subsystem rework. This is not a
patch
that should be applied to the tree--it will break systems with I2C
busses
over multiplexers and probably something else--but
Hi everyone,
Here is the first draft of major I2C subsystem rework. This is not a patch
that should be applied to the tree--it will break systems with I2C busses
over multiplexers and probably something else--but rather a Request For
Comments. I would like to here all the objections, suggestions
6 matches
Mail list logo
