Hi,
In dvb-pll.c
freq = (div * stepsize) - offset
From debug get these values
freq = 19167 div = 1367
So i calculated offset using
( 1367 * 16) - 19167 = 26165755
What am i doing wrong, offsets are in the range of 125000.
Cheers Rob.
On Tue, June 5, 2007 10:27, Simon Baxter wrote:
Sorry - can you help me with the syntax for gnutv? I only get the menu!!
Try something like:
gnutv -channels channel.conf -out stdout NAME_OF_A_CHANNEL outfile.mpg
Let that run for a while and then see if you can play outfile.mpg with
xine or
En/na Paul ha escrit:
Q 2. DVB_Frontend_API document output is in what units (eg Db , % or
someother value)
eg
Frontend Function Calls
FE_READ_BER what units are these
Currend dvb api specification doesn't say anything.
An older version of the specification
On Tue, June 5, 2007 10:27, Simon Baxter wrote:
Sorry - can you help me with the syntax for gnutv? I only get the
menu!!
Try something like:
gnutv -channels channel.conf -out stdout NAME_OF_A_CHANNEL
outfile.mpg
Let that run for a while and then see if you can play outfile.mpg with
Hi Paul,
On Wed, 2007-06-06 at 13:02 +1000, Paul wrote:
I have a few questions and suggestions now I see some activity on the dvb-apps
Q.1 tzap
This seems loop indefinately can we also have option to limit the output to
a count or
duration eg -count 10 or -time 5 secs
Have you tried
On 6/06/2007 6:48 PM, Chris Malarky wrote:
Hi Paul,
On Wed, 2007-06-06 at 13:02 +1000, Paul wrote:
I have a few questions and suggestions now I see some activity on the
dvb-apps
Q.1 tzap
This seems loop indefinately can we also have option to limit the output to
a count or
duration
Hi,
On Wed, 2007-06-06 at 19:20 +1000, Paul wrote:
so femon and tzap work together? ahhh
They are both separate programs, but the data they report comes from the
same source.
Actually the big picture is I want to write a script which I can log these
values in a
database so I can gather
Le mercredi 06 juin 2007 05:28, Simon Baxter a écrit :
I'm trying to get a picture out of my budget TT-C1500 card/ci/cam and
having little success (but am making progress!). My cable provider
encrypts everything - so it has to run through the CAM.
the dvb-apps 'dvbstream' gives me the
On Tue, Jun 05, 2007 at 09:16:26PM -0700, Trent Piepho wrote:
On Sat, 2 Jun 2007, Johannes Stezenbach wrote:
Then I2C_M_STOP still makes sense, but the patch should document
that it's used only a workaround for broken hardware.
Well, I tried but no one on the i2c list liked the
Hi,
Am Mittwoch, 6. Juni 2007 12:22 schrieb Simon Baxter:
Le mercredi 06 juin 2007 05:28, Simon Baxter a écrit :
I'm trying to get a picture out of my budget TT-C1500 card/ci/cam and
having little success (but am making progress!). My cable provider
encrypts everything - so it has to run
Trent Piepho wrote:
Does the stv0297 require that no other i2c traffic, to a different device,
appear between the write and the read? Something like:
S stv_addr_W A reg_addr A P
S tuner_addr_W A tuner_data1 A tuner_data2 A P
S stv_addr_R A reg_data NA P
Will the i2c message to the
[EMAIL PROTECTED] ~]# kaffeine
kbuildsycoca running...
0
/dev/dvb/adapter0/frontend0 : opened ( ST STV0297 DVB-C )
/dev/dvb/adapter0/frontend1 : : No such file or directory
/dev/dvb/adapter1/frontend0 : : No such file or directory
QLayout unnamed added to QWidget unnamed, which already has
CamThread: cam 0 is ready
CamThread: LLCI cam slot detected
CamThread: pmt sent to cam
This looks correct (pmt has been found, encoded uploaded to the cam).
Are
you sure your cam works correctly with the used scrambling system /
smart
card?
The CAM/Smartcard work fine with the BDA
CamThread: cam 0 is ready
CamThread: LLCI cam slot detected
CamThread: pmt sent to cam
This looks correct (pmt has been found, encoded uploaded to the cam).
Are
you sure your cam works correctly with the used scrambling system /
smart
card?
The CAM/Smartcard work fine
Trent Piepho wrote:
I'm still unclear on exactly what the stv0297 requires. The datasheet says
one can't use a repeated start, but must have a stop between a read and a
write. That's simple enough, but has anyone actually verified that the
datasheet is really correct? I know many datasheets
Hello everybody reading this,
as outline attachment I send:
A. the unfinished driver called cx878, to be implied into the current
mercurial tree instead of /drivers/media/dvb/bt8xx it should be:
/drivers/media/dvb/cx878 (cx878.tar.bz2). Makefile and Kconfig need to be
changed then.
B. a dummy
e9hack wrote:
Trent Piepho wrote:
Does the stv0297 require that no other i2c traffic, to a different device,
appear between the write and the read? Something like:
S stv_addr_W A reg_addr A P
S tuner_addr_W A tuner_data1 A tuner_data2 A P
S stv_addr_R A reg_data NA P
Will
Hello everybody reading this,
as outline attachment I send:
A. the unfinished driver called cx878, to be implied into the current
mercurial tree instead of /drivers/media/dvb/bt8xx it should be:
/drivers/media/dvb/cx878 (cx878.tar.bz2). Makefile and Kconfig need to be
changed then.
B. a dummy
Oliver Endriss wrote:
Could you please test whether this works:
S stv_addr_W A reg_addr A Sr stv_addr_R A reg_data NA P
It doesn't work.
The following does work, if the Stop-Start isn't located in the same upload
command of the saa7146:
S stv_addr_W A reg_addr A P S stv_addr_R A reg_data
This is a section of dmesg from FC4 that works on initial boot
Linux version 2.6.16-1.2111_FC4 ([EMAIL PROTECTED]) (gcc version 4.0.2 20051125
(Red Hat 4.0.2-8)) #1 Sat May 20 19:59:40 EDT 2006
[snip]
hw_random hardware driver 1.0.0 loaded
Linux video capture interface: v1.00
cx2388x v4l2
e9hack wrote:
Oliver Endriss wrote:
Could you please test whether this works:
S stv_addr_W A reg_addr A Sr stv_addr_R A reg_data NA P
It doesn't work.
Hm, I wonder how stv0297_readregsI() in stv0297_cs2.c could ever work.
Any idea?
The following does work, if the Stop-Start isn't
Oliver Endriss wrote:
e9hack wrote:
Oliver Endriss wrote:
Could you please test whether this works:
S stv_addr_W A reg_addr A Sr stv_addr_R A reg_data NA P
It doesn't work.
Hm, I wonder how stv0297_readregsI() in stv0297_cs2.c could ever work.
Any idea?
Answering myself:
Peter D. wrote:
On Wednesday 30 May 2007 16:05, Sid Boyce wrote:
[snip]
CORE cx88[0]: subsystem: 17de:08a4, board: KWorld/VStream XPert DVB-T
[snip]
Any ideas?
Thanks and Regards
Sid.
I have a similar card, except it is 17de:08a6.
Is there any chance of static damage? Is the card
Any idea on Q3:
Q3. if I have two DVB devices how can I determine what device this maps?
What device manufacturer is adapter0?
is this stored somewhere in /proc filesystem?
I have two cards and adapter0 performs better than adapter1 but I want to be
sure which
that is.
I could try
Have you tried 'udevinfo' ? That will give you the specs on any device.
MD
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Paul
Sent: Wednesday, June 06, 2007 9:26 PM
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] dvb-apps questions
Any idea on
while I was browsing udev I came up with this primitive way:
cd /sys/class/dvb
f0device=`cat dvb0.frontend0/device/device`
f0vendor=`cat dvb0.frontend0/device/vendor`
echo frontend0 : v=$f0vendor dev=$f0device
lspci -d $f0vendor:$f0device
f1device=`cat dvb1.frontend0/device/device`
26 matches
Mail list logo
