Re: CI USB

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 24 January 2010 09:56, Konstantin Dimitrov <kosio.dimitrov@xxxxxxxxx> wrote:
> On Sun, Jan 24, 2010 at 10:54 AM, Konstantin Dimitrov
> <kosio.dimitrov@xxxxxxxxx> wrote:
>> On Sun, Jan 24, 2010 at 10:12 AM, Manu Abraham <abraham.manu@xxxxxxxxx> wrote:
>>> On Sun, Jan 24, 2010 at 11:49 AM, Konstantin Dimitrov
>>> <kosio.dimitrov@xxxxxxxxx> wrote:
>>>> On Sun, Jan 24, 2010 at 1:43 AM, Manu Abraham <abraham.manu@xxxxxxxxx> wrote:
>>>>> On Sun, Jan 24, 2010 at 1:45 AM, Konstantin Dimitrov
>>>>> <kosio.dimitrov@xxxxxxxxx> wrote:
>>>>>> On Sat, Jan 23, 2010 at 1:31 AM, Manu Abraham <abraham.manu@xxxxxxxxx> wrote:
>>>>>>> On Sun, Jan 10, 2010 at 9:21 PM, Ian Wilkinson <null@xxxxxxxxxxxxxxxxx> wrote:
>>>>>>>> HoP wrote:
>>>>>>>>
>>>>>>>> I don't know the details into the USB device, but each of those CAM's
>>>>>>>> have bandwidth limits on them and they vary from one CAM to the other.
>>>>>>>> Also, there is a limit on the number of simultaneous PID's that which
>>>>>>>> you can decrypt.
>>>>>>>>
>>>>>>>> Some allow only 1 PID, some allow 3. Those are the basic CAM's for
>>>>>>>> home usage.The most expensive CAM's allow a maximum of 24 PID's. But
>>>>>>>>
>>>>>>>>
>>>>>>>> You, of course, ment number of descramblers not PIDS because it is evident
>>>>>>>> that getting TV service descrambled, you need as minimum 2 PIDS for A/V.
>>>>>>>>
>>>>>>>> Anyway, it is very good note. Users, in general, don't know about it.
>>>>>>>>
>>>>>>>
>>>>>>> If it is using a CI+ plus chip (I heard from someone that it is a CI+
>>>>>>> chip inside) :
>>>>>>> http://www.smardtv.com/index.php?page=ciplus
>>>>>>>
>>>>>>> After reading the CI+ specifications, I doubt that it can be supported
>>>>>>> under Linux with open source support, without a paired decoder
>>>>>>> hardware or software decoder. A paired open source software decoder
>>>>>>> seems highly unlikely, as the output of the CI+ module is eventually
>>>>>>> an encrypted stream which can be descrambled with the relevant keys.
>>>>>>> The TS is not supposed to be stored on disk, or that's what the whole
>>>>>>> concept is for CI+
>>>>>>>
>>>>>>> http://www.ci-plus.com/data/ci-plus_overview_v2009-07-06.pdf
>>>>>>>
>>>>>>> See pages 7, 8 , 12, 15
>>>>>>>
>>>>>>> It could be possible to pair a software decoder with a key and hence
>>>>>>> under Windows, but under Linux I would really doubt it, if it happens
>>>>>>> to be a CI+ chip
>>>>>>
>>>>>> at least in Windows Hauppage WinTV-CI USB (which is OEM version of
>>>>>> SmartDTV USB CI) allows you to capture the decrypted stream to your
>>>>>> hard drive (i've just tested it).
>>>>>
>>>>>
>>>>> Maybe it is not CI+ itself in the first place
>>>>>
>>>>>
>>>>>> so, i can't see a reason why even if it has CI+ chip inside same
>>>>>> functionally as in Windows can't be provided in Linux if someone
>>>>>> developed a driver.
>>>>>
>>>>>
>>>>> It would be interesting to know what chips the hardware has  ...
>>>>
>>>> i can confirm the information here:
>>>>
>>>> * http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-CI
>>>>
>>>> and it contains:
>>>>
>>>> * "an FX2 from Cypress (CY7C68013A) and a FPGA (Actel Proasic-plus, APA075-F)"
>>>>
>>>
>>>
>>> No CI+ in there ... Generic USB bridge with microcontroller and
>>> possibly a FPGA programmed by Hauppauge themselves, most probably. The
>>
>> no, the whole Hauppauge device is actually made by SmartDTV even on
>> the board there is a title "SmartDTV Rev..."
>>
>> also, Terratec device is the same as Hauppauge device, they even look the same:
>>
>> http://www.terratec.net/en/products/Cinergy_CI_USB_2296.html
>>
>> and Terratec driver for Windows says "Copyright SmarDTV.", which means
>> it's made by SmarDTV.
>>
>> actually, Terratec driver for Windows is essentially the same as
>> Hauppauge one, because firmware extracted from both drivers is the
>> same (they update the firmware with driver updates, so matching
>> versions of Terratec and Hauppauge driver is needed to check that the
>> firmwares are the same).
>>
>>> bridge would be similar to other DVB USB devices, Application on the
>>> FPGA would be more or less similar to the one found on general DVB CI
>>> devices.
>>>
>>> If it's not a Masked FPGA, it would need to load it's instructions
>>> some place, maybe an EEPROM or maybe from the firmware that you need
>>> load itself. Some part of the firmware that you load could be partly
>>> for the microcontroller on the USB bridge as well.
>>
>> i believe that "40 A3" firmware requests are for the USB controller
>
> typo, "40 A0" firmware requests are for the USB controller
>
>> and then the subsequent "40 A3" firmware requests are to load the FPGA
>> instructions through the USB controller.
>>
>>>
>>>
>>> Manu
>>>
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

According to this page

http://www.bsc-bvba.be/linux/dvb/

the firmware load problem was solved about a month ago

What is needed in the way of resources to solve this problem?

Regards
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux