All of lore.kernel.org
 help / color / mirror / Atom feed
From: thomas schorpp <thomas.schorpp@googlemail.com>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] CI/CAM fixes for knc1 dvb-s cards
Date: Sat, 22 Mar 2008 16:46:54 +0100	[thread overview]
Message-ID: <47E529EE.901@googlemail.com> (raw)
In-Reply-To: <200803221413.24352.christophpfister@gmail.com>

Christoph Pfister wrote:
> Am Samstag 22 März 2008 schrieb e9hack:
>> Christoph Pfister schrieb:
>>> Hi,
>>>
>>> Can somebody please pick up those patches (descriptions inlined)?
>>>
>>> Thanks,
>>>
>>> Christoph
>> diff -r 1886a5ea2f84 -r f252381440c1
>> linux/drivers/media/dvb/ttpci/budget-av.c ---
>> a/linux/drivers/media/dvb/ttpci/budget-av.c	Fri Mar 21 08:04:55 2008 -0300
>> +++ b/linux/drivers/media/dvb/ttpci/budget-av.c	Fri Mar 21 19:29:15 2008
>> +0100 @@ -178,7 +178,7 @@ static int ciintf_read_cam_control(struc
>>   	udelay(1);
>>
>>   	result = ttpci_budget_debiread(&budget_av->budget, DEBICICAM, address &
>> 3, 1, 0, 0); -	if ((result == -ETIMEDOUT) || ((result == 0xff) && ((address
>> & 3) < 2))) { +	if ((result == -ETIMEDOUT) || ((result == 0xff) &&
>> ((address & 3) == 1))) { ciintf_slot_shutdown(ca, slot);
>>   		printk(KERN_INFO "budget-av: cam ejected 3\n");
>>   		return -ETIMEDOUT;
>>
>>
>> IMHO you should remove the test for 0xff . Without your patch, it wasn't
>> possible to read 0xff from address 0 and 1. Now it isn't possible to read
>> 0xff from address 1.
> 
> Address 1 is the status register; bits 2-5 are reserved according to en50221 
> and should be zero, so this case is less problematic with regards to 0xff 
> checking.
> 
> On second thoughts it's probably better to remove the check altogether, 
> because a) budget-av isn't here to check standards conformance - the higher 
> layers know better how to deal with the content and b) who should care if the 
> other status bits work correctly ;)

Better remove all CI stuff from that wrong place.
Why is all that CI and tuner frontend (which dvb budget card has got a analogtv demod?) 
code in the budget__AV__ module ?
Pls move it to budget__CI__  and budget modules, and have the budget_av/_ci 
stuff detected there and loaded and utilized *if* needed, the current ci-code  
blocks saa7113 analog capture on plus cards and could, according to manu's research, 
confuse a knc1 dvb-s2 card completely.

and who needs cam polling? do we have got a majority of users hotswapping cams?
i want that be clarified before sending rejectable patches.

>> -Hartmut
> 
> Christoph

y
tom

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  reply	other threads:[~2008-03-22 15:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-21 19:24 [linux-dvb] CI/CAM fixes for knc1 dvb-s cards Christoph Pfister
2008-03-22  6:32 ` Oliver Endriss
2008-03-22 12:56   ` Christoph Pfister
2008-03-28 17:20   ` Christoph Pfister
2008-03-28 21:57     ` Christoph Pfister
2008-04-03 23:33     ` Oliver Endriss
2008-04-05 13:14       ` Christoph Pfister
2008-04-11 22:01         ` Oliver Endriss
2008-03-22 11:31 ` e9hack
2008-03-22 13:13   ` Christoph Pfister
2008-03-22 15:46     ` thomas schorpp [this message]
2008-03-28 10:45 ` Arthur Konovalov
2008-03-28 14:35   ` Christoph Pfister
2008-03-28 15:06     ` Arthur Konovalov
2008-03-28 17:16       ` Christoph Pfister
2008-03-28 20:22         ` Arthur Konovalov
2008-03-28 22:02           ` Christoph Pfister
2008-03-28 23:59             ` Arthur Konovalov
2008-03-29 15:00               ` Christoph Pfister

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=47E529EE.901@googlemail.com \
    --to=thomas.schorpp@googlemail.com \
    --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 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.