[linux-dvb] Re: API changes (was: C/A routing Question)
Ralph Metzler wrote: Hi, Florian Schirmer writes: Yes, this should be the responsibility of the demux. Just add capability ioctls there. The frontend could be rather dumb. Syncing to TS boundaries, etc. can also be handled by the demux. It will have to do that anyway for budget cards which deliver unaligned data (e.g. Bt878/fusion cards). Demux hardware usually does it by itself. In the latest Fusion code i've pushed all the sync handling down to the (soft) demux. It needs some tweaks here and there but it basically works. I.e. open(/dev/.../dvrN), then DMX_DVR_SET_PIDS(int num, int16_t pids[])? Would a PID bitmap as parameter also make sense if many PIDs are used? On the other hand, the PID number usually probably will not be that high and one can use 0x2000 for the whole TS again. Sounds good and makes sense to me. Beside this it's pretty trivial to implement, we wanted to add a PID lookup bitmap anyway... Yes. This should make recording all PIDs of one service very easy. A software filter implementation should also be simple. Now this kind of filter even seems to fit perfectly to some hardware as Rob McConnell described in his mail. IMHO the dvr is comletely useless. Instead of adding more and more features to it we should remove it. At the same time we have to change the demux API to allow more than one pid filter per fd. If it is possible to route more than one pid into the same buffer you will basically get the functions the dvr device provides. If we do it carefully we're able to extend the API without loosing compatibility. Yes, let's throw the dvr device out. ok. We still need a precise API proposal. I dont know alot about hw that provides dvr units. But the hw/driver should be able to deal with that internally without forcing the user to know about wether it has dvr support or not. If there is any reason why the hw or sw requires a dvr device please elaborate why. Thx! As long as the dvr units are connected to one of the other demux channels (same input) this should be fine. One should also consider if the driver should be able to tell the application what it can do in hardware and with direct DMA and what has to be emulated and copied in software. Especially on hardware with low power CPUs (low MHz ARM/MIPS) this could make big differences. yes, and especially this hardware has usually a very flexible and powerful DMA controller, we should use it as much as possible... Holger -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: Compilation under RedHat 8.0
I did not succeed compiling DVB on a RedHat 8.0 station, installed with kernel-headers and kernel-source. Can anyone runnig RedHat 8.0 be so kind to help me? I have the same problem. Can't get this compiled. I already posted something on this 2 or 3 days ago, but no one answered me. topic is : [linux-dvb] can't compile CVS on my new RH8.0 Here, I'm showing the output from make Regards, -- Alexandre CONRAD Research Development tel : +33 1 30 80 55 00 fax : +33 1 30 56 50 20 TLV 6, rue de la plaine 78860 - SAINT NOM LA BRETECHE FRANCE -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: Compilation under RedHat 8.0
Le Jeudi 27 Février 2003 09:49, Alexandre CONRAD a écrit : I have the same problem. Can't get this compiled. I already posted something on this 2 or 3 days ago, but no one answered me. DVB drivers will not be included in RedHat distro before a long time (not even in 8.1). So we need to find a solution. What I would like to do is release an RPM for http://www.freshrpm.org. Before everything, how can we compile the modules? Please help. This is so unusual to go directly to make without ./configure first. Would anyone be so kind to help us. We don't even know if a compilation under Redhat 8.0 is technicaly possible. Cheers, Jean-Michel -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Newbie question
Hi all, I've got the Technotrend TT PCline premium T card installed on Linux Mandrake 8.2 (kernel 2.4.18) When I do 'make insmod' I got some error messages, what should I do to make it work? Here is what I got: /usr/src/linux/scripts/pathdown.sh: TOPDIR: parameter null or not set DIR=`pwd`; (cd /usr/src/linux; make SUBDIRS=$DIR modules) make[1]: Entering directory `/usr/src/linux-2.4.18-6mdk' make -C /root/DVB/driver CFLAGS=-D__KERNEL__ -I/usr/src/linux-2.4.18-6mdk/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i586 -DMODULE -DMODVERSIONS -include /usr/src/linux-2.4.18-6mdk/include/linux/modversions.h MAKING_MODULES=1 modules make[2]: Entering directory `/root/DVB/driver' ld -m elf_i386 -r -o dvb-core.o dmxdev.o dvb_demux.o dvb_net.o dvb_i2c.o dvb_filter.o dvb_frontend.o dvbdev.o compat.o dvb_ksyms.o make -C av7110 modules make[3]: Entering directory `/root/DVB/driver/av7110' ld -m elf_i386 -r -o dvb-ttpci.o saa7146_core.o saa7146_v4l.o av7110.o av7110_ir.o make[3]: Entering directory '/root/DVB/driver/av7110' make -C frontends modules make[3]: Entering directory `/root/DVB/driver/frontends' make[3]: Nothing to be done `modules'. make[3]: Leaving directory `/root/DVB/driver/frontends' make[2]: Leaving directory `/root/DVB/driver' make[1]: Leaving directory `/usr/src/linux-2.4.18-6mdk' ( \ insmod videodev;\ \ insmod dvb-core.o dvb_shutdown_timeout=0; \ make -C frontends insmod; \ make -C av7110 insmod; \ ) Using /lib/modules/2.4.18-6mdk/kernel/drivers/media/video/videodev.o.gz make[1]: Entering directory '/root/DVB/driver/frontends' insmod alps_bsrv2.o; insmod alps_tdmb7.o; insmod alps_tdlb7.o; insmod grundig_29504-401.o; insmod grundig_29504-491.o; insmod stv0299.o; insmod ves1820.o; make[1]: Leaving directory `/root/DVB/driver/frontends' make[1]: Entering directory `/root/DVB/driver/av7110' insmod input; \ insmod evdev; \ insmod dvb-ttpci.o; Using /lib/modules/2.4.18-6mdk/kernel/drivers/input/input.o.gz Using /lib/modules/2.4.18-6mdk/kernel/drivers/input/evdev.o.gz make[1]: *** [insmod] Segmentation fault make[1]: Leaving directory `/root/DVB/driver/av7110' make: *** [insmod] Error 2 After this, my system or some processes often freezes, can anyone help me? Besides, I got a former Technotrend Card TT-DVB-T PCi bought in 2001. Can I use the NEWSTRUCT driver to make it work? Thanks a lot for your help, Anne-Laure -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] AW: Re: API changes (was: C/A routing Question)
Hi,
Yes, let's throw the dvr device out.
ok. We still need a precise API proposal.
Here we go:
New IOCTLs:
int ioctl(int fd, int request = DMX_ADD_FILTER, struct dmx_filter_params
*params);
typedef enum
{
DMX_FMT_TS,
DMX_FMT_PES,
DMX_FMT_SEC,
DMX_FMT_PES_HDR,
DMX_FMT_STC,
DMX_FMT_ES,
...
} dmx_format_t;
typedef enum
{
DMX_DEC_NONE,
DMX_DEC_VIDEO0,
DMX_DEC_VIDEO1,
DMX_DEC_VIDEO2,
DMX_DEC_AUDIO0,
DMX_DEC_AUDIO1,
DMX_DEC_AUDIO2,
DMX_DEC_PCR0,
DMX_DEC_PCR1,
DMX_DEC_PCR2,
...
} dmx_decoder_t;
struct dmx_filter_params
{
uint32_t num;
uint16_t pid;
uint32_t fe_map;
#define FE_ALL 0
#define FE_MEM 1
#define FE_HW1 2
#define FE_HW2 4
#define FE_HW2 8
dmx_format_t format;
dmx_decoder_t decoder;
dmx_filter_t sec_filter;
uint32_t sec_timeout;
uint32_t sec_flags;
#define DMX_CHECK_CRC 1
#define DMX_ONESHOT 2
#define DMX_IMMEDIATE_START 4
}
- Will add filters.
- All output will be routed to the same fd.
- Some restrictions apply: Only filters of the same type (TS or PES or SEC)
are allowed.
- Num must be unique (or should be set by the demux?)
- Merging in section support is not necessesary but makes sense (IMHO)
- dmx_decoder_t can be split into just a single type of every decoder and
then adding a new uint32_t dec_num; field. Dunno what is more reasonable.
- Internally each filter still maps into a single feed. So there is no need
to fiddle around with any device driver. (Hopefully :)
- I've added an fe_map in favour to a SELECT_SOURCE IOCTL. Makes more sense
i think. Now you can select the fe on the fly.
- The old interface can be mapped with sane defaults (eg FE_ALL) to the new
interface if we want to maintain compatibility.
int ioctl(int fd, int request = DMX_DEL_FILTER, uint32_t num);
- Will remove filters
- num must be the value as specified (or returned) by the DMX_ADD_FILTER
IOCTL.
Comments?
Bye,
Florian
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as
subject.
[linux-dvb] Re: SV: Re: Compilation under RedHat 8.0
Le Jeudi 27 Février 2003 10:26, Martin Altemark a écrit : You have to recompile the kernel since the kernel shipped with 8.0 do not loadable module support, plus that you need to add video for linux and i2c modules. The stock kernel as loadable module support, of course !!! Could you tell me the names of the modules for video for linux and i2c, so that I try loading them manually. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] vdr problem
Hi, I have mapped the keys of PC Keyboard to work with VDR application.I can enter into the channels menu and change the parameters.I changed the freq-1150 S/R 28125 POL-H VPID-517 APID-700 and said ok but it doent show any video.I have changed the channels.conf as follows RTPi:1150:h:S100.5E:28125:517:700:0:0:30:0:0:0 DW:1150:h:S100.5E:28125:2305:2306:0:0:1:0:0:0 RAIi:1150:h:S100.5E:28125:513:644:0:0:3:0:0:0 I also changed the setup.conf to LnbFrequHi = 0 LnbFrequLo = 0 LnbSLOF = 0 I am using vdr-1.0.0pre2. Regards, Sheetal Pandey ** This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated. ** -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: Compiling dvb-kernel
Hello Hagen, I try to compile the actual dvb-kernel cvs Version (cvs download 20 minutes ago) to use under actual 2.5.63 kernel. Making and restarting without problems. I can't insert the dvb-ttpci module (oops). I noticed this, too. Runtime insertion of the modules and in-kernel-compiled driver both don't work at the moment. With loadable modules, you'll get an oops upon insertion, with the driver being compiled into the kernel, the driver will start up ok, but the first access to the video-part (ie. /dev/video0) will oops, too. Perhaps some change in the PCI/module subsystem between .59 and .63 triggeres some bug. I'll investigate this. CU Michael. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: can't compile CVS on my new RH8.0
Hi, since Redhat seems to patch the kernel include files you'll have to find out this on your own. I don't have the RH includes here. First of all try to find out what's wrong in /usr/src/linux-2.4.18-14/include/linux/sched.h line 6. Probably the RH guys screwed up something and you have to include another file before sched.h in order to provide the proper declaration of this thing. Holger Alexandre CONRAD wrote: Hi, cvs -d :pserver:[EMAIL PROTECTED]:/cvs/linuxtv co DVB cd DVB/ cvs update -dPA make (cd driver; make) /usr/src/linux/scripts/pathdown.sh: line 4: TOPDIR: parameter null or not set make[1]: Entering directory `/usr/local/src/DVB/driver' DIR=`pwd`; (cd /usr/src/linux; make SUBDIRS=$DIR modules) make[2]: Entering directory `/usr/src/linux-2.4.18-14' make -r -f tmp_include_depends all make[3]: Entering directory `/usr/src/linux-2.4.18-14' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/usr/src/linux-2.4.18-14' make -C /usr/local/src/DVB/driver CFLAGS=-D__KERNEL__ -I/usr/src/linux-2.4.18-14/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -DMODULE -DMODVERSIONS -include /usr/src/linux-2.4.18-14/include/linux/modversions.h MAKING_MODULES=1 modules make[3]: Entering directory `/usr/local/src/DVB/driver' gcc -D__KERNEL__ -I/usr/src/linux-2.4.18-14/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -DMODULE -DMODVERSIONS -include /usr/src/linux-2.4.18-14/include/linux/modversions.h -I ../include -I . -MD -nostdinc -I /usr/lib/gcc-lib/i386-redhat-linux/3.2/include -DKBUILD_BASENAME=dmxdev -c -o dmxdev.o dmxdev.c In file included from /usr/src/linux-2.4.18-14/include/linux/vmalloc.h:4, from dmxdev.c:24: /usr/src/linux-2.4.18-14/include/linux/sched.h:6: invalid suffix on integer constant /usr/src/linux-2.4.18-14/include/linux/sched.h:6: parse error before numeric constant /usr/src/linux-2.4.18-14/include/linux/sched.h:6: warning: function declaration isn't a prototype In file included from /usr/src/linux-2.4.18-14/include/linux/ptrace.h:24, from /usr/src/linux-2.4.18-14/include/linux/binfmts.h:4, from /usr/src/linux-2.4.18-14/include/linux/sched.h:9, from /usr/src/linux-2.4.18-14/include/linux/vmalloc.h:4, from dmxdev.c:24: [...] /usr/src/linux-2.4.18-14/include/linux/devfs_fs_kernel.h: In function `devfs_unregister_chrdev_R77f3e0ce': /usr/src/linux-2.4.18-14/include/linux/devfs_fs_kernel.h:256: warning: implicit declaration of function `unregister_chrdev_Rc192d491' /usr/src/linux-2.4.18-14/include/linux/devfs_fs_kernel.h: In function `devfs_unregister_blkdev_R5ca0f0f0': /usr/src/linux-2.4.18-14/include/linux/devfs_fs_kernel.h:260: warning: implicit declaration of function `unregister_blkdev_Reac1c4af' In file included from dmxdev.c:30: compat.h: In function `cond_resched': compat.h:56: warning: implicit declaration of function `schedule_R4292364c' dmxdev.c: In function `dvb_dmxdev_buffer_write': dmxdev.c:86: warning: implicit declaration of function `printk_R1b7d4074' dmxdev.c: In function `dvb_dvr_release': dmxdev.c:255: warning: implicit declaration of function `vfree_R2fd1d81c' dmxdev.c: In function `dvb_dmxdev_filter_timer': dmxdev.c:350: warning: implicit declaration of function `del_timer_Rfc62f16d' dmxdev.c:354: `jiffies_R0da02d67' undeclared (first use in this function) dmxdev.c:355: warning: implicit declaration of function `add_timer_Ra19eacf8' make[3]: *** [dmxdev.o] Error 1 make[3]: Leaving directory `/usr/local/src/DVB/driver' make[2]: *** [_mod_/usr/local/src/DVB/driver] Error 2 make[2]: Leaving directory `/usr/src/linux-2.4.18-14' make[1]: *** [here] Error 2 make[1]: Leaving directory `/usr/local/src/DVB/driver' make: *** [dvb] Error 2 Thanks for your help. Regards, -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: Compilation under RedHat 8.0
Jean-Michel POURE wrote: Le Jeudi 27 Février 2003 09:49, Alexandre CONRAD a écrit : I have the same problem. Can't get this compiled. I already posted something on this 2 or 3 days ago, but no one answered me. DVB drivers will not be included in RedHat distro before a long time (not even in 8.1). So we need to find a solution. What I would like to do is release an RPM for http://www.freshrpm.org. Before everything, how can we compile the modules? Please help. This is so unusual to go directly to make without ./configure first. Would anyone be so kind to help us. We don't even know if a compilation under Redhat 8.0 is technicaly possible. Read the README and INSTALL file. When your distribution screwed up the kernel include files get a fresh and recent kernel from http://www.kernel.org/, configure + install this one before building the DVB driver. Holger -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: AW: Re: API changes (was: C/A routing Question)
Hi Florian,
We need an additional info ioctl() to query the demux capabilities, e.g.
the allowed number of filters of a particular type in this demux
channels before we can request a filter on a specific filter_params-num.
Holger
Florian Schirmer wrote:
Hi,
Yes, let's throw the dvr device out.
ok. We still need a precise API proposal.
Here we go:
New IOCTLs:
int ioctl(int fd, int request = DMX_ADD_FILTER, struct dmx_filter_params
*params);
typedef enum
{
DMX_FMT_TS,
DMX_FMT_PES,
DMX_FMT_SEC,
DMX_FMT_PES_HDR,
DMX_FMT_STC,
DMX_FMT_ES,
...
} dmx_format_t;
typedef enum
{
DMX_DEC_NONE,
DMX_DEC_VIDEO0,
DMX_DEC_VIDEO1,
DMX_DEC_VIDEO2,
DMX_DEC_AUDIO0,
DMX_DEC_AUDIO1,
DMX_DEC_AUDIO2,
DMX_DEC_PCR0,
DMX_DEC_PCR1,
DMX_DEC_PCR2,
...
} dmx_decoder_t;
struct dmx_filter_params
{
uint32_t num;
uint16_t pid;
uint32_t fe_map;
#define FE_ALL 0
#define FE_MEM 1
#define FE_HW1 2
#define FE_HW2 4
#define FE_HW2 8
dmx_format_t format;
dmx_decoder_t decoder;
dmx_filter_t sec_filter;
uint32_t sec_timeout;
uint32_t sec_flags;
#define DMX_CHECK_CRC 1
#define DMX_ONESHOT 2
#define DMX_IMMEDIATE_START 4
}
- Will add filters.
- All output will be routed to the same fd.
- Some restrictions apply: Only filters of the same type (TS or PES or SEC)
are allowed.
- Num must be unique (or should be set by the demux?)
- Merging in section support is not necessesary but makes sense (IMHO)
- dmx_decoder_t can be split into just a single type of every decoder and
then adding a new uint32_t dec_num; field. Dunno what is more reasonable.
- Internally each filter still maps into a single feed. So there is no need
to fiddle around with any device driver. (Hopefully :)
- I've added an fe_map in favour to a SELECT_SOURCE IOCTL. Makes more sense
i think. Now you can select the fe on the fly.
- The old interface can be mapped with sane defaults (eg FE_ALL) to the new
interface if we want to maintain compatibility.
int ioctl(int fd, int request = DMX_DEL_FILTER, uint32_t num);
- Will remove filters
- num must be the value as specified (or returned) by the DMX_ADD_FILTER
IOCTL.
Comments?
Bye,
Florian
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as
subject.
[linux-dvb] ts analyzer
Hi list, I would get out some information from a transport stream read from fd_demux by unsigned char buffer[188]; is there any struct to know? Something could help me with sample-code or links ?Thanks. _ Comunica in un altra dimensione con MSN Extra Storage! http://www.msn.it/msnservizi/es/extra_storage_tag/ -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] AW: Re: AW: Re: API changes (was: C/A routing Question)
Hi, We need an additional info ioctl() to query the demux capabilities, e.g. the allowed number of filters of a particular type in this demux channels before we can request a filter on a specific filter_params-num. filter_params-num is a unique identifier. The only purpose is to allow the removal of _this_ filter later again. I dont think we need an additional IOCTL. Bye, Florian -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: Compilation under RedHat 8.0
Le Jeudi 27 Février 2003 11:10, Holger Waechtler a écrit : Read the README and INSTALL file. When your distribution screwed up the kernel include files get a fresh and recent kernel from http://www.kernel.org/, configure + install this one before building the DVB driver. I both read them. What I would like to do is create a set of RPMs for RedHat 8.0. I don't care (yet) about the latest dev kernel, because it cannot be installed as an RPM and will probably create dependency problems under RedHat 8.0 / 8. 1 installation. Has anyone installed DVB under a RedHat stock kernel? if yes, please give us more information on the list. For example, I need to know how to hack the /usr/src/linux-2.4/configs files. Cheers, Jean-Michel -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] SV: Re: Compilation under RedHat 8.0
I have installed under a redhat 8.0 kernel. Just recompile the kernel with loadable module support, + compile video for linux and i2c modules. -Ursprungligt meddelande- Från: Jean-Michel POURE [mailto:[EMAIL PROTECTED] Skickat: Thursday, February 27, 2003 11:47 AM Till: Holger Waechtler Kopia: Alexandre CONRAD; [EMAIL PROTECTED] Ämne: [linux-dvb] Re: Compilation under RedHat 8.0 Le Jeudi 27 Février 2003 11:10, Holger Waechtler a écrit : Read the README and INSTALL file. When your distribution screwed up the kernel include files get a fresh and recent kernel from http://www.kernel.org/, configure + install this one before building the DVB driver. I both read them. What I would like to do is create a set of RPMs for RedHat 8.0. I don't care (yet) about the latest dev kernel, because it cannot be installed as an RPM and will probably create dependency problems under RedHat 8.0 / 8. 1 installation. Has anyone installed DVB under a RedHat stock kernel? if yes, please give us more information on the list. For example, I need to know how to hack the /usr/src/linux-2.4/configs files. Cheers, Jean-Michel -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: ts analyzer
Andrea Gerardi wrote: Hi list, I would get out some information from a transport stream read from fd_demux by unsigned char buffer[188]; is there any struct to know? Something could help me with sample-code or links ?Thanks. Maybe you want to take a look on dvbsnoop: http://cvs.berlios.de/cgi-bin/viewcvs.cgi/tuxbox/apps/dvb/dvbsnoop/ Holger -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: AW: Re: AW: Re: API changes (was: C/A routing Question)
Florian Schirmer wrote: Hi, We need an additional info ioctl() to query the demux capabilities, e.g. the allowed number of filters of a particular type in this demux channels before we can request a filter on a specific filter_params-num. filter_params-num is a unique identifier. The only purpose is to allow the removal of _this_ filter later again. I dont think we need an additional IOCTL. ah, ok - I interpreted this as index into a filterbank... Holger -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: SV: Re: Compilation under RedHat 8.0
Le Jeudi 27 Février 2003 10:26, Martin Altemark a écrit : You have to recompile the kernel since the kernel shipped with 8.0 do not loadable module support, plus that you need to add video for linux and i2c modules. Thanks for your replies. RedHat 8.0 has loadable module supports as it loads several modules compiled separately. Can you confirm 8.0 does not have loadable modules, it would be very surprising. Where did you get this information? Maybe I miss something, as I am not very familiar with kernel compilation. Do you run a RedHat 8.0 yourself? Cheers, Jean-Michel POURE -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: SV: Re: Compilation under RedHat 8.0
Le Jeudi 27 Février 2003 11:52, Martin Altemark a écrit : I have installed under a redhat 8.0 kernel. Just recompile the kernel with loadable module support, + compile video for linux and i2c modules. OK, will see what I can do. Will try to hack the stock src.rpm to produce a matching kernel. rpmbuild --rebuild kernel.spec. Cheers, Jean-Michel POURE -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] SV: SV: Re: Compilation under RedHat 8.0
Yes I do. If your kernel has loadable module support, then just compile the modules and load them? -Ursprungligt meddelande- Från: Jean-Michel POURE [mailto:[EMAIL PROTECTED] Skickat: Thursday, February 27, 2003 12:29 PM Till: Martin Altemark Kopia: [EMAIL PROTECTED] Ämne: Re: SV: [linux-dvb] Re: Compilation under RedHat 8.0 Le Jeudi 27 Février 2003 10:26, Martin Altemark a écrit : You have to recompile the kernel since the kernel shipped with 8.0 do not loadable module support, plus that you need to add video for linux and i2c modules. Thanks for your replies. RedHat 8.0 has loadable module supports as it loads several modules compiled separately. Can you confirm 8.0 does not have loadable modules, it would be very surprising. Where did you get this information? Maybe I miss something, as I am not very familiar with kernel compilation. Do you run a RedHat 8.0 yourself? Cheers, Jean-Michel POURE -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] AW: Re: API changes (was: C/A routing Question)
Florian Schirmer writes: - Will add filters. - All output will be routed to the same fd. - Some restrictions apply: Only filters of the same type (TS or PES or SEC) are allowed. Is it that useful to have multi PID filters for PES and section data? It also would be easier to handle multi PID filter hardware if all PIDs are allocated at once. Otherwise the driver will have to do lots of bookkeeping, especially if it has to decide what kind of hardware filter (single PID, or other) to use. - Num must be unique (or should be set by the demux?) - Merging in section support is not necessesary but makes sense (IMHO) - dmx_decoder_t can be split into just a single type of every decoder and then adding a new uint32_t dec_num; field. Dunno what is more reasonable. - Internally each filter still maps into a single feed. So there is no need to fiddle around with any device driver. (Hopefully :) For hardware with special multi-PID TS filters it won't be that easy. At least internally we will have to handle single and multi PID filters separately. Otherwise, the lower driver layers have no way to know which filters belong together higher up. We also need to expand the kernel demux API to handle this and also direct DMA into the higher level buffers. Here multi-PID section and PES filters also would make problems. Ralph -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: SV: SV: Re: Compilation under RedHat 8.0
Well, AFAIC, when i tried installing the dvb-kernel, it told me I didn't have loadable modules. So I did : cd /usr/src/linux ; make menuconfig Loadable module is already checked, so I just exit, save, and make dep. Now dvb-kernel doesn't complain about modules... But mean while, I forgot about dvb-kernel (cause I get errors), and I tried installing from cvs drivers instead. And it won't compile. I also get the errors I posted before. But I know that my kernel has module support. The i2c and v4l module are loaded by default in RH 7.2 / 7.3. I guess they are in RH8 also. Well, my webcam works, and it uses video4linux AFAIK, right ? Regards, -- Alexandre CONRAD Research Development tel : +33 1 30 80 55 00 fax : +33 1 30 56 50 20 TLV 6, rue de la plaine 78860 - SAINT NOM LA BRETECHE FRANCE Martin Altemark wrote: Yes I do. If your kernel has loadable module support, then just compile the modules and load them? -Ursprungligt meddelande- Från: Jean-Michel POURE [mailto:[EMAIL PROTECTED] Skickat: Thursday, February 27, 2003 12:29 PM Till: Martin Altemark Kopia: [EMAIL PROTECTED] Ämne: Re: SV: [linux-dvb] Re: Compilation under RedHat 8.0 Le Jeudi 27 Février 2003 10:26, Martin Altemark a écrit : You have to recompile the kernel since the kernel shipped with 8.0 do not loadable module support, plus that you need to add video for linux and i2c modules. Thanks for your replies. RedHat 8.0 has loadable module supports as it loads several modules compiled separately. Can you confirm 8.0 does not have loadable modules, it would be very surprising. Where did you get this information? Maybe I miss something, as I am not very familiar with kernel compilation. Do you run a RedHat 8.0 yourself? Cheers, Jean-Michel POURE -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: AW: Re: API changes (was: C/A routing Question)
Ralph Metzler wrote: Florian Schirmer writes: - Will add filters. - All output will be routed to the same fd. - Some restrictions apply: Only filters of the same type (TS or PES or SEC) are allowed. Is it that useful to have multi PID filters for PES and section data? you could write single-threaded code that sleeps using blocking read() on a single filedescriptor instead calling of calling select() for multiple ones... It also would be easier to handle multi PID filter hardware if all PIDs are allocated at once. Otherwise the driver will have to do lots of bookkeeping, especially if it has to decide what kind of hardware filter (single PID, or other) to use. passing the entire filterset at once instead of allocating filters one by one makes locking much easier, too... - Num must be unique (or should be set by the demux?) - Merging in section support is not necessesary but makes sense (IMHO) - dmx_decoder_t can be split into just a single type of every decoder and then adding a new uint32_t dec_num; field. Dunno what is more reasonable. - Internally each filter still maps into a single feed. So there is no need to fiddle around with any device driver. (Hopefully :) For hardware with special multi-PID TS filters it won't be that easy. At least internally we will have to handle single and multi PID filters separately. Otherwise, the lower driver layers have no way to know which filters belong together higher up. We also need to expand the kernel demux API to handle this and also direct DMA into the higher level buffers. Here multi-PID section and PES filters also would make problems. what kind of problems do you have in your mind? Holger -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: [holger@convergence.de: Re: API changes (was: C/A routing Question)]
On Wed, Feb 26, 2003 at 04:21:09PM +0100, Emard wrote: Also some /proc stuff for tuning and routing would be nice to have like echo 12441 /proc/dvb/adapter0/frontend0/frequency echo H /proc/dvb/adapter0/frontend0/polarization etc. so users wouldn't depend too much on (volatile) ioctls and precompiled szap binaries... I don't like it. It would just create a second API, with lots of problems regarding interaction with the C API. Some /proc entries would be nice for status and statistics, e.g. show the number of active filters, maybe count the TS packets or bytes etc. But it should be optional (CONFIG_DVB_PROC, we don't need it on a STB), and the /proc layout should be well thought out and stable, so one can write DVB monitor tools that use it. I'd rather postpone this discussion until the basics of the demux API are settled down. For me it's too much at once. Regards, Johannes -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: API changes (was: C/A routing Question)
Hi, On Thu, 2003-02-27 at 12:47, Ralph Metzler wrote: Is it that useful to have multi PID filters for PES and section data? It might be nice to set multiple section filters with different filter/mask-pairs on the same pid, e.g. for epg parsing, where one mask might not match all desired table ids exactly. You could dynamically expand or narrow filters without increasing the number of open file descriptors, thus maybe reducing the number of threads of select() stuff needed in userspace. (e.g. always filter current/next events in the background and occassionally add/remove some specific filters to get detailed event info or 7-day preview). Regards, Andreas -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: SV: SV: Re: Compilation under RedHat 8.0
Le Jeudi 27 Février 2003 13:00, Alexandre CONRAD a écrit : But I know that my kernel has module support. The i2c and v4l module are loaded by default in RH 7.2 / 7.3. I guess they are in RH8 also. Well, my webcam works, and it uses video4linux AFAIK, right ? I have exactly the same feeling. It would be very surprising if RedHat kernel did not have loadable modules, cideo4linux and i2c. On the converse, I wonder why DVB drivers are not provided with a ./configure script. This would solve our problem. This compilation script is so unusual. Cheers, Jean-Michel -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: SV: SV: Re: Compilation under RedHat 8.0
Jean-Michel POURE wrote: Le Jeudi 27 Février 2003 13:00, Alexandre CONRAD a écrit : But I know that my kernel has module support. The i2c and v4l module are loaded by default in RH 7.2 / 7.3. I guess they are in RH8 also. Well, my webcam works, and it uses video4linux AFAIK, right ? I have exactly the same feeling. It would be very surprising if RedHat kernel did not have loadable modules, cideo4linux and i2c. On the converse, I wonder why DVB drivers are not provided with a ./configure script. This would solve our problem. This compilation script is so unusual. What makes you think that this could solve your problem? Just get a fresh kernel from kernel.org (without any proprietary patches), build and install it, then follow the INSTALL instructions. It's pretty easy. Your kernel won't get built using configure scripts, too... Holger -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: Compilation under RedHat 8.0
Le Jeudi 27 Février 2003 13:00, Alexandre CONRAD a écrit : But I know that my kernel has module support. The i2c and v4l module are loaded by default in RH 7.2 / 7.3. I guess they are in RH8 also. Well, my webcam works, and it uses video4linux AFAIK, right ? I have exactly the same feeling. It would be very surprising if RedHat kernel did not have loadable modules, cideo4linux and i2c. The RH Kernal alway´s have loadable module support, but the driver take a look in /usr/src/linux if THIS source is configures for loadable module support. Because the source is clean at this moment, the driver could not find the needed modules support. try this: copy the RH System.map from /boot/System.map-2.4.xx to /usr/src/linux/System.map go to /usr/src/linux, make clean and make mrproper make menuconfig and load the current config from /boot (must be config-2.4.xx or so) save settings an go out of menuconfig make dep try to build the driver testet on Mandrake 9.1(rc1), worked without to compile a new kernel greetings A.Share On the converse, I wonder why DVB drivers are not provided with a ./configure script. This would solve our problem. This compilation script is so unusual. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: SV: SV: Re: Compilation under RedHat 8.0
Le Jeudi 27 Février 2003 13:48, Holger Waechtler a écrit : What makes you think that this could solve your problem? Just get a fresh kernel from kernel.org (without any proprietary patches), build and install it, then follow the INSTALL instructions. It's pretty easy. Your kernel won't get built using configure scripts, too... Thanks for your replies, but again : I don't want to use the latest kernel but RedHat stock kernel. The reason is that I would like to build DVB RPMs and upload them to FreshRPMs. Like me, many users are so tired of compiling again and again... It takes time and does not always succeed as you know... So anytime I can use or build an RPM, I do it. Do you know if DVB works with a stock RedHat kernel? To me, it is just a ./configure problem or a simple hack to add to the makefile. Did anyone compile DVB with a stock RedHat kernel or not? This is my only question. It seems obvious that DVB lacks a good configure script. Do I miss something? This is the first time I encouter an installation script without a ./configure first. Is this usual with kernel modules? I am pretty new, maybe I miss something. Cheers, Jean-Michel -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: Compilation under RedHat 8.0
Le Jeudi 27 Février 2003 14:11, Andreas Share a écrit : copy the RH System.map from /boot/System.map-2.4.xx to /usr/src/linux/System.map go to /usr/src/linux, make clean and make mrproper make menuconfig and load the current config from /boot (must be config-2.4.xx or so) save settings an go out of menuconfig make dep try to build the driver testet on Mandrake 9.1(rc1), worked without to compile a new kernel So many thanks, this is the information I needed. Will try to build an RPM soon. Cheers, Jean-Michel POURE -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: AW: Re: API changes (was: C/A routing Question)
Holger Waechtler writes: Ralph Metzler wrote: Florian Schirmer writes: - Will add filters. - All output will be routed to the same fd. - Some restrictions apply: Only filters of the same type (TS or PES or SEC) are allowed. Is it that useful to have multi PID filters for PES and section data? you could write single-threaded code that sleeps using blocking read() on a single filedescriptor instead calling of calling select() for multiple ones... OK. At least internally we will have to handle single and multi PID filters separately. Otherwise, the lower driver layers have no way to know which filters belong together higher up. We also need to expand the kernel demux API to handle this and also direct DMA into the higher level buffers. Here multi-PID section and PES filters also would make problems. what kind of problems do you have in your mind? You could e.g. not mmap the hardware DMA ring buffer. Ralph -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: SV: SV: Re: Compilation under RedHat 8.0
Jean-Michel POURE: This is the first time I encouter an installation script without a configure first. Is this usual with kernel modules? I am pretty new, maybe I miss something. People don't usually compile modules without the corresponding kernel source, drivers are supposed to come with the kernel, so there's little incentive to do polished compilation scripts (once a driver is polished, it's in the kernel!) it is a pain but all drivers I've compiled have been like that in some way, actually the DVB drivers seems quite good compared to others. Still, you can usually compile with just headers though after a bit of poking around. As for configure, this usually comes from the autoconf package whose aim is to detect platform, compiler differences which is useless for kernel modules: platform, you know it's Linux, no need to find which compiler you are using, only gcc compiles the kernel, no need to find which libxxx you're using, the kernel of course the kernel does not depend on shared libraries. So I guess there's little you could do with autoconf for modules. -- [EMAIL PROTECTED] -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: API changes (was: C/A routing Question)
Andreas Oberritter writes: On Thu, 2003-02-27 at 12:47, Ralph Metzler wrote: Is it that useful to have multi PID filters for PES and section data? It might be nice to set multiple section filters with different filter/mask-pairs on the same pid, e.g. for epg parsing, where one mask might not match all desired table ids exactly. You could dynamically expand or narrow filters without increasing the number of open file descriptors, thus maybe reducing the number of threads of select() stuff needed in userspace. (e.g. always filter current/next events in the background and occassionally add/remove some specific filters to get detailed event info or 7-day preview). OK, if the section filters are on the same PID it even would map better on most hardware and save copies because they often share the same buffer if they belong to the same PID feed. Ralph -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] [Fwd: Re: Re: SV: SV: Re: Compilation under RedHat 8.0]
ps : after the forwarded message below, I have tried Andreas Share's technic copy the RH System.map from /boot/System.map-2.4.xx to /usr/src/linux/System.map go to /usr/src/linux, make clean and make mrproper make menuconfig and load the current config from /boot (must be config-2.4.xx or so) save settings an go out of menuconfig make dep try to build the driver But I get the same problem... flashy video (nexus dvb-S here...) Regards, -- Alexandre CONRAD Research Development tel : +33 1 30 80 55 00 fax : +33 1 30 56 50 20 TLV 6, rue de la plaine 78860 - SAINT NOM LA BRETECHE FRANCE Original Message Subject: Re: [linux-dvb] Re: SV: SV: Re: Compilation under RedHat 8.0 Date: Thu, 27 Feb 2003 15:02:28 +0100 From: Alexandre CONRAD [EMAIL PROTECTED] To: Jürgen Zimmermann [EMAIL PROTECTED] References: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] What worked for me on RedHat = 8.0 is the following (borrowed from kernel-2.4.spec): cd /usr/src/linux make mrproper make oldconfig make oldconfig (Yes, twice! That's where the problem arise) make include/linux/version.h make dep ??!! cd /usr/local/src/DVB make (cd driver; make) /usr/src/linux/scripts/pathdown.sh: line 4: TOPDIR: parameter null or not set make[1]: Entering directory `/usr/local/src/DVB/driver' DIR=`pwd`; (cd /usr/src/linux; make SUBDIRS=$DIR modules) make[2]: Entering directory `/usr/src/linux-2.4.18-14' The present kernel configuration has modules disabled. Type 'make config' and enable loadable module support. Then build a kernel with module support enabled. make[2]: *** [modules] Error 1 make[2]: Leaving directory `/usr/src/linux-2.4.18-14' make[1]: *** [here] Error 2 make[1]: Leaving directory `/usr/local/src/DVB/driver' make: *** [dvb] Error 2 Now, I'll do again what I was telling you about : cd /usr/src/linux make menuconfig Loadable module support --- [*] Enable loadable module support [*] Set version information on all module symbols [*] Kernel module loader exit save : YES Saving your kernel configuration... make dep after a 1 or 2 minutes compiling... cd /usr/local/src/DVB make and... surprise !! it compiles all the way to the end !!! but... my TV ouput shows something wrong... like this flash that happens when you turn off your TV... and when I use ntuxplayer to read a video, I can't see anything but this strange flashy noise... Regards, -- Alexandre CONRAD Research Development tel : +33 1 30 80 55 00 fax : +33 1 30 56 50 20 TLV 6, rue de la plaine 78860 - SAINT NOM LA BRETECHE FRANCE -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] filesystem based API
Johannes Stezenbach: Some /proc entries would be nice for status and statistics, e.g. show the number of active filters, maybe count the TS packets or bytes etc. As you mention, it remembers me about an article that said that a long term goal for Linux would be to be able to configure stuff through small devices, rather than /proc if I recall correctly, for configuration. That is you'd do: echo 12211000 /dev/dvb0/frontend/frequency echo H /dev/dvb0/frontend/polarity echo 2200 /dev/dvb0/frontend/symbolrate etc. 'cat' the same to see an ASCII version of the current state. Then bingo, easy debugging from an ordinary shell, instant bindings for any scripting or otherwise language, complete removal of the C API, and no nasty ioctl (which is one of the great uglyness of Unix) anymore. I don't know if this is something already started in 2.5 or just a mere proposal which is floating around. If there's no infrastructure already in there, it would arguably not be wise to do it alone in DVB. It does require devfs or some equivalent of course, and I suspect old style devices may still be supported in 2.5. -- [EMAIL PROTECTED] -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: filesystem based API
Franck Arnaud wrote: As you mention, it remembers me about an article that said that a long term goal for Linux would be to be able to configure stuff through small devices, rather than /proc if I recall correctly, for configuration. That is you'd do: echo 12211000 /dev/dvb0/frontend/frequency echo H /dev/dvb0/frontend/polarity echo 2200 /dev/dvb0/frontend/symbolrate etc. 'cat' the same to see an ASCII version of the current state. Then bingo, easy debugging from an ordinary shell, instant bindings for any scripting or otherwise language, complete removal of the C API, and no nasty ioctl (which is one of the great uglyness of Unix) anymore. I don't know if this is something already started in 2.5 or just a mere proposal which is floating around. If there's no infrastructure already in there, it would arguably not be wise to do it alone in DVB. It does require devfs or some equivalent of course, and I suspect old style devices may still be supported in 2.5. There's sysfs (or whatever it's called currently), which goes in that direction. But I don't think it will replace ioctl() any time soon. AFAIK it is meant as a replacement for sysctls (/proc/sys/... or sysctl(2)) which are for system (i.e. kernel or driver) parameters for which no other API exits (e.g. due to the lack of devices which you could open). Regards, Johannes -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: AW: Re: API changes (was: C/A routing Question)
Florian Schirmer wrote:
typedef enum
{
DMX_FMT_TS,
DMX_FMT_PES,
DMX_FMT_SEC,
DMX_FMT_PES_HDR,
I'm still not convinced what this would be good for.
DMX_FMT_STC,
And this one does not make sense. PES packets (optionally) have a
PTS. This is fed to a PLL to recover a stable clock (the STC),
currently by settting a filter with DMX_PES_PCR and DMX_OUT_DECODER.
There's special hardware for clock recovery (to remove jitter etc.),
and it's often associated with the demux.
The STC is then used by the MPEG decoder for synchronization.
Or, in case of subtitles, by userspace programs.
DMX_FMT_ES,
...
} dmx_format_t;
typedef enum
{
DMX_DEC_NONE,
DMX_DEC_VIDEO0,
DMX_DEC_VIDEO1,
DMX_DEC_VIDEO2,
DMX_DEC_AUDIO0,
DMX_DEC_AUDIO1,
DMX_DEC_AUDIO2,
DMX_DEC_PCR0,
DMX_DEC_PCR1,
DMX_DEC_PCR2,
...
} dmx_decoder_t;
struct dmx_filter_params
{
uint32_t num;
s/num/id/
unique per demux file descriptor
uint16_t pid;
uint32_t fe_map;
#define FE_ALL 0
#define FE_MEM 1
#define FE_HW1 2
#define FE_HW2 4
#define FE_HW2 8
dmx_format_t format;
dmx_decoder_t decoder;
dmx_filter_t sec_filter;
uint32_t sec_timeout;
uint32_t sec_flags;
#define DMX_CHECK_CRC 1
#define DMX_ONESHOT 2
#define DMX_IMMEDIATE_START 4
I never used DMX_START and filters without DMX_IMMEDIATE_START.
Do we need it or should we drop DMX_START/DMX_STOP in favour of
DMX_ADD/DEL_FILTER? Or would DMX_STOP mean stop all filters?
Or even clear all filters?
}
- Num must be unique (or should be set by the demux?)
Let the app do the book-keeping and choose its own ids.
If we would set all filters in one ioctl we could use an array
and just use the array index as id. But with the more dynamic
DMX_ADD/DEL_FILTER concept the driver won't have a natural id.
- dmx_decoder_t can be split into just a single type of every decoder and
then adding a new uint32_t dec_num; field. Dunno what is more reasonable.
I don't like the dmx_decoder_t at all.
IMHO one should be able to say I want data passed to userspace, please
allocate buffers for that, or data will go to the MPEG decoder or the
HDD directly.
Data could go to both MPEG decoder and HDD. The demux should assign
a logical output_channel_id to the filter, and the MPEG decoder
would support a VIDEO/AUDIO_SET_SOURCE ioctl to connect the two.
If we eventually support direct to HDD stream recording this
would connect via the same mechanism.
- I've added an fe_map in favour to a SELECT_SOURCE IOCTL. Makes more sense
i think. Now you can select the fe on the fly.
I don't like it.
The problem here is that (depends on the hardware) the demux
can only process a limited number of input streams out of a larger
selection. If you need to switch the input routing it affects
all other filters of the same demux device.
That why a seperate DMX_SELECT_SOURCE is IMHO better.
Then we have input routing, filter specificaton and output routing
logically separated in the API. Just like when you draw a diagram of
you STB on paper you have sperate boxes for FE, demux, MPEG, HDD, ...
and then you connect them as appropriate. You roll it all in
one mega ioctl.
Regards,
Johannes
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as
subject.
[linux-dvb] Re: [holger@convergence.de: Re: API changes (was: C/A routing Question)]
I don't like it. It would just create a second API, with lots of problems regarding interaction with the C API. Alright, just a thougth for the future. However, automatic registration of the devices will be good for new kernel, (no more mknod /dev/dvb/.. c 123 45) Detected devices should present themselves as automatic filesystem nodes Some /proc entries would be nice for status and statistics, e.g. show the number of active filters, maybe count the TS packets or bytes etc. Yes, exactly. But it should be optional (CONFIG_DVB_PROC, we don't need it on a STB), and the /proc layout should be well thought out and stable, so one can write DVB monitor tools that use it. Of course, compile time option. Let this be just a wishlist entry after ioctl cleanup and global code stabilization regarding insmod/rmmods, 2.5.x compatibility etc I'd rather postpone this discussion until the basics of the demux API are settled down. For me it's too much at once. me too :) -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: [holger@convergence.de: Re: API changes (was:C/A routing Question)]
Emard wrote: I don't like it. It would just create a second API, with lots of problems regarding interaction with the C API. Alright, just a thougth for the future. However, automatic registration of the devices will be good for new kernel, (no more mknod /dev/dvb/.. c 123 45) Detected devices should present themselves as automatic filesystem nodes Use devfs, then it is handled exactly like this. Right now... Holger -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: [holger@convergence.de: Re: API changes (was: C/A routing Question)]
Use devfs, then it is handled exactly like this. Right now... It would be super if it can work automaticall without any changes in dvb-* Thnx! -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: [holger@convergence.de: Re: API changes (was:C/A routing Question)]
Emard wrote: Use devfs, then it is handled exactly like this. Right now... It would be super if it can work automaticall without any changes in dvb-* it does. Holger -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] dvbtune
Hi Malcolm I thought first I should get the signal locked and then try vdr. I know you dont use dvbtune but it is a similiar utility to dvbstream. I gave the command ./dvbtune -f 1150 -t 0 -s 28125 and get the following output: tuning DVB-S to L-Band:1150, Pol:H Srate=28125000, 22kHz=off SEC BUS MODE: IDLE (0) SEC VOLTAGE: 18 (4) SEC CONT TONE: OFF Getting frontend event Received failure event Getting frontend event Received failure event Getting frontend event Received failure event Not able to lock to the signal on the given frequency Can somebody help in sorting the problem? Malcolm, I will download dvbstream and try with that.Which version are using? Regards, Sheetal Pandey -Original Message- From: Malcolm Caldwell [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 8:00 PM To: Sheetal_Pandey Cc: [EMAIL PROTECTED] Subject: Re: [linux-dvb] vdr problem I not sure what your problem is. Perhaps you should try a newer version of vdr. I am using a developer version (1.1.20). vdr questions should be posted to the vdr email list and I have CCed the list and removed the dvb list. Is the channel working with a normal set to box? On Thu, 2003-02-27 at 19:12, Sheetal_Pandey wrote: Hi, I have mapped the keys of PC Keyboard to work with VDR application.I can enter into the channels menu and change the parameters.I changed the freq-1150 S/R 28125 POL-H VPID-517 APID-700 and said ok but it doent show any video.I have changed the channels.conf as follows RTPi:1150:h:S100.5E:28125:517:700:0:0:30:0:0:0 DW:1150:h:S100.5E:28125:2305:2306:0:0:1:0:0:0 RAIi:1150:h:S100.5E:28125:513:644:0:0:3:0:0:0 I also changed the setup.conf to LnbFrequHi = 0 LnbFrequLo = 0 LnbSLOF = 0 I am using vdr-1.0.0pre2. Regards, Sheetal Pandey ** This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated. ** ** This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated. ** -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
[linux-dvb] Re: dvbtune
Hello,
I just checked and this works for me:
./dvbtune -p H -s 28125 -i -f 115 -I 1 -m
So your problem is probably the frequency.
The basically code says:
if (freq 220) {
TAKE AWAY THE LOG
} else {
// this is an L-Band frequency
So L band frequencies need to be there as absolutes.
Also, the lines
tuning DVB-S to L-Band:1107310752, Pol:H Srate=28125000, 22kHz=off
Are wrong - the is not the real L-Band frequency as the code to
calculate that is after this printf!
On Fri, 2003-02-28 at 16:16, Sheetal_Pandey wrote:
Hi Malcolm
I thought first I should get the signal locked and then try vdr.
I know you dont use dvbtune but it is a similiar utility to dvbstream.
I gave the command ./dvbtune -f 1150 -t 0 -s 28125
and get the following output:
tuning DVB-S to L-Band:1150, Pol:H Srate=28125000, 22kHz=off
SEC BUS MODE: IDLE (0)
SEC VOLTAGE: 18 (4)
SEC CONT TONE: OFF
Getting frontend event
Received failure event
Getting frontend event
Received failure event
Getting frontend event
Received failure event
Not able to lock to the signal on the given frequency
Can somebody help in
sorting the problem?
Malcolm,
I will download dvbstream and try with that.Which version are using?
Regards,
Sheetal Pandey
-Original Message-
From: Malcolm Caldwell [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 27, 2003 8:00 PM
To: Sheetal_Pandey
Cc: [EMAIL PROTECTED]
Subject: Re: [linux-dvb] vdr problem
I not sure what your problem is.
Perhaps you should try a newer version of vdr. I am using a developer
version (1.1.20).
vdr questions should be posted to the vdr email list and I have CCed the
list and removed the dvb list.
Is the channel working with a normal set to box?
On Thu, 2003-02-27 at 19:12, Sheetal_Pandey wrote:
Hi,
I have mapped the keys of PC Keyboard to work with VDR application.I can
enter into the channels menu and change the parameters.I changed the
freq-1150 S/R 28125 POL-H VPID-517 APID-700 and said ok but it doent show
any video.I have changed the channels.conf as follows
RTPi:1150:h:S100.5E:28125:517:700:0:0:30:0:0:0
DW:1150:h:S100.5E:28125:2305:2306:0:0:1:0:0:0
RAIi:1150:h:S100.5E:28125:513:644:0:0:3:0:0:0
I also changed the setup.conf to
LnbFrequHi = 0
LnbFrequLo = 0
LnbSLOF = 0
I am using vdr-1.0.0pre2.
Regards,
Sheetal Pandey
**
This email (including any attachments) is intended for the sole use of the
intended recipient/s and may contain material that is CONFIDENTIAL AND
PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying
or
distribution or forwarding of any or all of the contents in this message
is
STRICTLY PROHIBITED. If you are not the intended recipient, please contact
the sender by email and delete all copies; your cooperation in this regard
is appreciated.
**
**
This email (including any attachments) is intended for the sole use of the
intended recipient/s and may contain material that is CONFIDENTIAL AND
PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or
distribution or forwarding of any or all of the contents in this message is
STRICTLY PROHIBITED. If you are not the intended recipient, please contact
the sender by email and delete all copies; your cooperation in this regard
is appreciated.
**
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as
subject.
[linux-dvb] dvbstream(CVS version) stream only when my router is on
hello, i have a problem: dvbstream(CVS version), wich works well with new DVB-drivers 1.0.0-pre1, start to stream only when my home DSL router is on. I didn't have such problem with previos combination between dvb dvbstream 0.4.2 and drivers 0.9.4. Hauppauge WinTV-NOVA-S PCI, Linux=SuSE 8.0 Kernel=2.4.18.SuSE 2x LAN=RTL8029(192.168.168.168) + TULIP(192.168.168.69) Router,NS 192.168.168.100 It was configuration always such in SUSE 7.2,7.3 and here is the same. where is the problem? thanks in advance:Ivan __ Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, more http://taxes.yahoo.com/ -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with unsubscribe linux-dvb as subject.
