Re: pctv452e oops

[Wolfgang Rohdewald]

On Mi, 2017-11-08 at 14:28 +0100, Wolfgang Rohdewald wrote:
> since kernel 4.9 I cannot use my four dvb-s2 USB receivers anymore, so
> I am stuck with 4.8.x
> 
> Now I tried again with an unmodified kernel 4.13.12. After some time, 
> I get 3 oopses (remember - I have 4 devices). The call trace is always
> the same.
> 
> 
> attached:
> 
> tasks.txt showing the timing of the oopses
> oops.txt with one of them

after this happens, lsmod shows a negative reference count:

Module  Size  Used by
stb089940960  -1

-- 
mit freundlichen Grüssen

Wolfgang Rohdewald

Re: pctv452e oops without HTML

[Wolfgang Rohdewald]

: 55f18baaf790
Nov  8 13:05:51 s5 kernel: [   81.588658] Code: 48 8b 03 48 8b 7b 08 48 83 c3 
18 4c 89 ea 4c 89 e6 ff d0 48 8b 03 48 85 c0 75 e8 65 ff 0d 81 84 f1 7e 75 9a 
e8 45 e0 f0 ff eb 93 <0f> ff eb 86 e8 22 e0 f0 ff 5b 41 5c 41 5d 5d c3 89 c2 e9 
54 ff 
Nov  8 13:05:51 s5 kernel: [   81.588677] ---[ end trace 63e8b9125c36dd89 ]---
Nov  8 13:05:51 s5 kernel: [   81.588928] dvb-usb: Technotrend TT Connect 
S2-3600 successfully deinitialized and disconnected.
Nov  8 13:05:51 s5 kernel: [   81.636514] dvb-usb: bulk message failed: -2 
(11/0)
Nov  8 13:05:51 s5 kernel: [   81.636518] pctv452e: I2C error -2; AA 44  10 04 
00 -> aa 44 31 07 10 04 00
Nov  8 13:05:51 s5 kernel: [   81.636522] dvb-usb: bulk message failed: -2 
(10/0)
Nov  8 13:05:51 s5 kernel: [   81.636524] pctv452e: I2C error -2; AA 45  D0 03 
00 -> aa 45 31 06 d0 03 00
Nov  7 20:06:00 s5 kernel: [115383.674654] task: 88021492bc00 task.stack: 
c9000db94000
Nov  7 20:06:01 s5 kernel: [115383.726668] task: 88021492bc00 task.stack: 
c9000db94000
Nov  7 20:06:01 s5 kernel: [115383.726774] task: 88021492bc00 task.stack: 
c9000db94000
Nov  7 20:15:48 s5 kernel: [   81.785461] task: 8801b93a8000 task.stack: 
c90003fd8000
Nov  7 20:15:48 s5 kernel: [   81.829401] task: 8801b93a8000 task.stack: 
c90003fd8000
Nov  7 20:15:48 s5 kernel: [   81.829494] task: 8801b93a8000 task.stack: 
c90003fd8000
Nov  7 23:41:01 s5 kernel: [ 6428.520760] task: 880202455a00 task.stack: 
c9000cc54000
Nov  7 23:41:01 s5 kernel: [ 6428.576760] task: 880202455a00 task.stack: 
c9000cc54000
Nov  7 23:41:01 s5 kernel: [ 6428.576904] task: 880202455a00 task.stack: 
c9000cc54000
Nov  8 13:05:51 s5 kernel: [   81.588604] task: 8801eb6bbc00 task.stack: 
c90008494000
Nov  8 13:05:51 s5 kernel: [   81.636567] task: 8801eb6bbc00 task.stack: 
c90008494000
Nov  8 13:05:51 s5 kernel: [   81.636667] task: 8801eb6bbc00 task.stack: 
c90008494000

[PATCH] [media] pctv452e: move buffer to heap, no mutex

[Max Kellermann]

Revert part of commit 73d5c5c864f4094, but move the buffer to the heap
(DMA capable), not to the stack (may not be DMA capable).  Instead of
sharing one buffer which needs mutex protection, do a new heap
allocation for each call.

This fixes a NULL pointer dereference which occurs when dvb_usb_init()
calls dvb_usb_device_power_ctrl() for the first time, before the
frontend has been attached; and it fixes a recursive deadlock because
tt3650_ci_msg_locked() has already locked the mutex.

Both regressions were caused by said commit 73d5c5c864f4094, which rendered
the pctv452e driver completely unusable (crashes instantly when
plugging in the device).

Signed-off-by: Max Kellermann <max.kellerm...@gmail.com>
---
 drivers/media/usb/dvb-usb/pctv452e.c |  133 ++
 1 file changed, 72 insertions(+), 61 deletions(-)

diff --git a/drivers/media/usb/dvb-usb/pctv452e.c 
b/drivers/media/usb/dvb-usb/pctv452e.c
index 07fa08b..d54ebe7 100644
--- a/drivers/media/usb/dvb-usb/pctv452e.c
+++ b/drivers/media/usb/dvb-usb/pctv452e.c
@@ -97,14 +97,13 @@ struct pctv452e_state {
u8 c;  /* transaction counter, wraps around...  */
u8 initialized; /* set to 1 if 0x15 has been sent */
u16 last_rc_key;
-
-   unsigned char data[80];
 };
 
 static int tt3650_ci_msg(struct dvb_usb_device *d, u8 cmd, u8 *data,
 unsigned int write_len, unsigned int read_len)
 {
struct pctv452e_state *state = (struct pctv452e_state *)d->priv;
+   u8 *buf;
u8 id;
unsigned int rlen;
int ret;
@@ -114,36 +113,39 @@ static int tt3650_ci_msg(struct dvb_usb_device *d, u8 
cmd, u8 *data,
return -EIO;
}
 
-   mutex_lock(>ca_mutex);
+   buf = kmalloc(64, GFP_KERNEL);
+   if (!buf)
+   return -ENOMEM;
+
id = state->c++;
 
-   state->data[0] = SYNC_BYTE_OUT;
-   state->data[1] = id;
-   state->data[2] = cmd;
-   state->data[3] = write_len;
+   buf[0] = SYNC_BYTE_OUT;
+   buf[1] = id;
+   buf[2] = cmd;
+   buf[3] = write_len;
 
-   memcpy(state->data + 4, data, write_len);
+   memcpy(buf + 4, data, write_len);
 
rlen = (read_len > 0) ? 64 : 0;
-   ret = dvb_usb_generic_rw(d, state->data, 4 + write_len,
- state->data, rlen, /* delay_ms */ 0);
+   ret = dvb_usb_generic_rw(d, buf, 4 + write_len,
+ buf, rlen, /* delay_ms */ 0);
if (0 != ret)
goto failed;
 
ret = -EIO;
-   if (SYNC_BYTE_IN != state->data[0] || id != state->data[1])
+   if (SYNC_BYTE_IN != buf[0] || id != buf[1])
goto failed;
 
-   memcpy(data, state->data + 4, read_len);
+   memcpy(data, buf + 4, read_len);
 
-   mutex_unlock(>ca_mutex);
+   kfree(buf);
return 0;
 
 failed:
err("CI error %d; %02X %02X %02X -> %*ph.",
-ret, SYNC_BYTE_OUT, id, cmd, 3, state->data);
+ret, SYNC_BYTE_OUT, id, cmd, 3, buf);
 
-   mutex_unlock(>ca_mutex);
+   kfree(buf);
return ret;
 }
 
