All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raimonds Cicans <ray@apollo.lv>
To: Hans Verkuil <hverkuil@xs4all.nl>,
	linux-media <linux-media@vger.kernel.org>,
	gtmkramer@xs4all.nl
Subject: Re: [PATCH] cx23885/vb2 regression: please test this patch
Date: Fri, 16 Jan 2015 18:20:25 +0200	[thread overview]
Message-ID: <54B93A49.1010108@apollo.lv> (raw)
In-Reply-To: <54B92620.6020408@xs4all.nl>

On 16.01.2015 16:54, Hans Verkuil wrote:
> On 01/13/2015 06:55 PM, Raimonds Cicans wrote:
>> On 13.01.2015 16:01, Hans Verkuil wrote:
>>> Can you both test this patch? It should (I hope) solve the problems you
>>> both had with the cx23885 driver.
>>>
> Can you check that the function cx23885_risc_field in
> drivers/media/pci/cx23885/cx23885-core.c uses "sg = sg_next(sg);"
> instead of "sg++;"?
There is no sg++ in whole drivers/media/pci/cx23885/ directory.
> To avoid confusion I would prefer that you test with a 3.18 or higher kernel
> and please state which kernel version you use and whether you used the
> media_build system or a specific git repo to build the drivers.
kernel: Gentoo Hardened kernel 3.18.1 (hardened part turned off)
media_build: pure original media_build
media tree: https://github.com/ljalves/linux_media (original linux-media 
plus some
new out of kernel TBS drivers (from this tree I need TBS6285 driver))
> I'm also interested if you can reproduce it using just command-line 
> tools (and let me know what it is you do).
For tests I use only command line tools: w_scan & dvb-fe-tool

Tests:
1) w_scan on first front end then after 5-10 seconds w_scan on other
2) w_scan on second front end then after 5-10 seconds w_scan on first
3) "dvb-fe-tool -d DVBS" on first front end then after 5-10 seconds 
w_scan on second front end then after 5-10 seconds w_scan on first
4) "dvb-fe-tool -d DVBS" on second front end then after 5-10 seconds 
w_scan on first front end then after 5-10 seconds w_scan on second

w_scan run on both front ends simultaneously.


 > Use only one DVB adapter, not both.

Do you mean one card or one front end?



Raimonds Cicans

  reply	other threads:[~2015-01-16 16:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 14:01 [PATCH] cx23885/vb2 regression: please test this patch Hans Verkuil
2015-01-13 16:59 ` Jurgen Kramer
2015-01-15 16:32   ` Jurgen Kramer
2015-01-16 14:58     ` Hans Verkuil
2015-01-16 16:48       ` Jurgen Kramer
2015-01-18  8:54       ` Jurgen Kramer
2015-01-18 10:40         ` Hans Verkuil
2015-01-18 12:35           ` Jurgen Kramer
2015-01-13 17:55 ` Raimonds Cicans
2015-01-14  6:16   ` Raimonds Cicans
2015-01-16 14:54   ` Hans Verkuil
2015-01-16 16:20     ` Raimonds Cicans [this message]
2015-01-16 16:48       ` Luis Alves
2015-01-16 17:38         ` Hans Verkuil
2015-01-16 17:40       ` Hans Verkuil
2015-01-16 19:05     ` Raimonds Cicans
2015-01-17 11:09       ` Hans Verkuil
2015-01-17 12:02         ` Raimonds Cicans
2015-01-17 12:30         ` Tycho Lürsen

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=54B93A49.1010108@apollo.lv \
    --to=ray@apollo.lv \
    --cc=gtmkramer@xs4all.nl \
    --cc=hverkuil@xs4all.nl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.