Moikka!
On 08.02.2014 15:28, David Jedelsky wrote:
Manu, Antti,
Thank you for explanation. Now I see that I patched wrong place. More
appropriate would be to concentrate on az6027 I2C code.
Maybe my device could be working with corrected I2C code.
And yes, I have to confirm that the current
On Sat, Feb 8, 2014 at 1:19 AM, David Jedelsky david.jedel...@gmail.com wrote:
That changes I2C functionality from STOP + START to repeated START.
Current functionality looks also very weird, as there is 5 messages sent,
all with STOP condition. I am not surprised if actually bug is still in
On 07.02.2014 22:54, Manu Abraham wrote:
On Sat, Feb 8, 2014 at 1:19 AM, David Jedelsky david.jedel...@gmail.com wrote:
That changes I2C functionality from STOP + START to repeated START.
Current functionality looks also very weird, as there is 5 messages sent,
all with STOP condition. I am not
On Sat, Feb 8, 2014 at 2:41 AM, Antti Palosaari cr...@iki.fi wrote:
On 07.02.2014 22:54, Manu Abraham wrote:
On Sat, Feb 8, 2014 at 1:19 AM, David Jedelsky david.jedel...@gmail.com
wrote:
That changes I2C functionality from STOP + START to repeated START.
Current functionality looks also
Moi David
On 06.02.2014 11:45, David Jedelsky wrote:
My TechniSat SkyStar 2 HD CI USB ID 14f7:0002 wasn't tuning DVB-S2 channels.
Investigation revealed that it doesn't read DVB-S2 registers out of stb0899.
Comparison with usb trafic of the Windows driver showed the correct
communication
Hi David,
On Thu, Feb 6, 2014 at 3:15 PM, David Jedelsky david.jedel...@gmail.com wrote:
My TechniSat SkyStar 2 HD CI USB ID 14f7:0002 wasn't tuning DVB-S2 channels.
Investigation revealed that it doesn't read DVB-S2 registers out of stb0899.
Comparison with usb trafic of the Windows driver
