Johannes Stezenbach wrote:
+static void show_existing_tuning_data_files(void)
+{
+#ifndef PREFIX
+#define PREFIX "/usr/local"
+#endif
+ static const char* prefixlist[] = { PREFIX"/share/dvb",
+ "/usr/share/dvb", "/etc/dvb",
+ "/usr/share/doc/packages/dvb", 0 };
Hm, I don't l
Johannes Stezenbach wrote:
Guido Draheim wrote:
here is a patch that will make `dvbscan` to list the series of
initial-data-files being installed in the system. It works on
all of /etc/dvb/dvb-?/* /usr/share/dvb/dvb-?/* and of course
that /usr/share/doc/packages/dvb/dvb-?/* ... it may help user
Johannes Stezenbach wrote:
Guido Draheim wrote:
Index: test/Makefile
===
RCS file: /cvs/linuxtv/dvb-apps/test/Makefile,v
retrieving revision 1.3
diff -u -r1.3 Makefile
--- test/Makefile 14 Feb 2004 22:04:51 - 1.3
+++
From: "Johannes Stezenbach" <[EMAIL PROTECTED]>
> > and AFC is interesting even if there is no sync.
>
> (sync & 2) tests if the carrier has been recovered.
> If we don't have a carrier, then AFC is undefined
> (AFC := difference between given frequency and
> recovered carrier frequency).
True, t
Ingolf Haberer wrote:
>
> Btw. in function ves1820_ioctl case FE_READ_STATUS is this correct:
>
> if (sync & 2)
> *status |= FE_HAS_SIGNAL;
> if (sync & 2)
> *status |= FE_HAS_CARRIER;
>
> What means bit 1?
0 := ves1820 is in signal acquisition mode
1 := ves1820 is in tracking mode
Robert Schlabbach wrote:
> From: "Ingolf Haberer" <[EMAIL PROTECTED]>
>
> > kernel: ves1820_ioctl FE_READ_STATUS status=0x7 AFC=19 3997400Hz
> > kernel: ves1820_ioctl FE_READ_STATUS status=0x7 AFC=19 0Hz
>
> Hmm, the AFC output appears to be somewhat buggy:
>
> if (sync & 2)
>/* AFC only
Guido Draheim wrote:
>
> here is a patch that will make `dvbscan` to list the series of
> initial-data-files being installed in the system. It works on
> all of /etc/dvb/dvb-?/* /usr/share/dvb/dvb-?/* and of course
> that /usr/share/doc/packages/dvb/dvb-?/* ... it may help user
> to get a clue (it
Guido Draheim wrote:
> Ludwig Nussel wrote:
> >
> >JFYI, the SUSE rpm puts the remote config files in
> >/usr/share/av7110_loadkeys, include files in /usr/include/dvb and
> >the test programs in /usr/lib/dvb/test. The channels.conf* and scan
> >config files are just in /usr/share/doc/packages/dvb.
Guido Draheim wrote:
> Index: test/Makefile
> ===
> RCS file: /cvs/linuxtv/dvb-apps/test/Makefile,v
> retrieving revision 1.3
> diff -u -r1.3 Makefile
> --- test/Makefile 14 Feb 2004 22:04:51 - 1.3
> +++ test/Makefile
Ludwig Nussel wrote:
Johannes Stezenbach wrote:
Guido Draheim wrote:
Furthermore, I did add install-etc extra targets that do not only
handle bindir files - there are some files like *.rc5 and the
series of channels.conf-* that should be present in the non-source
installation to be usable by us
Ludwig Nussel wrote:
Johannes Stezenbach wrote:
Guido Draheim wrote:
Furthermore, I did add install-etc extra targets that do not only
handle bindir files - there are some files like *.rc5 and the
series of channels.conf-* that should be present in the non-source
installation to be usable by user
Ludwig Nussel wrote:
>
> JFYI, the SUSE rpm puts the remote config files in
> /usr/share/av7110_loadkeys, include files in /usr/include/dvb and
> the test programs in /usr/lib/dvb/test. The channels.conf* and scan
> config files are just in /usr/share/doc/packages/dvb.
>
hmmm, okay, so I added th
Johannes Stezenbach wrote:
> Guido Draheim wrote:
> > Furthermore, I did add install-etc extra targets that do not only
> > handle bindir files - there are some files like *.rc5 and the
> > series of channels.conf-* that should be present in the non-source
> > installation to be usable by users. At
Guido Draheim wrote:
>
> >>-CVSROOT := $(shell cat CVS/Root)
> >>+CVSROOT := # $(shell cat CVS/Root)
> >
> >Is that error rpm specific?
>
> May be - I did just check it on the source tree and there is no problem.
> So perhaps this is really rpm specific and I just use it in the .spec,
> please do
Guido Draheim wrote:
> Johannes Stezenbach wrote:
> >
> >I don't like that. If there is a reason to rename
> >some of the programs, then we should do it in our CVS
> >(e.g. scan was renamed to dvbscan recently because there
> >was a conflict with some other "scan" [reported by suse]).
> >
>
> just
Johannes Stezenbach wrote:
Guido Draheim wrote:
reading channels from file '/home/guidod/.szap/1/channels.conf'
OK.
+ if (1) snprintf(confname, len, "%s/.czap/%i/%s",
+homedir, adapter, CHANNEL_FILE);
What's with that if (1)?
just a habit to
Johannes Stezenbach wrote:
Guido Draheim wrote:
this one is partly independent from the `install` patches,
reading out CVS/ROOT with a gnumake shell command leads to an error.
This is the tarball, not the cvs repo ;-) .. only after patching
we can make && make install from toplevel.
...
-CVSROO
Guido Draheim wrote:
> reading channels from file '/home/guidod/.szap/1/channels.conf'
OK.
> + if (1) snprintf(confname, len, "%s/.czap/%i/%s",
> + homedir, adapter, CHANNEL_FILE);
What's with that if (1)?
Johannes
--
Info:
To unsubscribe send a mail
Guido Draheim wrote:
> this one is partly independent from the `install` patches,
> reading out CVS/ROOT with a gnumake shell command leads to an error.
> This is the tarball, not the cvs repo ;-) .. only after patching
> we can make && make install from toplevel.
...
> -CVSROOT := $(shell cat CVS/
Guido Draheim wrote:
> When installing the various binaries, lots of information in the source
> code is not present - and manual pages do not exist either. The
> following patches do something verrry simple - the top-of-source
> comment /** ... */ is converted to a #define USAGE "" \ and
> app
Guido Draheim wrote:
> Johannes Stezenbach wrote:
> >
> >IMHO that's the wrong place. These files should either go
> >to /usr/share/dvb/ or /usr/lib/dvb/, or maybe even
> >/usr/share/docs/dvb/exaples/.
> >
> >I will apply your patch anyway (because I don't care that
> >much about LSB compliance), b
Johannes Stezenbach wrote:
I don't like that. If there is a reason to rename
some of the programs, then we should do it in our CVS
(e.g. scan was renamed to dvbscan recently because there
was a conflict with some other "scan" [reported by suse]).
just saw it on cvs update - and you missed a few p
Johannes Stezenbach wrote:
Guido Draheim wrote:
Perhaps that needs to be discussed globally - the various dvb-related
packages build a lot of example or not-just-example userland tools. Now,
there are already quite a number of them and with rpm packaging I tend
to not look too close but just go
Johannes Stezenbach wrote:
Guido Draheim wrote:
[make install & DESTDIR stuff]
Very nice. Thanks!
Furthermore, I did add install-etc extra targets that do not only
handle bindir files - there are some files like *.rc5 and the
series of channels.conf-* that should be present in the non-source
Guido Draheim wrote:
> Perhaps that needs to be discussed globally - the various dvb-related
> packages build a lot of example or not-just-example userland tools. Now,
> there are already quite a number of them and with rpm packaging I tend
> to not look too close but just go over it and install _a
Johannes Stezenbach wrote:
Guido Draheim wrote:
The patch puts in a `make install-destdir` target which does
also handle the usual DESTDIR variable for the staging area.
I would rather replace the ill-defined "install" target
with your sane definition.
Btw, when not downloading the dvb-ttpci
Johannes Stezenbach wrote:
Guido Draheim wrote:
Johannes Stezenbach wrote:
See README.bt8xx.
Hmmm, it still does not say how to go about it as a packager. As far as
I understand it one should not use dvb-bt8xx on a kernel without the
absolute latest fashion, so in 2.4.21 one should `rm dvb-bt8x
Guido Draheim wrote:
> [make install & DESTDIR stuff]
Very nice. Thanks!
> Furthermore, I did add install-etc extra targets that do not only
> handle bindir files - there are some files like *.rc5 and the
> series of channels.conf-* that should be present in the non-source
> installation to be us
Guido Draheim wrote:
> Johannes Stezenbach wrote:
> >See README.bt8xx.
>
> Hmmm, it still does not say how to go about it as a packager. As far as
> I understand it one should not use dvb-bt8xx on a kernel without the
> absolute latest fashion, so in 2.4.21 one should `rm dvb-bt8xx.o` and
> not sh
Guido Draheim wrote:
>
> The patch puts in a `make install-destdir` target which does
> also handle the usual DESTDIR variable for the staging area.
I would rather replace the ill-defined "install" target
with your sane definition.
> Btw, when not downloading the dvb-ttpci firmware, there is a
>
Johannes Stezenbach wrote:
Guido Draheim wrote:
Wolfgang Rohdewald wrote:
depmod: *** Unresolved symbols in /lib/modules/2.4.24/misc/dvb-bt8xx.o
depmod: bttv_get_i2c_adap
depmod: *** Unresolved symbols in
/lib/modules/2.4.21-0.13mdk/kernel/3rdparty/mod_dvb/dvb-bt8xx.o
depmod: b
Guido Draheim wrote:
> Wolfgang Rohdewald wrote:
> >depmod: *** Unresolved symbols in /lib/modules/2.4.24/misc/dvb-bt8xx.o
> >depmod: bttv_get_i2c_adap
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.21-0.13mdk/kernel/3rdparty/mod_dvb/dvb-bt8xx.o
> depmod: bttv_get_i2c_adap
Microspace
http://www.microspace.com
Quoting Jeremy Hall <[EMAIL PROTECTED]>:
> What sat provider are you using with this?
>
> In the new year, Andreas Schiffler wrote:
> >
> > just a quick update on my ventures in data reception services in the US
> > as discussed a few days ago on the list.
Q wrote:
Hi can anyone on this list tell me if there is a working Linux driver
for Wintv Nova-T?
Yes the linux-dvb driver code, see http://www.linuxtv.org/
Also what is the fron't end in Linux I should use to replace the WinTV
Windows based front end?
I would like to continue to be able to she
Hi can anyone on this list tell me if there is a
working Linux driver for Wintv Nova-T?
Also what is the fron't end in Linux I should use
to replace the WinTV Windows based front end?
I would like to continue to be able to shedule
recordings etc, just as I can in Windows.
Thanks in adv
Perhaps that needs to be discussed globally - the various dvb-related
packages build a lot of example or not-just-example userland tools. Now,
there are already quite a number of them and with rpm packaging I tend
to not look too close but just go over it and install _all_ of them.
In order to not
Marcus Metzler wrote:
Guido Draheim writes:
> [1 ]
> I had sent the patches to metzlerbros (rjkm) but so far no reply. So I
Wrong brother.
okay then ;-)
> think it is best to put them on linux-dvb message archive for other people
> who go to make rpm packages of libdvb - these patches migh
Guido Draheim writes:
> [1 ]
> I had sent the patches to metzlerbros (rjkm) but so far no reply. So I
Wrong brother.
> think it is best to put them on linux-dvb message archive for other people
> who go to make rpm packages of libdvb - these patches might help you. ;-)
>
Why should I pat
Johannes Stezenbach wrote:
> Matthias Appel wrote:
>> I was able to view TV with a Hauppauge Nexus-s using several drivers.
>> Now I have dvb-kernel from CVS running with kernel 2.4.21 (suse).
>> These days I bought a new DVB-s budget from KNC1:
>>
>> > KNC One DVB-S ver B1
>> > SU1278/SH - 3112
Hi,
I'm confused about interrupt handling in the dvb-bt8xx driver. It looks
like the dvb-bt8xx driver has its own interrupt handler, which checks
most interrupts including FBUS (pixel data fifo overrun).
However, I'm getting some messages in my kernel log from the interrupt
handler in the bttv dr
Wolfgang Rohdewald wrote:
> On Freitag 13 Februar 2004 20:17, Matthias Appel wrote:
>> With ./insmod debug (insmod ./mt312.o is commented out) i get no
>> remarkable errors, but when starting VDR some kernel Oopses. Needless
>> to say that there was no output to my TV :-(
> did you use the same g
On Sun, Feb 15, 2004 at 12:23:14AM +1100, [EMAIL PROTECTED] wrote:
> Does anyone have a fool proof way to compile the avermedia drivers. I've been
> tring for about a week and a half and just can't do it. I'm down to about six
> compile errors for bt878.o, dvb-bt8xx.o and sp887x.o. I can get the
Hey
Does anyone have a fool proof way to compile the avermedia drivers. I've been
tring for about a week and a half and just can't do it. I'm down to about six
compile errors for bt878.o, dvb-bt8xx.o and sp887x.o. I can get the others but
can't insert bttv.o. Will someone that has achieve this
Dave, your a super star!
On Sat, 2004-02-14 at 12:58, Dave Chapman wrote:
> Scott White wrote:
> > I cant seem to get any output from my DVB-T card and I'm going to have
> > to revert to you guys for some advice. I've used this card plenty of
> > times in the past so I am doing something wrong.
Scott White wrote:
I cant seem to get any output from my DVB-T card and I'm going to have
to revert to you guys for some advice. I've used this card plenty of
times in the past so I am doing something wrong. Any suggestions or
pointers would be gratefully received
Tzap gives
/tzap "BBC ONE"
usin
I had sent the patches to metzlerbros (rjkm) but so far no reply. So I
think it is best to put them on linux-dvb message archive for other people
who go to make rpm packages of libdvb - these patches might help you. ;-)
cheers,
-- guido http://google.de/search?q=gui
Up to now I am using wrapper scripts to set -c /abs/path/to/channel.conf
for secondary adapter(s). Since I am there patching dvb-apps, here are
some patches that will make the channel switchters to look into
per-adapter subdirectories first - i.e.
$ dvb_szap -a 1 pro7
reading channels from file '/h
this one is partly independent from the `install` patches,
reading out CVS/ROOT with a gnumake shell command leads to an error.
This is the tarball, not the cvs repo ;-) .. only after patching
we can make && make install from toplevel.
cheers
-- guido http://google.
When installing the various binaries, lots of information in the source
code is not present - and manual pages do not exist either. The
following patches do something verrry simple - the top-of-source
comment /** ... */ is converted to a #define USAGE "" \ and
appended to the simple-help string
I cant seem to get any output from my DVB-T card and I'm going to have
to revert to you guys for some advice. I've used this card plenty of
times in the past so I am doing something wrong. Any suggestions or
pointers would be gratefully received
Tzap gives
/tzap "BBC ONE"
using '/dev/dvb/adapte
Wolfgang Rohdewald wrote:
On Samstag 14 Februar 2004 11:36, Guido Draheim wrote:
Additionally, I had seen unresolved symbols (from depmod)
about bt8xx IIRC but the current modules.dep does not give
me a hint as to what that were back then. May be I'll check
later into this.
maybe those?
[EMAI
Guido Draheim wrote:
Yes. I did just a test recording. Now there is just one problem left:
the 'szap' command does not have a '-c' flag anymore which used to
be there in the old dvb modules 'szap' version. That breaks my scripts
and at the moment I do not know how to access the second card - whic
Actually, almost all subdirectories of linuxtv-dvb-apps-1.1.0 did not
have any `make install` target at all. The patches do append such
targets and enough of them that you can do `make install` from the
toplevel directory.
While being there, some targets did have a `make install` but they
were usin
On Samstag 14 Februar 2004 11:36, Guido Draheim wrote:
> Additionally, I had seen unresolved symbols (from depmod)
> about bt8xx IIRC but the current modules.dep does not give
> me a hint as to what that were back then. May be I'll check
> later into this.
maybe those?
[EMAIL PROTECTED]:/var/log#
Okay, so now that I see the packages are functional, let's get
slowly into the patch queue - quite a number coming up ;-)
* linuxtv-dvb-1.1.0 build-2.4 make install
doing `make install` will effectivly execute this:
-su -c "mkdir -p $(DEST); cp -v $(obj-m) $(DEST); \
depmod -a ; sh ../
Michael Hunold wrote:
Hello Guido,
On 14.02.2004 01:31, Guido Draheim schrieb:
Now finally, I want to check my two ttpci cards - before that I was to
invent a modules.conf since linuxtv-dvb does not contain anymore some
modules.conf file as it used to be in the old dvb-modules series. Anyway,
Hello Guido,
On 14.02.2004 01:31, Guido Draheim schrieb:
Now finally, I want to check my two ttpci cards - before that I was to
invent a modules.conf since linuxtv-dvb does not contain anymore some
modules.conf file as it used to be in the old dvb-modules series. Anyway,
one can guess a list base
57 matches
Mail list logo
