Wolfram Joost wrote:
Hi,
it works on boards with hardware i2c enabled. Changing the I2C_M_NOSTART
to 0, as you did, is the right thing to do here.
Ahh, OK.
Please fix the i2c host driver to handle RESTART conditions properly
instead of introducing dirty hacks in the device drivers, these will
[EMAIL PROTECTED] wrote:
Hello,
I'm currently stuck on making the mt352 driver work with my TechniSat
AirStar2 DVB-T card.
That card uses the mt352 chip with some Samsung tuner.
I came across this forum when I googled a bit:
http://pvrguide.no-ip.com/bbs-old/viewtopic.php?t=3413
This TechniSat
Hi,
it works on boards with hardware i2c enabled. Changing the I2C_M_NOSTART
to 0, as you did, is the right thing to do here.
Ahh, OK.
Attached is a patch against CVS that makes software I2C work, as well as
implementing the second policy.
I think that's a good way to handle the
Hi,
Attached is a patch against CVS that makes software I2C work, as well as
implementing the second policy.
I had a closer look to your patch:
+ unsigned char acqctl = 0x0B;/* suggest spectral inversion on, force mode,
guard */
I think it should be set to 0x5B. If the FE looses
Attached is a patch against CVS that makes software I2C work, as well as
implementing the second policy.
I had a closer look to your patch:
+ unsigned char acqctl = 0x0B;/* suggest spectral inversion on, force mode,
guard */
I think it should be set to 0x5B. If the FE looses the
[EMAIL PROTECTED] wrote:
Hello,
I'm currently stuck on making the mt352 driver work with my TechniSat
AirStar2 DVB-T card.
That card uses the mt352 chip with some Samsung tuner.
I came across this forum when I googled a bit:
http://pvrguide.no-ip.com/bbs-old/viewtopic.php?t=3413
This
Hi,
data with the tuner), but I simply don't know if those tuner-dependent
variables work with the Samsung tuner (don't think so after my
If it is the same tuner (network interface module) avermedia uses, then the
tuner-paramters should be correct.
My question now is: Did you get any
Hello,
On Monday 28 June 2004 18:54, [EMAIL PROTECTED] wrote:
Also, I found some oddities when looking at the mt352 driver.
The TechniSat AirStar2 uses a FlexCop IIB b2c2 chip that works with the
SkyStar2 module, but in the linuxtv cvs-tree the skystar2.c has the
following check in
Antonio Mancuso wrote:
Hello,
On Monday 28 June 2004 18:54, [EMAIL PROTECTED] wrote:
Also, I found some oddities when looking at the mt352 driver.
The TechniSat AirStar2 uses a FlexCop IIB b2c2 chip that works with the
SkyStar2 module, but in the linuxtv cvs-tree the skystar2.c has the
Bjorn writes:
In mt352.c the read command is contains the following:
struct i2c_msg msg [] = { { .addr = I2C_MT352_ADDR,
.flags = I2C_M_NOSTART,
.buf = b0, .len = 1 },
{ .addr =
10 matches
Mail list logo
