All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brice Dubost <dubost@crans.org>
To: "pierre.gronlier" <ticapix@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: problem with libdvben50221 and powercam pro V4 [almost solved]
Date: Wed, 27 Jan 2010 11:05:28 +0100	[thread overview]
Message-ID: <4B600FE8.5060205@crans.org> (raw)
In-Reply-To: <4B5D6A6B.9030900@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2103 bytes --]

pierre.gronlier wrote:
> pierre gronlier wrote, On 01/24/2010 11:03 PM:
>> DUBOST Brice <dubost <at> crans.ens-cachan.fr> writes:
>>> Manu Abraham a écrit :
>>>> Hi Brice,
>>>>
>>>> On Mon, Jan 25, 2010 at 12:09 AM, DUBOST Brice
>>>> <dubost <at> crans.ens-cachan.fr> wrote:
>>>>> Hello
>>>>>
>>>>> Powercam just made a new version of their cam, the version 4
>>>>>
>>>>> Unfortunately this CAM doesn't work with gnutv and applications based on
>>>>> libdvben50221
>>>>>
>>>>> This cam return TIMEOUT errors (en50221_stdcam_llci_poll: Error reported
>>>>> by stack:-3) after showing the supported ressource id.
>>>>>
>>>>> The problem is that this camreturns two times the list of supported ids
>>>>> (as shown in the log) this behavior make the llci_lookup_callback
>>>>> (en50221_stdcam_llci.c line 338)  failing to give the good ressource_id
>>>>> at the second call because there is already a session number (in the
>>>>> test app the session number is not tested)
>>>>>
>>>>> I solved the problem commenting out the test for the session number as
>>>>> showed in the joined patch (against the latest dvb-apps, cloned today)
>> I will run some tests with a TT3200 card too and a Netup card tomorrow.
>>
>> Regarding the cam returning two times the list of valid cam ids, wouldn't be
>> better if the manufacturer corrects it in the cam firmware ?
>> What says the en50221 norm about it ?
>>
> 
> Indeed, with the patch applied, the command gnutv -adapter 0 -cammenu is
> working fine with a netup card too.
> 
> I will try to update to the last revision of pcam firmware (v4.2) and
> report this behaviour to the manufacturer.
> 


Hello, a bit more information on this issue

Just for information, Here I attach you the log of another test I did,
the CAM answers the list of available Ids several times (each time you
change it basically) on the same session.

Manu : the test in the libdvben50221 was intended to deal with which case ?

I notice also that the decoding can fail if the PMT_ASK is sent between
the two ca_list answer at the beginning (this is a bit boring).

Regards

-- 
Brice




