Em 12-01-2012 14:22, Gianluca Gennari escreveu:
Il 11/01/2012 20:19, Jim Darby ha scritto:
On 11/01/12 01:05, Antti Palosaari wrote:
[snip]
Also latest LinuxTV.org devel could be interesting to see. There is
one patch that changes em28xx driver endpoint configuration. But as
that patch is
Il 13/01/2012 12:21, Mauro Carvalho Chehab ha scritto:
Em 12-01-2012 14:22, Gianluca Gennari escreveu:
Il 11/01/2012 20:19, Jim Darby ha scritto:
On 11/01/12 01:05, Antti Palosaari wrote:
[snip]
Also latest LinuxTV.org devel could be interesting to see. There is
one patch that changes em28xx
On 13/01/12 11:21, Mauro Carvalho Chehab wrote:
Hmm... this patch shouldn't be causing troubles for an application that
only uses DVBv3 call. Is Kaffeine filling the DTV_DELIVERY_SYSTEM with
SYS_UNDEFINED (0)?
I think this is perhaps where (some of) our problems are starting. I
just looked
Il 13/01/2012 14:09, Jim Darby ha scritto:
On 13/01/12 11:21, Mauro Carvalho Chehab wrote:
Hmm... this patch shouldn't be causing troubles for an application that
only uses DVBv3 call. Is Kaffeine filling the DTV_DELIVERY_SYSTEM with
SYS_UNDEFINED (0)?
I think this is perhaps where (some
On 10 January 2012 13:28, Jim Darby uberscuba...@gmail.com wrote:
I've been using a PCTV Nanostick T2 USB DVB-T2 receiver (one of the few that
supports DVB-T2) for over six months with a 3.0 kernel with no problems.
Seeing the 3.2 kernel I thought I'd upgrade and now I seem to have hit a
Il 11/01/2012 20:19, Jim Darby ha scritto:
On 11/01/12 01:05, Antti Palosaari wrote:
[snip]
Also latest LinuxTV.org devel could be interesting to see. There is
one patch that changes em28xx driver endpoint configuration. But as
that patch is going for 3.3 it should not be cause of issue, but
On 12/01/12 16:22, Gianluca Gennari wrote:
Hi Jim,
you spotted a regression in the latest media_build release from
11/01/2012.
I had the same problem here:
dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to
delivery system 0
with 3 totally different sticks (em28xx, dvb-usb,
I'm still unsure about the first. It might be a 32/64-bit problem (based on
evidence from Simon Jones), it might be flaky hardware or it might be a real
problem. I'm planning to build the 3.2.0 kernel (minus the linux-media
patches) for 64-bit on different hardware and see what happens.
As
Il 12/01/2012 17:35, Jim Darby ha scritto:
On 12/01/12 16:22, Gianluca Gennari wrote:
Hi Jim,
you spotted a regression in the latest media_build release from
11/01/2012.
I had the same problem here:
dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to
delivery system 0
I thought I'd batch all the answers together.
Andy suggested something about transfer buffers being dropped out of
rotation. I'm not sure exactly what this is but if it's anything like
ethernet buffering it would explain it. It would also explain why it
lasts longer on the lower bit rate
On 11/01/12 01:05, Antti Palosaari wrote:
[snip]
Also latest LinuxTV.org devel could be interesting to see. There is
one patch that changes em28xx driver endpoint configuration. But as
that patch is going for 3.3 it should not be cause of issue, but I
wonder if it could fix... Use
The Nanostick works fine for between 5 and 25 minutes and then without any
error messages cuts out. The TS drops to a tiny stream of non-TS data. It
seems to contain a lot of 0x00s and 0xffs.
What does femon show for demodulator statistics?
--
Steven Toth - Kernel Labs
On 10/01/12 13:54, Steven Toth wrote:
The Nanostick works fine for between 5 and 25 minutes and then without any
error messages cuts out. The TS drops to a tiny stream of non-TS data. It
seems to contain a lot of 0x00s and 0xffs.
What does femon show for demodulator statistics?
Well... I
Steven Toth st...@kernellabs.com wrote:
status SCVYL | signal | snr 00ee | ber | unc |
FE_HAS_LOCK
status SCVYL | signal | snr 00f0 | ber | unc |
FE_HAS_LOCK
and when it stopped working, this time an hour later, nothing had
changed.
In fact, it
On 01/10/2012 03:28 PM, Jim Darby wrote:
I've been using a PCTV Nanostick T2 USB DVB-T2 receiver (one of the few
that supports DVB-T2) for over six months with a 3.0 kernel with no
problems.
The key drivers in use are em28xx, cxd2820r and tda18271.
Seeing the 3.2 kernel I thought I'd upgrade
15 matches
Mail list logo
