Hi all,
a quick question about the tevii S480: I need to tune to a transponder
which does DVB-S2 45MS/s (QPSK). I have a dying TBS 6921 which was able
to sustain this rate flawlessly, but the spec of the S480 seems to
indicate that it should do it also, but I'd like to know if someone has
Hi all,
I am really interested in buying this board, and I would like to know if
someone has already tested it, with success or not!
Thx
Bye
Manu
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Hi all,
I have recently contacted TBS support to see if they have new products,
and they do have something in the pipeline: the 6921 and 8921, about to
be released, IIRC end of november. I am interested in whicether that has
good linux support. On this link you can check the specs and chips:
h
Goga777 a écrit :
I have recently purchased Proftuners S2-8000 PCI-e card which consist of :
* CX23885 pci-e interface
* STB6100 Frontend
* STV0900 Demodulator
Vendor company supposed that card has Linux support via additional
patch in their support page. I applied patch to v4l-dvb and
s2-lipli
T. Taner a écrit :
Hi,
I have recently purchased Proftuners S2-8000 PCI-e card which consist of :
* CX23885 pci-e interface
* STB6100 Frontend
* STV0900 Demodulator
Vendor company supposed that card has Linux support via additional
patch in their support page. I applied patch to v4l-dvb and
s2
Sorry to hijack the thread abit, but I have seen this in the specs:
# *Multi standard demodulation*
* DVBS2 QPSK, 8PSK
* Up to 45Msps DVBS, DVBS2 QPSK and 8PSK
Is it actually able to do 45 Msps DVB-S2 (in QPSK is sufficient for me)?
TIA
Bye
Manu
--
To unsubscribe from this list: send th
SE a écrit :
hi list
v4l-dvb still lacks fast and reliable dvb-s lock for stb08899 chipsets. This
problem was adressed by Alex Betis two years ago [1]+[2]resulting in a patch
[3] that made its way into s2-liplianin, not v4l-dvb.
With minor adjustments by me this patch now offers reliable dvb
rjkm a écrit :
Hi Johannes,
Johannes Stezenbach writes:
> > So, I would like to hear your opinions about how to handle such CA devices
> > regarding device names/types, the DVB API and user libraries.
>
> it looks like there isn't much interest from DVB developers
> in that topic... I'
Marko Ristola a écrit :
Hi.
I have written some Mantis bandwidth related
DMA transfer optimizations on June/July this year.
They are now waiting for approval by Manu Abraham.
Those reduce CPU pressure, increasing the bandwidth
that can be received from the DVB card. 45MS/s bandwidth
support wi
VDR User a écrit :
Look at the vp-1041 I think.
From what I gathered it is not able to do 45MS/s for DVB-S2.
Thanks anyway,
Manu
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger
Goga777 a écrit :
If someone has tested a DVB-S2 card at 45MS/s (I am interested in QPSK
moslty) please speak out ;-).
I dont need CI, dual tuner can be a bonus but definitely not mandatory.
I already asked the question, so sorry to come back again with it, but I
did not get a clear answer: the
If someone has tested a DVB-S2 card at 45MS/s (I am interested in QPSK
moslty) please speak out ;-).
I dont need CI, dual tuner can be a bonus but definitely not mandatory.
I already asked the question, so sorry to come back again with it, but I
did not get a clear answer: the only thing I know
OJ a écrit :
I am using this card:
http://www.linuxtv.org/wiki/index.php/Mystique_SaTiX-S2_Dual (v2)
According to the wiki I should use the ngene driver, but I am not able
to compile it. Downloaded the latest version from Mercury yesterday.
Error message when compiling:
$ make ngene
make -C /ho
code unknown a écrit :
Hi,
I am using a Terratec Cinergy S2 HD with Mantis driver and so far the
card runs without problems.
The only thing is that CAM seems not to be supported - it is defined
out from the source code:
#if 0
err = mantis_ca_init(mantis);
if (err < 0) {
dprintk(
Hi all,
just going on my quest for dvb-s2 card supporting 45MS/s rate for DVB-S2
QPSK. Does this card work reliably (CI included)?
And if you know of others working reliably (with or without CI) let me
know please.
TIA
Bye
Manu
--
To unsubscribe from this list: send the line "unsubscribe linux-
Hi all,
I found this link on a forum:
http://www.anysee.com/eng/product/anyseeE30PS2Plus.php
which, after more information seems to be a stv0903 based card with CI
which is tested (from the info given by the forum guy) at 45MS/s for
DVB-S2 (the saint-Graal for me to get my HD pay channels here
Konstantin Dimitrov a écrit :
On Mon, May 31, 2010 at 5:05 AM, Emmanuel <mailto:eall...@gmail.com>> wrote:
Konstantin Dimitrov a écrit :
hello, i can't comment on your questions about the Wiki, but i
made
the driver for TBS 6980 and i can ensur
Konstantin Dimitrov a écrit :
hello, i can't comment on your questions about the Wiki, but i made
the driver for TBS 6980 and i can ensure you that the driver will be
released as open-source under GPL as soon as i have permission to do
that, but compared to other cards at least even at the moment
Hi all,
I am looking for a high rate dvb-s2 card with CI support (dual tuner is
not a priority). I saw that the mystique seems to be supported, but I am
not sure about the CI support. Can someone tell me where we are now or
will be in the near future?
TIA
Bye
Manu
--
To unsubscribe from this l
Ronald Flou a écrit :
Hallo,
I own the following cards:
Mystique SaTiX-S2 V2 CI Dual
Mystique CI Interface f. Mystique SaTiX-S2 Dual
The Mystique SaTiX-S2 V2 CI Dual is working following the instructions
on http://www.linuxtv.org/wiki/index.php/Mystique_SaTiX-S2_Dual
and
http://www.vd
Hi all,
I am looking for a DVB-S/S2 card able to reliably tune to high symbol
rates DVB-S2 (here I have a transponder with 45MS/s), I also need this
with CI support. I have seen that mystix cards could be a good candidate
but I am not sure. PCI or PCIe is OK, dual tuner is not mandatory.
TIA,
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
Manu Abraham a écrit :
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 USB CI adapter support?
Last posts I can find are from
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 with Luc Brosen
Newsy Paper a écrit :
thanks to Andreas Regel + Manu Abraham for their work.
I just tested those problem transponders. If I set SR to 29998 instead of 3
they finally work with recent s2-liplian changeset.
Thank you for your great work and thanks to all the others involved in v4l
driver de
Dmitry Torokhov a écrit :
On Mon, Dec 07, 2009 at 06:54:39PM +0100, Emmanuel Fusté wrote:
Mauro Carvalho Chehab wrote:
In summary,
While the current EVIO[G|S]KEYCODE works sub-optimally for scancodes up
to 16 bytes
(since a read loop for 2^16 is not that expensive), the current
ut layer and finally using real
scancode -> keycode mappings everywhere if it is cleaner/convenient.
Best regards,
Emmanuel.
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
TV/KEY_DVD, etc.
Wait, wait, KEY_TV, KEY_DVD, KEY_TAPE - they should be used to select
media inputs in a device/application. My receiver accepts codees like
that.
Yes, it seem that there is confusion here.
Forget my proposition. It is a corner case that could be handled later
if needed
put layer to surcharge the vendor or device with a specific
value/mask for following keypresses of such remote. The mask could be
choose to generate out of bound value in regards of the used protocol
for the vendor or the device part to not overlap with another existing
remote.
Generate a complet
ion timing and low cpu/power usage (no
userspace busywait loop).
Device with hardware decoding and or no raw capability feed directly the input
subsystem to be dispatched to the different evdev devices.
lircd could still be used for his scripting part as seen in (1)
For the raw receivers, we could have in kernel decoders and/or lircd in user
space. It is just the mater of feeding a sort of lirc device instead of the in
kernel decoder. But please, raw ir data in the form of pulse event has nothing
to do with the input and event layer.
Splitting one source of input events into several different evdev interfaces is
a very simple thing at the input subsystem layer. And as explain, this
splitting should never never never be based on protocol/vendor/device/command
scancode groups but only based on mapping table.
My two cents,
Cheers,
Emmanuel.
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
It is perhaps time to resurrect Jon Smirl's work about In-kernel IR remote
control support ?
See http://marc.info/?l=linux-kernel&m=122591465821297&w=2 and all discussions
around it.
Rega
31 matches
Mail list logo