@@ -410,53 +412,57 @@ static int pctv452e_i2c_msg(struct dvb_usb_device *d, u8 
addr,
u8 *rcv_buf, u8 rcv_len)
 {
struct pctv452e_state *state = (struct pctv452e_state *)d->priv;
+   u8 *buf;
u8 id;
int ret;
 
-   mutex_lock(>ca_mutex);
+   buf = kmalloc(64, GFP_KERNEL);
+   if (!buf)
+   return -ENOMEM;
+
id = state->c++;
 
ret = -EINVAL;
if (snd_len > 64 - 7 || rcv_len > 64 - 7)
goto failed;
 
-   state->data[0] = SYNC_BYTE_OUT;
-   state->data[1] = id;
-   state->data[2] = PCTV_CMD_I2C;
-   state->data[3] = snd_len + 3;
-   state->data[4] = addr << 1;
-   state->data[5] = snd_len;
-   state->data[6] = rcv_len;
+   buf[0] = SYNC_BYTE_OUT;
+   buf[1] = id;
+   buf[2] = PCTV_CMD_I2C;
+   buf[3] = snd_len + 3;
+   buf[4] = addr << 1;
+   buf[5] = snd_len;
+   buf[6] = rcv_len;
 
-   memcpy(state->data + 7, snd_buf, snd_len);
+   memcpy(buf + 7, snd_buf, snd_len);
 
-   ret = dvb_usb_generic_rw(d, state->data, 7 + snd_len,
- state->data, /* rcv_len */ 64,
+   ret = dvb_usb_generic_rw(d, buf, 7 + snd_len,
+ buf, /* rcv_len */ 64,
  /* delay_ms */ 0);
if (ret < 0)
goto failed;
 
/* TT USB protocol error. */
ret = -EIO;
-   if (SYNC_BYTE_IN != state->data[0] || id != state->data[1])
+   if (SYNC_BYTE_IN != buf[0] || id != buf[1])
goto failed;
 
/* I2C device didn't respond as expected. */
ret = -EREMOTEIO;
-   if (state->dat

[PATCH] [media] pctv452e: fix double lock bug

[Iago Abal]

From: Iago Abal <m...@iagoabal.eu>

Commit 73d5c5c864f4 protected the body of `tt3650_ci_msg' with state->ca_mutex.
This is not needed: 1) this function is always called from a context where that
lock is held; and 2) there exists a `tt3650_ci_msg_locked' wrapper that does
exactly the same.

This leads to double lock as reported by the EBA (http://www.iagoabal.eu/eba)
static bug finder:

a) Function `tt3650_ci_msg_locked' takes state->ca_mutex in line 156 and
   then calls `tt3650_ci_msg' in line 157.

b) Function `tt3650_ci_slot_reset' takes state->ca_mutex in line 297 and
   then calls `tt3650_ci_msg' in line 299.

Fixes: 73d5c5c864f4 ("[media] pctv452e: don't do DMA on stack")
Signed-off-by: Iago Abal <m...@iagoabal.eu>
---
 drivers/media/usb/dvb-usb/pctv452e.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/drivers/media/usb/dvb-usb/pctv452e.c 
b/drivers/media/usb/dvb-usb/pctv452e.c
index 07fa08b..c718fd9 100644
--- a/drivers/media/usb/dvb-usb/pctv452e.c
+++ b/drivers/media/usb/dvb-usb/pctv452e.c
@@ -114,7 +114,6 @@ static int tt3650_ci_msg(struct dvb_usb_device *d, u8 cmd, 
u8 *data,
return -EIO;
}
 
-   mutex_lock(>ca_mutex);
id = state->c++;
 
state->data[0] = SYNC_BYTE_OUT;
@@ -136,7 +135,6 @@ static int tt3650_ci_msg(struct dvb_usb_device *d, u8 cmd, 
u8 *data,
 
memcpy(data, state->data + 4, read_len);
 
-   mutex_unlock(>ca_mutex);
return 0;
 
 failed:
-- 
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH] pctv452e: fix semicolon.cocci warnings

[kbuild test robot]

drivers/media/usb/dvb-usb/pctv452e.c:115:2-3: Unneeded semicolon


 Remove unneeded semicolon.

Generated by: scripts/coccinelle/misc/semicolon.cocci

CC: Mauro Carvalho Chehab 
Signed-off-by: Fengguang Wu 
---

 pctv452e.c |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/drivers/media/usb/dvb-usb/pctv452e.c
+++ b/drivers/media/usb/dvb-usb/pctv452e.c
@@ -112,7 +112,7 @@ static int tt3650_ci_msg(struct dvb_usb_
if (!data || (write_len > 64 - 4) || (read_len > 64 - 4)) {
err("%s: transfer data invalid", __func__);
return -EIO;
-   };
+   }
 
mutex_lock(>ca_mutex);
id = state->c++;
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH v2 22/31] pctv452e: don't call BUG_ON() on non-fatal error

[Mauro Carvalho Chehab]

There are some conditions on this driver that are tested with
BUG_ON() with are not serious enough to hang a machine.

So, just return an error if this happens.

Signed-off-by: Mauro Carvalho Chehab 
---
 drivers/media/usb/dvb-usb/pctv452e.c | 7 ---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/drivers/media/usb/dvb-usb/pctv452e.c 
b/drivers/media/usb/dvb-usb/pctv452e.c
index 58b685094904..7ad0006c5ae0 100644
--- a/drivers/media/usb/dvb-usb/pctv452e.c
+++ b/drivers/media/usb/dvb-usb/pctv452e.c
@@ -109,9 +109,10 @@ static int tt3650_ci_msg(struct dvb_usb_device *d, u8 cmd, 
u8 *data,
unsigned int rlen;
int ret;
 
-   BUG_ON(NULL == data && 0 != (write_len | read_len));
-   BUG_ON(write_len > 64 - 4);
-   BUG_ON(read_len > 64 - 4);
+   if (!data || (write_len > 64 - 4) || (read_len > 64 - 4)) {
+   err("%s: transfer data invalid", __func__);
+   return -EIO;
+   };
 
mutex_lock(>ca_mutex);
id = state->c++;
-- 
2.7.4


--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH v2 21/31] pctv452e: don't do DMA on stack

[Mauro Carvalho Chehab]

The USB control messages require DMA to work. We cannot pass
a stack-allocated buffer, as it is not warranted that the
stack would be into a DMA enabled area.

Reviewed-By: Patrick Boettcher 
Signed-off-by: Mauro Carvalho Chehab 
---
 drivers/media/usb/dvb-usb/pctv452e.c | 129 ---
 1 file changed, 74 insertions(+), 55 deletions(-)

diff --git a/drivers/media/usb/dvb-usb/pctv452e.c 
b/drivers/media/usb/dvb-usb/pctv452e.c
index c05de1b088a4..58b685094904 100644
--- a/drivers/media/usb/dvb-usb/pctv452e.c
+++ b/drivers/media/usb/dvb-usb/pctv452e.c
@@ -97,13 +97,14 @@ struct pctv452e_state {
u8 c;  /* transaction counter, wraps around...  */
u8 initialized; /* set to 1 if 0x15 has been sent */
u16 last_rc_key;
+
+   unsigned char data[80];
 };
 
 static int tt3650_ci_msg(struct dvb_usb_device *d, u8 cmd, u8 *data,
 unsigned int write_len, unsigned int read_len)
 {
struct pctv452e_state *state = (struct pctv452e_state *)d->priv;
-   u8 buf[64];
u8 id;
unsigned int rlen;
int ret;
@@ -112,33 +113,36 @@ static int tt3650_ci_msg(struct dvb_usb_device *d, u8 
cmd, u8 *data,
BUG_ON(write_len > 64 - 4);
BUG_ON(read_len > 64 - 4);
 
+   mutex_lock(>ca_mutex);
id = state->c++;
 
-   buf[0] = SYNC_BYTE_OUT;
-   buf[1] = id;
-   buf[2] = cmd;
-   buf[3] = write_len;
+   state->data[0] = SYNC_BYTE_OUT;
+   state->data[1] = id;
+   state->data[2] = cmd;
+   state->data[3] = write_len;
 
-   memcpy(buf + 4, data, write_len);
+   memcpy(state->data + 4, data, write_len);
 
rlen = (read_len > 0) ? 64 : 0;
-   ret = dvb_usb_generic_rw(d, buf, 4 + write_len,
- buf, rlen, /* delay_ms */ 0);
+   ret = dvb_usb_generic_rw(d, state->data, 4 + write_len,
+ state->data, rlen, /* delay_ms */ 0);
if (0 != ret)
goto failed;
 
ret = -EIO;
-   if (SYNC_BYTE_IN != buf[0] || id != buf[1])
+   if (SYNC_BYTE_IN != state->data[0] || id != state->data[1])
goto failed;
 
-   memcpy(data, buf + 4, read_len);
+   memcpy(data, state->data + 4, read_len);
 
+   mutex_unlock(>ca_mutex);
return 0;
 
 failed:
err("CI error %d; %02X %02X %02X -> %*ph.",
-ret, SYNC_BYTE_OUT, id, cmd, 3, buf);
+ret, SYNC_BYTE_OUT, id, cmd, 3, state->data);
 
+   mutex_unlock(>ca_mutex);
return ret;
 }
 
@@ -405,52 +409,53 @@ static int pctv452e_i2c_msg(struct dvb_usb_device *d, u8 
addr,
u8 *rcv_buf, u8 rcv_len)
 {
struct pctv452e_state *state = (struct pctv452e_state *)d->priv;
-   u8 buf[64];
u8 id;
int ret;
 
+   mutex_lock(>ca_mutex);
id = state->c++;
 
ret = -EINVAL;
if (snd_len > 64 - 7 || rcv_len > 64 - 7)
goto failed;
 
-   buf[0] = SYNC_BYTE_OUT;
-   buf[1] = id;
-   buf[2] = PCTV_CMD_I2C;
-   buf[3] = snd_len + 3;
-   buf[4] = addr << 1;
-   buf[5] = snd_len;
-   buf[6] = rcv_len;
+   state->data[0] = SYNC_BYTE_OUT;
+   state->data[1] = id;
+   state->data[2] = PCTV_CMD_I2C;
+   state->data[3] = snd_len + 3;
+   state->data[4] = addr << 1;
+   state->data[5] = snd_len;
+   state->data[6] = rcv_len;
 
-   memcpy(buf + 7, snd_buf, snd_len);
+   memcpy(state->data + 7, snd_buf, snd_len);
 
-   ret = dvb_usb_generic_rw(d, buf, 7 + snd_len,
- buf, /* rcv_len */ 64,
+   ret = dvb_usb_generic_rw(d, state->data, 7 + snd_len,
+ state->data, /* rcv_len */ 64,
  /* delay_ms */ 0);
if (ret < 0)
goto failed;
 
/* TT USB protocol error. */
ret = -EIO;
-   if (SYNC_BYTE_IN != buf[0] || id != buf[1])
+   if (SYNC_BYTE_IN != state->data[0] || id != state->data[1])
goto failed;
 
/* I2C device didn't respond as expected. */
ret = -EREMOTEIO;
-   if (buf[5] < snd_len || buf[6] < rcv_len)
+   if (state->data[5] < snd_len || state->data[6] < rcv_len)
goto failed;
 
-   memcpy(rcv_buf, buf + 7, rcv_len);
+   memcpy(rcv_buf, state->data + 7, rcv_len);
+   mutex_unlock(>ca_mutex);
 
return rcv_len;
 
 failed:
-   err("I2C error %d; %02X %02X  %02X %02X %02X -> "
-"%02X %02X  %02X %02X %02X.",
+   err("I2C error %d; %02X %02X  %02X %02X %02X -> %*ph",
 ret, SYNC_BYTE_OUT, id, addr << 1, snd_len, rcv_len,
-buf[0], buf[1], buf[4], buf[5], buf[6]);
+7, state->data);
 
+   mutex_unlock(>ca_mutex);
return ret;
 }
 
@@ -499,8 +504,7 @@ static u32 pctv452e_i2c_func(struct i2c_adapter *adapter)
 static 

Re: [PATCH 20/26] pctv452e: don't do DMA on stack

[Patrick Boettcher]

On Fri,  7 Oct 2016 14:24:30 -0300
Mauro Carvalho Chehab  wrote:

> The USB control messages require DMA to work. We cannot pass
> a stack-allocated buffer, as it is not warranted that the
> stack would be into a DMA enabled area.
> 
> Signed-off-by: Mauro Carvalho Chehab 
> ---
>  drivers/media/usb/dvb-usb/pctv452e.c | 110
> ++- 1 file changed, 58 insertions(+),
> 52 deletions(-)
> 
> diff --git a/drivers/media/usb/dvb-usb/pctv452e.c
> b/drivers/media/usb/dvb-usb/pctv452e.c index
> c05de1b088a4..855fe9d34b59 100644 ---
> a/drivers/media/usb/dvb-usb/pctv452e.c +++
> b/drivers/media/usb/dvb-usb/pctv452e.c @@ -97,13 +97,14 @@ struct
> pctv452e_state { u8 c;   /* transaction counter, wraps
> around...  */ u8 initialized; /* set to 1 if 0x15 has been sent */
>   u16 last_rc_key;
> +
> + unsigned char data[80];
>  };
>  
>  static int tt3650_ci_msg(struct dvb_usb_device *d, u8 cmd, u8 *data,
>unsigned int write_len, unsigned int
> read_len) {
>   struct pctv452e_state *state = (struct pctv452e_state
> *)d->priv;
> - u8 buf[64];
>   u8 id;
>   unsigned int rlen;
>   int ret;
> @@ -114,30 +115,30 @@ static int tt3650_ci_msg(struct dvb_usb_device
> *d, u8 cmd, u8 *data, 
>   id = state->c++;
>  
> - buf[0] = SYNC_BYTE_OUT;
> - buf[1] = id;
> - buf[2] = cmd;
> - buf[3] = write_len;
> + state->data[0] = SYNC_BYTE_OUT;
> + state->data[1] = id;
> + state->data[2] = cmd;
> + state->data[3] = write_len;
>  
> - memcpy(buf + 4, data, write_len);
> + memcpy(state->data + 4, data, write_len);
>  
>   rlen = (read_len > 0) ? 64 : 0;
> - ret = dvb_usb_generic_rw(d, buf, 4 + write_len,
> -   buf, rlen, /* delay_ms */ 0);
> + ret = dvb_usb_generic_rw(d, state->data, 4 + write_len,
> +   state->data, rlen, /* delay_ms */
> 0); if (0 != ret)
>   goto failed;
>  
>   ret = -EIO;
> - if (SYNC_BYTE_IN != buf[0] || id != buf[1])
> + if (SYNC_BYTE_IN != state->data[0] || id != state->data[1])
>   goto failed;
>  
> - memcpy(data, buf + 4, read_len);
> + memcpy(data, state->data + 4, read_len);
>  
>   return 0;
>  
>  failed:
>   err("CI error %d; %02X %02X %02X -> %*ph.",
> -  ret, SYNC_BYTE_OUT, id, cmd, 3, buf);
> +  ret, SYNC_BYTE_OUT, id, cmd, 3, state->data);
>  
>   return ret;
>  }
> @@ -405,7 +406,6 @@ static int pctv452e_i2c_msg(struct dvb_usb_device
> *d, u8 addr, u8 *rcv_buf, u8 rcv_len)
>  {
>   struct pctv452e_state *state = (struct pctv452e_state
> *)d->priv;
> - u8 buf[64];
>   u8 id;
>   int ret;
>  
> @@ -415,42 +415,40 @@ static int pctv452e_i2c_msg(struct
> dvb_usb_device *d, u8 addr, if (snd_len > 64 - 7 || rcv_len > 64 - 7)
>   goto failed;
>  
> - buf[0] = SYNC_BYTE_OUT;
> - buf[1] = id;
> - buf[2] = PCTV_CMD_I2C;
> - buf[3] = snd_len + 3;
> - buf[4] = addr << 1;
> - buf[5] = snd_len;
> - buf[6] = rcv_len;
> + state->data[0] = SYNC_BYTE_OUT;
> + state->data[1] = id;
> + state->data[2] = PCTV_CMD_I2C;
> + state->data[3] = snd_len + 3;
> + state->data[4] = addr << 1;
> + state->data[5] = snd_len;
> + state->data[6] = rcv_len;
>  
> - memcpy(buf + 7, snd_buf, snd_len);
> + memcpy(state->data + 7, snd_buf, snd_len);
>  
> - ret = dvb_usb_generic_rw(d, buf, 7 + snd_len,
> -   buf, /* rcv_len */ 64,
> + ret = dvb_usb_generic_rw(d, state->data, 7 + snd_len,
> +   state->data, /* rcv_len */ 64,
> /* delay_ms */ 0);
>   if (ret < 0)
>   goto failed;
>  
>   /* TT USB protocol error. */
>   ret = -EIO;
> - if (SYNC_BYTE_IN != buf[0] || id != buf[1])
> + if (SYNC_BYTE_IN != state->data[0] || id != state->data[1])
>   goto failed;
>  
>   /* I2C device didn't respond as expected. */
>   ret = -EREMOTEIO;
> - if (buf[5] < snd_len || buf[6] < rcv_len)
> + if (state->data[5] < snd_len || state->data[6] < rcv_len)
>   goto failed;
>  
> - memcpy(rcv_buf, buf + 7, rcv_len);
> + memcpy(rcv_buf, state->data + 7, rcv_len);
>  
>   return rcv_len;
>  
>  failed:
> - err("I2C error %d; %02X %02X  %02X %02X %02X -> "
> -  "%02X %02X  %02X %02X %02X.",
> + err("I2C error %d; %02X %02X  %02X %02X %02X -> %*ph",
>ret, SYNC_BYTE_OUT, id, addr << 1, snd_len, rcv_len,
> -  buf[0], buf[1], buf[4], buf[5], buf[6]);
> -
> +  7, state->data);
>   return ret;
>  }
>  
> @@ -499,8 +497,7 @@ static u32 pctv452e_i2c_func(struct i2c_adapter
> *adapter) static int pctv452e_power_ctrl(struct dvb_usb_device *d,
> int i) {
>   struct pctv452e_state *state = (struct pctv452e_state
> *)d->priv;
> - u8 b0[] = { 

[PATCH v2 21/26] pctv452e: don't call BUG_ON() on non-fatal error

[Mauro Carvalho Chehab]

There are some conditions on this driver that are tested with
BUG_ON() with are not serious enough to hang a machine.

So, just return an error if this happens.

Signed-off-by: Mauro Carvalho Chehab 
---

v2: simplify the logic and use its own error message.


 drivers/media/usb/dvb-usb/pctv452e.c | 7 ---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/drivers/media/usb/dvb-usb/pctv452e.c 
b/drivers/media/usb/dvb-usb/pctv452e.c
index 855fe9d34b59..f70202e6e3eb 100644
--- a/drivers/media/usb/dvb-usb/pctv452e.c
+++ b/drivers/media/usb/dvb-usb/pctv452e.c
@@ -109,9 +109,10 @@ static int tt3650_ci_msg(struct dvb_usb_device *d, u8 cmd, 
u8 *data,
unsigned int rlen;
int ret;
 
-   BUG_ON(NULL == data && 0 != (write_len | read_len));
-   BUG_ON(write_len > 64 - 4);
-   BUG_ON(read_len > 64 - 4);
+   if (!data || (write_len > 64 - 4) || (read_len > 64 - 4)) {
+   err("%s: transfer data invalid", __func__);
+   return -EIO;
+   };
 
id = state->c++;
 
-- 
2.7.4


--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH 21/26] pctv452e: don't call BUG_ON() on non-fatal error

[Mauro Carvalho Chehab]

There are some conditions on this driver that are tested with
BUG_ON() with are not serious enough to hang a machine.

So, just return an error if this happens.

Signed-off-by: Mauro Carvalho Chehab 
---
 drivers/media/usb/dvb-usb/pctv452e.c | 8 +---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/drivers/media/usb/dvb-usb/pctv452e.c 
b/drivers/media/usb/dvb-usb/pctv452e.c
index 855fe9d34b59..14bd927c50d8 100644
--- a/drivers/media/usb/dvb-usb/pctv452e.c
+++ b/drivers/media/usb/dvb-usb/pctv452e.c
@@ -109,9 +109,11 @@ static int tt3650_ci_msg(struct dvb_usb_device *d, u8 cmd, 
u8 *data,
unsigned int rlen;
int ret;
 
-   BUG_ON(NULL == data && 0 != (write_len | read_len));
-   BUG_ON(write_len > 64 - 4);
-   BUG_ON(read_len > 64 - 4);
+   if (NULL == data && 0 != (write_len | read_len) ||
+   write_len > 64 - 4) || (read_len > 64 - 4)) {
+   ret = -EIO;
+   goto failed;
+   };
 
id = state->c++;
 
-- 
2.7.4


--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH 20/26] pctv452e: don't do DMA on stack

[Mauro Carvalho Chehab]

The USB control messages require DMA to work. We cannot pass
a stack-allocated buffer, as it is not warranted that the
stack would be into a DMA enabled area.

Signed-off-by: Mauro Carvalho Chehab 
---
 drivers/media/usb/dvb-usb/pctv452e.c | 110 ++-
 1 file changed, 58 insertions(+), 52 deletions(-)

diff --git a/drivers/media/usb/dvb-usb/pctv452e.c 
b/drivers/media/usb/dvb-usb/pctv452e.c
index c05de1b088a4..855fe9d34b59 100644
--- a/drivers/media/usb/dvb-usb/pctv452e.c
+++ b/drivers/media/usb/dvb-usb/pctv452e.c
@@ -97,13 +97,14 @@ struct pctv452e_state {
u8 c;  /* transaction counter, wraps around...  */
u8 initialized; /* set to 1 if 0x15 has been sent */
u16 last_rc_key;
+
+   unsigned char data[80];
 };
 
 static int tt3650_ci_msg(struct dvb_usb_device *d, u8 cmd, u8 *data,
 unsigned int write_len, unsigned int read_len)
 {
struct pctv452e_state *state = (struct pctv452e_state *)d->priv;
-   u8 buf[64];
u8 id;
unsigned int rlen;
int ret;
@@ -114,30 +115,30 @@ static int tt3650_ci_msg(struct dvb_usb_device *d, u8 
cmd, u8 *data,
 
id = state->c++;
 
-   buf[0] = SYNC_BYTE_OUT;
-   buf[1] = id;
-   buf[2] = cmd;
-   buf[3] = write_len;
+   state->data[0] = SYNC_BYTE_OUT;
+   state->data[1] = id;
+   state->data[2] = cmd;
+   state->data[3] = write_len;
 
-   memcpy(buf + 4, data, write_len);
+   memcpy(state->data + 4, data, write_len);
 
rlen = (read_len > 0) ? 64 : 0;
-   ret = dvb_usb_generic_rw(d, buf, 4 + write_len,
- buf, rlen, /* delay_ms */ 0);
+   ret = dvb_usb_generic_rw(d, state->data, 4 + write_len,
+ state->data, rlen, /* delay_ms */ 0);
if (0 != ret)
goto failed;
 
ret = -EIO;
-   if (SYNC_BYTE_IN != buf[0] || id != buf[1])
+   if (SYNC_BYTE_IN != state->data[0] || id != state->data[1])
goto failed;
 
-   memcpy(data, buf + 4, read_len);
+   memcpy(data, state->data + 4, read_len);
 
return 0;
 
 failed:
err("CI error %d; %02X %02X %02X -> %*ph.",
-ret, SYNC_BYTE_OUT, id, cmd, 3, buf);
+ret, SYNC_BYTE_OUT, id, cmd, 3, state->data);
 
return ret;
 }
@@ -405,7 +406,6 @@ static int pctv452e_i2c_msg(struct dvb_usb_device *d, u8 
addr,
u8 *rcv_buf, u8 rcv_len)
 {
struct pctv452e_state *state = (struct pctv452e_state *)d->priv;
-   u8 buf[64];
u8 id;
int ret;
 
@@ -415,42 +415,40 @@ static int pctv452e_i2c_msg(struct dvb_usb_device *d, u8 
addr,
if (snd_len > 64 - 7 || rcv_len > 64 - 7)
goto failed;
 
-   buf[0] = SYNC_BYTE_OUT;
-   buf[1] = id;
-   buf[2] = PCTV_CMD_I2C;
-   buf[3] = snd_len + 3;
-   buf[4] = addr << 1;
-   buf[5] = snd_len;
-   buf[6] = rcv_len;
+   state->data[0] = SYNC_BYTE_OUT;
+   state->data[1] = id;
+   state->data[2] = PCTV_CMD_I2C;
+   state->data[3] = snd_len + 3;
+   state->data[4] = addr << 1;
+   state->data[5] = snd_len;
+   state->data[6] = rcv_len;
 
-   memcpy(buf + 7, snd_buf, snd_len);
+   memcpy(state->data + 7, snd_buf, snd_len);
 
-   ret = dvb_usb_generic_rw(d, buf, 7 + snd_len,
- buf, /* rcv_len */ 64,
+   ret = dvb_usb_generic_rw(d, state->data, 7 + snd_len,
+ state->data, /* rcv_len */ 64,
  /* delay_ms */ 0);
if (ret < 0)
goto failed;
 
/* TT USB protocol error. */
ret = -EIO;
-   if (SYNC_BYTE_IN != buf[0] || id != buf[1])
+   if (SYNC_BYTE_IN != state->data[0] || id != state->data[1])
goto failed;
 
/* I2C device didn't respond as expected. */
ret = -EREMOTEIO;
-   if (buf[5] < snd_len || buf[6] < rcv_len)
+   if (state->data[5] < snd_len || state->data[6] < rcv_len)
goto failed;
 
-   memcpy(rcv_buf, buf + 7, rcv_len);
+   memcpy(rcv_buf, state->data + 7, rcv_len);
 
return rcv_len;
 
 failed:
-   err("I2C error %d; %02X %02X  %02X %02X %02X -> "
-"%02X %02X  %02X %02X %02X.",
+   err("I2C error %d; %02X %02X  %02X %02X %02X -> %*ph",
 ret, SYNC_BYTE_OUT, id, addr << 1, snd_len, rcv_len,
-buf[0], buf[1], buf[4], buf[5], buf[6]);
-
+7, state->data);
return ret;
 }
 
@@ -499,8 +497,7 @@ static u32 pctv452e_i2c_func(struct i2c_adapter *adapter)
 static int pctv452e_power_ctrl(struct dvb_usb_device *d, int i)
 {
struct pctv452e_state *state = (struct pctv452e_state *)d->priv;
-   u8 b0[] = { 0xaa, 0, PCTV_CMD_RESET, 1, 0 };
-   u8 rx[PCTV_ANSWER_LEN];
+   u8 *rx;
int ret;
 
info("%s: %d\n", __func__, i);
@@ 

[PATCH] pctv452e: correct parameters for TechnoTrend TT S2-3600

[Olli Salonen]

2008-02-25 Andre Weidemann added support for TT S2-3600 and noted
that he still gets image distortions every now and then.

It seems to be common knowledge in many projects that changing
the USB parameters seems to help. OpenELEC has included this patch
for a few years, for example. Nobody bothered to report the issue
upstream though, it seems.

References:
https://github.com/OpenELEC/OpenELEC.tv/issues/1957
http://www.vdr-portal.de/board60-linux/board14-betriebssystem/board96-yavdr/p1033458-darstellungsproblem-bei-2-tt-3600-usb/#post1033458
 (in German)

I'd suggest we include the patch below. Any objections?

Signed-off-by: Olli Salonen 
---
 drivers/media/usb/dvb-usb/pctv452e.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/media/usb/dvb-usb/pctv452e.c 
b/drivers/media/usb/dvb-usb/pctv452e.c
index ec397c4..c05de1b 100644
--- a/drivers/media/usb/dvb-usb/pctv452e.c
+++ b/drivers/media/usb/dvb-usb/pctv452e.c
@@ -995,11 +995,11 @@ static struct dvb_usb_device_properties 
tt_connect_s2_3600_properties = {
/* parameter for the MPEG2-data transfer */
.stream = {
.type = USB_ISOC,
-   .count = 7,
+   .count = 4,
.endpoint = 0x02,
.u = {
.isoc = {
-   .framesperurb = 4,
+   .framesperurb = 64,
.framesize = 940,
.interval = 1
}
-- 
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH] [media] pctv452e: Replace memset with eth_zero_addr

[Vaishali Thakkar]

Use eth_zero_addr to assign the zero address to the given address
array instead of memset when second argument is address of zero.
Note that the 6 in the third argument of memset appears to represent
an ethernet address size (ETH_ALEN).

The Coccinelle semantic patch that makes this change is as follows:

// smpl
@eth_zero_addr@
expression e;
@@

-memset(e,0x00,6);
+eth_zero_addr(e);
// /smpl

Signed-off-by: Vaishali Thakkar vthakkar1...@gmail.com
---
 drivers/media/usb/dvb-usb/pctv452e.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/media/usb/dvb-usb/pctv452e.c 
b/drivers/media/usb/dvb-usb/pctv452e.c
index d17618f..ec397c4 100644
--- a/drivers/media/usb/dvb-usb/pctv452e.c
+++ b/drivers/media/usb/dvb-usb/pctv452e.c
@@ -611,7 +611,7 @@ static int pctv452e_read_mac_address(struct dvb_usb_device 
*d, u8 mac[6])
return 0;
 
 failed:
-   memset(mac, 0, 6);
+   eth_zero_addr(mac);
 
return ret;
 }
-- 
1.9.1

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH 09/29] pctv452e: fix sparse warnings

[Hans Verkuil]

From: Hans Verkuil hans.verk...@cisco.com

drivers/media/usb/dvb-usb/pctv452e.c:886:64: warning: Using plain integer as 
NULL pointer
drivers/media/usb/dvb-usb/pctv452e.c:903:63: warning: Using plain integer as 
NULL pointer
drivers/media/usb/dvb-usb/pctv452e.c:968:19: warning: Using plain integer as 
NULL pointer
drivers/media/usb/dvb-usb/pctv452e.c:1026:19: warning: Using plain integer as 
NULL pointer

Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
 drivers/media/usb/dvb-usb/pctv452e.c | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/media/usb/dvb-usb/pctv452e.c 
b/drivers/media/usb/dvb-usb/pctv452e.c
index bdfe896..d17618f 100644
--- a/drivers/media/usb/dvb-usb/pctv452e.c
+++ b/drivers/media/usb/dvb-usb/pctv452e.c
@@ -883,7 +883,7 @@ static int pctv452e_frontend_attach(struct dvb_usb_adapter 
*a)
if (!a-fe_adap[0].fe)
return -ENODEV;
if ((dvb_attach(lnbp22_attach, a-fe_adap[0].fe,
-   a-dev-i2c_adap)) == 0)
+   a-dev-i2c_adap)) == NULL)
err(Cannot attach lnbp22\n);
 
id = a-dev-desc-warm_ids[0];
@@ -900,7 +900,7 @@ static int pctv452e_tuner_attach(struct dvb_usb_adapter *a)
if (!a-fe_adap[0].fe)
return -ENODEV;
if (dvb_attach(stb6100_attach, a-fe_adap[0].fe, stb6100_config,
-   a-dev-i2c_adap) == 0) {
+   a-dev-i2c_adap) == NULL) {
err(%s failed\n, __func__);
return -ENODEV;
}
@@ -965,7 +965,7 @@ static struct dvb_usb_device_properties pctv452e_properties 
= {
  .cold_ids = { NULL, NULL }, /* this is a warm only device */
  .warm_ids = { pctv452e_usb_table[0], NULL }
},
-   { 0 },
+   { NULL },
}
 };
 
@@ -1023,7 +1023,7 @@ static struct dvb_usb_device_properties 
tt_connect_s2_3600_properties = {
  .cold_ids = { NULL, NULL },
  .warm_ids = { pctv452e_usb_table[2], NULL }
},
-   { 0 },
+   { NULL },
}
 };
 
-- 
2.1.0.rc1

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[Antti Palosaari]

Hi guys,
I was able to got that device, just because of you, and I cannot 
reproduce that error. I ran it many hours against signal from modulator 
yesterday and it didn't hang. I used szap  mplayer. Also I ran w_scan. 
Only problem I saw was these I2C errors printed.


So you make tests, likely using szap, and say how I can make it hang?

regards
Antti



On 07/02/2012 07:33 PM, Steve Hill wrote:


I've been using a Technotrend TT 3600 USB DVB-S2 receiver for a couple
of years, which has (largely) been working fine under the S2-liplianin
pctv452e driver.  I've been aware of a lot of documented problems with
running this receiver under the 3.x kernel, so I've stuck with the 2.6
series kernels.

Unfortunately I've now had to upgrade to the 3.2.0 kernel for other
unrelated reasons, and it seems that the device is more or less unusable
under this kernel.  With the stock 3.2.0 kernel, the driver produces
numerous I2C errors and is quite unreliable.  The I2C errors seem to be
produced exclusively as a result of stb_6100_read_reg() reading register
F, and notably all calls to stb6100_read_regs() seem to succeed, so I've
replaced the stb_6100_read_reg() function with a call to
stb6100_read_regs(), so it reads all the registers and then returns the
requested one, rather than reading just the requested register.  This
seems to make the I2C errors disappear.

However, the card is still very unreliable - after about 5 minutes of
receiving a channel (using MythTV), it breaks.  No errors logged in
dmesg, but MythTV logs:

DevRdB(/dev/dvb/adapter0/frontend0) Error: Poll giving up
DVBSH(/dev/dvb/adapter0/frontend0) Error: Device error detected
DVBRec(7:/dev/dvb/adapter0/frontend0) Error: Stream handler died
unexpectedly.


Can anyone give me any pointers that might help?  I've searched and
searched and all I can see if people saying that it won't work since the
DVB-S2 code was integrated into the kernel tree, but I've not seen
anyone try to figure out _why_ it won't work.

Thanks.




--
http://palosaari.fi/
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[Steve Hill]

On 04/07/12 17:22, Antti Palosaari wrote:


  As the new DVB-USB fixes many bugs I ask you to test it. I converted
  pctv452e driver for you:
http://git.linuxtv.org/anttip/media_tree.git/shortlog/refs/heads/pctv452e


