fact that
the issue
>> does not exist with the STB0899 driver.
>>
>> Regarding the documentation, I don't have any wrt to the USB
bridge, but
>> only for the demodulator, tuner. But my hands are tied on that
front, due
t; I can assure you that the STB0899 driver works well for S2 with most
>> USB bridges and PCI bridges, which brings me to the fact that the issue
>> does not exist with the STB0899 driver.
>>
>> Regarding the documentation, I don't have any wrt to the USB bridge, but
&g
CI REV 2.0
The information on a white sticker on the PCB states:
Model AD-SB301, Project ID: 6027
DVB-S2, CI, USB Box (on-line update)
H/W Ver: A1, PID/VID: 14F7 / 0002
manufactured and sent to me by Azurewave.
It has a broken ferrite cored inductor on it, which appears to be on the
power line to
in my hardware museum, I did find a
Technisat Skystar USB2 HD CI REV 2.0
The information on a white sticker on the PCB states:
Model AD-SB301, Project ID: 6027
DVB-S2, CI, USB Box (on-line update)
H/W Ver: A1, PID/VID: 14F7 / 0002
manufactured and sent to me by Azurewave.
It has a broken fe
Hi David,
On Thu, Feb 6, 2014 at 3:15 PM, David Jedelsky wrote:
>
> My TechniSat SkyStar 2 HD CI USB ID 14f7:0002 wasn't tuning DVB-S2 channels.
> Investigation revealed that it doesn't read DVB-S2 registers out of stb0899.
> Comparison with usb trafic of the Windows dri
Moi David
On 06.02.2014 11:45, David Jedelsky wrote:
My TechniSat SkyStar 2 HD CI USB ID 14f7:0002 wasn't tuning DVB-S2 channels.
Investigation revealed that it doesn't read DVB-S2 registers out of stb0899.
Comparison with usb trafic of the Windows driver showed the correct
communicat
My TechniSat SkyStar 2 HD CI USB ID 14f7:0002 wasn't tuning DVB-S2 channels.
Investigation revealed that it doesn't read DVB-S2 registers out of stb0899.
Comparison with usb trafic of the Windows driver showed the correct
communication scheme. This patch implements it.
The question is, w
Individually each of them work. When both of them are connected I get
corrupted video as soon as I tune to another channel. There is no
specific pattern in the logs, but now and then trouble about too large
packets when communicating with the CAM appears in dmesg, which could
make sense given the p
On Tue (Tuesday) 08.Jun (June) 2010, 12:14, Bjørn Mork wrote:
> Markus Rechberger writes:
>
> > Trident is also still improving the quality of their driver and
> > firmware, it very much makes
> > sense that they handle their driver especially since those DRX drivers
> > are very complex
> > (b
On Tue, Jun 8, 2010 at 12:14 PM, Bjørn Mork wrote:
> Markus Rechberger writes:
>
>> Trident is also still improving the quality of their driver and
>> firmware, it very much makes
>> sense that they handle their driver especially since those DRX drivers
>> are very complex
>> (basically too compl
Markus Rechberger writes:
> Trident is also still improving the quality of their driver and
> firmware, it very much makes
> sense that they handle their driver especially since those DRX drivers
> are very complex
> (basically too complex for being handled by the community, the drivers
> would j
On Tue, Jun 8, 2010 at 10:03 AM, Jan-Pascal van Best
wrote:
> On Tue, June 8, 2010 08:26, Tobias Maier wrote:
>>> The Micronas DRX series seems to 'evil' in that there
>>> is only a closed-source driver and the manufacturer doesn't cooperate
>>> with open source developers.
>> Have you asked them
On Tue, June 8, 2010 08:26, Tobias Maier wrote:
>> The Micronas DRX series seems to 'evil' in that there
>> is only a closed-source driver and the manufacturer doesn't cooperate
>> with open source developers.
> Have you asked them or are you simply asuming this because there is no
> open source dr
On 06/07/2010 09:01 AM, Tobias Maier wrote:
> on the card is a Micronas DRX 3913 JKA2 which is a combined analog
> cable, DVB-C and DVB-T Demodulator.
> any chance this device is supported soon? Anything i can do to get
> this going?
>
Hi Tobias,
I'm in the market for a USB DVB-C device, and I'
This is the device:
http://www.technisat.com/index9332.html?nav=PC_products,en,76-229
lsusb:
Bus 001 Device 005: ID 14f7:0003
on the card is a Micronas DRX 3913 JKA2 which is a combined analog
cable, DVB-C and DVB-T Demodulator.
best hit I can get with google is
http://www.tridentmicro.com/produ
gt;>>>>>> 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
>>
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 c
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+ mo
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
>>>> c
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 deco
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
>>
>&g
cept 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 l
On Sun, Jan 10, 2010 at 9:21 PM, Ian Wilkinson 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 de
HoP a écrit :
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 bas
2008 (Terratec Cinergy CI USB &
Hauppauge WinTV-CI).
That attempt seems to have stranded with Luc Brosens (who gave it a
shot back then) asking for help.
The chip manufacturer introduced a usb stick as well;
http://www.smardtv.com/index.php?page=products_listing&rubrique=pctv§ion=usbcam
bu
ratec Cinergy CI USB &
Hauppauge WinTV-CI).
That attempt seems to have stranded with Luc Brosens (who gave it a
shot back then) asking for help.
The chip manufacturer introduced a usb stick as well;
http://www.smardtv.com/index.php?page=products_listing&rubrique=pctv§ion=usbcam
but besi
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
> 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 CA
On Sun, Jan 10, 2010 at 5:09 PM, Emmanuel wrote:
> Markus Rechberger a écrit :
>>
>> On Sat, Jan 2, 2010 at 11:55 PM, HoP wrote:
>>
>>>
>>> Hi Jonas
>>>
>>>
>>>>
>>>> Does anyone know if there's any progress on
Markus Rechberger a écrit :
On Sat, Jan 2, 2010 at 11:55 PM, HoP wrote:
Hi Jonas
Does anyone know if there's any progress on USB CI adapter support?
Last posts I can find are from 2008 (Terratec Cinergy CI USB &
Hauppauge WinTV-CI).
That attempt seems to have stranded
On Sat, Jan 2, 2010 at 11:55 PM, HoP wrote:
> Hi Jonas
>
>> Does anyone know if there's any progress on USB CI adapter support?
>> Last posts I can find are from 2008 (Terratec Cinergy CI USB &
>> Hauppauge WinTV-CI).
>>
>> That attempt seems to
> BTW, Hauppauge's WinTV-CI looked much more promissing.
> At least when I started reading whole thread about it here:
> http://www.mail-archive.com/linux-...@linuxtv.org/msg28113.html
>
> Unfortunatelly, last Steve's note about not getting anything
> (even any answer) has disappointed me fully. An
Hi Jonas
> Does anyone know if there's any progress on USB CI adapter support?
> Last posts I can find are from 2008 (Terratec Cinergy CI USB &
> Hauppauge WinTV-CI).
>
> That attempt seems to have stranded with Luc Brosens (who gave it a
> shot back then) as
Hi All,
Does anyone know if there's any progress on USB CI adapter support?
Last posts I can find are from 2008 (Terratec Cinergy CI USB &
Hauppauge WinTV-CI).
That attempt seems to have stranded with Luc Brosens (who gave it a
shot back then) asking for help.
The chip manufacturer int
34 matches
Mail list logo
