[linux-dvb] Re: [vdr] Re: dxr3/vdr problem
Malcolm Caldwell writes: > (Kai - I home you don't mind - I think this discussion might receive > better response on the dvb email list.) > > This thread started when I wrote that I was having problems trying to > run vdr with a budget card using a dxr3 as the output. I don't think I > am the only one. > > The problem is I have a poor quality signal (due to various factors > including weather). > > These errors get through the dvb driver to vdr and on to the the dxr3. > The dxr3 device crashes - sometimes requiring a restart of vdr to reopen > the device etc, sometimes requiring a reboot. Others have reported > having to reload the dxr3 drivers. (although reloading the dxr3 drivers > has never worked for me - but thats OT) My system only ever runs a few > hours before crashing. > > Kai argues that the dvb drivers should not be passing frames with errors > through to applications. Given that there is FEC etc in the dvb spec > this may be so - I don't know. I also don't know if a budget card is > capable of doing this. > All the error correction required and possible for the DVB signal is already done by the frontend. Any remaining errors cannot be fixed on the transport stream level. It would not make sense to check the MPEG stream on the ES level inside the driver. It is the task of the MPEG decoder to fix or ignore these problems. E.g. the hardware MPEG decoder of the av7110 already does these things which are often necessary for MPEG streams received from a error prone source. The dxr3 decoder is probably a little more picky because it was not developed for decoding a broken stream. Marcus -- /\ | Dr. Marcus O.C. Metzler| | ||---| | [EMAIL PROTECTED]| http://www.metzlerbros.de/| \/ -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: [PATCH] video_device->close
Hello Denis, I added a close function that stops DMA which is highly appreciated and the normal behaviour of v4l drivers. The functionality is implemented for < 2.5 only, yet. A patch for "dvb-kernel" is not necessary, because of the different driver design. There, the dedicated file operations for the v4l-device (in saa7146_fops.c) call a release function for the v4l part (in saa7146_video.c), which shuts down the video dma when the device is closed. CU Michael. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: [vdr] Re: dxr3/vdr problem
(Kai - I home you don't mind - I think this discussion might receive better response on the dvb email list.) This thread started when I wrote that I was having problems trying to run vdr with a budget card using a dxr3 as the output. I don't think I am the only one. The problem is I have a poor quality signal (due to various factors including weather). These errors get through the dvb driver to vdr and on to the the dxr3. The dxr3 device crashes - sometimes requiring a restart of vdr to reopen the device etc, sometimes requiring a reboot. Others have reported having to reload the dxr3 drivers. (although reloading the dxr3 drivers has never worked for me - but thats OT) My system only ever runs a few hours before crashing. Kai argues that the dvb drivers should not be passing frames with errors through to applications. Given that there is FEC etc in the dvb spec this may be so - I don't know. I also don't know if a budget card is capable of doing this. What do people here think? On Mon, 2003-03-03 at 00:38, Kai Moeller wrote: > On Friday 28 February 2003 14:58, Rantanen Teemu wrote: > > > From: Stefan Schluenss [mailto:[EMAIL PROTECTED] > > > > > > Malcom is using DVB-T if i remember correctly and the currently > > > implemented > > > DVB-T systems seems to be more in an experimental state than in > > > production state ;-) > > > > I'd rather say that transport errors are more likely to happen on DVB-T > > then on DVB-C (should 'never' happen) or on DVB-S (can happen on bad > > weather). > > > > > The question is who (driver/vdr/dxr3-plugin) has to take care of corrupt > > > data ?! In Kai's opinion the data has to be checked and rejected inside > > > the > > > driver and such corrcupt data should never reach upper layers (the dxr3- > > > plugin). > > > > Considering that full error checking is somewhat complex operation (correct > > me if I'm wrong), I'd rather see that amount of code and CPU time not in > > kernel, but in user space. > > > > Sorry, but I think you're wrong. The FEC mechanisms are defined in the DVB > standards and hopefully implemented within the hardware/firmware of the DVB > card. The TS packets, VDR receives from the driver, all have a > transport_error_indicator bit which should be set to '1' when there is at > least 1 uncorrectable bit error (see ISO/IEC 13818-1). > > => So actually it should be quite easy to detect defect TS packets. > PES packets (the Dxr3Plugin receives PES) don't have such an error bit (PES is > used for transmissions where bit errors are unlikely). The only errors the > plugin is able to detect are weird entries within the PES header (and we > already added some more checks on request) but these are not the only errors > which may crash your system. > > Regards, > > Kai > > -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] [PATCH] video_device->close
Hi,
I added a close function that stops DMA which is highly
appreciated and the normal behaviour of v4l drivers.
The functionality is implemented for < 2.5 only, yet.
--
Best regards,
Denis Oliver Kropp
.--.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"--"
Convergence GmbH
Index: driver/av7110/av7110.c
===
RCS file: /cvs/linuxtv/DVB/driver/av7110/av7110.c,v
retrieving revision 1.28
diff -u -r1.28 av7110.c
--- driver/av7110/av7110.c 24 Feb 2003 22:53:05 - 1.28
+++ driver/av7110/av7110.c 4 Mar 2003 17:15:47 -
@@ -3250,6 +3250,17 @@
return mask;
}
+#if (LINUX_VERSION_CODE < KERNEL_VERSION(2,5,0))
+static
+void dvb_close(struct video_device *dev)
+{
+ int zero = 0;
+ av7110_t *av7110 = dev->priv;
+
+ /* Disable video DMA */
+ saacomm(SAA7146_V4L_CCAPTURE, &zero);
+}
+#endif
#if !(LINUX_VERSION_CODE < KERNEL_VERSION(2,5,0))
static struct file_operations dvb_fops = {
@@ -3274,6 +3285,7 @@
#if LINUX_VERSION_CODE < KERNEL_VERSION(2,5,0)
.ioctl = dvb_ioctl,
.mmap = dvb_mmap,
+ .close = dvb_close
#else
.fops = &dvb_fops
#endif
[linux-dvb] Re: DVB-C as cable modem
Emard wrote: HI all Owners of the cables and DVB-C (with or without onboard mpeg): Can DVB-C work as cable modem, not only receiving but also transmitting packets? no. Will upcoming usb FX2 have cable modem capability? Right now we have a terrestrial frontend, so the answer is no. Holger -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] DVB-C as cable modem
HI all Owners of the cables and DVB-C (with or without onboard mpeg): Can DVB-C work as cable modem, not only receiving but also transmitting packets? Will upcoming usb FX2 have cable modem capability? ... if it can maybe it would be good to support it in the current drivers and have in mind future api modifications Emard -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: V4L issues with linux dvb driver
Hello Billy, Quite. Still, I can only test with what I have, and I currently only use the bttv drivers from the kernel, so, only V4L1 here. ;-) Ok. I'm not annoyed. :) I appreciate this discussion alot. No, V4L1 does not support alternate mode, but I really wanted to move to V4L2 and only support drivers that support ALTERNATE mode, since then I can rip out all my nasty /dev/rtc code. Sleeping for exactly 16.6ms for NTSC sources really sucks. Oh well. Ok, understood. I have a question. For my support pages, what cards does your driver work with, and where is a link to a webpage describing your driver? My original project page is http://www.gdv.uni-hannover.de/~hunold1/linux/saa7146/index.html but that's rather uninteresting for DVB users. You can find an explanation of the current DVB driver situation at http://linuxtv.org/dvb/drivers.xml The important point missing there is to clearly state the switch from v4l1 to v4l2 and a list of application that work. Yes, I want a 20ms wakeup for PAL sources, 16.6ms for NTSC, since this is our output framerate. Ok, I'll add it to the TODO list. CU Michael. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Multiple programs extraction
Dear all, how many programs/services can be managed at the same time by a single DVB receiver (for example is it possible to extract at the same time IP/MPE flows belonging to different programs)? Thanks Gaetano - Salve, il messaggio che hai ricevuto è stato inviato per mezzo del sistema di web mail interfree. Se anche tu vuoi una casella di posta free visita il sito http://club.interfree.it Ti aspettiamo! - -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: V4L issues with linux dvb driver
Michael Hunold ([EMAIL PROTECTED]): > I don't have access to the webpage, so I cannot add informations there > easily. 8-( Who does have access? -- Billy Biggs [EMAIL PROTECTED] -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: V4L issues with linux dvb driver
Hey Michael, > I admit that all other v4l2 drivers mostly only support the > "old/inofficial" v4l2 api (before it went to the 2.5.x kernel), so > this will take some time until 2.6.x finally comes out... Quite. Still, I can only test with what I have, and I currently only use the bttv drivers from the kernel, so, only V4L1 here. ;-) > > One annoyance for me right now is that while V4L2 supports ALTERNATE > > mode, the bttv V4L2 driver currently fills both buffers at frame > > rate, making this very important feature very useless. > > I don't want to annoy you, but: does v4l1 support this? I'm not annoyed. :) I appreciate this discussion alot. No, V4L1 does not support alternate mode, but I really wanted to move to V4L2 and only support drivers that support ALTERNATE mode, since then I can rip out all my nasty /dev/rtc code. Sleeping for exactly 16.6ms for NTSC sources really sucks. Oh well. > There are several reasons: the user basis for my analog saa7146 > drivers is very small and nobody apparently has asked for this or has > been using tvtime. The user basis for the DVB basis is much larger, > but not many are using the new "dvb-kernel" driver. Additionally, more > and more users switch from full-featured DVB-cards to el-cheapo > budget-cards without mpeg-decoding and video-functionality, so they > don't need a tv application any more. I have a question. For my support pages, what cards does your driver work with, and where is a link to a webpage describing your driver? > You could borrow ideas from "xawtv", which supports v4l1, pre-2.5.x > v4l2 and v4l2 at once. It should be fairly easy to detect the presence > of v4l2 on a user's system and then compile different modules for > v4l1/2 support, no? Yes this will likely be some of the basis for my code, however I do not intend to support random drivers that use the pre-2.5.x API. > I'll have a look at how complicated adding field capturing to > alternating buffers is. > > You basically want to queue twice as many buffers with half the size, > getting one field every 20ms, right? Yes, I want a 20ms wakeup for PAL sources, 16.6ms for NTSC, since this is our output framerate. -- Billy Biggs [EMAIL PROTECTED] -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: V4L issues with linux dvb driver
Hello Billy, Not exactly the end of the world, and bt878 already has this problem, the chip supports separate saturation/hue but the API sucks. We're currently kinda holding off on our auto-calibration stuff until we go to V4L2. Ok. Thanks, I appreciate your interest. We're definitely in a bad situation with V4L2 right now, even more so that many V4L2 drivers are in various stages of development when drivers exist for V4L1 that work. I consider bttv/saa7134/saa7146 the most important video devices, and at least Gerd Knorr is trying very hard to get his stuff into good shape. I admit that all other v4l2 drivers mostly only support the "old/inofficial" v4l2 api (before it went to the 2.5.x kernel), so this will take some time until 2.6.x finally comes out... However, you're not the first person to have been presented a bug or problem in their V4L1 code and then be uninterested in fixing it, saying that we should move to the V4L2 interface :) 8-) Some more explanations: about 2,5 years ago, the video part of the DVB driver was created on the current (at that time) version of my v4l1 driver, ie. the development was forked. I changed to v4l2 later and developed my "analog" drivers further. Because of that the DVB "head" driver is still v4l1, while I've been working on v4l2 only. I haven't touched the v4l1 code for years now. So I simply cannot fix it, because I would have to start almost from 0. But I ported the video subsystem of the DVB driver to my "new" saa7146 subsystem lately, this is "dvb-kernel" in CVS. One annoyance for me right now is that while V4L2 supports ALTERNATE mode, the bttv V4L2 driver currently fills both buffers at frame rate, making this very important feature very useless. I don't want to annoy you, but: does v4l1 support this? Does your driver support ALTERNATE mode? Can I get woken up every field? I don't like the idea of moving to V4L2 when a major driver like this lies about their support of ALTERNATE mode... The "dvb-kernel" v4l2 driver is not "alternate" aware. Currently it does *not support* capturing fields to different buffers, althought the hardware can do this. There are several reasons: the user basis for my analog saa7146 drivers is very small and nobody apparently has asked for this or has been using tvtime. The user basis for the DVB basis is much larger, but not many are using the new "dvb-kernel" driver. Additionally, more and more users switch from full-featured DVB-cards to el-cheapo budget-cards without mpeg-decoding and video-functionality, so they don't need a tv application any more. Finally, it is essential to me that users be able to use the kernel packages from their distribution and not compile their own. So, this means I must support V4L1. Your patch is a nice start to V4L2 support, but unfortunately the end result is going to look a little different as I try to support both at once in a clean way. You could borrow ideas from "xawtv", which supports v4l1, pre-2.5.x v4l2 and v4l2 at once. It should be fairly easy to detect the presence of v4l2 on a user's system and then compile different modules for v4l1/2 support, no? Comments? I'd almost rather see some more effort put into the V4L1 compatibility code until 2.6 is released, although I understand that even when 2.6 comes out, we'll still have to go through a phase of supporting both APIs. I wouldn't count on the compatibility layer, but instead natively support both apis. Concentrate on bttv for the v4l1 driver, all other drivers (saa7134/saa7146) should work through v4l2 (except the alternate capture of course) I'll have a look at how complicated adding field capturing to alternating buffers is. You basically want to queue twice as many buffers with half the size, getting one field every 20ms, right? CU Michael. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: V4L issues with linux dvb driver
Hello Billy, If you encounter any more bug reports regarding the "linuxtv.org" DVB driver, please encourage the users to try the "dvb-kernel" driver from the project's CVS (remember: it can be compiled under 2.4.x as well) and use the benefits of v4l2. There is no indication of this at all on your webpage, and in fact, this driver (linuxtv-dvb-1.0.0-pre1) was released quite recently. Can you please indicate on this page that there will be problems with applications such as tvtime? I don't have access to the webpage, so I cannot add informations there easily. 8-( But I'm currently writing a howto about DVB and applications, where I'm trying to explain the different drivers and the use of the most common applications. I'll add a section about "tvtime" there for sure. I'm having alot of problems with it, there are annoying bugs with it and the saa7134 driver for sure that made my life a total pain (and the saa7134 supports the old-style-mmap() interface). CU Michael. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: Compiling dvb-kernel
Hello Hagen, 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. Any success ? It's fixed in CVS now. There were function "modifiers" (which specify functions as init or exit functions) for some functions, that caused the module to oops upon insertion. I've tested it with 2.5.63 and 2.4.20. CU Michael. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: V4L issues with linux dvb driver
Michael Hunold ([EMAIL PROTECTED]): > Unfortunately, the driver does not support the > "old-style-mmap()-interface" through the compatiblity layer. 8-( > > This is the reason, why "tvtime" only gets one capture buffer and > that's why the performance sucks. Thanks for this analysis. I'm updating our hardware support pages to explain the situation. > Two solutions: > 1) Add these extra hooks to the driver, so the compatiblity layer is > satisfied. > > I don't like this solution, because there are many more problems > regarding the interaction between saa7146 and v4l. One example: your > driver expects hue/brightness/colour/contrast, while the saa7146 > delivers brightness/constrast/saturation only... Not exactly the end of the world, and bt878 already has this problem, the chip supports separate saturation/hue but the API sucks. We're currently kinda holding off on our auto-calibration stuff until we go to V4L2. > 2) Switch to v4l2. Drivers are available for all common chipsets > (bt8x8, saa7134, saa7146), they will be part of the 2.6.x kernel by > default. > > To support this, I made a quick-and-dirty hack porting "tvtime" to > v4l2. I fixed most stuff to PAL and threw out everything that's not > needed. Some quirks were necessary to squeeze the v4l1 capture scheme > to the way v4l2 works. The subsystem should be redesigned though. > > I attached a diff to the current CVS to this mail. You need to put > "videodev2.h" for example to /usr/include/linux. Thanks, I appreciate your interest. We're definitely in a bad situation with V4L2 right now, even more so that many V4L2 drivers are in various stages of development when drivers exist for V4L1 that work. However, you're not the first person to have been presented a bug or problem in their V4L1 code and then be uninterested in fixing it, saying that we should move to the V4L2 interface :) One annoyance for me right now is that while V4L2 supports ALTERNATE mode, the bttv V4L2 driver currently fills both buffers at frame rate, making this very important feature very useless. Does your driver support ALTERNATE mode? Can I get woken up every field? I don't like the idea of moving to V4L2 when a major driver like this lies about their support of ALTERNATE mode... Finally, it is essential to me that users be able to use the kernel packages from their distribution and not compile their own. So, this means I must support V4L1. Your patch is a nice start to V4L2 support, but unfortunately the end result is going to look a little different as I try to support both at once in a clean way. Comments? I'd almost rather see some more effort put into the V4L1 compatibility code until 2.6 is released, although I understand that even when 2.6 comes out, we'll still have to go through a phase of supporting both APIs. -- Billy Biggs [EMAIL PROTECTED] -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: DSM-CC implementation
On Tue, Mar 04, 2003 at 09:38:48AM +0100, Marc Rovira Vall wrote: > > Does anybody know an implementation of the DSM-CC specification? I'm > developing a DVB data broadcasting application that works with private > sections but I'm having some problems trying to build the DSM-CC > architecture protocol. http://sourceforge.net/projects/dvbsak has something, but I don't know its status. HTH, Johannes -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: V4L issues with linux dvb driver
Hi Michael, > to make a long story short: "linuxtv-dvb-1.0.0-pre1" and the so-called > DVB "head" or "newstruct" drivers are v4l1 drivers. Ok. > Although the code is based on my original saa7146 driver, I won't > change it anymore. "dvb-kernel" is the basis for the upcoming 2.6.x > kernel and it can be compiled under 2.4.x as well. Alright. > If you encounter any more bug reports regarding the "linuxtv.org" DVB > driver, please encourage the users to try the "dvb-kernel" driver from > the project's CVS (remember: it can be compiled under 2.4.x as well) > and use the benefits of v4l2. There is no indication of this at all on your webpage, and in fact, this driver (linuxtv-dvb-1.0.0-pre1) was released quite recently. Can you please indicate on this page that there will be problems with applications such as tvtime? > Is your application v4l2 aware? No, I will expand in my reply to your other mail. > Or do you rely on the compatibility layer? I'm having alot of problems with it, there are annoying bugs with it and the saa7134 driver for sure that made my life a total pain (and the saa7134 supports the old-style-mmap() interface). -- Billy Biggs [EMAIL PROTECTED] -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: V4L issues with linux dvb driver
Hello Billy, I'll have a look at this later today and test the "dvb-kernel" driver with "tvtime" and come back to you later. Ok, I see that "tvterm" uses plain v4l, so it should work through the compatibility layer. Unfortunately, the driver does not support the "old-style-mmap()-interface" through the compatiblity layer. 8-( "Old style" means, that all capture buffers are mmap()ed in a single call, the buffers are separated by offsets. Using v4l2, you mmap() every single buffer individually. For the compatibility layer to work, you need some extra hooks, that are not present in the current driver. This is the reason, why "tvtime" only gets one capture buffer and that's why the performance sucks. Two solutions: 1) Add these extra hooks to the driver, so the compatiblity layer is satisfied. I don't like this solution, because there are many more problems regarding the interaction between saa7146 and v4l. One example: your driver expects hue/brightness/colour/contrast, while the saa7146 delivers brightness/constrast/saturation only... 2) Switch to v4l2. Drivers are available for all common chipsets (bt8x8, saa7134, saa7146), they will be part of the 2.6.x kernel by default. To support this, I made a quick-and-dirty hack porting "tvtime" to v4l2. I fixed most stuff to PAL and threw out everything that's not needed. Some quirks were necessary to squeeze the v4l1 capture scheme to the way v4l2 works. The subsystem should be redesigned though. I attached a diff to the current CVS to this mail. You need to put "videodev2.h" for example to /usr/include/linux. CU Michael. tvtime_v4l2.diff.gz Description: GNU Zip compressed data
[linux-dvb] Re: WinTV Nova - no video device
Hello, I had dvbtune_0.3-2 and dvbstream_0.4pre2-1 mainly working with dvb-driver-_0.9.4 yesterday. I used the stable debian packages. You need the CVS versions of dvbstream/dvbtune to work with the CVS or 1.0.0-pre1 DVB drivers. Regards and Best Wishes, Robert W -Original Message- From: Andreas Pfeil [mailto:[EMAIL PROTECTED] Sent: 04 March 2003 10:23 To: [EMAIL PROTECTED] Subject: [linux-dvb] WinTV Nova - no video device === This e-mail is intended for the person it is addressed to only. The information contained in it may be confidential and/or protected by law. If you are not the intended recipient of this message, you must not make any use of this information, or copy or show it to any person. Please contact us immediately to tell us that you have received this e-mail, and return the original to us. Any use, forwarding, printing or copying of this message is strictly prohibited. No part of this message can be considered a request for goods or services. === Any questions about Bookham's E-Mail service should be directed to [EMAIL PROTECTED] -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hallo, I'm trying to run 2 WinTV Nova cards on a PIII with Kernel 2.4.19. Installing DVB driver (CVS, 20030203) works just fine (no error messages), but I do not seem to get access to a video device. (This PC is supposed to be MPEG-2 video recorder, I basically need the MPEG-Stream). I tried to get data with dvbstream (dvbstream-0.4pre2), the error message is appended. I tried to start vdr (1.0.4), which results as well in an error "Giving up, no video device found". Can anybody help me? Thanks, Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+ZH6L6sUSgqub6HARAijwAJsHN1iH79p3KtHNO9jpZrRPrIOM9ACg4YMh 5dRmHbXQVVhsUaJ1fCJrfYo= =tszX -END PGP SIGNATURE- -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject. === This e-mail is intended for the person it is addressed to only. The information contained in it may be confidential and/or protected by law. If you are not the intended recipient of this message, you must not make any use of this information, or copy or show it to any person. Please contact us immediately to tell us that you have received this e-mail, and return the original to us. Any use, forwarding, printing or copying of this message is strictly prohibited. No part of this message can be considered a request for goods or services. === Any questions about Bookham's E-Mail service should be directed to [EMAIL PROTECTED] -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: Reader idle
Hi, >and my terminal doesn't show anything (no error, no message, nothing) so I >don't know where it the problem!!! The frontend will power down after 1 sec if you dont keep it open. Either open the fe yourself or use szap -r. Bye Florian -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] WinTV Nova - no video device
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hallo, I'm trying to run 2 WinTV Nova cards on a PIII with Kernel 2.4.19. Installing DVB driver (CVS, 20030203) works just fine (no error messages), but I do not seem to get access to a video device. (This PC is supposed to be MPEG-2 video recorder, I basically need the MPEG-Stream). I tried to get data with dvbstream (dvbstream-0.4pre2), the error message is appended. I tried to start vdr (1.0.4), which results as well in an error "Giving up, no video device found". Can anybody help me? Thanks, Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+ZH6L6sUSgqub6HARAijwAJsHN1iH79p3KtHNO9jpZrRPrIOM9ACg4YMh 5dRmHbXQVVhsUaJ1fCJrfYo= =tszX -END PGP SIGNATURE- -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Reader idle
Hi list,
I'm using API 3.0 to develop a Ts-reader with this pes filter:
struct dmx_pes_filter_params flt;
if((ioctl(fd_demuxv, DMX_SET_BUFFER_SIZE, TS_BUF_SIZE))<0){
perror("DMX_SET_BUFFER_SIZE failed:");
return -1;
}
memset(&flt,0,sizeof(struct dmx_pes_filter_params));
flt.pid = pid;
flt.input = DMX_IN_FRONTEND;
flt.output = DMX_OUT_TS_TAP;
flt.pes_type = DMX_PES_OTHER;
flt.flags = DMX_IMMEDIATE_START;
where
#define TS_BUF_SIZE 4096
but when I test the sw (after sint. with dvbtune), it work fine only 1 time
otherwise stop itself at :
n = read(fd_dvr,buf,sizeof(buf)); uint8_t buf[188];
and my terminal doesn't show anything (no error, no message, nothing) so I
don't know where it the problem!!!
Note: after insmod or reboot my sw go well; at the second chance stop!
Why?Thanks
_
MSN Foto: condividi, ritocca e stampa le tue foto online
http://photos.msn.it
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as
subject.
[linux-dvb] Re: WinTV Nova-T PCI, debian novice
Woop, Whoop, Woop, Woop, Whoop, Woop, Whoop, Woop, Whoop, wooop, , Whoop, Woop, Woop, Woop, Whoop. Thank You Gregor, After a bit of flitting about between dvbstream and dvbtune I got a heap load of channel data from Multiplexes 2 & A. This is the first responsive thing this cards done since I got it for X-mas. So I'll uninstall and rebuild with the cvs dvbtune / dvbstream with DVB driver 1.0.0-pre. It time to face up to my irrational fear of the debian kernel sources. Regards and Best Wishes, Rob -Original Message- From: Gregor Lawatscheck [mailto:[EMAIL PROTECTED] Sent: 03 March 2003 11:08 To: [EMAIL PROTECTED] Subject: [linux-dvb] Re: WinTV Nova-T PCI, debian novice At 09:43 03/03/2003, you wrote: >I tried tuning to the BBC channels: > [EMAIL PROTECTED]:~$ dvbtune -c 0 -f 57800 -i > tuning DVB-T to 57800 > Getting frontend event > Received completion event > Event: Frequency: 57800 > Bit error rate: 57 > Signal strength: 0 > SNR: 0 > FE_STATUS: FE_HAS_POWER FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER >FE_HAS_VITERBI FE_HAS_SYNC > > Nothing to read from fd_pat > Nothing to read from fd_sdt > >and here I give up. >Can I fix what I've got? >Is there a better set of packages to use with a nova-t in the uk? > (I have an irrational fear of the debian kernel sources.) Hi Robert, dvbtune 0.42 which works with the 0.9.4 driver doesn't support setting the Modulation (QAM) or FEC on the command line. All but the ITV (oxf: 85) and C5 (oxf: 713833) Transmitter went to FEC 3_4 and QAM 16 sometime late in 2002. If you intend to stream / pipe to watch TV with Mplayer dvbstream is probably the best tool available. Try using cvs dvbtune / dvbstream ( http://sourceforge.net/cvs/?group_id=50669) where you can specify these settings on the command line with DVB driver 1.0.0-pre1 ( http://www.linuxtv.org/news/js/dvbrelease1.xml ). Other than that, something that appears to become popular with UK DVB-T folk these days is to ebay a cheap DXR3 MPEG2 decoder card with TV-out for 10 quid and use it with vdr ( http://www.cadsoft.de/people/kls/vdr ) to watch telly. For more about this see the vdr mailinglist archives at http://www.linuxtv.org/mailinglists/vdr/ Hope that helps, Gregor -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject. === This e-mail is intended for the person it is addressed to only. The information contained in it may be confidential and/or protected by law. If you are not the intended recipient of this message, you must not make any use of this information, or copy or show it to any person. Please contact us immediately to tell us that you have received this e-mail, and return the original to us. Any use, forwarding, printing or copying of this message is strictly prohibited. No part of this message can be considered a request for goods or services. === Any questions about Bookham's E-Mail service should be directed to [EMAIL PROTECTED] -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] 答复: [linux-dvb] DSM-CC implementation
I want to know also. -邮件原件- 发件人: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 代表 Marc Rovira Vall 发送时间: 2003年3月4日 16:39 收件人: [EMAIL PROTECTED] 主题: [linux-dvb] DSM-CC implementation Hi list, Does anybody know an implementation of the DSM-CC specification? I'm developing a DVB data broadcasting application that works with private sections but I'm having some problems trying to build the DSM-CC architecture protocol. Thank you all for your help. Greetings. Marc R. -- 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] Compiling dvb-kernel
Any success ? > -Ursprüngliche Nachricht- > Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 27. Februar 2003 10:58 > An: H.Schöbel > Cc: [EMAIL PROTECTED] > Betreff: Re: [linux-dvb] 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] DSM-CC implementation
Hi list, Does anybody know an implementation of the DSM-CC specification? I'm developing a DVB data broadcasting application that works with private sections but I'm having some problems trying to build the DSM-CC architecture protocol. Thank you all for your help. Greetings. Marc R. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] From Jonas Chen
Dear All: Do you have Object Carousel Generator Software? Sincerely yours, Jonas Chen -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: Can't compile driver
Marc Hutten wrote: Hello, When I try to build the driver I get the following error your kernel include files are screwed up. Get, compile and install a fresh+clean kernel from http://www.kernel.org/. Thenafter please ask your linux distibutor not to break kernel include files by proprietary patchsets. Holger " 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 . -g -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/asm/ptrace.h:60: invalid suffix on integer constant /usr/src/linux-2.4.18-14/include/asm/ptrace.h:60: parse error before numeric constant /usr/src/linux-2.4.18-14/include/asm/ptrace.h:60: `show_regs_R_ver_str' declared as function returning a function /usr/src/linux-2.4.18-14/include/asm/ptrace.h:60: warning: function declaration isn't a prototype In file included from /usr/src/linux-2.4.18-14/include/linux/wait.h:13, from /usr/src/linux-2.4.18-14/include/linux/fs.h:12, from /usr/src/linux-2.4.18-14/include/linux/capability.h:17, from /usr/src/linux-2.4.18-14/include/linux/binfmts.h:5, 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: " I tried it after a clean install of RedHat 8.0 I also build a bzImage make clean make dep make bzImage install driver (lilo) the new kernel started, but compiling the driver running the new driver resulted in the same error. What am I doing wrong? Best regards, Marc Hutten -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