I've had chance to give this kernel a go.  Unfortunately I'm getting an 
(unrelated) crash, which appears to be caused by IP forwarding.  The 
crash basically makes it unusable so I'm not actually able to test the 
PCTV driver. :(


I'll add the stack trace here for reference, although as mentioned, it 
doesn't appear to be related to the DVB drivers:


[  126.188809] [ cut here ]
[  126.193455] kernel BUG at mm/slab.c:505!
[  126.197388] Internal error: Oops - BUG: 0 [#1] ARM
[  126.202191] Modules linked in: ctr twofish_generic twofish_common 
camellia_generic serpent_generic blowfish_generic blowfish_common cao

[  126.261699] CPU: 0Not tainted  (3.5.0-rc5+ #1)
[  126.266510] PC is at kfree+0xa0/0xfc
[  126.270096] LR is at __kfree_skb+0x14/0xbc
[  126.274204] pc : [c00c991c]lr : [c0275a20]psr: 4093
[  126.274204] sp : deadbb20  ip : 00ff  fp : deadbba4
[  126.285729] r10: c045b0a4  r9 :   r8 : 0001
[  126.290971] r7 :   r6 : a013  r5 : de2e7034  r4 : de2e7000
[  126.297519] r3 : c08bdce0  r2 :   r1 :   r0 : de2e7000
[  126.304069] Flags: nZcv  IRQs off  FIQs on  Mode SVC_32  ISA ARM 
Segment user

[  126.311315] Control: 0005397f  Table: 1eac8000  DAC: 0015
[  126.317078] Process tput (pid: 1411, stack limit = 0xdeada270)
[  126.322930] Stack: (0xdeadbb20 to 0xdeadc000)
[  126.327304] bb20: de11a5e0 de2e7034 0003 c0275a20 de11a5e0 
c02aa448 ded95000 00012c9f
[  126.335518] bb40:  de11a5e0 de2e7034 de11a5e0 de2e7034 
deadbba4 0008 
[  126.343732] bb60: c048e8c0 c02a885c ded95000 0001 0002 
c045b084 df904000 deadbba4
[  126.351946] bb80: 0008 c027d77c    
c04915f4  de11a5e0
[  126.360161] bba0: deada000 c045b0a4 c08bdce0 de11a5e0 2fcded46 
df9045dc df904000 8000
[  126.368374] bbc0:  df904460  bf01c054  
0005  df904460
[  126.376588] bbe0:  0010 df90454c 0080 df9059b0 
 df904600 
[  126.384802] bc00: def2be38 df90454c c0492360 0001 c04b5bc0 
012c  0080
[  126.393017] bc20: c0492368 c027db90 c04b5bcc b3c1 c04b5bcc 
deada000 0001 000c
[  126.401232] bc40: c04b5bc0 0003 0100 c0491bcc c0468944 
c0025f68  c046a7f0
[  126.409446] bc60:  000a deadbcdc 000b  
fed20200 deadbcdc c04915f4
[  126.417660] bc80:  c0491bcc 000200da c002618c 000b 
c000f850 c009c228 4013
[  126.425874] bca0: fed20200 c000e574 c04915f4  0385 
0004 0041 
[  126.434089] bcc0: a18a4473 0002 c04915f4  c0491bcc 
000200da 0001bc8c deadbcf4
[  126.442303] bce0: c009c28c c009c228 4013   
 deada000 c009c28c
[  126.450516] bd00: 0041 0001bc8c 0385 c009e830 0041 
 0002 0001
[  126.458732] bd20: 0018  c0491bd0   
deada000 c04915f4 0002
[  126.466945] bd40:   deadbd8c c04915f4 0122 
000200da deada000 
[  126.475159] bd60: 0002 def2be38  c0491bcc 0001 
c009eebc 0001 0041
[  126.483374] bd80: c04915f4 0002 dedb41c0 de0e50f8 0100 
  df48d868
[  126.491587] bda0: 0002 002a de42ae04 dee49b78 c0491bd0 
0200  000200da
[  126.499801] bdc0: 0010   c00b5234 de87b69c 
 0028 002a
[  126.508016] bde0: c04915f4 c0527580 def2be38 def2be38 0001 
bea81000 de9a3204 def2be38
[  126.516230] be00:  de42aca0 deacafa8 c00b6f94 002a 
0028  
[  126.524445] be20:  deada000 b6d7b000   
 deadbe78 bea81000
[  126.532659] be40: deac8000 05f5 de42aca0 def2be38 0029 
deacafa8  c00b76ec
[  126.540874] be60: deacafa8 0029 deadbfb0 bea81c34 def2be38 
def2eb60 de42aca0 0029
[  126.549088] be80: 0817 c0015548 deadbf08 b6efb000 deadbf08 
c00b8390 de42acd4 
[  126.557302] bea0: deacadb8 de42aca0 b6efafff b6efb000 df59f1c8 
df59f1a4 b6eed000 
[  126.565517] bec0: b6efb000 b6eed000 deadbf08 de0fa548 df9af70c 
b6eed000  c08cd1c0
[  126.573730] bee0:  c08cd1c0  0817 c045e414 
bea81c34 deadbfb0 
[  126.581944] bf00:  b6f2  c0008404  
  c00d5018
[  126.590158] bf20:   017d  de0fa548 
  de0fa548
[  126.598373] bf40:  b6efb000 b6eed000 c00ba184 de42aca0 
de0fa548  c00bb3c4
[  126.606588] bf60: b6efb000 b6eed000 d71f de42acd4  
b6eed000 de42aca0 c000eae8
[  126.614802] bf80: deada000  bea83aec c00bb450 b6f2 
08b4  8bd4

Re: pctv452e

[Marx]

On 11.07.2012 01:13, Antti Palosaari wrote:

All these tests shows your device is running as it should.
There are errors in almost every case, they are absent in your example. 
Is it ok?



Test VDR again to see if it breaks.
VDR unfortunatelly doesn't work saying frontend 0/0 timed out while 
tuning to channel 21, tp 26 and ERROR: streamdev: protocol 
violation (VTP) from 127.0.0.1:38551. In fact I cannot play any stream 
directly via VDR, but it can be caused by some incompatibility between 
VDR and the newest kernel.

VDR reads EPG properly so there is something wrong with it.
But it's probem not for this list.

Today test works like yesterday.

I will wait and test again later.

Marx

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[Marx]

I've attached stream analysis via ffmpeg in another post. I can upload 
saved stream if needed. I simply don't know how to check if weak signal 
is problem. Szap (or extended version szap-s2) gives me some numbers but 
I don't know how to properly read them.

Is this pctv452e device known to have poor reception?
Marx

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[Marx]

On 09.07.2012 19:46, Antti Palosaari wrote:


# tune to channel:
szap -r CHANNEL NAME

-r option is important here as it routes stream to /dev/dvb/adapter0/dvr0


done


# dump channels from tuned multiplex (if you don't have that command
just skip):
scandvb -c


marx@wuwek:~/zmaz$ scan -c
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
0x 0x10d7: pmt_pid 0x0104 TVN -- TVN (running, scrambled)
0x 0x10d8: pmt_pid 0x0105 TVN -- TVN 24 (running, scrambled)
0x 0x10d9: pmt_pid 0x0106 TVN -- TVN Siedem (running, scrambled)
0x 0x10da: pmt_pid 0x0107 TVN -- nSport (running, scrambled)
0x 0x10dc: pmt_pid 0x0109 TVN -- Mango 24 (running)
0x 0x10dd: pmt_pid 0x010a ITI -- TTV (running, scrambled)
0x 0x10de: pmt_pid 0x010b TVN -- TVN Meteo (running, scrambled)
0x 0x10df: pmt_pid 0x010c TVN -- TVN Turbo (running, scrambled)
0x 0x10e0: pmt_pid 0x010d TVN -- TVN Style (running, scrambled)
0x 0x10e1: pmt_pid 0x010e TVN -- Test (running, scrambled)
0x 0x10e2: pmt_pid 0x010f TVN -- TVN CNBC (running, scrambled)
0x 0x10ed: pmt_pid 0x0118 TVN -- Test_Radio (running)
0x 0x3aca: pmt_pid 0x0101 TVN -- Upload (running)
dumping lists (13 services)
TVN  (0x10d7) 01: PCR == V   V 0x0200 A 0x028a (pol) 
TT 0x0240 AC3 0x028b SUB 0x1771
TVN 24   (0x10d8) 01: PCR == V   V 0x0201 A 0x0294 (pol) 
0x0295 (org) SUB 0x177c
TVN Siedem   (0x10d9) 01: PCR == V   V 0x0202 A 0x029e (pol) 
TT 0x0242 AC3 0x029f SUB 0x1772

nSport   (0x10da) 01: PCR == V   V 0x0203 A 0x02a8 (pol)
Mango 24 (0x10dc) 01: PCR == V   V 0x0205 A 0x02bc (pol) 
TT 0x0245
TTV  (0x10dd) 01: PCR == V   V 0x0206 A 0x02c6 (pol) 
TT 0x0246 AC3 0x02c7
TVN Meteo(0x10de) 01: PCR == V   V 0x0207 A 0x02d0 (pol) 
0x02d1 (org) SUB 0x1782
TVN Turbo(0x10df) 01: PCR == V   V 0x0208 A 0x02da (pol) 
TT 0x0247 AC3 0x02db SUB 0x1773
TVN Style(0x10e0) 01: PCR == V   V 0x0209 A 0x02e4 (pol) 
TT 0x0248 AC3 0x02e5 SUB 0x1774
Test (0x10e1) 01: PCR == V   V 0x020a A 0x02ee (pol) 
TT 0x0249

TVN CNBC (0x10e2) 01: PCR == V   V 0x020b A 0x02f8 (pol)
Test_Radio   (0x10ed) 02: PCR == AA 0x0320 (eng)
Upload   (0x3aca) 01: PCR 0x1fff
Done.




Could be named as scan, dvbscan, scandvb


# save tuned channel to file (lets say 20 second):
cat /dev/dvb/adapter0/dvr0  test.ts



actually seems like ffmpeg could read directly dvr0
ffmpeg -i /dev/dvb/adapter0/dvr0
takes ~20 seconds or so until results are shown


marx@wuwek:~/zmaz$ ffmpeg -i /dev/dvb/adapter0/dvr0
p11-kit: couldn't load module: 
/usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: 
/usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open 
shared object file: No such file or directory

ffmpeg version 0.8.3-6:0.8.3-4, Copyright (c) 2000-2012 the Libav developers
  built on Jun 26 2012 07:23:46 with gcc 4.7.1
*** THIS PROGRAM IS DEPRECATED ***
This program is only provided for compatibility and will be removed in a 
future release. Please use avconv instead.

[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 5 got 6
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 0 got 1
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 2 got 3
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 5 got 6
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 15 got 0
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 7 got 8
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 11 got 12
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 13 got 14
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 7 got 8
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 15 got 0
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 4 got 5
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 10 got 11
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 2 got 4
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 5 got 3
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 11 got 12
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 14 got 15
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 1 got 2
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 10 got 11
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 1 got 2
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 3 got 1
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 7 got 9
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 10 got 9





# check if ffmpeg finds video and audio
ffmpeg -i test.ts

marx@wuwek:~/zmaz$ ffmpeg -i test.ts
p11-kit: couldn't load module: 

Re: pctv452e

[Antti Palosaari]

On 07/10/2012 09:39 AM, Marx wrote:

On 09.07.2012 19:46, Antti Palosaari wrote:


# tune to channel:
szap -r CHANNEL NAME

-r option is important here as it routes stream to /dev/dvb/adapter0/dvr0


done


# dump channels from tuned multiplex (if you don't have that command
just skip):
scandvb -c


marx@wuwek:~/zmaz$ scan -c
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
0x 0x10d7: pmt_pid 0x0104 TVN -- TVN (running, scrambled)
0x 0x10d8: pmt_pid 0x0105 TVN -- TVN 24 (running, scrambled)
0x 0x10d9: pmt_pid 0x0106 TVN -- TVN Siedem (running, scrambled)
0x 0x10da: pmt_pid 0x0107 TVN -- nSport (running, scrambled)
0x 0x10dc: pmt_pid 0x0109 TVN -- Mango 24 (running)
0x 0x10dd: pmt_pid 0x010a ITI -- TTV (running, scrambled)
0x 0x10de: pmt_pid 0x010b TVN -- TVN Meteo (running, scrambled)
0x 0x10df: pmt_pid 0x010c TVN -- TVN Turbo (running, scrambled)
0x 0x10e0: pmt_pid 0x010d TVN -- TVN Style (running, scrambled)
0x 0x10e1: pmt_pid 0x010e TVN -- Test (running, scrambled)
0x 0x10e2: pmt_pid 0x010f TVN -- TVN CNBC (running, scrambled)
0x 0x10ed: pmt_pid 0x0118 TVN -- Test_Radio (running)
0x 0x3aca: pmt_pid 0x0101 TVN -- Upload (running)
dumping lists (13 services)
TVN  (0x10d7) 01: PCR == V   V 0x0200 A 0x028a (pol)
TT 0x0240 AC3 0x028b SUB 0x1771
TVN 24   (0x10d8) 01: PCR == V   V 0x0201 A 0x0294 (pol)
0x0295 (org) SUB 0x177c
TVN Siedem   (0x10d9) 01: PCR == V   V 0x0202 A 0x029e (pol)
TT 0x0242 AC3 0x029f SUB 0x1772
nSport   (0x10da) 01: PCR == V   V 0x0203 A 0x02a8 (pol)
Mango 24 (0x10dc) 01: PCR == V   V 0x0205 A 0x02bc (pol)
TT 0x0245
TTV  (0x10dd) 01: PCR == V   V 0x0206 A 0x02c6 (pol)
TT 0x0246 AC3 0x02c7
TVN Meteo(0x10de) 01: PCR == V   V 0x0207 A 0x02d0 (pol)
0x02d1 (org) SUB 0x1782
TVN Turbo(0x10df) 01: PCR == V   V 0x0208 A 0x02da (pol)
TT 0x0247 AC3 0x02db SUB 0x1773
TVN Style(0x10e0) 01: PCR == V   V 0x0209 A 0x02e4 (pol)
TT 0x0248 AC3 0x02e5 SUB 0x1774
Test (0x10e1) 01: PCR == V   V 0x020a A 0x02ee (pol)
TT 0x0249
TVN CNBC (0x10e2) 01: PCR == V   V 0x020b A 0x02f8 (pol)
Test_Radio   (0x10ed) 02: PCR == AA 0x0320 (eng)
Upload   (0x3aca) 01: PCR 0x1fff
Done.




Could be named as scan, dvbscan, scandvb


# save tuned channel to file (lets say 20 second):
cat /dev/dvb/adapter0/dvr0  test.ts



actually seems like ffmpeg could read directly dvr0
ffmpeg -i /dev/dvb/adapter0/dvr0
takes ~20 seconds or so until results are shown


marx@wuwek:~/zmaz$ ffmpeg -i /dev/dvb/adapter0/dvr0
p11-kit: couldn't load module:
/usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so:
/usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open
shared object file: No such file or directory
ffmpeg version 0.8.3-6:0.8.3-4, Copyright (c) 2000-2012 the Libav
developers
   built on Jun 26 2012 07:23:46 with gcc 4.7.1
*** THIS PROGRAM IS DEPRECATED ***
This program is only provided for compatibility and will be removed in a
future release. Please use avconv instead.
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 5 got 6
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 0 got 1
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 2 got 3
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 5 got 6
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 15 got 0
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 7 got 8
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 11 got 12
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 13 got 14
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 7 got 8
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 15 got 0
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 4 got 5
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 10 got 11
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 2 got 4
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 5 got 3
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 11 got 12
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 14 got 15
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 1 got 2
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 10 got 11
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 1 got 2
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 3 got 1
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 7 got 9
[mpegts @ 0x8cd5900] Continuity check failed for pid 520 expected 10 got 9





# check if ffmpeg finds video and audio
ffmpeg -i test.ts

marx@wuwek:~/zmaz$ ffmpeg -i test.ts
p11-kit: couldn't load module:

Re: pctv452e

[poma]

On 07/10/2012 08:43 AM, Marx wrote:
 I've attached stream analysis via ffmpeg in another post. I can upload
 saved stream if needed. I simply don't know how to check if weak signal
 is problem. Szap (or extended version szap-s2) gives me some numbers but
 I don't know how to properly read them.

…ffprobe
Play with a femon, dvbsnoop, …
http://www.linuxtv.org/wiki/index.php/LinuxTV_dvb-apps
http://www.linuxtv.org/wiki/index.php/Dvbsnoop
Read a bit
http://www.linuxtv.org/wiki/index.php/Testing_reception_quality

 Is this pctv452e device known to have poor reception?

modinfo stb6100 | grep author ;)
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[Devin Heitmueller]

On Tue, Jul 10, 2012 at 11:51 AM, poma pomidorabelis...@gmail.com wrote:
 Is this pctv452e device known to have poor reception?

Traditionally speaking, these problems are usually not the hardware
itself - it tends to be crappy Linux drivers.  Somebody gets support
working for a chip on some product, and then somebody else does a
cut/paste of the code to make some other product work.  They see it
getting signal lock under optimal tuning conditions and declare
success.

Making any given device work *well* tends to be much harder than
making it work at all.

Want to rule out bad hardware design?  Drop it into a Windows machine
and see how it performs.  If it works fine under Windows but poorly
under Linux, then you definitely have a Linux driver problem.

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[Marx]

W dniu 2012-07-10 11:33, Antti Palosaari pisze:


Seems like stream is broken. It should look like that:

Input #0, mpegts, from '/dev/dvb/adapter0/dvr0':
   Duration: N/A, start: 19013.637311, bitrate: 15224 kb/s
 Stream #0:0[0x231]: Audio: mp2, 48000 Hz, stereo, s16, 224 kb/s
 Stream #0:1[0x131]: Video: mpeg2video (Main), yuv420p, 720x576 [SAR
64:45 DAR 16:9], 15000 kb/s, 26.89 fps, 25 tbr, 90k tbn, 50 tbc


You have said it works some times. Could you try to using tzap + ffmpeg
cases when it works and when it does not. Use FTA channels to analyze as
I think ffmpeg could not say much about encrypted streams.


It's hard to say it works because I have no GUI on this PC and I don't 
know a method to share directly device/stream into PC.

Hovewer I've tried to tune and analyze several FTA channels.
I have now better results because:
1) i've disconnected pctv device (USB  power)
2) poweroff
3) poweron
4) connect device
If I simply reboot or reconnect device - it doesn't help.

[   67.544510] Linux media interface: v0.10
[   67.565420] Linux video capture interface: v2.00
[   67.834186] saa7146: register extension 'av7110'
[ 1536.841356] usb 1-4: new high-speed USB device number 2 using ehci_hcd
[ 1537.437957] usb 1-4: New USB device found, idVendor=2304, idProduct=021f
[ 1537.437971] usb 1-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0

[ 1537.437980] usb 1-4: Product: PCTV452e
[ 1537.437989] usb 1-4: Manufacturer: Pinnacle
[ 1537.556548] usb 1-4: dvb_usbv2: found a 'PCTV HDTV USB' in warm state
[ 1537.556560] pctv452e_power_ctrl: 1
[ 1537.556565] pctv452e_power_ctrl: step 1
[ 1537.556570] pctv452e_power_ctrl: step 2
[ 1537.557057] pctv452e_power_ctrl: step 3
[ 1537.557197] usbcore: registered new interface driver dvb_usb_pctv452e
[ 1537.557263] pctv452e_power_ctrl: step 4
[ 1537.557491] pctv452e_power_ctrl: step 5
[ 1537.557610] usb 1-4: dvb_usbv2: will pass the complete MPEG2 
transport stream to the software demuxer

[ 1537.557670] DVB: registering new adapter (PCTV HDTV USB)
[ 1537.602916] stb0899_attach: Attaching STB0899
[ 1537.611531] DVB: registering adapter 0 frontend 0 (STB0899 
Multistandard)...

[ 1537.625143] stb6100_attach: Attaching STB6100
[ 1537.625158] pctv452e_power_ctrl: 0
[ 1537.625173] usb 1-4: dvb_usbv2: 'PCTV HDTV USB' successfully 
initialized and connected


I don't know why it say device is in warm state. As I understand warm 
means with firmware loaded(?), but this device was completely switched off.


1) Mango 24
wuwek:~# szap -n 51 -r
reading channels from file '/root/.szap/channels.conf'
zapping to 51 'Mango 24;TVN':
sat 0, frequency = 11393 MHz V, symbolrate 2750, vpid = 0x0205, apid 
= 0x02bc sid = 0x0245

using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
status 1f | signal 01c6 | snr 0093 | ber  | unc fffe | 
FE_HAS_LOCK


wuwek:~# ffmpeg -i /dev/dvb/adapter0/dvr0
p11-kit: couldn't load module: 
/usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: 
/usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open 
shared object file: No such file or directory

ffmpeg version 0.8.3-6:0.8.3-4, Copyright (c) 2000-2012 the Libav developers
  built on Jun 26 2012 07:23:46 with gcc 4.7.1
*** THIS PROGRAM IS DEPRECATED ***
This program is only provided for compatibility and will be removed in a 
future release. Please use avconv instead.

[mpeg2video @ 0x8d47940] mpeg_decode_postinit() failure
[mp3 @ 0x8d4a5c0] Header missing
Last message repeated 2 times
[mpegts @ 0x8d43900] max_analyze_duration reached
[mpegts @ 0x8d43900] Estimating duration from bitrate, this may be 
inaccurate

Input #0, mpegts, from '/dev/dvb/adapter0/dvr0':
  Duration: N/A, start: 90810.592967, bitrate: 1 kb/s
Stream #0.0[0x205]: Video: mpeg2video (Main), yuv420p, 480x576 [PAR 
32:15 DAR 16:9], 1 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc

Stream #0.1[0x2bc]: Audio: mp3, 0 channels, s16
At least one output file must be specified

2. Eska TV
wuwek:~# szap -n 52 -r
reading channels from file '/root/.szap/channels.conf'
zapping to 52 'Eska TV;ITI':
sat 0, frequency = 11508 MHz V, symbolrate 2750, vpid = 0x020a, apid 
= 0x02d6 sid = 0x

using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
status 1f | signal 01ce | snr 008e | ber  | unc fffe | 
FE_HAS_LOCK


wuwek:~# ffmpeg -i /dev/dvb/adapter0/dvr0
p11-kit: couldn't load module: 
/usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: 
/usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open 
shared object file: No such file or directory

ffmpeg version 0.8.3-6:0.8.3-4, Copyright (c) 2000-2012 the Libav developers
  built on Jun 26 2012 07:23:46 with gcc 4.7.1
*** THIS PROGRAM IS DEPRECATED ***
This program is only provided for compatibility and will be removed in a 
future release. Please use avconv instead.

[mpegts @ 0x9f1e900] max_analyze_duration reached
[mpegts @ 0x9f1e900] Estimating duration from bitrate, this may be 
inaccurate

Re: pctv452e

[poma]

On 07/10/2012 05:58 PM, Devin Heitmueller wrote:
 On Tue, Jul 10, 2012 at 11:51 AM, poma pomidorabelis...@gmail.com wrote:
 Is this pctv452e device known to have poor reception?
 
 Traditionally speaking, these problems are usually not the hardware
 itself - it tends to be crappy Linux drivers.  Somebody gets support
 working for a chip on some product, and then somebody else does a
 cut/paste of the code to make some other product work.  They see it
 getting signal lock under optimal tuning conditions and declare
 success.
 
 Making any given device work *well* tends to be much harder than
 making it work at all.
 
 Want to rule out bad hardware design?  Drop it into a Windows machine
 and see how it performs.  If it works fine under Windows but poorly
 under Linux, then you definitely have a Linux driver problem.
 
 Devin
 

This one is for Marx?

cheers,
poma

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[Antti Palosaari]

On 07/11/2012 12:08 AM, Marx wrote:

W dniu 2012-07-10 11:33, Antti Palosaari pisze:


Seems like stream is broken. It should look like that:

Input #0, mpegts, from '/dev/dvb/adapter0/dvr0':
   Duration: N/A, start: 19013.637311, bitrate: 15224 kb/s
 Stream #0:0[0x231]: Audio: mp2, 48000 Hz, stereo, s16, 224 kb/s
 Stream #0:1[0x131]: Video: mpeg2video (Main), yuv420p, 720x576 [SAR
64:45 DAR 16:9], 15000 kb/s, 26.89 fps, 25 tbr, 90k tbn, 50 tbc


You have said it works some times. Could you try to using tzap + ffmpeg
cases when it works and when it does not. Use FTA channels to analyze as
I think ffmpeg could not say much about encrypted streams.


It's hard to say it works because I have no GUI on this PC and I don't
know a method to share directly device/stream into PC.
Hovewer I've tried to tune and analyze several FTA channels.
I have now better results because:
1) i've disconnected pctv device (USB  power)
2) poweroff
3) poweron
4) connect device
If I simply reboot or reconnect device - it doesn't help.

[   67.544510] Linux media interface: v0.10
[   67.565420] Linux video capture interface: v2.00
[   67.834186] saa7146: register extension 'av7110'
[ 1536.841356] usb 1-4: new high-speed USB device number 2 using ehci_hcd
[ 1537.437957] usb 1-4: New USB device found, idVendor=2304, idProduct=021f
[ 1537.437971] usb 1-4: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[ 1537.437980] usb 1-4: Product: PCTV452e
[ 1537.437989] usb 1-4: Manufacturer: Pinnacle
[ 1537.556548] usb 1-4: dvb_usbv2: found a 'PCTV HDTV USB' in warm state
[ 1537.556560] pctv452e_power_ctrl: 1
[ 1537.556565] pctv452e_power_ctrl: step 1
[ 1537.556570] pctv452e_power_ctrl: step 2
[ 1537.557057] pctv452e_power_ctrl: step 3
[ 1537.557197] usbcore: registered new interface driver dvb_usb_pctv452e
[ 1537.557263] pctv452e_power_ctrl: step 4
[ 1537.557491] pctv452e_power_ctrl: step 5
[ 1537.557610] usb 1-4: dvb_usbv2: will pass the complete MPEG2
transport stream to the software demuxer
[ 1537.557670] DVB: registering new adapter (PCTV HDTV USB)
[ 1537.602916] stb0899_attach: Attaching STB0899
[ 1537.611531] DVB: registering adapter 0 frontend 0 (STB0899
Multistandard)...
[ 1537.625143] stb6100_attach: Attaching STB6100
[ 1537.625158] pctv452e_power_ctrl: 0
[ 1537.625173] usb 1-4: dvb_usbv2: 'PCTV HDTV USB' successfully
initialized and connected

I don't know why it say device is in warm state. As I understand warm
means with firmware loaded(?), but this device was completely switched off.


Because it does not need to firmware downloaded by the driver. It 
downloads firmware from the eeprom. As it does not need firmware to be 
downloaded by driver it is always warm from the driver point of view.



1) Mango 24
wuwek:~# szap -n 51 -r
reading channels from file '/root/.szap/channels.conf'
zapping to 51 'Mango 24;TVN':
sat 0, frequency = 11393 MHz V, symbolrate 2750, vpid = 0x0205, apid
= 0x02bc sid = 0x0245
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
status 1f | signal 01c6 | snr 0093 | ber  | unc fffe |
FE_HAS_LOCK

wuwek:~# ffmpeg -i /dev/dvb/adapter0/dvr0
p11-kit: couldn't load module:
/usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so:
/usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open
shared object file: No such file or directory
ffmpeg version 0.8.3-6:0.8.3-4, Copyright (c) 2000-2012 the Libav
developers
   built on Jun 26 2012 07:23:46 with gcc 4.7.1
*** THIS PROGRAM IS DEPRECATED ***
This program is only provided for compatibility and will be removed in a
future release. Please use avconv instead.
[mpeg2video @ 0x8d47940] mpeg_decode_postinit() failure
[mp3 @ 0x8d4a5c0] Header missing
 Last message repeated 2 times