[-- Attachment #2: CAMpowercamV4.1.txt --]
[-- Type: text/plain, Size: 3807 bytes --]

Found a CAM on adapter1... waiting...
en50221_tl_register_slot
slotid: 0
tcid: 1
Press a key to enter menu
00:Host originated transport connection 1 connected
00:Public resource lookup callback 1 1 1
00:CAM connecting to resource 00010041, session_number 1
00:CAM successfully connected to resource 00010041, session_number 1
00:test_rm_reply_callback
00:test_rm_enq_callback
00:Public resource lookup callback 2 1 1
00:CAM connecting to resource 00020041, session_number 2
00:CAM successfully connected to resource 00020041, session_number 2
00:test_ai_callback
  Application type: 01
  Application manufacturer: 02ca
  Manufacturer code: 3000
  Menu string: PCAM V4.1
00:Public resource lookup callback 3 1 1
00:CAM connecting to resource 00030041, session_number 3
00:CAM successfully connected to resource 00030041, session_number 3
00:test_ca_info_callback
  Supported CA ID: 0500
00:Connection to resource 00030041, session_number 3 closed
00:Public resource lookup callback 3 1 1
00:CAM connecting to resource 00030041, session_number 3
00:CAM successfully connected to resource 00030041, session_number 3
00:test_ca_info_callback
  Supported CA ID: 0500

00:Public resource lookup callback 64 1 1
00:CAM connecting to resource 00400041, session_number 4
00:CAM successfully connected to resource 00400041, session_number 4
00:test_mmi_display_control_callback
  cmd_id: 01
  mode: 01
00:test_mmi_menu_callback
  title: PCAM V4.1
  sub_title: Select a language
  bottom: 
  item 1: English
  item 2: French
  item 3: Spanish
  item 4: German
  item 5: Russian
  item 6: Arabic A
  item 7: Arabic B
  raw_length: 0
1
00:test_mmi_menu_callback
  title: PCAM V4.1
  sub_title: Main Menu
  bottom: Select one and press 'OK' to continue
  item 1: SmartCard & PIN
  item 2: CAS
  item 3: VP: 21680
  item 4: Download Status
  raw_length: 0
2
00:test_mmi_menu_callback
  title: PCAM V4.1
  sub_title: Currently selected CAS: 
  bottom: Please select 'Yes' or 'No' and press 'OK' to continue
  item 1: Do you want to change it?
  item 2: No
  item 3: Yes
  raw_length: 0
3
00:test_mmi_menu_callback
  title: PCAM V4.1
  sub_title: Currently selected CAS:
  bottom: Please select an option and press 'OK' to continue
  item 1: ALL
  item 2: Embedded Channels & PIN [OFF]
  item 3: MOSAIC-S [OFF]
  item 4: MOSAIC-V [ON]
  item 5: MOSAIC-I [OFF]
  item 6: MOSAIC-B [OFF]
  item 7: MOSAIC-C [OFF]
  item 8: MOSAIC-X [OFF]
  item 9: KEYFLY [OFF]
  raw_length: 0
3
00:test_mmi_menu_callback
  title: PCAM V4.1
  sub_title: Currently selected CAS:
  bottom: Please select an option and press 'OK' to continue
  item 1: ALL
  item 2: Embedded Channels & PIN [OFF]
  item 3: MOSAIC-S [ON]
  item 4: MOSAIC-V [ON]
  item 5: MOSAIC-I [OFF]
  item 6: MOSAIC-B [OFF]
  item 7: MOSAIC-C [OFF]
  item 8: MOSAIC-X [OFF]
  item 9: KEYFLY [OFF]
  raw_length: 0
00:Connection to resource 00030041, session_number 3 closed
00:Public resource lookup callback 3 1 1
00:CAM connecting to resource 00030041, session_number 3
00:CAM successfully connected to resource 00030041, session_number 3
00:test_ca_info_callback
  Supported CA ID: 0100
  Supported CA ID: 0500
3
00:test_mmi_menu_callback
  title: PCAM V4.1
  sub_title: Currently selected CAS:
  bottom: Please select an option and press 'OK' to continue
  item 1: ALL
  item 2: Embedded Channels & PIN [OFF]
  item 3: MOSAIC-S [OFF]
  item 4: MOSAIC-V [ON]
  item 5: MOSAIC-I [OFF]
  item 6: MOSAIC-B [OFF]
  item 7: MOSAIC-C [OFF]
  item 8: MOSAIC-X [OFF]
  item 9: KEYFLY [OFF]
  raw_length: 0
00:Connection to resource 00030041, session_number 3 closed
00:Public resource lookup callback 3 1 1
00:CAM connecting to resource 00030041, session_number 3
00:CAM successfully connected to resource 00030041, session_number 3
00:test_ca_info_callback
  Supported CA ID: 0500


  reply	other threads:[~2010-01-27 10:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-24 20:09 problem with libdvben50221 and powercam pro V4 [almost solved] DUBOST Brice
2010-01-24 21:22 ` Manu Abraham
2010-01-24 21:43   ` DUBOST Brice
2010-01-24 22:03     ` pierre gronlier
2010-01-25  9:54       ` pierre.gronlier
2010-01-27 10:05         ` Brice Dubost [this message]
2010-01-25 10:38       ` Manu Abraham

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=4B600FE8.5060205@crans.org \
    --to=dubost@crans.org \
    --cc=linux-media@vger.kernel.org \
    --cc=ticapix@gmail.com \
    /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.