From: Ingo Peukes <admin@ipnetwork.de>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Cinergy T2 Kernel Oops on Linkstation Live V1 (Marvel Orion ARM Architecture)
Date: Fri, 09 May 2008 11:53:41 +0200 [thread overview]
Message-ID: <48241F25.40607@ipnetwork.de> (raw)
In-Reply-To: <4824034D.7000700@free.fr>
Hello Thierry,
Thierry Merle wrote:
> Hi Ingo,
>
> Ingo Peukes a écrit :
>> Hello everyone...
>>
>> a few days ago I bought e Pinnacle PCTV200e to try if it works with my
>> Linkstation. After getting some drivers for it from here:
>> http://ubuntuforums.org/showthread.php?t=511676&page=8
>> As result I just got the same kernel oops, only triggered by the dvb_usb
>> module instead of the cinergyT2 one.
>>
> Is it the same ManufacturerID/VendorID as the cinergyT2 device or did you make some adaptations to make your Pinnacle device to work with the cinergyT2 driver?
>
Well, think I was a bit unclear here.
I don't use the cinergyT2 module with the Pinnacle device.
The v4l-dvb drivers I found on the ubuntu forum contains a separate
driver for the PCTV200e. What I was trying to say is that both drivers
trigger the same oops, in case of the PCTV it originates in dvb-usb.ko
and in case of the cinergy in cinergyT2.ko
>> Today I found a patch sent to this list on 01/20/2008 by Michele
>> Scorcia. Although it is for kernel 2.6.20.4 and written to fix a problem
>> on a mips platform the description of the problem came close to mine. So
>> I applied it to the usb-urb.c from the above archive and built the modules.
>> After that the oops was gone and the PCTV runs without problems.
>> The cinergy driver still triggers the oops but i think that's normal
>> cause it does not use the dvb-usb module and would need a separate patch.
>> The new cinergyT2 driver from Tomi Orava works just fine so I give it a
>> chance instead of fixing the old one.
>> Another reason for this is that I tried both receivers on my desktop
>> with the same kernel and v4l-dvb sources as I use on the Linkstation and
>> couldn't make them run both at the same time. dmesg shows no errors but
>> w_scan hangs when both drivers are loaded. Either receiver alone works
>> great but together none does.
>> This problem does not exist with the new driver.
>>
> I hope Tomi will be able to finalize his patch so we will be able to replace the old one.
> The old driver is monolithic and does not follow the dvb framework evolutions/bug corrections.
Hope so too, as I stated in my reply to the 'Tester wanted ...' thread
it works good except the signal recognition is very poor compared to the
old driver.
>
>>
>> Here's the patch I use, only difference to the one from Michele Scorcia
>> are the line numbers:
>>
> Please post this patch in an email with [PATCH] in subject and with the Signed-off-by: name <email> line so that maintainers get aware of the patch, and don't miss it.
> See: http://www.linuxtv.org/v4lwiki/index.php/How_to_submit_patches
Thanks for the hint, will do that :)
>
> Thanks
> Thierry
REgrads
Ingo PEukes
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-05-09 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 9:40 [linux-dvb] Cinergy T2 Kernel Oops on Linkstation Live V1 (Marvel Orion ARM Architecture) Ingo Peukes
2008-05-08 21:46 ` Ingo Peukes
2008-05-09 7:54 ` Thierry Merle
2008-05-09 9:53 ` Ingo Peukes [this message]
2008-05-13 9:03 ` Tino Keitel
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=48241F25.40607@ipnetwork.de \
--to=admin@ipnetwork.de \
--cc=linux-dvb@linuxtv.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