[mpegts @ 0x8d43900] max_analyze_duration reached
[mpegts @ 0x8d43900] Estimating duration from bitrate, this may be
inaccurate
Input #0, mpegts, from '/dev/dvb/adapter0/dvr0':
   Duration: N/A, start: 90810.592967, bitrate: 1 kb/s
 Stream #0.0[0x205]: Video: mpeg2video (Main), yuv420p, 480x576 [PAR
32:15 DAR 16:9], 1 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc
 Stream #0.1[0x2bc]: Audio: mp3, 0 channels, s16
At least one output file must be specified

2. Eska TV
wuwek:~# szap -n 52 -r
reading channels from file '/root/.szap/channels.conf'
zapping to 52 'Eska TV;ITI':
sat 0, frequency = 11508 MHz V, symbolrate 2750, vpid = 0x020a, apid
= 0x02d6 sid = 0x
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
status 1f | signal 01ce | snr 008e | ber  | unc fffe |
FE_HAS_LOCK

wuwek:~# ffmpeg -i /dev/dvb/adapter0/dvr0
p11-kit: couldn't load module:
/usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so:
/usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open
shared object file: No such file or directory
ffmpeg version 0.8.3-6:0.8.3-4, Copyright (c) 2000-2012 the Libav
developers
   built on Jun 26 2012 07:23:46 with gcc 4.7.1
*** THIS PROGRAM IS DEPRECATED ***
This program is only provided

Re: pctv452e

[Marx]

On 08.07.2012 14:32, Antti Palosaari wrote:

I suspect you stopped szap ?

You cannot use dvbdate or dvbtraffic, nor read data from dvr0 unless
frontend is tuned. Leave szap running backround and try again.


That way it works, and I can save stream. Hovewer it's strange because I 
shouldn't have to constatly tune channel to watch it, and on previous 
cards it was enough to tune once and then use other commands.

I base my knowledge on
http://www.linuxtv.org/wiki/index.php/Testing_your_DVB_device
There is nothing about constant tuning channel to use it. Am I missing 
something?

Marx

