linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Darby <uberscubajim@gmail.com>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH] [media] dvb-core: preserve the delivery system at cache clear
Date: Sat, 14 Jan 2012 00:00:06 +0000	[thread overview]
Message-ID: <4F10C586.3030600@gmail.com> (raw)
In-Reply-To: <1326462636-8869-1-git-send-email-mchehab@redhat.com>

Thanks for the patch Mauro. According to Gianluca that solves the 
backwards compatibility issue. This is great news.

In other news I've tried a few experiments. Firstly I tried using a 
3.2.0 unmodified straight out of the box kernel on my Core 2 64-bit 
system. I was unable to produce any faults. This would tend to lead one 
to suspect that it's a 32-bit problem or that my 32-bit machine is a bit 
flaky or slow.

So, as I wanted to try the new alpha 3 for Mageia 2 (a Mandriva fork) 
out and it has a 3.0 kernel that seemed to be a good idea. The bad news 
is that I'd run out of hardware. So I thought I'd be clever and run it 
as a virtual machine on my Core 2 system.

The good news is that it correctly recognised the stick and it seemed to 
work for standard definition. However, after setting it to record some 
HDTV programmes it failed. More importantly it failed in the same way as 
the 32-bit system.

This makes me think it's some kind of timing problem. The USB 
passthrough of VirtualBox may well not operate at the performance 
required for HDTV. Also by this time I'd put the stick on a USB 
extension lead which may have adversely affected the power feed.

For my next series of tests I plan to run it again on bare hardware. I'm 
going to try and use my older Core 2 machine which should have the CPU 
and electrical power.

None of which explains why it works on the 32-bit Athlon XP 2200+ when 
it's running 3.0.0 though. And has done so reliably for some time. Maybe 
some other things are happening in the kernel that much up the device 
timing or something.

Anyway, I'll keep people posted as to the progression of the testing.

Best regards,

Jim.

  parent reply	other threads:[~2012-01-14  0:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10 13:28 Possible regression in 3.2 kernel with PCTV Nanostick T2 (em28xx, cxd2820r and tda18271) Jim Darby
2012-01-10 13:54 ` Steven Toth
2012-01-10 23:22   ` Jim Darby
2012-01-11  0:01     ` Steven Toth
2012-01-11  0:34       ` Andy Walls
2012-01-11  1:05 ` Antti Palosaari
2012-01-11 11:30   ` Jim Darby
2012-01-11 19:19   ` Jim Darby
2012-01-12 16:22     ` Gianluca Gennari
2012-01-12 16:35       ` Jim Darby
2012-01-12 17:13         ` Simon Jones
2012-01-12 17:34         ` Gianluca Gennari
2012-01-13 11:21       ` Mauro Carvalho Chehab
2012-01-13 11:45         ` Gianluca Gennari
2012-01-13 13:50           ` [PATCH] [media] dvb-core: preserve the delivery system at cache clear Mauro Carvalho Chehab
2012-01-13 16:04             ` Gianluca Gennari
2012-01-14  0:00             ` Jim Darby [this message]
2012-01-14 14:51               ` Mauro Carvalho Chehab
2012-01-13 13:09         ` Possible regression in 3.2 kernel with PCTV Nanostick T2 (em28xx, cxd2820r and tda18271) Jim Darby
2012-01-13 14:24           ` Gianluca Gennari
2012-01-12 14:29 ` Simon Jones

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F10C586.3030600@gmail.com \
    --to=uberscubajim@gmail.com \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).