wuwek:/var/lib/vdr/kanaly# nohup ./szap-s2 -n 41 -r 
[1] 4888
wuwek:/var/lib/vdr/kanaly# nohup: zignorowanie wejścia i dołączenie 
wyników do `nohup.out'


wuwek:/var/lib/vdr/kanaly#
wuwek:/var/lib/vdr/kanaly# ps ax|grep szap
 4888 pts/1S  0:00 ./szap-s2 -n 41 -r
 4891 pts/1S+ 0:00 grep szap
wuwek:/var/lib/vdr/kanaly# dvbdate
Mon Jul  9 07:12:43 2012
wuwek:/var/lib/vdr/kanaly# dvbtraffic
 9 p/s 1 kb/s14 kbit
0001 9 p/s 1 kb/s14 kbit
0011 1 p/s 0 kb/s 2 kbit
0014 0 p/s 0 kb/s 1 kbit
010429 p/s 5 kb/s44 kbit
010858 p/s10 kb/s88 kbit
010964 p/s11 kb/s97 kbit
0e04   309 p/s56 kb/s   465 kbit
0e77   228 p/s41 kb/s   343 kbit
0e7859 p/s10 kb/s90 kbit
17d5  2139 p/s   392 kb/s  3217 kbit
17df90 p/s16 kb/s   136 kbit
17e090 p/s16 kb/s   136 kbit
1831 4 p/s 0 kb/s 7 kbit
1832 9 p/s 1 kb/s14 kbit
1833 9 p/s 1 kb/s14 kbit
1834 4 p/s 0 kb/s 7 kbit
1836 9 p/s 1 kb/s14 kbit
1839  1247 p/s   228 kb/s  1876 kbit
184390 p/s16 kb/s   136 kbit
184490 p/s16 kb/s   136 kbit
1895 4 p/s 0 kb/s 7 kbit
1896 9 p/s 1 kb/s14 kbit
1897 9 p/s 1 kb/s14 kbit

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[Antti Palosaari]

On 07/09/2012 09:24 AM, Marx wrote:

On 08.07.2012 14:32, Antti Palosaari wrote:

I suspect you stopped szap ?

You cannot use dvbdate or dvbtraffic, nor read data from dvr0 unless
frontend is tuned. Leave szap running backround and try again.


That way it works, and I can save stream. Hovewer it's strange because I
shouldn't have to constatly tune channel to watch it, and on previous
cards it was enough to tune once and then use other commands.
I base my knowledge on
http://www.linuxtv.org/wiki/index.php/Testing_your_DVB_device
There is nothing about constant tuning channel to use it. Am I missing
something?


given wiki-page says:

4. After you've tuned a frequency and program

a) You could now start up your simple TV watching application and decode 
the stream you have tuned.


For example, while keeping {a,c,s,t}zap running in the first console 
shell, open up another console and run



Behavior have been always same, at least for the DVB USB.

So you don't have problems at all?

regards
Antti

--
http://palosaari.fi/


--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[Marx]

W dniu 2012-07-09 10:42, Antti Palosaari pisze:

On 07/09/2012 09:24 AM, Marx wrote:

On 08.07.2012 14:32, Antti Palosaari wrote:

I suspect you stopped szap ?

You cannot use dvbdate or dvbtraffic, nor read data from dvr0 unless
frontend is tuned. Leave szap running backround and try again.


That way it works, and I can save stream. Hovewer it's strange because I
shouldn't have to constatly tune channel to watch it, and on previous
cards it was enough to tune once and then use other commands.
I base my knowledge on
http://www.linuxtv.org/wiki/index.php/Testing_your_DVB_device
There is nothing about constant tuning channel to use it. Am I missing
something?


given wiki-page says:

4. After you've tuned a frequency and program

a) You could now start up your simple TV watching application and decode
the stream you have tuned.

For example, while keeping {a,c,s,t}zap running in the first console
shell, open up another console and run


Behavior have been always same, at least for the DVB USB.

So you don't have problems at all?


ok, my fault
problem still exists
VDR doesn't play any channel, and while you asked me to abandon it, I 
saved some data using

 cat /dev/dvb/adapter0/dvr0  /mnt/video/test3.ts
while tuning in the background.

Stream saved that way is unplayable (I play it using VLC for windows - 
it played almost all proper TS strems in the past I had). I've tried all 
software I have - to play this streams - no way.


So
- I can tune only 2/3 of channels
- TS stream saves with errors
- traditional tuner on the same (brand new) dish works ok
- i've exchanged cables between the two

is it possible that pctv device is less sensitive and the problem is 
with too weak signal?


Marx

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[Antti Palosaari]

On 07/09/2012 07:44 PM, Marx wrote:

W dniu 2012-07-09 10:42, Antti Palosaari pisze:

On 07/09/2012 09:24 AM, Marx wrote:

On 08.07.2012 14:32, Antti Palosaari wrote:

I suspect you stopped szap ?

You cannot use dvbdate or dvbtraffic, nor read data from dvr0 unless
frontend is tuned. Leave szap running backround and try again.


That way it works, and I can save stream. Hovewer it's strange because I
shouldn't have to constatly tune channel to watch it, and on previous
cards it was enough to tune once and then use other commands.
I base my knowledge on
http://www.linuxtv.org/wiki/index.php/Testing_your_DVB_device
There is nothing about constant tuning channel to use it. Am I missing
something?


given wiki-page says:

4. After you've tuned a frequency and program

a) You could now start up your simple TV watching application and decode
the stream you have tuned.

For example, while keeping {a,c,s,t}zap running in the first console
shell, open up another console and run


Behavior have been always same, at least for the DVB USB.

So you don't have problems at all?


ok, my fault
problem still exists
VDR doesn't play any channel, and while you asked me to abandon it, I
saved some data using
  cat /dev/dvb/adapter0/dvr0  /mnt/video/test3.ts
while tuning in the background.

Stream saved that way is unplayable (I play it using VLC for windows -
it played almost all proper TS strems in the past I had). I've tried all
software I have - to play this streams - no way.

So
- I can tune only 2/3 of channels
- TS stream saves with errors
- traditional tuner on the same (brand new) dish works ok
- i've exchanged cables between the two

is it possible that pctv device is less sensitive and the problem is
with too weak signal?


If VDR does not work at all, but other tools are working, it could be 
compatibility issue between VDR and Kernel.


# tune to channel:
szap -r CHANNEL NAME
# dump channels from tuned multiplex (if you don't have that command 
just skip):

scandvb -c
# save tuned channel to file (lets say 20 second):
cat /dev/dvb/adapter0/dvr0  test.ts
# check if ffmpeg finds video and audio
ffmpeg -i test.ts

and post result here

regards
Antti

--
http://palosaari.fi/


--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[Antti Palosaari]

On 07/09/2012 08:38 PM, Antti Palosaari wrote:

On 07/09/2012 07:44 PM, Marx wrote:

W dniu 2012-07-09 10:42, Antti Palosaari pisze:

On 07/09/2012 09:24 AM, Marx wrote:

On 08.07.2012 14:32, Antti Palosaari wrote:

I suspect you stopped szap ?

You cannot use dvbdate or dvbtraffic, nor read data from dvr0 unless
frontend is tuned. Leave szap running backround and try again.


That way it works, and I can save stream. Hovewer it's strange
because I
shouldn't have to constatly tune channel to watch it, and on previous
cards it was enough to tune once and then use other commands.
I base my knowledge on
http://www.linuxtv.org/wiki/index.php/Testing_your_DVB_device
There is nothing about constant tuning channel to use it. Am I missing
something?


given wiki-page says:

4. After you've tuned a frequency and program

a) You could now start up your simple TV watching application and decode
the stream you have tuned.

For example, while keeping {a,c,s,t}zap running in the first console
shell, open up another console and run


Behavior have been always same, at least for the DVB USB.

So you don't have problems at all?


ok, my fault
problem still exists
VDR doesn't play any channel, and while you asked me to abandon it, I
saved some data using
  cat /dev/dvb/adapter0/dvr0  /mnt/video/test3.ts
while tuning in the background.

Stream saved that way is unplayable (I play it using VLC for windows -
it played almost all proper TS strems in the past I had). I've tried all
software I have - to play this streams - no way.

So
- I can tune only 2/3 of channels
- TS stream saves with errors
- traditional tuner on the same (brand new) dish works ok
- i've exchanged cables between the two

is it possible that pctv device is less sensitive and the problem is
with too weak signal?


If VDR does not work at all, but other tools are working, it could be
compatibility issue between VDR and Kernel.

# tune to channel:
szap -r CHANNEL NAME

-r option is important here as it routes stream to /dev/dvb/adapter0/dvr0


# dump channels from tuned multiplex (if you don't have that command
just skip):
scandvb -c

Could be named as scan, dvbscan, scandvb


# save tuned channel to file (lets say 20 second):
cat /dev/dvb/adapter0/dvr0  test.ts

actually seems like ffmpeg could read directly dvr0
ffmpeg -i /dev/dvb/adapter0/dvr0
takes ~20 seconds or so until results are shown


# check if ffmpeg finds video and audio
ffmpeg -i test.ts

and post result here


Antti


--
http://palosaari.fi/


--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[poma]

On 07/09/2012 06:44 PM, Marx wrote:
 W dniu 2012-07-09 10:42, Antti Palosaari pisze:
 On 07/09/2012 09:24 AM, Marx wrote:
 On 08.07.2012 14:32, Antti Palosaari wrote:
 I suspect you stopped szap ?

 You cannot use dvbdate or dvbtraffic, nor read data from dvr0 unless
 frontend is tuned. Leave szap running backround and try again.

 That way it works, and I can save stream. Hovewer it's strange because I
 shouldn't have to constatly tune channel to watch it, and on previous
 cards it was enough to tune once and then use other commands.
 I base my knowledge on
 http://www.linuxtv.org/wiki/index.php/Testing_your_DVB_device
 There is nothing about constant tuning channel to use it. Am I missing
 something?

 given wiki-page says:
 
 4. After you've tuned a frequency and program

 a) You could now start up your simple TV watching application and decode
 the stream you have tuned.

 For example, while keeping {a,c,s,t}zap running in the first console
 shell, open up another console and run
 

 Behavior have been always same, at least for the DVB USB.

 So you don't have problems at all?
 
 ok, my fault
 problem still exists
 VDR doesn't play any channel, and while you asked me to abandon it, I
 saved some data using
  cat /dev/dvb/adapter0/dvr0  /mnt/video/test3.ts
 while tuning in the background.
 
 Stream saved that way is unplayable (I play it using VLC for windows -
 it played almost all proper TS strems in the past I had). I've tried all
 software I have - to play this streams - no way.
 
 So
 - I can tune only 2/3 of channels
 - TS stream saves with errors
 - traditional tuner on the same (brand new) dish works ok
 - i've exchanged cables between the two
 
 is it possible that pctv device is less sensitive and the problem is
 with too weak signal?

Good reception on one device, completely different story on another
device - same cable; different tuner sensitivity.
It is *very* important to achieve *very* good signal reception with
larger dish(DVB-S) and/or Yagi-Uda(DVB-T) - focal angle/directional gain.
Try this one:
dvbstream -f freq -o 8192  full-mux.ts
enough free disk space ;)
mplayer -cache 8912 full-mux.ts (TAB-TAB-TAB…)
or
dvbstream -f freq -o vid aid tid pid  single-stream.ts

cheers,
poma
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[Antti Palosaari]

On 07/08/2012 02:07 AM, Marx wrote:

W dniu 2012-07-07 02:00, Antti Palosaari pisze:

I don't know what can i do next.


Get the rid of vdr and use only szap/vlc/mplayer only to see if it works.

This computer is remote headless without any GUI, but ok - I'll do my
best (that's why I use VDR - I can using streamdev play it on local PC).


And install latest patch from here:
http://git.linuxtv.org/anttip/media_tree.git/shortlog/refs/heads/pctv452e

it just ignores the I2C error coming from wrong I2C address used which
could have some effect for STB6100 driver.

Patch works as expected - no more I2C errors in error log. Very nice.

Lacking GUI I tried to save stream on HDD.

wuwek:~# szap -n 51 -r
reading channels from file '/root/.szap/channels.conf'
zapping to 51 'Mango 24;TVN':
sat 0, frequency = 11393 MHz V, symbolrate 2750, vpid = 0x0205, apid
= 0x02bc sid = 0x0245
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
status 1f | signal 01ce | snr 0095 | ber  | unc fffe |
FE_HAS_LOCK
status 1f | signal 01ce | snr 0094 | ber  | unc fffe |
FE_HAS_LOCK
status 1f | signal 01ce | snr 0094 | ber  | unc fffe |
FE_HAS_LOCK
wuwek:~# ls /dev/dvb/adapter0/
demux0 dvr0   frontend0  net0
wuwek:~# cat /dev/dvb/adapter0/dvr0  /mnt/video/test.ts
^C
wuwek:~# ls -l /mnt/video/test.ts
-rw-r--r-- 1 root root 0 lip  8 00:37 /mnt/video/test.ts
wuwek:~# dvbdate
dvbdate: Unable to get time from multiplex.
wuwek:~# dvbtraffic
dvbdemux_set_pid_filter: Invalid argument

I've tried to tune many different channels (log at the end), it works
for many of them, some (all HD) doesn't work. I've used szap-s2 because
szap doesn't work with DVB-S2 channels. For DVB-S channels szap produces
results the same as szap-s2.
I've tried to save some different channels (as above) but none saved
anything, so there is still something wrong with this driver.
Marx


I suspect you stopped szap ?

You cannot use dvbdate or dvbtraffic, nor read data from dvr0 unless 
frontend is tuned. Leave szap running backround and try again.


regards
Antti




kern.log:
Jul  8 00:16:29 wuwek kernel: [6.001815] input: HD-Audio Generic
HDMI/DP,pcm=3 as /devices/pci:00/:00:01.1/sound/card0/input3
Jul  8 00:16:29 wuwek kernel: [6.066989] usb 1-4: dvb_usbv2: found a
'PCTV HDTV USB' in warm state
Jul  8 00:16:29 wuwek kernel: [6.067002] pctv452e_power_ctrl: 1
Jul  8 00:16:29 wuwek kernel: [6.067007] pctv452e_power_ctrl: step 1
Jul  8 00:16:29 wuwek kernel: [6.067012] pctv452e_power_ctrl: step 2
Jul  8 00:16:29 wuwek kernel: [6.067559] pctv452e_power_ctrl: step 3
Jul  8 00:16:29 wuwek kernel: [6.067684] usbcore: registered new
interface driver dvb_usb_pctv452e
Jul  8 00:16:29 wuwek kernel: [6.067745] pctv452e_power_ctrl: step 4
Jul  8 00:16:29 wuwek kernel: [6.067996] pctv452e_power_ctrl: step 5
Jul  8 00:16:29 wuwek kernel: [6.068113] usb 1-4: dvb_usbv2: will
pass the complete MPEG2 transport stream to the software demuxer
Jul  8 00:16:29 wuwek kernel: [6.068175] DVB: registering new
adapter (PCTV HDTV USB)
Jul  8 00:16:29 wuwek kernel: [6.117522] input: HDA ATI SB Line as
/devices/pci:00/:00:14.2/sound/card1/input4
Jul  8 00:16:29 wuwek kernel: [6.117730] input: HDA ATI SB Rear Mic
as /devices/pci:00/:00:14.2/sound/card1/input5
Jul  8 00:16:29 wuwek kernel: [6.118330] input: HDA ATI SB Line Out
CLFE as /devices/pci:00/:00:14.2/sound/card1/input6
Jul  8 00:16:29 wuwek kernel: [6.118482] input: HDA ATI SB Line Out
Surround as /devices/pci:00/:00:14.2/sound/card1/input7
Jul  8 00:16:29 wuwek kernel: [6.121096] input: HDA ATI SB Line Out
Front as /devices/pci:00/:00:14.2/sound/card1/input8
Jul  8 00:16:29 wuwek kernel: [6.157236] stb0899_attach: Attaching
STB0899
Jul  8 00:16:29 wuwek kernel: [6.182361] DVB: registering adapter 0
frontend 0 (STB0899 Multistandard)...
Jul  8 00:16:29 wuwek kernel: [6.209194] stb6100_attach: Attaching
STB6100
Jul  8 00:16:29 wuwek kernel: [6.209208] pctv452e_power_ctrl: 0
Jul  8 00:16:29 wuwek kernel: [6.209224] usb 1-4: dvb_usbv2: 'PCTV
HDTV USB' successfully initialized and connected
Jul  8 00:16:29 wuwek kernel: [7.998317] Adding 2097148k swap on
/dev/sda2.  Priority:-1 extents:1 across:2097148k
(...)
Jul  8 00:16:49 wuwek kernel: [   58.654218] pctv452e_power_ctrl: 1
Jul  8 00:16:49 wuwek kernel: [   58.654229] pctv452e_power_ctrl: step 1
Jul  8 00:27:05 wuwek kernel: [  674.833814] pctv452e_power_ctrl: 0
Jul  8 00:27:30 wuwek kernel: [  699.336350] pctv452e_power_ctrl: 1
Jul  8 00:27:30 wuwek kernel: [  699.336363] pctv452e_power_ctrl: step 1
Jul  8 00:28:08 wuwek kernel: [  737.552961] pctv452e_power_ctrl: 0


wuwek:/var/lib/vdr/kanaly# ./szap-s2 -n 2 -x -r
reading channels from file '/root/.szap/channels.conf'
zapping to 2 'TVN Turbo;TVN':
delivery DVB-S, modulation QPSK
sat 0, frequency 11393 MHz V, symbolrate 2750, coderate 5/6

Re: pctv452e

[Marx]

W dniu 2012-07-07 02:00, Antti Palosaari pisze:

I don't know what can i do next.


Get the rid of vdr and use only szap/vlc/mplayer only to see if it works.
This computer is remote headless without any GUI, but ok - I'll do my 
best (that's why I use VDR - I can using streamdev play it on local PC).



And install latest patch from here:
http://git.linuxtv.org/anttip/media_tree.git/shortlog/refs/heads/pctv452e

it just ignores the I2C error coming from wrong I2C address used which
could have some effect for STB6100 driver.

Patch works as expected - no more I2C errors in error log. Very nice.

Lacking GUI I tried to save stream on HDD.

wuwek:~# szap -n 51 -r
reading channels from file '/root/.szap/channels.conf'
zapping to 51 'Mango 24;TVN':
sat 0, frequency = 11393 MHz V, symbolrate 2750, vpid = 0x0205, apid 
= 0x02bc sid = 0x0245

using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
status 1f | signal 01ce | snr 0095 | ber  | unc fffe | 
FE_HAS_LOCK
status 1f | signal 01ce | snr 0094 | ber  | unc fffe | 
FE_HAS_LOCK
status 1f | signal 01ce | snr 0094 | ber  | unc fffe | 
FE_HAS_LOCK

wuwek:~# ls /dev/dvb/adapter0/
demux0 dvr0   frontend0  net0
wuwek:~# cat /dev/dvb/adapter0/dvr0  /mnt/video/test.ts
^C
wuwek:~# ls -l /mnt/video/test.ts
-rw-r--r-- 1 root root 0 lip  8 00:37 /mnt/video/test.ts
wuwek:~# dvbdate
dvbdate: Unable to get time from multiplex.
wuwek:~# dvbtraffic
dvbdemux_set_pid_filter: Invalid argument

I've tried to tune many different channels (log at the end), it works 
for many of them, some (all HD) doesn't work. I've used szap-s2 because 
szap doesn't work with DVB-S2 channels. For DVB-S channels szap produces 
results the same as szap-s2.
I've tried to save some different channels (as above) but none saved 
anything, so there is still something wrong with this driver.

Marx

kern.log:
Jul  8 00:16:29 wuwek kernel: [6.001815] input: HD-Audio Generic 
HDMI/DP,pcm=3 as /devices/pci:00/:00:01.1/sound/card0/input3
Jul  8 00:16:29 wuwek kernel: [6.066989] usb 1-4: dvb_usbv2: found a 
'PCTV HDTV USB' in warm state

Jul  8 00:16:29 wuwek kernel: [6.067002] pctv452e_power_ctrl: 1
Jul  8 00:16:29 wuwek kernel: [6.067007] pctv452e_power_ctrl: step 1
Jul  8 00:16:29 wuwek kernel: [6.067012] pctv452e_power_ctrl: step 2
Jul  8 00:16:29 wuwek kernel: [6.067559] pctv452e_power_ctrl: step 3
Jul  8 00:16:29 wuwek kernel: [6.067684] usbcore: registered new 
interface driver dvb_usb_pctv452e

Jul  8 00:16:29 wuwek kernel: [6.067745] pctv452e_power_ctrl: step 4
Jul  8 00:16:29 wuwek kernel: [6.067996] pctv452e_power_ctrl: step 5
Jul  8 00:16:29 wuwek kernel: [6.068113] usb 1-4: dvb_usbv2: will 
pass the complete MPEG2 transport stream to the software demuxer
Jul  8 00:16:29 wuwek kernel: [6.068175] DVB: registering new 
adapter (PCTV HDTV USB)
Jul  8 00:16:29 wuwek kernel: [6.117522] input: HDA ATI SB Line as 
/devices/pci:00/:00:14.2/sound/card1/input4
Jul  8 00:16:29 wuwek kernel: [6.117730] input: HDA ATI SB Rear Mic 
as /devices/pci:00/:00:14.2/sound/card1/input5
Jul  8 00:16:29 wuwek kernel: [6.118330] input: HDA ATI SB Line Out 
CLFE as /devices/pci:00/:00:14.2/sound/card1/input6
Jul  8 00:16:29 wuwek kernel: [6.118482] input: HDA ATI SB Line Out 
Surround as /devices/pci:00/:00:14.2/sound/card1/input7
Jul  8 00:16:29 wuwek kernel: [6.121096] input: HDA ATI SB Line Out 
Front as /devices/pci:00/:00:14.2/sound/card1/input8
Jul  8 00:16:29 wuwek kernel: [6.157236] stb0899_attach: Attaching 
STB0899
Jul  8 00:16:29 wuwek kernel: [6.182361] DVB: registering adapter 0 
frontend 0 (STB0899 Multistandard)...
Jul  8 00:16:29 wuwek kernel: [6.209194] stb6100_attach: Attaching 
STB6100

Jul  8 00:16:29 wuwek kernel: [6.209208] pctv452e_power_ctrl: 0
Jul  8 00:16:29 wuwek kernel: [6.209224] usb 1-4: dvb_usbv2: 'PCTV 
HDTV USB' successfully initialized and connected
Jul  8 00:16:29 wuwek kernel: [7.998317] Adding 2097148k swap on 
/dev/sda2.  Priority:-1 extents:1 across:2097148k

(...)
Jul  8 00:16:49 wuwek kernel: [   58.654218] pctv452e_power_ctrl: 1
Jul  8 00:16:49 wuwek kernel: [   58.654229] pctv452e_power_ctrl: step 1
Jul  8 00:27:05 wuwek kernel: [  674.833814] pctv452e_power_ctrl: 0
Jul  8 00:27:30 wuwek kernel: [  699.336350] pctv452e_power_ctrl: 1
Jul  8 00:27:30 wuwek kernel: [  699.336363] pctv452e_power_ctrl: step 1
Jul  8 00:28:08 wuwek kernel: [  737.552961] pctv452e_power_ctrl: 0


wuwek:/var/lib/vdr/kanaly# ./szap-s2 -n 2 -x -r
reading channels from file '/root/.szap/channels.conf'
zapping to 2 'TVN Turbo;TVN':
delivery DVB-S, modulation QPSK
sat 0, frequency 11393 MHz V, symbolrate 2750, coderate 5/6, rolloff 
0.35

vpid 0x0208, apid 0x02da, sid 0x0247
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
status 1f | signal 01ce | snr 008b | ber  | unc fffe

Re: pctv452e

[Marx]

On 05.07.2012 16:23, Antti Palosaari wrote:

Check if those modules are enabled, in file .config
CONFIG_DVB_USB_V2=m
CONFIG_DVB_USB_PCTV452E=m

use make menuconfig to enable if disabled. Then make  make
install_modules  make install as usually.


You were right, I didn't have this options anabled. I've enabled both 
via 'make menuconfig' and recompiled kernel. Driver loaded succesfully, 
I haven time to test only a few SD channels, and they were working, but 
some encrypted and HD didn't. I have to check yet why.


Anyway when using card logs are full of i2c errors

Jul  6 07:04:19 wuwek kernel: [6.087199] input: HDA ATI SB Line Out 
Front as /devices/pci:00/:00:14.2/sound/card

1/input8
Jul  6 07:04:19 wuwek kernel: [6.108046] stb6100_attach: Attaching 
STB6100

Jul  6 07:04:19 wuwek kernel: [6.108054] pctv452e_power_ctrl: 0
Jul  6 07:04:19 wuwek kernel: [6.108063] usb 1-4: dvb_usbv2: 'PCTV 
HDTV USB' successfully initialized and connected
Jul  6 07:04:19 wuwek kernel: [7.659462] Adding 2097148k swap on 
/dev/sda2.  Priority:-1 extents:1 across:2097148k
Jul  6 07:04:19 wuwek kernel: [7.707592] EXT4-fs (sda1): re-mounted. 
Opts: (null)


(...)

Jul  6 07:04:21 wuwek kernel: [   45.112483] Bluetooth: BNEP (Ethernet 
Emulation) ver 1.3
Jul  6 07:04:21 wuwek kernel: [   45.112496] Bluetooth: BNEP filters: 
protocol multicast

Jul  6 07:04:40 wuwek kernel: [   64.367411] pctv452e_power_ctrl: 1
Jul  6 07:04:48 wuwek kernel: [   72.693972] I2C error -121; AA 0B  CC 
00 01 - 55 0B  CC 00 00.
Jul  6 07:04:59 wuwek kernel: [   83.605643] I2C error -121; AA 49  CC 
00 01 - 55 49  CC 00 00.
Jul  6 07:05:10 wuwek kernel: [   94.565805] I2C error -121; AA EE  CC 
00 01 - 55 EE  CC 00 00.
Jul  6 07:05:10 wuwek kernel: [   94.578295] I2C error -121; AA 05  CC 
00 01 - 55 05  CC 00 00.
Jul  6 07:05:10 wuwek kernel: [   94.637539] I2C error -121; AA 20  CC 
00 01 - 55 20  CC 00 00.
Jul  6 07:05:18 wuwek kernel: [  102.525868] I2C error -121; AA 08  CC 
00 01 - 55 08  CC 00 00.
Jul  6 07:05:18 wuwek kernel: [  102.538359] I2C error -121; AA 1F  CC 
00 01 - 55 1F  CC 00 00.
Jul  6 07:05:18 wuwek kernel: [  102.597603] I2C error -121; AA 3A  CC 
00 01 - 55 3A  CC 00 00.
Jul  6 07:05:29 wuwek kernel: [  113.765372] I2C error -121; AA F5  CC 
00 01 - 55 F5  CC 00 00.
Jul  6 07:05:29 wuwek kernel: [  113.777986] I2C error -121; AA 0C  CC 
00 01 - 55 0C  CC 00 00.
Jul  6 07:05:29 wuwek kernel: [  113.837480] I2C error -121; AA 27  CC 
00 01 - 55 27  CC 00 00.
Jul  6 07:05:35 wuwek kernel: [  120.069153] I2C error -121; AA CF  CC 
00 01 - 55 CF  CC 00 00.
Jul  6 07:05:37 wuwek kernel: [  121.325610] I2C error -121; AA A7  CC 
00 01 - 55 A7  CC 00 00.
Jul  6 07:05:38 wuwek kernel: [  122.581565] I2C error -121; AA 7F  CC 
00 01 - 55 7F  CC 00 00.
Jul  6 07:05:39 wuwek kernel: [  123.841526] I2C error -121; AA 57  CC 
00 01 - 55 57  CC 00 00.
Jul  6 07:05:40 wuwek kernel: [  125.096979] I2C error -121; AA 2F  CC 
00 01 - 55 2F  CC 00 00.
Jul  6 07:05:42 wuwek kernel: [  126.353689] I2C error -121; AA 07  CC 
00 01 - 55 07  CC 00 00.



I will test tonight when I have more time
Marx

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[Antti Palosaari]

On 07/06/2012 09:13 AM, Marx wrote:

On 05.07.2012 16:23, Antti Palosaari wrote:

Check if those modules are enabled, in file .config
CONFIG_DVB_USB_V2=m
CONFIG_DVB_USB_PCTV452E=m

use make menuconfig to enable if disabled. Then make  make
install_modules  make install as usually.


You were right, I didn't have this options anabled. I've enabled both
via 'make menuconfig' and recompiled kernel. Driver loaded succesfully,
I haven time to test only a few SD channels, and they were working, but
some encrypted and HD didn't. I have to check yet why.


Did I missed something? PCTV device does not support CI/CAM and thus no 
support for encrypted channels. Is there still CI slot?



Anyway when using card logs are full of i2c errors


Argh! But this must be issue of earlier driver too.

I debug it and it seems to be totally clueless implementation of 
stb6100_read_reg() as it sets device address like device address + 
register address. This makes stb6100 I2C address of tuner set for that 
request 0x66 whilst it should be 0x60. Is that code never tested...


pctv452e DVB USB driver behaves just correctly as it says this is not 
valid and returns error.


Also pctv452e I2C adapter supports only I2C operations that are done 
with repeated STOP condition - but I cannot see there is logic to sent 
STOP after last message. I suspect it is not correct as logically but 
will work - very common mistake with many I2C adapters we have.



Jul  6 07:04:19 wuwek kernel: [6.087199] input: HDA ATI SB Line Out
Front as /devices/pci:00/:00:14.2/sound/card
1/input8
Jul  6 07:04:19 wuwek kernel: [6.108046] stb6100_attach: Attaching
STB6100
Jul  6 07:04:19 wuwek kernel: [6.108054] pctv452e_power_ctrl: 0
Jul  6 07:04:19 wuwek kernel: [6.108063] usb 1-4: dvb_usbv2: 'PCTV
HDTV USB' successfully initialized and connected
Jul  6 07:04:19 wuwek kernel: [7.659462] Adding 2097148k swap on
/dev/sda2.  Priority:-1 extents:1 across:2097148k
Jul  6 07:04:19 wuwek kernel: [7.707592] EXT4-fs (sda1): re-mounted.
Opts: (null)

(...)

Jul  6 07:04:21 wuwek kernel: [   45.112483] Bluetooth: BNEP (Ethernet
Emulation) ver 1.3
Jul  6 07:04:21 wuwek kernel: [   45.112496] Bluetooth: BNEP filters:
protocol multicast
Jul  6 07:04:40 wuwek kernel: [   64.367411] pctv452e_power_ctrl: 1
Jul  6 07:04:48 wuwek kernel: [   72.693972] I2C error -121; AA 0B  CC
00 01 - 55 0B  CC 00 00.
Jul  6 07:04:59 wuwek kernel: [   83.605643] I2C error -121; AA 49  CC
00 01 - 55 49  CC 00 00.
Jul  6 07:05:10 wuwek kernel: [   94.565805] I2C error -121; AA EE  CC
00 01 - 55 EE  CC 00 00.
Jul  6 07:05:10 wuwek kernel: [   94.578295] I2C error -121; AA 05  CC
00 01 - 55 05  CC 00 00.
Jul  6 07:05:10 wuwek kernel: [   94.637539] I2C error -121; AA 20  CC
00 01 - 55 20  CC 00 00.
Jul  6 07:05:18 wuwek kernel: [  102.525868] I2C error -121; AA 08  CC
00 01 - 55 08  CC 00 00.
Jul  6 07:05:18 wuwek kernel: [  102.538359] I2C error -121; AA 1F  CC
00 01 - 55 1F  CC 00 00.
Jul  6 07:05:18 wuwek kernel: [  102.597603] I2C error -121; AA 3A  CC
00 01 - 55 3A  CC 00 00.
Jul  6 07:05:29 wuwek kernel: [  113.765372] I2C error -121; AA F5  CC
00 01 - 55 F5  CC 00 00.
Jul  6 07:05:29 wuwek kernel: [  113.777986] I2C error -121; AA 0C  CC
00 01 - 55 0C  CC 00 00.
Jul  6 07:05:29 wuwek kernel: [  113.837480] I2C error -121; AA 27  CC
00 01 - 55 27  CC 00 00.
Jul  6 07:05:35 wuwek kernel: [  120.069153] I2C error -121; AA CF  CC
00 01 - 55 CF  CC 00 00.
Jul  6 07:05:37 wuwek kernel: [  121.325610] I2C error -121; AA A7  CC
00 01 - 55 A7  CC 00 00.
Jul  6 07:05:38 wuwek kernel: [  122.581565] I2C error -121; AA 7F  CC
00 01 - 55 7F  CC 00 00.
Jul  6 07:05:39 wuwek kernel: [  123.841526] I2C error -121; AA 57  CC
00 01 - 55 57  CC 00 00.
Jul  6 07:05:40 wuwek kernel: [  125.096979] I2C error -121; AA 2F  CC
00 01 - 55 2F  CC 00 00.
Jul  6 07:05:42 wuwek kernel: [  126.353689] I2C error -121; AA 07  CC
00 01 - 55 07  CC 00 00.


Regardless of those errors it still works?


I will test tonight when I have more time
Marx


regards
Antti

--
http://palosaari.fi/


--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[Marx]

On 06.07.2012 11:34, Antti Palosaari wrote:

Did I missed something? PCTV device does not support CI/CAM and thus no
support for encrypted channels. Is there still CI slot?


no, I simply use external reader with plugin in VDR. Unfortunetelly on 
Hotbird there is no unencrypted HD channel I can use to test.



Anyway when using card logs are full of i2c errors


Argh! But this must be issue of earlier driver too.


yes, those errors were in logs earlier on previous driver. Hovewer 
previous driver allowed to play only once or two time and then was 
stopping work. And i've never played successfully HD channel on this card.



I debug it and it seems to be totally clueless implementation of
stb6100_read_reg() as it sets device address like device address +
register address. This makes stb6100 I2C address of tuner set for that
request 0x66 whilst it should be 0x60. Is that code never tested...

pctv452e DVB USB driver behaves just correctly as it says this is not
valid and returns error.

Also pctv452e I2C adapter supports only I2C operations that are done
with repeated STOP condition - but I cannot see there is logic to sent
STOP after last message. I suspect it is not correct as logically but
will work - very common mistake with many I2C adapters we have.


I have second card in this computer
http://www.proftuners.com/prof8000.html
which uses STB6100 (and also STV0903 and CX23885).
I wasn't aware that both of this card uses the same chip (as I see from 
http://www.linuxtv.org/wiki/index.php/TechnoTrend_TT-connect_S2-3650_CI 
it uses STB6100 too).

Can it be a problem? Anyway i will take off this second card a test again.


Regardless of those errors it still works?


Thank you for help. I had only a few minutes at the morning to test it 
and it partly worked. More test are planned tonight and I will write 
here outcomes.


Marx

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[Antti Palosaari]

On 07/06/2012 02:04 PM, Marx wrote:

On 06.07.2012 11:34, Antti Palosaari wrote:

Did I missed something? PCTV device does not support CI/CAM and thus no
support for encrypted channels. Is there still CI slot?


no, I simply use external reader with plugin in VDR. Unfortunetelly on
Hotbird there is no unencrypted HD channel I can use to test.


From the driver / device perspective HD or SD channel does not have 
much difference - difference is just used video codec and likely wider 
stream. For demodulator driver perspective there could some difference 
as HD channels are more often transmitted using DVB-S2 standard - but 
not always.


Also as you are using SoftCAM there is no difference from driver POV if 
stream is encrypted or unencrypted. Device just moves bits from the 
antenna to the computer - it does not know if those bits are encrypted 
or not.



Anyway when using card logs are full of i2c errors


Argh! But this must be issue of earlier driver too.


yes, those errors were in logs earlier on previous driver. Hovewer
previous driver allowed to play only once or two time and then was
stopping work. And i've never played successfully HD channel on this card.


Could you say what was the original problem of your device?


I debug it and it seems to be totally clueless implementation of
stb6100_read_reg() as it sets device address like device address +
register address. This makes stb6100 I2C address of tuner set for that
request 0x66 whilst it should be 0x60. Is that code never tested...

pctv452e DVB USB driver behaves just correctly as it says this is not
valid and returns error.

Also pctv452e I2C adapter supports only I2C operations that are done
with repeated STOP condition - but I cannot see there is logic to sent
STOP after last message. I suspect it is not correct as logically but
will work - very common mistake with many I2C adapters we have.


Oops, s/repeated STOP condition/repeated START condition/


I have second card in this computer
http://www.proftuners.com/prof8000.html
which uses STB6100 (and also STV0903 and CX23885).
I wasn't aware that both of this card uses the same chip (as I see from
http://www.linuxtv.org/wiki/index.php/TechnoTrend_TT-connect_S2-3650_CI
it uses STB6100 too).
Can it be a problem? Anyway i will take off this second card a test again.


I never say it could not be problem, but it is highly unlikely. Anyhow 
it is possible there is some static variables inside driver that could 
have effect. But it is very very unlikely and those kind of shared 
variables should not exits without very good reason.



Regardless of those errors it still works?


Thank you for help. I had only a few minutes at the morning to test it
and it partly worked. More test are planned tonight and I will write
here outcomes.


Still waiting


regards
Antti

--
http://palosaari.fi/


--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[Marx]

Driver doesn't work good.
I've took out the second card, so there is only pctv452e connected.
It worked the same way as usually.
At first driver was playing some SD channels (encrypted and FTA - no 
matter), it even played one HD channel for the first time ever, but 
after it it refused to play any more channels. I've restarted computer, 
but it didn't help.


Logs from boot:
Jul  6 18:22:11 wuwek kernel: [5.948597] input: HD-Audio Generic 
HDMI/DP,pcm=3 as /devices/pci:00/:00:01.1/sound/card0/input3
Jul  6 18:22:11 wuwek kernel: [6.121534] input: HDA ATI SB Line as 
/devices/pci:00/:00:14.2/sound/card1/input4
Jul  6 18:22:11 wuwek kernel: [6.121770] input: HDA ATI SB Rear Mic 
as /devices/pci:00/:00:14.2/sound/card1/input5
Jul  6 18:22:11 wuwek kernel: [6.123094] input: HDA ATI SB Line Out 
CLFE as /devices/pci:00/:00:14.2/sound/card1/input6
Jul  6 18:22:11 wuwek kernel: [6.125812] input: HDA ATI SB Line Out 
Surround as /devices/pci:00/:00:14.2/sound/card1/input7
Jul  6 18:22:11 wuwek kernel: [6.126523] input: HDA ATI SB Line Out 
Front as /devices/pci:00/:00:14.2/sound/card1/input8
Jul  6 18:22:11 wuwek kernel: [6.276933] usb 1-4: dvb_usbv2: found a 
'PCTV HDTV USB' in warm state

Jul  6 18:22:11 wuwek kernel: [6.276945] pctv452e_power_ctrl: 1
Jul  6 18:22:11 wuwek kernel: [6.277544] usbcore: registered new 
interface driver dvb_usb_pctv452e
Jul  6 18:22:11 wuwek kernel: [6.278000] usb 1-4: dvb_usbv2: will 
pass the complete MPEG2 transport stream to the software demuxer
Jul  6 18:22:11 wuwek kernel: [6.278041] DVB: registering new 
adapter (PCTV HDTV USB)
Jul  6 18:22:11 wuwek kernel: [6.342525] stb0899_attach: Attaching 
STB0899
Jul  6 18:22:11 wuwek kernel: [6.375893] DVB: registering adapter 0 
frontend 0 (STB0899 Multistandard)...
ul  6 18:22:11 wuwek kernel: [6.399122] stb6100_attach: Attaching 
STB6100

Jul  6 18:22:11 wuwek kernel: [6.399137] pctv452e_power_ctrl: 0
Jul  6 18:22:11 wuwek kernel: [6.399152] usb 1-4: dvb_usbv2: 'PCTV 
HDTV USB' successfully initialized and connected
Jul  6 18:22:11 wuwek kernel: [7.959465] Adding 2097148k swap on 
/dev/sda2.  Priority:-1 extents:1 across:2097148k
Jul  6 18:22:11 wuwek kernel: [8.009082] EXT4-fs (sda1): re-mounted. 
Opts: (null)
Jul  6 18:22:11 wuwek kernel: [8.393422] EXT4-fs (sda1): re-mounted. 
Opts: errors=remount-ro

Jul  6 18:22:11 wuwek kernel: [8.507454] loop: module loaded
Jul  6 18:22:11 wuwek kernel: [8.535684] nf_conntrack version 0.5.0 
(16384 buckets, 65536 max)
Jul  6 18:22:11 wuwek kernel: [8.609385] w83627ehf: Found NCT6775F 
chip at 0x290
Jul  6 18:22:11 wuwek kernel: [8.609767] hwmon_vid: Unknown VRM 
version of your x86 CPU
Jul  6 18:22:11 wuwek kernel: [   10.634908] EXT4-fs (sda3): mounted 
filesystem with ordered data mode. Opts: errors=remount-ro
Jul  6 18:22:11 wuwek kernel: [   10.715194] EXT4-fs (sda4): mounted 
filesystem with ordered data mode. Opts: errors=remount-ro
Jul  6 18:22:11 wuwek kernel: [   13.602684] Netfilter messages via 
NETLINK v0.30.

Jul  6 18:22:11 wuwek kernel: [   13.782616] ip_set: protocol 6
Jul  6 18:22:11 wuwek kernel: [   15.613353] xt_nfacct: Unknown symbol 
nfnl_acct_put (err 0)
Jul  6 18:22:11 wuwek kernel: [   15.613451] xt_nfacct: Unknown symbol 
nfnl_acct_update (err 0)
Jul  6 18:22:11 wuwek kernel: [   15.613522] xt_nfacct: Unknown symbol 
nfnl_acct_find_get (err 0)
Jul  6 18:22:11 wuwek kernel: [   16.475299] xt_time: kernel timezone is 
+0200
Jul  6 18:22:11 wuwek kernel: [   20.154987] ip_tables: (C) 2000-2006 
Netfilter Core Team
Jul  6 18:22:11 wuwek kernel: [   21.228305] ip6_tables: (C) 2000-2006 
Netfilter Core Team

Jul  6 18:22:11 wuwek kernel: [   22.182152] Bridge firewalling registered
Jul  6 18:22:11 wuwek kernel: [   22.685996] r8169 :04:00.0: eth6: 
link down
Jul  6 18:22:11 wuwek kernel: [   22.686014] r8169 :04:00.0: eth6: 
link down
Jul  6 18:22:11 wuwek kernel: [   22.686366] IPv6: ADDRCONF(NETDEV_UP): 
eth6: link is not ready
Jul  6 18:22:11 wuwek kernel: [   34.686600] r8169 :04:00.0: eth6: 
link up
Jul  6 18:22:11 wuwek kernel: [   34.687111] IPv6: 
ADDRCONF(NETDEV_CHANGE): eth6: link becomes ready
Jul  6 18:22:11 wuwek kernel: [   41.261271] RPC: Registered named UNIX 
socket transport module.
Jul  6 18:22:11 wuwek kernel: [   41.261279] RPC: Registered udp 
transport module.
Jul  6 18:22:11 wuwek kernel: [   41.261282] RPC: Registered tcp 
transport module.
Jul  6 18:22:11 wuwek kernel: [   41.261284] RPC: Registered tcp NFSv4.1 
backchannel transport module.

Jul  6 18:22:11 wuwek kernel: [   41.308018] FS-Cache: Loaded
Jul  6 18:22:11 wuwek kernel: [   41.361383] NFS: Registering the 
id_resolver key type

Jul  6 18:22:11 wuwek kernel: [   41.361424] Key type id_resolver registered
Jul  6 18:22:11 wuwek kernel: [   41.361441] FS-Cache: Netfs 'nfs' 
registered for caching
Jul  6 18:22:11 wuwek kernel

Re: pctv452e

[Antti Palosaari]

On 07/07/2012 01:23 AM, Marx wrote:

Driver doesn't work good.
I've took out the second card, so there is only pctv452e connected.
It worked the same way as usually.
At first driver was playing some SD channels (encrypted and FTA - no
matter), it even played one HD channel for the first time ever, but
after it it refused to play any more channels. I've restarted computer,
but it didn't help.


Sounds bad. It should be always enough just remove device, boot and plug 
device back.



Jul  6 18:22:42 wuwek kernel: [   73.801143] I2C error -121; AA AE  CC
00 01 - 55 AE  CC 00 00.





HD channels desire better signal, but i'm sure signal is ok because it's
twin setup and on second port I have traditional tuner which works ok
with all channels.

Original problem - it's rather long story. To say it short: I have 4 DVB
tuners and none of them works reliable. I'm able to make each of them
recognized, scan channels etc. To concentrate on pctv452e: it works from
the beginning the same way as I've written above. It outputs endlessly
i2c errors, usually allows to switch 4-5 times channels and then it
stops working. What is strange - scan works, szap2 works on some
channels, on others doesn't work.


Those I2C errors coming from the bug I explained earlier. It could be 
also reason of all problems.



Let's get for example FTA channel Mango 24.
Mango 24;TVN:11393:v:S13.0E:27500:517=2:700=pol@4:581:0:4316:318:1000:0

wuwek:~# szap -n 51 -r
reading channels from file '/root/.szap/channels.conf'
zapping to 51 'Mango 24;TVN':
sat 0, frequency = 11393 MHz V, symbolrate 2750, vpid = 0x0205, apid
= 0x02bc sid = 0x0245
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
status 1f | signal 01c6 | snr 0095 | ber  | unc fffe |
FE_HAS_LOCK
status 1f | signal 01c6 | snr 0094 | ber  | unc fffe |
FE_HAS_LOCK
status 1f | signal 01c6 | snr 0095 | ber  | unc fffe |
FE_HAS_LOCK
status 1f | signal 01c6 | snr 0094 | ber  | unc fffe |
FE_HAS_LOCK


Seems to work fine.


but it doesn't now play in VDR.


You can use it only from application at the time. It is used by szap so 
vdr could not use it.



Unplug and plug again USB cable:
Jul  7 00:05:53 wuwek kernel: [20664.576589] pctv452e_power_ctrl: 0
Jul  7 00:06:08 wuwek kernel: [20679.752198] usb 1-4: USB disconnect,
device number 2
Jul  7 00:06:08 wuwek kernel: [20679.752728] usb 1-4: dvb_usbv2:
usb_bulk_msg() failed=-19
Jul  7 00:06:08 wuwek kernel: [20679.752779] I2C error -19; AA E6  10 04
00 - AA E6  10 04 00.
Jul  7 00:06:08 wuwek kernel: [20679.752876] usb 1-4: dvb_usbv2:
usb_bulk_msg() failed=-19
Jul  7 00:06:08 wuwek kernel: [20679.752909] I2C error -19; AA E7  D0 03
00 - AA E7  D0 03 00.


Nothing special, device is removed and ongoing control commands fails 
because no device.



Device isn't recognized. Again the same:

Jul  7 00:09:29 wuwek kernel: [20880.538582] INFO: task khubd:83 blocked
for more than 120 seconds.
Jul  7 00:09:29 wuwek kernel: [20880.538624] echo 0 
/proc/sys/kernel/hung_task_timeout_secs disables this message.
Jul  7 00:09:29 wuwek kernel: [20880.538669] khubd   D f72fe064
 083  2 0x
Jul  7 00:09:29 wuwek kernel: [20880.538683]  f5bf4180 0046 
f72fe064 c1115e10 f6e13208 c14989c0 c14989c0
Jul  7 00:09:29 wuwek kernel: [20880.538704]  f6d774c0 f71b1600 f6d774c0
f71b1608 f6d774c0 0282 f6cbe1e0 f71b1600
Jul  7 00:09:29 wuwek kernel: [20880.538723]  f6cbe1e0 f6d77540 0246
c12d22a6 0246 0246 c104408a 0002
Jul  7 00:09:29 wuwek kernel: [20880.538742] Call Trace:
Jul  7 00:09:29 wuwek kernel: [20880.538763]  [c1115e10] ?
remove_dir+0x20/0x25
Jul  7 00:09:29 wuwek kernel: [20880.538780]  [c12d22a6] ?
_raw_spin_lock_irqsave+0x11/0x30
Jul  7 00:09:29 wuwek kernel: [20880.538797]  [c104408a] ?
prepare_to_wait+0x57/0x5f
Jul  7 00:09:29 wuwek kernel: [20880.538880]  [f8542751] ?
dvb_dmxdev_release+0x5a/0xf0 [dvb_core]
Jul  7 00:09:29 wuwek kernel: [20880.538895]  [c1043f3e] ?
bit_waitqueue+0x47/0x47
Jul  7 00:09:29 wuwek kernel: [20880.538926]  [f84b46c1] ?
dvb_usb_adapter_dvb_exit+0x31/0x48 [dvb_usbv2]
Jul  7 00:09:29 wuwek kernel: [20880.538956]  [f84b5055] ?
dvb_usbv2_disconnect+0xc9/0x128 [dvb_usbv2]
Jul  7 00:09:29 wuwek kernel: [20880.539025]  [c1206845] ?
rpm_suspend+0x3ed/0x3ed
Jul  7 00:09:29 wuwek kernel: [20880.539038]  [c120721b] ?
pm_schedule_suspend+0x8e/0x8e
Jul  7 00:09:29 wuwek kernel: [20880.539113]  [f82564da] ?
usb_unbind_interface+0x46/0x106 [usbcore]
Jul  7 00:09:29 wuwek kernel: [20880.539147]  [c120070f] ?
__device_release_driver+0x60/0x97
Jul  7 00:09:29 wuwek kernel: [20880.539160]  [c120075b] ?
device_release_driver+0x15/0x1e
Jul  7 00:09:29 wuwek kernel: [20880.539173]  [c120020b] ?
bus_remove_device+0xa1/0xb0
Jul  7 00:09:29 wuwek kernel: [20880.539185]  [c11feb9a] ?
device_del+0xe6/0x130
Jul  7 00:09:29 wuwek kernel: [20880.539236]  [f8254d02] ?
usb_disable_device+0x56/0x13a [usbcore]
Jul  7 00:09:29 wuwek kernel

Re: pctv452e

[Antti Palosaari]

On 07/05/2012 04:14 PM, Marx wrote:

Maybe i did something wrong because I'm new to git, so below are steps i
followed to compile new driver set:
1) git clone git://linuxtv.org/anttip/media_tree.git
2) git checkout -b pctv452e origin/pctv452e
3) copy config file from 3.4 kernel
4) make menuconfig, check everything seems ok, quit  save
5) build kernel Debian way, and install it, reboot

wuwek:~# uname -a
Linux wuwek 3.5.0-rc5+ #1 SMP Thu Jul 5 09:22:36 CEST 2012 i686 GNU/Linux

wuwek:~# lsusb
Bus 001 Device 002: ID 2304:021f Pinnacle Systems, Inc. PCTV Sat HDTV
Pro BDA Device
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


wuwek:~/pctv/pctv452e/media_tree# ls /dev/dvb*
ls: nie ma dostępu do /dev/dvb*: Nie ma takiego pliku ani katalogu

So, while device is recognized, and a driver seems to recognize device,
there is no /dev/dvb* devices, so something went wrong.

What can I do more?

Marx

Ps. I'm attaching dmesg output. The second dvb card is internal Prof
Revolution 8000.


I didn't load whole driver. Test load it manually first using modprobe 
dvb_usb_pctv452e


Check if those modules are enabled, in file .config
CONFIG_DVB_USB_V2=m
CONFIG_DVB_USB_PCTV452E=m

use make menuconfig to enable if disabled. Then make  make 
install_modules  make install as usually.


regards
Antti


--
http://palosaari.fi/


--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[Marx]

On 04.07.2012 01:04, Antti Palosaari wrote:

Your claims about my DVB-USB-framework work is quite bullshit. I am not
going to convert all drivers to the new framework just doing compile
tests.


I'm not bashing you, I see you are doing very good job, and not only you 
but many people here. I don't like mess and refactoring is good thing. 
The problem is that often makers of hardware doesn't support their linux 
drivers and changes in DVB core doesn't help it.
Like with pctv452e - device was working, i've bought it as supported and 
now it works only partially.
I don't think there is easy solution to that problem. Card maker should 
support drivers but in reality we should be happy if he do any working 
driver for linux.


And thank you for modified driver, I will try it at home and of course 
will write how it is working.

Marx

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

re: pctv452e

[Steve Hill]

 Ps. Steve, could you please give me full version of kernel which
 works with pctv452e?

I think it was 2.6.37-1-kirkwood from Debian which I was using (this is 
an ARM system).


 As the new DVB-USB fixes many bugs I ask you to test it. I converted 
 pctv452e driver for you:


 http://git.linuxtv.org/anttip/media_tree.git/shortlog/refs/heads/pctv452e

 Only PCTV device supported currently, not TechnoTrend at that time.

Can I ask why it only works on the PCTV devices?  I was under the 
impression that the TechnoTrend hardware was identical?



If you are able to provide any pointers as to where the TechnoTrend 
support is broken (or what debugging I should be turning on to figure 
out where it is broken) then that would be helpful.


Thanks.

--

 - Steve

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[Antti Palosaari]

On 07/04/2012 07:04 PM, Steve Hill wrote:

  Ps. Steve, could you please give me full version of kernel which
  works with pctv452e?

I think it was 2.6.37-1-kirkwood from Debian which I was using (this is
an ARM system).

  As the new DVB-USB fixes many bugs I ask you to test it. I converted
  pctv452e driver for you:
 
 
http://git.linuxtv.org/anttip/media_tree.git/shortlog/refs/heads/pctv452e
 
  Only PCTV device supported currently, not TechnoTrend at that time.

Can I ask why it only works on the PCTV devices?  I was under the
impression that the TechnoTrend hardware was identical?


If you are able to provide any pointers as to where the TechnoTrend
support is broken (or what debugging I should be turning on to figure
out where it is broken) then that would be helpful.


I don't have hardware, no PCTV neither TechnoTrend. I just converted 
PCTV as Marx seems to have such device and he was blaming. Code wasn't 
100% similar, for example TechnoTrend has CI PCTV doesn't.


It should not fix problems but it could since I fixed some nasty bugs. 
Lets wait test report first and make decision what to do after that.


regards
Antti

--
http://palosaari.fi/


--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[Antti Palosaari]

On 07/04/2012 09:53 PM, André Weidemann wrote:

On 04.07.2012 18:22, Antti Palosaari wrote:

On 07/04/2012 07:04 PM, Steve Hill wrote:

  Ps. Steve, could you please give me full version of kernel which
  works with pctv452e?

I think it was 2.6.37-1-kirkwood from Debian which I was using (this is
an ARM system).

  As the new DVB-USB fixes many bugs I ask you to test it. I converted
  pctv452e driver for you:
 
 
http://git.linuxtv.org/anttip/media_tree.git/shortlog/refs/heads/pctv452e

 
  Only PCTV device supported currently, not TechnoTrend at that time.

Can I ask why it only works on the PCTV devices?  I was under the
impression that the TechnoTrend hardware was identical?


If you are able to provide any pointers as to where the TechnoTrend
support is broken (or what debugging I should be turning on to figure
out where it is broken) then that would be helpful.


I don't have hardware, no PCTV neither TechnoTrend. I just converted
PCTV as Marx seems to have such device and he was blaming. Code wasn't
100% similar, for example TechnoTrend has CI PCTV doesn't.

It should not fix problems but it could since I fixed some nasty bugs.
Lets wait test report first and make decision what to do after that.


The pctv452e and TT-connect S2-3600 are identical in hardware. Only USB
IDs and remote control codes differ between the two. The Pinnacle box
has its own remote. The TT-connect uses the same RC as the TT-budget
series.
The TT-connect S2-3650-CI has an additional CI slot.


OK. In addition to CI support and remote controller there was also 
.read_mac_address() callback implemented for TechnoTrend. But as 
.read_mac_address() is heavily optional and useless it could be possible 
driver author just left it unimplemented for PCTV - or PCTV does not has 
MAC address.


You seems to be marked as a one module author, I can guess you know reason?

Also if you has hardware, could you make some tests in order to get that 
driver fixed :]


regards
Antti

--
http://palosaari.fi/


--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[André Weidemann]

On 04.07.2012 18:22, Antti Palosaari wrote:

On 07/04/2012 07:04 PM, Steve Hill wrote:

  Ps. Steve, could you please give me full version of kernel which
  works with pctv452e?

I think it was 2.6.37-1-kirkwood from Debian which I was using (this is
an ARM system).

  As the new DVB-USB fixes many bugs I ask you to test it. I converted
  pctv452e driver for you:
 
 
http://git.linuxtv.org/anttip/media_tree.git/shortlog/refs/heads/pctv452e
 
  Only PCTV device supported currently, not TechnoTrend at that time.

Can I ask why it only works on the PCTV devices?  I was under the
impression that the TechnoTrend hardware was identical?


If you are able to provide any pointers as to where the TechnoTrend
support is broken (or what debugging I should be turning on to figure
out where it is broken) then that would be helpful.


I don't have hardware, no PCTV neither TechnoTrend. I just converted
PCTV as Marx seems to have such device and he was blaming. Code wasn't
100% similar, for example TechnoTrend has CI PCTV doesn't.

It should not fix problems but it could since I fixed some nasty bugs.
Lets wait test report first and make decision what to do after that.


The pctv452e and TT-connect S2-3600 are identical in hardware. Only USB 
IDs and remote control codes differ between the two. The Pinnacle box 
has its own remote. The TT-connect uses the same RC as the TT-budget series.

The TT-connect S2-3650-CI has an additional CI slot.

André

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[Marx]

W dniu 2012-07-04 18:22, Antti Palosaari pisze:

I don't have hardware, no PCTV neither TechnoTrend. I just converted
PCTV as Marx seems to have such device and he was blaming. Code wasn't
100% similar, for example TechnoTrend has CI PCTV doesn't.

It should not fix problems but it could since I fixed some nasty bugs.
Lets wait test report first and make decision what to do after that.


I've connected device and I'm starting to checkout from git and compiling.
Marx

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: pctv452e

[Antti Palosaari]

On 07/03/2012 10:46 AM, Marx wrote:

On 02.07.2012 18:33, Steve Hill wrote:

Can anyone give me any pointers that might help? I've searched and
searched and all I can see if people saying that it won't work since the
DVB-S2 code was integrated into the kernel tree, but I've not seen
anyone try to figure out _why_ it won't work.


I'm on the same boat.
I have 3 DVB-S2 cards, one of them is pctv452e, and none of them works
reliable. Yes, it's very frustrating that card which claims linux
support has this support broken. The problem is that community which
uses DVB cards is much smaller then those using other equipment. So
there are no test of every device in each kernel release.
I'm reading this list for some time and often see patches which refactor
some drivers, but the only check is compilation check.
totally rewritten DVB-USB-framework will not help to have more drivers
too. Makers of dvb cards often don't provide linux driver, or provide
only once in form of patches. You will not apply such patch into new DVB
stack. Makers must constantly refactor their drivers to suit new
kernels, and there are only a few which do this. I don't know why they
simply don't join this list and push drivers into kernel and then
provide support.
I don't know what's future of DVB stack, but I see that changes in DVB
stack causes meany problems with drivers. Often driver is written once
and later unsupported - changes make it non-functional and there is
nobody who can fix it. Exactly like with pctv452e driver.


Your claims about my DVB-USB-framework work is quite bullshit. I am not 
going to convert all drivers to the new framework just doing compile 
tests. I am heavily aware it is too risky thus I implemented it as a 
alternative, converting drivers one by one when you have hardware in 
hands to test. If such big changes were made to the existing code surely 
there is breakages.


And it fixes some existing DVB-USB bugs, actually all I was aware. Also 
it removes all the hacks, and also bugs coming those hacks, from many 
drivers. Most notable complex AF9015 and AF9035. See AF9015 before 
change and after change - code size is reduced something like 25% and 
binary size too.



Marx

Ps. Steve, could you please give me full version of kernel which works
with pctv452e?


As the new DVB-USB fixes many bugs I ask you to test it. I converted 
pctv452e driver for you:

http://git.linuxtv.org/anttip/media_tree.git/shortlog/refs/heads/pctv452e

Only PCTV device supported currently, not TechnoTrend at that time.


regards
Antti

--
http://palosaari.fi/


--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

pctv452e

[Steve Hill]

I've been using a Technotrend TT 3600 USB DVB-S2 receiver for a couple 
of years, which has (largely) been working fine under the S2-liplianin 
pctv452e driver.  I've been aware of a lot of documented problems with 
running this receiver under the 3.x kernel, so I've stuck with the 2.6 
series kernels.


Unfortunately I've now had to upgrade to the 3.2.0 kernel for other 
unrelated reasons, and it seems that the device is more or less unusable 
under this kernel.  With the stock 3.2.0 kernel, the driver produces 
numerous I2C errors and is quite unreliable.  The I2C errors seem to be 
produced exclusively as a result of stb_6100_read_reg() reading register 
F, and notably all calls to stb6100_read_regs() seem to succeed, so I've 
replaced the stb_6100_read_reg() function with a call to 
stb6100_read_regs(), so it reads all the registers and then returns the 
requested one, rather than reading just the requested register.  This 
seems to make the I2C errors disappear.


However, the card is still very unreliable - after about 5 minutes of 
receiving a channel (using MythTV), it breaks.  No errors logged in 
dmesg, but MythTV logs:


DevRdB(/dev/dvb/adapter0/frontend0) Error: Poll giving up
DVBSH(/dev/dvb/adapter0/frontend0) Error: Device error detected
DVBRec(7:/dev/dvb/adapter0/frontend0) Error: Stream handler died 
unexpectedly.



Can anyone give me any pointers that might help?  I've searched and 
searched and all I can see if people saying that it won't work since the 
DVB-S2 code was integrated into the kernel tree, but I've not seen 
anyone try to figure out _why_ it won't work.


Thanks.

--

 - Steve

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

pctv452e usb (Technotrend TT Connect S2-3600) DM1105N

[Joe Holden]

Hi guys,

Since updating to 3.3.1 from 3.2.x my DVB-S2 tuner has stopped working 
and seems to block when accessed:


[ 6182.111792] pctv452e: I2C error -110; AA 0F  D0 03 00 - AA 0F  D0 03 00.
[ 6182.419919] dvb-usb: error -110 while querying for an remote control 
event.
[ 6182.989972] dvb-usb: error -110 while querying for an remote control 
event.

[ 6184.170082] dvb-usb: bulk message failed: -110 (4/0)
[ 6184.185065] dvb-usb: error -110 while querying for an remote control 
event.
[ 6184.356753] dvb-usb: error -110 while querying for an remote control 
event.


The I2C errors were logged under 3.2 also but the card still worked.
Has anything substantanial changed? Can enable debug and/or ssh access 
if it would help diagnose the problem...


I also have a DM1105 based card that doesn't attach:

[ 1623.471563] DVB: registering new adapter (dm1105)
[ 1623.721678] dm1105 :00:0b.0: MAC 00:00:00:00:00:00
[ 1645.919891] si21xx: si21xx_attach
[ 1651.283255] si21xx: si21_readreg: readreg error (reg == 0x01, ret == -6)
[ 1656.653869] si21xx: si21_writereg: writereg error (reg == 0x01, data 
== 0x40, ret == -6)

[ 1662.223209] si21xx: si21_readreg: readreg error (reg == 0x00, ret == -6)
[ 1662.223235] dm1105 :00:0b.0: could not attach frontend

Any idea what I could do to find out whats wrong?

Thanks,
J
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

PCTV452e / S2-3600 displays I2C error

[Neil Sutton]

Hi all,

I'm not entirely sure if this is the correct list, but I compiled the
latest 3.2 RC3 kernel to get native support of my S2-3600 tuner
(s2-liplianin seems to cause trouble with my other tuner).

I enabled the PCTV452e module in the kernel and the device detects ok;

[   12.075239] dvb-usb: found a 'Technotrend TT Connect S2-3600' in warm state.
[   12.076620] dvb-usb: will pass the complete MPEG2 transport stream
to the software demuxer.
[   12.080767] dvb-usb: MAC address: 00:d0:5c:64:54:95
[   12.759115] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold
state, will try to load a firmware
[   13.298383] dvb-usb: Technotrend TT Connect S2-3600 successfully
initialized and connected.
[   13.464394] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw'
[   14.180319] dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state.
[   14.180429] dvb-usb: will pass the complete MPEG2 transport stream
to the software demuxer.
[   15.356117] dvb-usb: Hauppauge Nova-T Stick successfully
initialized and connected.
[   15.356832] usbcore: registered new interface driver dvb_usb_dib0700

But when I try to make any tuning with the device I get no picture and
the following get put to syslog;

Dec  2 01:01:26 MicroServer kernel: [ 1535.331468] dvb-usb: could not
submit URB no. 0 - get them all back
Dec  2 01:01:26 MicroServer kernel: [ 1535.372388] pctv452e: I2C error
-121; AA 97  CC 00 01 - 55 97  CC 00 00.
Dec  2 01:01:26 MicroServer kernel: [ 1535.385003] pctv452e: I2C error
-121; AA AE  CC 00 01 - 55 AE  CC 00 00.
Dec  2 01:01:26 MicroServer kernel: [ 1535.444992] pctv452e: I2C error
-121; AA C9  CC 00 01 - 55 C9  CC 00 00.
Dec  2 01:01:46 MicroServer kernel: [ 1555.665248] dvb-usb: could not
submit URB no. 0 - get them all back
Dec  2 01:01:46 MicroServer kernel: [ 1555.708805] pctv452e: I2C error
-121; AA 2E  CC 00 01 - 55 2E  CC 00 00.
Dec  2 01:01:46 MicroServer kernel: [ 1555.722046] pctv452e: I2C error
-121; AA 45  CC 00 01 - 55 45  CC 00 00.
Dec  2 01:01:46 MicroServer kernel: [ 1555.784543] pctv452e: I2C error
-121; AA 60  CC 00 01 - 55 60  CC 00 00.

The 'URB' errors appear each time the card moves to a new transponder,
the I2C errors appear to be when the card is attempting to lock a
channel within the current transponder.

Does anyone have any thoughts on what might be causing this ? - I've
had a search around but can't really find the problem mentioned
anywhere... the device works fine under the latest liplianin drivers.

Many Thanks
Neil
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] pctv452e: hm.. tidy bogus code up

[André Weidemann]

Hi Mauro,

On 30.09.2011 22:58, Igor M. Liplianin wrote:

Currently, usb_register calls two times with cloned structures, but for
different driver names. Let's remove it.


It looks like the comments and the patch under 
http://patchwork.linuxtv.org/patch/8042/ got mixed up.


Regards,
 André
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] pctv452e: hm.. tidy bogus code up

[Igor M. Liplianin]

В сообщении от 6 октября 2011 11:35:51 автор André Weidemann написал:
 Hi Mauro,
 
 On 30.09.2011 22:58, Igor M. Liplianin wrote:
  Currently, usb_register calls two times with cloned structures, but for
  different driver names. Let's remove it.
 
 It looks like the comments and the patch under
 http://patchwork.linuxtv.org/patch/8042/ got mixed up.
 
 Regards,
   André
git format-patch generated original in attachement.
-- 
Igor M. Liplianin
Microsoft Windows Free Zone - Linux used for all Computing Tasks
From 2e078ba46048c34b501174c5abc766a3bf812bb0 Mon Sep 17 00:00:00 2001
From: Igor M. Liplianin liplia...@me.by
Date: Fri, 30 Sep 2011 23:13:29 +0300
Subject: [PATCH] pctv452e: hm.. tidy bogus code up
To: mche...@infradead.org, linux-media@vger.kernel.org

Signed-off-by: Igor M. Liplianin liplia...@me.by
---
 drivers/media/dvb/dvb-usb/pctv452e.c |   16 +---
 1 files changed, 1 insertions(+), 15 deletions(-)

diff --git a/drivers/media/dvb/dvb-usb/pctv452e.c 
b/drivers/media/dvb/dvb-usb/pctv452e.c
index 9a5c811..f9aec5c 100644
--- a/drivers/media/dvb/dvb-usb/pctv452e.c
+++ b/drivers/media/dvb/dvb-usb/pctv452e.c
@@ -1012,7 +1012,7 @@ static struct dvb_usb_device_properties 
tt_connect_s2_3600_properties = {
 
.i2c_algo = pctv452e_i2c_algo,
 
-   .generic_bulk_ctrl_endpoint = 1, /* allow generice rw function*/
+   .generic_bulk_ctrl_endpoint = 1, /* allow generic rw function*/
 
.num_device_descs = 2,
.devices = {
@@ -1055,22 +1055,9 @@ static struct usb_driver pctv452e_usb_driver = {
.id_table   = pctv452e_usb_table,
 };
 
-static struct usb_driver tt_connects2_3600_usb_driver = {
-   .name   = dvb-usb-tt-connect-s2-3600-01.fw,
-   .probe  = pctv452e_usb_probe,
-   .disconnect = pctv452e_usb_disconnect,
-   .id_table   = pctv452e_usb_table,
-};
-
 static int __init pctv452e_usb_init(void)
 {
int ret = usb_register(pctv452e_usb_driver);
-
-   if (ret) {
-   err(%s: usb_register failed! Error %d, __FILE__, ret);
-   return ret;
-   }
-   ret = usb_register(tt_connects2_3600_usb_driver);
if (ret)
err(%s: usb_register failed! Error %d, __FILE__, ret);
 
@@ -1080,7 +1067,6 @@ static int __init pctv452e_usb_init(void)
 static void __exit pctv452e_usb_exit(void)
 {
usb_deregister(pctv452e_usb_driver);
-   usb_deregister(tt_connects2_3600_usb_driver);
 }
 
 module_init(pctv452e_usb_init);
-- 
1.7.5.1

Re: [PATCH] pctv452e: hm.. tidy bogus code up

[André Weidemann]

Hi Igor,

On 30.09.2011 22:58, Igor M. Liplianin wrote:

Currently, usb_register calls two times with cloned structures, but for
different driver names. Let's remove it.

Signed-off-by: Igor M. Liplianinliplia...@me.by


Well spotted... The cloned struct should have been removed a long time 
go. The final version of patch I submitted for the tt-connect S2-3600, 
did not contain it anymore: 
http://www.linuxtv.org/pipermail/linux-dvb/2008-March/024233.html


Acked-by: André Weideammandre.weidem...@web.de

Regards
 André
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] pctv452e: hm.. tidy bogus code up

[André Weidemann]

On 03.10.2011 14:30, André Weidemann wrote:

Hi Igor,

On 30.09.2011 22:58, Igor M. Liplianin wrote:

Currently, usb_register calls two times with cloned structures, but for
different driver names. Let's remove it.

Signed-off-by: Igor M. Liplianinliplia...@me.by


Well spotted... The cloned struct should have been removed a long time
go. The final version of patch I submitted for the tt-connect S2-3600,
did not contain it anymore:
http://www.linuxtv.org/pipermail/linux-dvb/2008-March/024233.html

Acked-by: André Weideammandre.weidem...@web.de


This should read:
Acked-by: André Weidemannandre.weidem...@web.de

;-)

Regards
 André
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[PATCH] pctv452e: hm.. tidy bogus code up

[Igor M. Liplianin]

Currently, usb_register calls two times with cloned structures, but for 
different driver names. Let's remove it.

Signed-off-by: Igor M. Liplianin liplia...@me.by
---
 drivers/media/dvb/dvb-usb/pctv452e.c |   16 +---
 1 files changed, 1 insertions(+), 15 deletions(-)

diff --git a/drivers/media/dvb/dvb-usb/pctv452e.c b/drivers/media/dvb/dvb-
usb/pctv452e.c
index 9a5c811..f9aec5c 100644
--- a/drivers/media/dvb/dvb-usb/pctv452e.c
+++ b/drivers/media/dvb/dvb-usb/pctv452e.c
@@ -1012,7 +1012,7 @@ static struct dvb_usb_device_properties 
tt_connect_s2_3600_properties = {
 
.i2c_algo = pctv452e_i2c_algo,
 
-   .generic_bulk_ctrl_endpoint = 1, /* allow generice rw function*/
+   .generic_bulk_ctrl_endpoint = 1, /* allow generic rw function*/
 
.num_device_descs = 2,
.devices = {
@@ -1055,22 +1055,9 @@ static struct usb_driver pctv452e_usb_driver = {
.id_table   = pctv452e_usb_table,
 };
 
-static struct usb_driver tt_connects2_3600_usb_driver = {
-   .name   = dvb-usb-tt-connect-s2-3600-01.fw,
-   .probe  = pctv452e_usb_probe,
-   .disconnect = pctv452e_usb_disconnect,
-   .id_table   = pctv452e_usb_table,
-};
-
 static int __init pctv452e_usb_init(void)
 {
int ret = usb_register(pctv452e_usb_driver);
-
-   if (ret) {
-   err(%s: usb_register failed! Error %d, __FILE__, ret);
-   return ret;
-   }
-   ret = usb_register(tt_connects2_3600_usb_driver);
if (ret)
err(%s: usb_register failed! Error %d, __FILE__, ret);
 
@@ -1080,7 +1067,6 @@ static int __init pctv452e_usb_init(void)
 static void __exit pctv452e_usb_exit(void)
 {
usb_deregister(pctv452e_usb_driver);
-   usb_deregister(tt_connects2_3600_usb_driver);
 }
 
 module_init(pctv452e_usb_init);
-- 
1.7.5.1

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] Add support for PCTV452E.

[Dominik Kuhlen]

Hi all,

sorry for being quiet such a long time

On Tuesday 13 September 2011 08:04:51 Steffen Barszus wrote:
 On Wed, 15 Jun 2011 18:44:35 +0300
 Igor M. Liplianin liplia...@me.by wrote:
 
  From my point of view we can count the beginning was here:
  
  http://www.spinics.net/lists/linux-dvb/msg26431.html
  
  The later history is difficult to restore, but possible.
 
 
 After some searching it looks like this is the first occurrence of the
 driver:
 http://www.linuxtv.org/pipermail/linux-dvb/2007-October/021403.html
 
 Further it looks like Dominik Kuhlen is not responding at that mail (as
 he has been on copy on one of the last mails. 
 
 So looks like we cant get the signed-off-by from him. 
Where do you want me to put that line?
Although I cannot test the current code atm I trust the other testers and 
I'd like to see it included in the main tree. Improvements can still be added 
later...

Dominik
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] Add support for PCTV452E.

[Igor M. Liplianin]

В сообщении от 27 сентября 2011 10:55:11 автор Dominik Kuhlen написал:
 Hi all,
 
 sorry for being quiet such a long time
 
 On Tuesday 13 September 2011 08:04:51 Steffen Barszus wrote:
  On Wed, 15 Jun 2011 18:44:35 +0300
  
  Igor M. Liplianin liplia...@me.by wrote:
   From my point of view we can count the beginning was here:
   
   http://www.spinics.net/lists/linux-dvb/msg26431.html
   
   The later history is difficult to restore, but possible.
  
  After some searching it looks like this is the first occurrence of the
  driver:
  http://www.linuxtv.org/pipermail/linux-dvb/2007-October/021403.html
  
  Further it looks like Dominik Kuhlen is not responding at that mail (as
  he has been on copy on one of the last mails.
  
  So looks like we cant get the signed-off-by from him.
 
 Where do you want me to put that line?
 Although I cannot test the current code atm I trust the other testers and
 I'd like to see it included in the main tree. Improvements can still be
 added later...
 
 Dominik
Welcome, Dominik!

Igor
-- 
Igor M. Liplianin
Microsoft Windows Free Zone - Linux used for all Computing Tasks
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] Add support for PCTV452E.

[Mauro Carvalho Chehab]

Em 27-09-2011 04:55, Dominik Kuhlen escreveu:
 Hi all,
 
 sorry for being quiet such a long time
 
 On Tuesday 13 September 2011 08:04:51 Steffen Barszus wrote:
 On Wed, 15 Jun 2011 18:44:35 +0300
 Igor M. Liplianin liplia...@me.by wrote:

 From my point of view we can count the beginning was here:

 http://www.spinics.net/lists/linux-dvb/msg26431.html

 The later history is difficult to restore, but possible.


 After some searching it looks like this is the first occurrence of the
 driver:
 http://www.linuxtv.org/pipermail/linux-dvb/2007-October/021403.html

 Further it looks like Dominik Kuhlen is not responding at that mail (as
 he has been on copy on one of the last mails. 

 So looks like we cant get the signed-off-by from him. 
 Where do you want me to put that line?
 Although I cannot test the current code atm I trust the other testers and 
 I'd like to see it included in the main tree. Improvements can still be added 
 later...

Just reply to this thread with your Signed-off-by: and I'll add it when 
submitting
the patch upstream.

Thank you!
Mauro
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] Add support for PCTV452E.

[Igor M. Liplianin]

Here is my version.
Made with git format-patch for branch staging/for_v3.2
From cc44ac937f36ed51335eb11a7e28cf047a979a1c Mon Sep 17 00:00:00 2001
From: Igor M. Liplianin liplia...@me.by
Date: Fri, 23 Sep 2011 23:31:25 +0300
Subject: [PATCH] Add support for pctv452e
To: mche...@infradead.org, linux-media@vger.kernel.org

Signed-off-by: Igor M. Liplianin liplia...@me.by
---
 drivers/media/dvb/dvb-usb/Kconfig   |   13 +
 drivers/media/dvb/dvb-usb/Makefile  |4 +
 drivers/media/dvb/dvb-usb/dvb-usb-ids.h |3 +
 drivers/media/dvb/dvb-usb/pctv452e.c| 1182 +++
 drivers/media/dvb/frontends/Kconfig |   10 +
 drivers/media/dvb/frontends/Makefile|1 +
 drivers/media/dvb/frontends/lnbp22.c|  148 
 drivers/media/dvb/frontends/lnbp22.h|   57 ++
 drivers/media/dvb/ttpci/ttpci-eeprom.c  |   29 +
 drivers/media/dvb/ttpci/ttpci-eeprom.h  |1 +
 10 files changed, 1448 insertions(+), 0 deletions(-)
 create mode 100644 drivers/media/dvb/dvb-usb/pctv452e.c
 create mode 100644 drivers/media/dvb/frontends/lnbp22.c
 create mode 100644 drivers/media/dvb/frontends/lnbp22.h

diff --git a/drivers/media/dvb/dvb-usb/Kconfig b/drivers/media/dvb/dvb-usb/Kconfig
index 2c773827..5825716 100644
--- a/drivers/media/dvb/dvb-usb/Kconfig
+++ b/drivers/media/dvb/dvb-usb/Kconfig
@@ -258,6 +258,19 @@ config DVB_USB_AF9005_REMOTE
 	  Say Y here to support the default remote control decoding for the
 	  Afatech AF9005 based receiver.
 
+config DVB_USB_PCTV452E
+	tristate Pinnacle PCTV HDTV Pro USB device/TT Connect S2-3600
+	depends on DVB_USB
+	select TTPCI_EEPROM
+	select DVB_LNBP22 if !DVB_FE_CUSTOMISE
+	select DVB_STB0899 if !DVB_FE_CUSTOMISE
+	select DVB_STB6100 if !DVB_FE_CUSTOMISE
+	help
+	  Support for external USB adapter designed by Pinnacle,
+	  shipped under the brand name 'PCTV HDTV Pro USB'.
+	  Also supports TT Connect S2-3600/3650 cards.
+	  Say Y if you own such a device and want to use it.
+
 config DVB_USB_DW2102
 	tristate DvbWorld  TeVii DVB-S/S2 USB2.0 support
 	depends on DVB_USB
diff --git a/drivers/media/dvb/dvb-usb/Makefile b/drivers/media/dvb/dvb-usb/Makefile
index 06f75f6..7d0710b 100644
--- a/drivers/media/dvb/dvb-usb/Makefile
+++ b/drivers/media/dvb/dvb-usb/Makefile
@@ -64,6 +64,9 @@ obj-$(CONFIG_DVB_USB_AF9005_REMOTE) += dvb-usb-af9005-remote.o
 dvb-usb-anysee-objs = anysee.o
 obj-$(CONFIG_DVB_USB_ANYSEE) += dvb-usb-anysee.o
 
+dvb-usb-pctv452e-objs = pctv452e.o
+obj-$(CONFIG_DVB_USB_PCTV452E) += dvb-usb-pctv452e.o
+
 dvb-usb-dw2102-objs = dw2102.o
 obj-$(CONFIG_DVB_USB_DW2102) += dvb-usb-dw2102.o
 
@@ -104,4 +107,5 @@ obj-$(CONFIG_DVB_USB_MXL111SF) += mxl111sf-tuner.o
 ccflags-y += -Idrivers/media/dvb/dvb-core/ -Idrivers/media/dvb/frontends/
 # due to tuner-xc3028
 ccflags-y += -Idrivers/media/common/tuners
+EXTRA_CFLAGS += -Idrivers/media/dvb/ttpci
 
diff --git a/drivers/media/dvb/dvb-usb/dvb-usb-ids.h b/drivers/media/dvb/dvb-usb/dvb-usb-ids.h
index 7433261..2ad33ba 100644
--- a/drivers/media/dvb/dvb-usb/dvb-usb-ids.h
+++ b/drivers/media/dvb/dvb-usb/dvb-usb-ids.h
@@ -241,6 +241,9 @@
 #define USB_PID_PCTV_200E0x020e
 #define USB_PID_PCTV_400E0x020f
 #define USB_PID_PCTV_450E0x0222
+#define USB_PID_PCTV_452E0x021f
+#define USB_PID_TECHNOTREND_CONNECT_S2_3600		0x3007
+#define USB_PID_TECHNOTREND_CONNECT_S2_3650_CI		0x300a
 #define USB_PID_NEBULA_DIGITV0x0201
 #define USB_PID_DVICO_BLUEBIRD_LGDT			0xd820
 #define USB_PID_DVICO_BLUEBIRD_LG064F_COLD		0xd500
diff --git a/drivers/media/dvb/dvb-usb/pctv452e.c b/drivers/media/dvb/dvb-usb/pctv452e.c
new file mode 100644
index 000..6151b3e
--- /dev/null
+++ b/drivers/media/dvb/dvb-usb/pctv452e.c
@@ -0,0 +1,1182 @@
+/*
+ * PCTV 452e DVB driver
+ *
+ * Copyright (c) 2006-2008 Dominik Kuhlen dkuh...@gmx.net
+ *
+ * TT connect S2-3650-CI Common Interface support, MAC readout
+ * Copyright (C) 2008 Michael H. Schimek mschi...@gmx.at
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License as
+ * published by the Free Software Foundation; either version 2 of
+ * the License, or (at your option) any later version.
+ */
+
+/* dvb usb framework */
+#define DVB_USB_LOG_PREFIX pctv452e
+#include dvb-usb.h
+
+/* Demodulator */
+#include stb0899_drv.h
+#include stb0899_reg.h
+#include stb0899_cfg.h
+/* Tuner */
+#include stb6100.h
+#include stb6100_cfg.h
+/* FE Power */
+#include lnbp22.h
+
+#include dvb_ca_en50221.h
+#include ttpci-eeprom.h
+
+static int debug;
+module_param(debug, int, 0644);
+MODULE_PARM_DESC(debug, Turn on/off debugging (default:off).);
+
+DVB_DEFINE_MOD_OPT_ADAPTER_NR(adapter_nr);
+
+#define ISO_BUF_COUNT  4
+#define FRAMES_PER_ISO_BUF 4
+#define ISO_FRAME_SIZE 940
+#define ISOC_INTERFACE_ALTERNATIVE 3
+
+#define SYNC_BYTE_OUT 0xaa
+#define SYNC_BYTE_IN  0x55
+
+/* guessed: (copied from ttusb-budget) */
+#define PCTV_CMD_RESET 0x15
+/* command to poll IR receiver */
+#define PCTV_CMD_IR

Re: [PATCH] Add support for PCTV452E.

[Igor M. Liplianin]

В сообщении от 23 сентября 2011 23:58:15 автор Oliver Freyermuth написал:
 Thanks for the review!
 
 As this is the first time I touched module- / kernel-code and I am not
 really familiar with the structures of the rc-system, I do not really
 feel up to porting to non-legacy rc-support (Igors version also appears
 to use rc-legacy), and up to now, it was only combining patches and
 fixing small glitches for me.
 However, feel free to use me as a tester (I have the hardware available,
 after all) or flood me with links to guidelines or further instructions.
 
 Thanks again,
  Oliver Freyermuth


Note, this patch is good for testing with media_build system. Just in case 
someone want not to load ~500 Mb kernel git tree, then configure, compile, 
install vmlinuz and so on, so on.

-- 
Igor M. Liplianin
Microsoft Windows Free Zone - Linux used for all Computing Tasks
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] Add support for PCTV452E.

[Igor M. Liplianin]

В сообщении от 24 сентября 2011 00:11:21 автор Igor M. Liplianin написал:
 В сообщении от 23 сентября 2011 23:58:15 автор Oliver Freyermuth написал:
  Thanks for the review!
  
  As this is the first time I touched module- / kernel-code and I am not
  really familiar with the structures of the rc-system, I do not really
  feel up to porting to non-legacy rc-support (Igors version also appears
  to use rc-legacy), and up to now, it was only combining patches and
  fixing small glitches for me.
  However, feel free to use me as a tester (I have the hardware available,
  after all) or flood me with links to guidelines or further instructions.
  
  Thanks again,
  
   Oliver Freyermuth
 
 Note, this patch is good for testing with media_build system. Just in case
 someone want not to load ~500 Mb kernel git tree, then configure, compile,
 install vmlinuz and so on, so on.
Sorry, wrong patch, forget to amend. This patch.
-- 
Igor M. Liplianin
Microsoft Windows Free Zone - Linux used for all Computing Tasks
From ae2acc4401230c17b68f74f806501de5d710a386 Mon Sep 17 00:00:00 2001
From: Igor M. Liplianin liplia...@me.by
Date: Sat, 24 Sep 2011 00:33:50 +0300
Subject: [PATCH] Add support for pctv452e
To: mche...@infradead.org, linux-media@vger.kernel.org

Signed-off-by: Igor M. Liplianin liplia...@me.by
---
 drivers/media/dvb/dvb-usb/Kconfig   |   13 +
 drivers/media/dvb/dvb-usb/Makefile  |4 +
 drivers/media/dvb/dvb-usb/dvb-usb-ids.h |3 +
 drivers/media/dvb/dvb-usb/pctv452e.c| 1093 +++
 drivers/media/dvb/frontends/Kconfig |   10 +
 drivers/media/dvb/frontends/Makefile|1 +
 drivers/media/dvb/frontends/lnbp22.c|  148 +
 drivers/media/dvb/frontends/lnbp22.h|   57 ++
 drivers/media/dvb/ttpci/ttpci-eeprom.c  |   29 +
 drivers/media/dvb/ttpci/ttpci-eeprom.h  |1 +
 10 files changed, 1359 insertions(+), 0 deletions(-)
 create mode 100644 drivers/media/dvb/dvb-usb/pctv452e.c
 create mode 100644 drivers/media/dvb/frontends/lnbp22.c
 create mode 100644 drivers/media/dvb/frontends/lnbp22.h

diff --git a/drivers/media/dvb/dvb-usb/Kconfig b/drivers/media/dvb/dvb-usb/Kconfig
index 2c773827..5825716 100644
--- a/drivers/media/dvb/dvb-usb/Kconfig
+++ b/drivers/media/dvb/dvb-usb/Kconfig
@@ -258,6 +258,19 @@ config DVB_USB_AF9005_REMOTE
 	  Say Y here to support the default remote control decoding for the
 	  Afatech AF9005 based receiver.
 
+config DVB_USB_PCTV452E
+	tristate Pinnacle PCTV HDTV Pro USB device/TT Connect S2-3600
+	depends on DVB_USB
+	select TTPCI_EEPROM
+	select DVB_LNBP22 if !DVB_FE_CUSTOMISE
+	select DVB_STB0899 if !DVB_FE_CUSTOMISE
+	select DVB_STB6100 if !DVB_FE_CUSTOMISE
+	help
+	  Support for external USB adapter designed by Pinnacle,
+	  shipped under the brand name 'PCTV HDTV Pro USB'.
+	  Also supports TT Connect S2-3600/3650 cards.
+	  Say Y if you own such a device and want to use it.
+
 config DVB_USB_DW2102
 	tristate DvbWorld  TeVii DVB-S/S2 USB2.0 support
 	depends on DVB_USB
diff --git a/drivers/media/dvb/dvb-usb/Makefile b/drivers/media/dvb/dvb-usb/Makefile
index 06f75f6..7d0710b 100644
--- a/drivers/media/dvb/dvb-usb/Makefile
+++ b/drivers/media/dvb/dvb-usb/Makefile
@@ -64,6 +64,9 @@ obj-$(CONFIG_DVB_USB_AF9005_REMOTE) += dvb-usb-af9005-remote.o
 dvb-usb-anysee-objs = anysee.o
 obj-$(CONFIG_DVB_USB_ANYSEE) += dvb-usb-anysee.o
 
+dvb-usb-pctv452e-objs = pctv452e.o
+obj-$(CONFIG_DVB_USB_PCTV452E) += dvb-usb-pctv452e.o
+
 dvb-usb-dw2102-objs = dw2102.o
 obj-$(CONFIG_DVB_USB_DW2102) += dvb-usb-dw2102.o
 
@@ -104,4 +107,5 @@ obj-$(CONFIG_DVB_USB_MXL111SF) += mxl111sf-tuner.o
 ccflags-y += -Idrivers/media/dvb/dvb-core/ -Idrivers/media/dvb/frontends/
 # due to tuner-xc3028
 ccflags-y += -Idrivers/media/common/tuners
+EXTRA_CFLAGS += -Idrivers/media/dvb/ttpci
 
diff --git a/drivers/media/dvb/dvb-usb/dvb-usb-ids.h b/drivers/media/dvb/dvb-usb/dvb-usb-ids.h
index 7433261..2ad33ba 100644
--- a/drivers/media/dvb/dvb-usb/dvb-usb-ids.h
+++ b/drivers/media/dvb/dvb-usb/dvb-usb-ids.h
@@ -241,6 +241,9 @@
 #define USB_PID_PCTV_200E0x020e
 #define USB_PID_PCTV_400E0x020f
 #define USB_PID_PCTV_450E0x0222
+#define USB_PID_PCTV_452E0x021f
+#define USB_PID_TECHNOTREND_CONNECT_S2_3600		0x3007
+#define USB_PID_TECHNOTREND_CONNECT_S2_3650_CI		0x300a
 #define USB_PID_NEBULA_DIGITV0x0201
 #define USB_PID_DVICO_BLUEBIRD_LGDT			0xd820
 #define USB_PID_DVICO_BLUEBIRD_LG064F_COLD		0xd500
diff --git a/drivers/media/dvb/dvb-usb/pctv452e.c b/drivers/media/dvb/dvb-usb/pctv452e.c
new file mode 100644
index 000..9a5c811
--- /dev/null
+++ b/drivers/media/dvb/dvb-usb/pctv452e.c
@@ -0,0 +1,1093 @@
+/*
+ * PCTV 452e DVB driver
+ *
+ * Copyright (c) 2006-2008 Dominik Kuhlen dkuh...@gmx.net
+ *
+ * TT connect S2-3650-CI Common Interface support, MAC readout
+ * Copyright (C) 2008 Michael H. Schimek mschi...@gmx.at
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public

Re: [PATCH] Add support for PCTV452E.

[Steffen Barszus]

On Wed, 15 Jun 2011 18:44:35 +0300
Igor M. Liplianin liplia...@me.by wrote:

 From my point of view we can count the beginning was here:
 
 http://www.spinics.net/lists/linux-dvb/msg26431.html
 
 The later history is difficult to restore, but possible.


After some searching it looks like this is the first occurrence of the
driver:
http://www.linuxtv.org/pipermail/linux-dvb/2007-October/021403.html

Further it looks like Dominik Kuhlen is not responding at that mail (as
he has been on copy on one of the last mails. 

So looks like we cant get the signed-off-by from him. 

Does that mean the patch can't be applied and needs to be rewritten
from scratch even if the author put the code under GPL2 back then ? Is
there any rule for this ?

See comment of  Oliver Freyermuth - the driver seems to work (after
altering it to make it work with current kernel), also got some postive
feedback for it for kernel 2.6.38 and current 3.2 media_tree. 

Does someone have a definitive answer on how to go ahead ? What else is
missing ?

Thanks :) 

Steffen

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] Add support for PCTV452E.

[Oliver Freyermuth]

Am 23.07.2011 13:24, schrieb Steffen Barszus:
  On Tue, 24 May 2011 21:51:22 +0200
  Hans Petter Selasky hsela...@c2i.net wrote:
 
  NOTES:
 
  Sources were taken from the following repositorium as of today:
  http://mercurial.intuxication.org/hg/s2-liplianin/
 
  And depend on the zig-zag fix posted today.
 
  Did a first test on the patch.
  [   96.780040] usb 1-8: new high speed USB device using ehci_hcd and
address 5
  [   97.376058] dvb_usb_pctv452e: Unknown symbol
ttpci_eeprom_decode_mac (err 0)
 
Same here.

  Looks like this patch didn't make it into patchwork - Mauro can you
  check that ?
 
 
  I think the patch for ttpci-eeprom.c is missing this:
 
  --- linux/drivers/media/dvb/ttpci/ttpci-eeprom.c.orig   2011-07-23
11:00:49.0 +
  +++ linux/drivers/media/dvb/ttpci/ttpci-eeprom.c2011-07-23
11:04:00.0 +
  @@ -165,6 +165,7 @@ int ttpci_eeprom_parse_mac(struct i2c_ad
   }
 
   EXPORT_SYMBOL(ttpci_eeprom_parse_mac);
  +EXPORT_SYMBOL(ttpci_eeprom_decode_mac);
 
   MODULE_LICENSE(GPL);
   MODULE_AUTHOR(Ralph Metzler, Marcus Metzler, others);
This patch indeed fixed it for me.
Module now loads, detects the card and appears to be successful.

However, when I try to tune, syslog shows:
Jul 29 02:46:00 sandy kernel: [  122.986314] pctv452e_power_ctrl: 1
Jul 29 02:46:01 sandy kernel: [  124.041037] pctv452e: I2C error -121;
AA 31  CC 00 01 - 55 31  CC 00 00.
Jul 29 02:46:01 sandy kernel: [  124.056408] pctv452e: I2C error -121;
AA 48  CC 00 01 - 55 48  CC 00 00.
Jul 29 02:46:01 sandy kernel: [  124.100998] pctv452e: I2C error -121;
AA 63  CC 00 01 - 55 63  CC 00 00.
[...cut...]
Jul 29 02:46:30 sandy kernel: [  153.265552] pctv452e: I2C error -121;
AA 95  CC 00 01 - 55 95  CC 00 00.
Jul 29 02:46:31 sandy kernel: [  153.812108] pctv452e_power_ctrl: 0

Tuning is not possible here (Kernel 3.0 in use).
Anybody with the same issue?

Reference for the 'normal' users who just want to use their card:
I have now downgraded to 2.6.38 again on my Sandy Bridge board
(sacrificing working reboot...) for s2liplianin does not like
bkl-removal in 2.6.39 and definitely no 3.0-tree.

s2liplianin on 2.6.38 works perfectly with this card. It also has much
better support for my other az6027 than the in-tree-modules (still, no
signal for any DVB-S2 with the az6027).

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] Add support for PCTV452E.

[Steffen Barszus]

On Tue, 24 May 2011 21:51:22 +0200
Hans Petter Selasky hsela...@c2i.net wrote:

 NOTES:
 
 Sources were taken from the following repositorium as of today:
 http://mercurial.intuxication.org/hg/s2-liplianin/
 
 And depend on the zig-zag fix posted today.

Did a first test on the patch. 
[   96.780040] usb 1-8: new high speed USB device using ehci_hcd and address 5
[   97.376058] dvb_usb_pctv452e: Unknown symbol ttpci_eeprom_decode_mac (err 0)

Looks like this patch didn't make it into patchwork - Mauro can you
check that ?


I think the patch for ttpci-eeprom.c is missing this: 

--- linux/drivers/media/dvb/ttpci/ttpci-eeprom.c.orig   2011-07-23 
11:00:49.0 +
+++ linux/drivers/media/dvb/ttpci/ttpci-eeprom.c2011-07-23 
11:04:00.0 +
@@ -165,6 +165,7 @@ int ttpci_eeprom_parse_mac(struct i2c_ad
 }
 
 EXPORT_SYMBOL(ttpci_eeprom_parse_mac);
+EXPORT_SYMBOL(ttpci_eeprom_decode_mac);
 
 MODULE_LICENSE(GPL);
 MODULE_AUTHOR(Ralph Metzler, Marcus Metzler, others);
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] Add support for PCTV452E.

[Igor M. Liplianin]

From my point of view we can count the beginning was here:

http://www.spinics.net/lists/linux-dvb/msg26431.html

The later history is difficult to restore, but possible.

BR
Igor
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] Add support for PCTV452E.

[Doychin Dokov]

The same thing happens when the devices are on different USB buses:
Bus 002 Device 004: ID 0b48:300a TechnoTrend AG TT-connect S2-3650 CI
Bus 001 Device 007: ID 0b48:3006 TechnoTrend AG TT-connect S-2400 DVB-S
Bus 001 Device 004: ID 734c:5980 TBS Technologies China

When the S2-3650 CI scans, the stream output from the TBS is gone. When 
it's done scanning / locking, the TBS continues to work fine. The S-2400 
is not affected in any way, nor it affects the other receivers.


It seems the issue is not relative to the devices being on the same USB 
bus, nor the kernel used. I've tried Debian's 2.6.32.5 and 2.6.38-bpo2 
on a Debian Squeeze system.


На 11.6.2011 г. 19:38 ч., Doychin Dokov написа:

i've been using the patches in the latest media_tree for some hours -
the S2-3650 CI seems to work. There's one thing that disturbs me, though
- when it scans / locks on a frequency, another device on the same PC,
using the same stb6100, gets stuck for a moment. Any ideas what might be
the cause for that? The two devices do not share common RF input signal,
but are on the same USB bus:
Bus 001 Device 004: ID 734c:5980 TBS Technologies China
Bus 001 Device 003: ID 0b48:300a TechnoTrend AG TT-connect S2-3650 CI

The TBS device is a QBOX2 SI, which works with their official driver
from their web-site.

There's also a third DVB device in the system - a TT S-2400 (which is on
the other USB bus, though), which does not exhibit any problems related
with the first two devices, nor causes them to get stuck when it's
scanning.

I'll try to switch devices around and see if anything changes.



--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] Add support for PCTV452E.

[Doychin Dokov]

On 2.6.32.5 with s2-liplianin tree this is not observed, i.e. everything
works as expected - the S2-3650 does not cause the TBS device to stutter.

На 12.6.2011 г. 23:27 ч., Doychin Dokov написа:

The same thing happens when the devices are on different USB buses:
Bus 002 Device 004: ID 0b48:300a TechnoTrend AG TT-connect S2-3650 CI
Bus 001 Device 007: ID 0b48:3006 TechnoTrend AG TT-connect S-2400 DVB-S
Bus 001 Device 004: ID 734c:5980 TBS Technologies China

When the S2-3650 CI scans, the stream output from the TBS is gone. When
it's done scanning / locking, the TBS continues to work fine. The S-2400
is not affected in any way, nor it affects the other receivers.

It seems the issue is not relative to the devices being on the same USB
bus, nor the kernel used. I've tried Debian's 2.6.32.5 and 2.6.38-bpo2
on a Debian Squeeze system.

На 11.6.2011 г. 19:38 ч., Doychin Dokov написа:

i've been using the patches in the latest media_tree for some hours -
the S2-3650 CI seems to work. There's one thing that disturbs me, though
- when it scans / locks on a frequency, another device on the same PC,
using the same stb6100, gets stuck for a moment. Any ideas what might be
the cause for that? The two devices do not share common RF input signal,
but are on the same USB bus:
Bus 001 Device 004: ID 734c:5980 TBS Technologies China
Bus 001 Device 003: ID 0b48:300a TechnoTrend AG TT-connect S2-3650 CI

The TBS device is a QBOX2 SI, which works with their official driver
from their web-site.

There's also a third DVB device in the system - a TT S-2400 (which is on
the other USB bus, though), which does not exhibit any problems related
with the first two devices, nor causes them to get stuck when it's
scanning.

I'll try to switch devices around and see if anything changes.





--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] Add support for PCTV452E.

[Doychin Dokov]

I also confirmed it works with s2-liplianin on Debian's 2.6.38-bpo2 
kernel without such problems.


Another thing I've tested is to compile the media_tree with the stb6100, 
but the problem persist, so it seems it's not related to the component 
that both devices share.


Any ideas what might be the reason for that, or at least where I should 
focus at searching?


На 13.6.2011 г. 00:38 ч., Doychin Dokov написа:

On 2.6.32.5 with s2-liplianin tree this is not observed, i.e. everything
works as expected - the S2-3650 does not cause the TBS device to stutter.

На 12.6.2011 г. 23:27 ч., Doychin Dokov написа:

The same thing happens when the devices are on different USB buses:
Bus 002 Device 004: ID 0b48:300a TechnoTrend AG TT-connect S2-3650 CI
Bus 001 Device 007: ID 0b48:3006 TechnoTrend AG TT-connect S-2400 DVB-S
Bus 001 Device 004: ID 734c:5980 TBS Technologies China

When the S2-3650 CI scans, the stream output from the TBS is gone. When
it's done scanning / locking, the TBS continues to work fine. The S-2400
is not affected in any way, nor it affects the other receivers.

It seems the issue is not relative to the devices being on the same USB
bus, nor the kernel used. I've tried Debian's 2.6.32.5 and 2.6.38-bpo2
on a Debian Squeeze system.

На 11.6.2011 г. 19:38 ч., Doychin Dokov написа:

i've been using the patches in the latest media_tree for some hours -
the S2-3650 CI seems to work. There's one thing that disturbs me, though
- when it scans / locks on a frequency, another device on the same PC,
using the same stb6100, gets stuck for a moment. Any ideas what might be
the cause for that? The two devices do not share common RF input signal,
but are on the same USB bus:
Bus 001 Device 004: ID 734c:5980 TBS Technologies China
Bus 001 Device 003: ID 0b48:300a TechnoTrend AG TT-connect S2-3650 CI

The TBS device is a QBOX2 SI, which works with their official driver
from their web-site.

There's also a third DVB device in the system - a TT S-2400 (which is on
the other USB bus, though), which does not exhibit any problems related
with the first two devices, nor causes them to get stuck when it's
scanning.

I'll try to switch devices around and see if anything changes.







--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] Add support for PCTV452E.

[Doychin Dokov]

i've been using the patches in the latest media_tree for some hours - 
the S2-3650 CI seems to work. There's one thing that disturbs me, though 
- when it scans / locks on a frequency, another device on the same PC, 
using the same stb6100, gets stuck for a moment. Any ideas what might be 
the cause for that? The two devices do not share common RF input signal, 
but are on the same USB bus:

Bus 001 Device 004: ID 734c:5980 TBS Technologies China
Bus 001 Device 003: ID 0b48:300a TechnoTrend AG TT-connect S2-3650 CI

The TBS device is a QBOX2 SI, which works with their official driver 
from their web-site.


There's also a third DVB device in the system - a TT S-2400 (which is on 
the other USB bus, though), which does not exhibit any problems related 
with the first two devices, nor causes them to get stuck when it's scanning.


I'll try to switch devices around and see if anything changes.

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] Add support for PCTV452E.

[Doychin Dokov]

I think you've missed this line at the end of ttpci-eeprom.c :

EXPORT_SYMBOL(ttpci_eeprom_decode_mac);

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

pctv452e driver status

[Davide Cavalca]

Hi,

I've managed to make my TechnoTrend TT-connect S2-3650 CI work using the
pctv452e driver from s2-lipianin on 2.6.35.10. It runs fine (both
regular and HD channels), but there are some minor issues:
- vdr-femon always reports a very low signal strenght (between 0 and
2%), I guess the driver is reporting an incorrect value
- about 1 out of 3 remote control key press is reported twice (I'm using
vdr-remote for it)
I haven't managed to test the CI part yet as I don't have any CI module
handy.

Are there any plans to merge this driver in the media tree and/or
eventually push it to the kernel?

Thanks,
Davide
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [linux-dvb] diseqc 2.0 on stb0899 / pctv452e (TT S2-3xxx and the likes)

[Harald Milz]

On Sun, Aug 09, 2009 at 11:26:01PM +0200, Martijn wrote:
 When I go through the s2-liplianin dvb drivers I noticed the DiSEqC 2.0 
 freq marker in the stb0899_priv.h header file. Also according to the 
 STB0899 datasheet DiSEqC 2.0 is supported. Does this mean that the pctv452e 
 driver does not implement the 2.0 specifications? I have seen the S2-3650 
 work through a DiSEqC 1.0 switch without any problems.

Does anyone have an idea as far as this matter? I'd like to use 2 or 3 S2-36xx
parts with a Quad monoblock LNB (Lemon-Inverto) which in principle contains a
DiSEqC switch.

I tried an earlier HG pull from September but my LNB seems to receive only
Hotbird channels, and not all of them to begin with. No Astra channels so far.

I see no mentions of a newer DiSEqC code in pctv452e.c in the changelog - was
there any progress on this? 

TIA!

-- 
We really don't have any enemies.  It's just that some of our best
friends are trying to kill us.
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [linux-dvb] diseqc 2.0 on stb0899 / pctv452e (TT S2-3xxx and the likes)

[Harald Milz]

On Sun, Aug 09, 2009 at 11:26:01PM +0200, Martijn wrote:
 When I go through the s2-liplianin dvb drivers I noticed the DiSEqC 2.0 
 freq marker in the stb0899_priv.h header file. Also according to the 
 STB0899 datasheet DiSEqC 2.0 is supported. Does this mean that the pctv452e 
 driver does not implement the 2.0 specifications? I have seen the S2-3650 
 work through a DiSEqC 1.0 switch without any problems.


Does anyone have an idea as far as this matter? I'd like to use 2 or 3 S2-36xx
parts with a Quad monoblock LNB which in principle contains a DiSEqC switch.
Anything to watch out for? Am I looking for an LNB that talks DiSEqC 1.0? 


-- 
If all the world's economists were laid end to end, we wouldn't reach a
conclusion.
-- William Baumol
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [linux-dvb] S2API (pctv452e) artefacts in video stream

[Rietzschel Carsten]

Hi Manu,
Hello together,

in the meantime I was able to test the device on windows. It works  
without any problems for over an hour.


Also I tried again different SAT- und USB-cables.
Also with all other USB-devices dettached - the error still comes.

First I'm getting TS continuity errors
and after a while (let's say 15 minutest) ...

Jan 30 14:42:20 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 30 14:42:20 vdr ttusb2: there might have been an error during  
control message transfer. (rlen = 4, was 0)

Jan 30 14:42:20 vdr ttusb2: i2c transfer failed.
Jan 30 14:42:22 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 30 14:42:22 vdr ttusb2: there might have been an error during  
control message transfer. (rlen = 3, was 0)

Jan 30 14:42:22 vdr ttusb2: i2c transfer failed.
Jan 30 14:42:24 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 30 14:42:24 vdr ttusb2: there might have been an error during  
control message transfer. (rlen = 4, was 0)



Thanks for your help!
darav
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [linux-dvb] S2API (pctv452e) artefacts in video stream

[darav]

Hi again,

has anybody an idea what's going wrong here?
I'm still having this problem.
Is there anything I can do to help here?

Thanks in advance,
darav

P.S.: now posting on the new mailinglist. Sorry for double-post.

Jan 28 12:03:09 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:11 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:11 vdr ttusb2: there might have been an error during  
control message transfer. (rlen = 3, was 0)

Jan 28 12:03:11 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:13 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:13 vdr ttusb2: there might have been an error during  
control message transfer. (rlen = 3, was 0)

Jan 28 12:03:13 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:15 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:15 vdr ttusb2: there might have been an error during  
control message transfer. (rlen = 4, was 0)

Jan 28 12:03:15 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:17 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:17 vdr ttusb2: there might have been an error during  
control message transfer. (rlen = 3, was 0)

Jan 28 12:03:17 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:19 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:19 vdr ttusb2: there might have been an error during  
control message transfer. (rlen = 4, was 0)

Jan 28 12:03:19 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:21 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:21 vdr ttusb2: there might have been an error during  
control message transfer. (rlen = 3, was 0)

Jan 28 12:03:21 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:23 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:23 vdr ttusb2: there might have been an error during  
control message transfer. (rlen = 4, was 0)

Jan 28 12:03:23 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:25 vdr dvb-usb: bulk message failed: -110 (8/0)
Jan 28 12:03:25 vdr ttusb2: there might have been an error during  
control message transfer. (rlen = 4, was 0)

Jan 28 12:03:25 vdr ttusb2: i2c transfer failed.
Jan 28 12:03:27 vdr dvb-usb: bulk message failed: -110 (9/0)
Jan 28 12:03:27 vdr ttusb2: there might have been an error during  
control message transfer. (rlen = 3, was 0)

Jan 28 12:03:27 vdr ttusb2: i2c transfer failed.



Am 12.01.2009 um 19:10 schrieb da...@gmx.de:


Hi!

The same problem exists with my PCTV 400e.
It seems to be problem with the USB part.
When I enable USB-Debug- in the kernel, I get this:

ttusb2: i2c transfer failed.
dvb-usb: bulk message failed: -22 (9/70)
ttusb2: there might have been an error during control message  
transfer. (rlen = 3, was 0)

...
ttusb2: i2c transfer failed.
dvb-usb: bulk message failed: -22 (9/70)
ttusb2: there might have been an error during control message  
transfer. (rlen = 3, was 0)


It's the same with 2.6.28 in-kernel-drivers and with the Igor  
Liplianin's tree.


(A also had this problem some years ago on a PPC-Mac-Mini. The  
workaround was to disable HIGHMEM. But it doesn't work now.

I'm now on x86 32bit).

I also want to help. But how?

Best Regards,
darav

Am 12.01.2009 um 13:16 schrieb Jens Krehbiel-Gräther:


Hi!

So this problem concerns more people and should be a general bug??
My device is working well in windows, so it could not be the dish,  
the

cable or the device itself.

Can I do anything for debugging this problem? Let me know!

Jens


dbox2al...@netscape.net schrieb:


i can confirm the very same problem symptoms with a technotrend  
dvb-s2

3600 usb device.

-Original Message-
From: gimli gi...@dark-green.com
To: Artem Makhutov ar...@makhutov.org
Cc: linux-...@linuxtv.org
Sent: Mon, 5 Jan 2009 2:20 pm
Subject: Re: [linux-dvb] S2API (pctv452e) artefacts in video stream

Artem Makhutov schrieb:


Hi,






On Mon, Jan 05, 2009 at 02:02:16PM +0100, Jens Krehbiel-Gräther  
wrote:



Hi!







I use a Pinnacle USB-Receiver (PCTV Sat HDTV Pro). The module is



dvb-usb-pctv452e.






I use the repository from Igor Liplianin (actual hg release).  
The module


compiles and loads fine. The scanning with scan-s2 and zapping  
with



szap-s2 also wirk fine.



But when I record TV from the USB-device with cat


/dev/dvb/adapter0/dvr0  (filename) I got the TV-Stream of the  
actual



tv-station (zapped with szap-s2 -r SAT.1 for example).



This recorded video has artefacts, even missed frames.






Anyone else having this problem? I remember that on multiproto  
there was



a similar prob

lem with the pctv452e until Dominik Kuhlen patched


somthing since then the video was OK. Is it possible that the same



error is in the S2API-driver?







I have similar problems with my SkyStar HD (stb0899), but I



am still using the multiproto drivers.







Regards, Artem







___



linux-dvb mailing list



linux-...@linuxtv.org



http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb




Hi have also a similar problem on the TerraTec Cinergy S2 PCI HD

Re: [linux-dvb] S2API (pctv452e) artefacts in video stream

[Manu Abraham]

da...@gmx.de wrote:
 Hi again,
 
 has anybody an idea what's going wrong here?
 I'm still having this problem.
 Is there anything I can do to help here?
 
 Thanks in advance,
 darav
 
 P.S.: now posting on the new mailinglist. Sorry for double-post.
 
 Jan 28 12:03:09 vdr ttusb2: i2c transfer failed.
 Jan 28 12:03:11 vdr dvb-usb: bulk message failed: -110 (9/0)
 Jan 28 12:03:11 vdr ttusb2: there might have been an error during
 control message transfer. (rlen = 3, was 0)
 Jan 28 12:03:11 vdr ttusb2: i2c transfer failed.
 Jan 28 12:03:13 vdr dvb-usb: bulk message failed: -110 (9/0)
 Jan 28 12:03:13 vdr ttusb2: there might have been an error during
 control message transfer. (rlen = 3, was 0)
 Jan 28 12:03:13 vdr ttusb2: i2c transfer failed.


Looks like the demodulator did not respond at all, maybe it went
bad. Does your device work in a windows environment ?

Regards,
Manu
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html