[vdr] OT: Noise and Power Supply [Was: Re: [PATCH] RGB/PAL over VGA at variable frame rate]
Dear Theunis, Am Mittwoch, den 23.07.2008, 09:41 +0200 schrieb Theunis Potgieter: Only thing making a noise now is the already relatively quiet power supply. You probably already know this, but anyway. There are power supplies called picoPSU which have no fans and are, as far as I understand, more efficient. See [1] for example. Additionally you need an AC/DC adapter which gets, I think, pretty hot but it is placed outside of the case. Also it is a little more expensive than a “normal” PSU but you probably also save some money because of the better efficiency. Regards, Paul [1] http://www.bigbruin.com/reviews05/review.php?item=picopsufile=1 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] OT: [vdr-webvideo] Question to implementation (was: Re: [ANNOUNCE] vdr-webvideo 0.0.2)
Dear Antti, is this plugin just a backend for for example clive or youtube-dl or did you implement the download algorithms all by yourself? I guess the latter one, because the former mentioned packages are not in your build-depend list. But I just want to make sure. Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] OT: VDR for grandparents
Dear list, has anyone on this list any experience in setting up VDR for older people like grandparents? It would be nice, if she/he could share her/his experience or point me to information on the WWW. Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] OT: VDR for grandparents
Dear everyone, thank you for your fast replies. Am Sonntag, den 26.10.2008, 21:30 +0200 schrieb Kartsa: VDR User kirjoitti: has anyone on this list any experience in setting up VDR for older people like grandparents? It would be nice, if she/he could share her/his experience or point me to information on the WWW. I have experience with second best thing after grandparents. A totally clueless user. Since I have setup VDR as the backend sitting near the dish, and added a MediaMVP box next to the TV set, she can use it, record stuff, delete recording, everything. We are using the Hauppauge MediaMVP together with the vdr-plugin-vompserver on the VDR system. Another vote for MediaMVP and vompserver. The user interface is IMO easier to operate than commercial PVRs such as the Humax, and the noisy recorder can be kept out of the living room. While I have not had experience with this myself, I do know a few users who've set up VDR for (grand)parents and wives. From the feedback I've heard, VDR works really well in those scenarios which I think says a lot! ;) I've put a couple of systems up for clueless users with no problem. And now that I think of it one of them is actually a grandmother :) Though I do not think that it is a handicap ;) The good thing is I can maintain them remotely if for some reason it's necessary and thus avoid making time to go there. That is very appealing for me too. I also have a MediaMVP at home but the problem with it is it does not support subtitles and we have a couple channels here using them. Could you please post the hardware components you used. As Tony said in his reply the remote control seems to be one of the crucial parts. I think my “clueless” people would not need a separate server and client, since they just have one TV. So I guess, one could put everything in one machine, which then should just run if they want to record or play a recording. And the cable signal is loopthroughed from the machine to the TV, when they just want to watch TV. Time shifting would not be available during this time though. I think, the machine would not be able to boot fast enough to be a nice user experience. Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] OT: Alice homeTV and vdr
Dear list, can you please share your experiences of using Alice homeTV [3] with vdr. Some more information [4] and [5]. 1. How is the quality [1]? 2. Does it work with the iptv plugin [2]? If not, what are you using? Thanks a lot, Paul [1] http://gutenburger.de/index.php?option=com_contentview=articleid=569:hansenet-laesst-gratis-fernsehencatid=56:video-downloadItemid=76 (German) [2] http://www.saunalahti.fi/~rahrenbe/vdr/iptv/ [3] http://www.alice-dsl.de/kundencenter/export/de/residential/alice_hometv/uebersicht.html (German) [4] http://www.ip-phone-forum.de/showthread.php?t=168118 (German) [5] http://www.ard-digital.de/14028_1 (German) signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [OT] Questions to VGA2SCART cable
Dear readers, I am planning to set up a low budget VDR using the VGA2SCART patches [1]. Therefore I need a VGA2SCART cable. The distance between the VDR and the CRT TV will be probably 5 meters. There are some howtos on the WWW on how to build a cable yourself [2]. But I am not experienced in soldering, so I have the following questions. 1. Are VGA2SCART cables you can buy also suitable and do you have experiences what manufactures produce good quality cables? Searching the WWW I found the following offers but no comparison or review about the quality. http://www.amazon.de/s/?ie=UTF8keywords=vga+scart+kabeltag=googhydr08-21index=apshvadid=1182511121ref=pd_sl_9bos8gcjec_e http://www.kauflux.de/?id=FROOGLE_artnr=8429706 http://shop.strato.de/epages/61223614.sf/?ObjectPath=/Shops/61223614/Products/avkabscavga50ViewAction=ViewProductViaPortalLocale=de_DE http://www.google.de/products?hl=deq=vga+scart+kabelum=1ie=UTF-8ei=G3ChSabnMtKd_gbns83WCwsa=Xoi=product_result_groupresnum=4ct=title http://www.supernature-forum.de/allgemeine-computerfragen/63171-grafik-gibt-es-vga-scart-kabel.html http://forum.fachinformatiker.de/hardware/122150-vga-scart-kabel-tv.html inakustik claims to have high quality cables. http://www.in-akustik.com/de/KABEL/Home-Video/VGA-Scartkabel.htm 2. Are there any disadvantages in buying these cables? a) I would guess, that most of the cables do not have plugs for audio next to the VGA plug, so that I will need to either use an amplifier or have to modify the cable and solder some wires to the SCART-plug. Thanks a lot, Paul ¹ With around 10 € for a 5 meter cable they do not seem to be that much expensive. [1] http://www.linuxtv.org/pipermail/vdr/2008-July/017347.html [2] http://www.vdr-portal.de/board/thread.php?postid=742945#post742945 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [OT] development infrastructur for VGA2SCART patch set (was: Re: Options for deinterlacing (or not))
Dear Thomas and fellow developers, Am Mittwoch, den 21.01.2009, 17:42 +0100 schrieb Thomas Hilber: On Wed, Jan 21, 2009 at 05:07:40PM +0200, Pasi Kärkkäinen wrote: I think someone should step ahead and help with the english docs.. unfortunately I can't do that atm, too busy with other things.. after travelling over 5 weeks in Australia this now is my major problem too:-) Is there a homepage for the VGA2SCART patch set with information about it? A repository? There seems to be some interest from people outside VDR Portal [1] in the patches. So a repository with all the different branches (for example yours and durchfliegers) could be used to manage the files. Would a Wiki page be useful or is the README enough? Have you already thought about this and came to the conclusion it is not necessary? Or could one ask the project your patches are related to, if they could set up a branch for each of the patches and the information is managed in a Wiki like VDR Wiki [2] or the one of Freedesktop [3]? Thanks, Paul [1] www.vdr-portal.de [2] http://www.vdr-wiki.de/wiki/index.php/Hauptseite [3] http://www.freedesktop.org/wiki/ signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [OT] Questions to VGA2SCART cable
Dear Christoph, thanks for your answer and saving me from trouble. I moved your answer inline. Am Mittwoch, den 25.02.2009, 13:25 +0100 schrieb C.Scheeder: Paul Menzel schrieb: Dear readers, I am planning to set up a low budget VDR using the VGA2SCART patches [1]. Therefore I need a VGA2SCART cable. The distance between the VDR and the CRT TV will be probably 5 meters. There are some howtos on the WWW on how to build a cable yourself [2]. But I am not experienced in soldering, so I have the following questions. 1. Are VGA2SCART cables you can buy also suitable and do you have experiences what manufactures produce good quality cables? Searching the WWW I found the following offers but no comparison or review about the quality. http://www.amazon.de/s/?ie=UTF8keywords=vga+scart+kabeltag=googhydr08-21index=apshvadid=1182511121ref=pd_sl_9bos8gcjec_e http://www.kauflux.de/?id=FROOGLE_artnr=8429706 http://shop.strato.de/epages/61223614.sf/?ObjectPath=/Shops/61223614/Products/avkabscavga50ViewAction=ViewProductViaPortalLocale=de_DE http://www.google.de/products?hl=deq=vga+scart+kabelum=1ie=UTF-8ei=G3ChSabnMtKd_gbns83WCwsa=Xoi=product_result_groupresnum=4ct=title http://www.supernature-forum.de/allgemeine-computerfragen/63171-grafik-gibt-es-vga-scart-kabel.html http://forum.fachinformatiker.de/hardware/122150-vga-scart-kabel-tv.html inakustik claims to have high quality cables. http://www.in-akustik.com/de/KABEL/Home-Video/VGA-Scartkabel.htm as far as i read, all these are kabels to connect a scart-OUTPUT to an VGA-INPUT. (scart-out of receiver to vga-in of a beamer/lcd-tv) These cables are useless for connecting a VGA-card to a monitor, as they do not handle the vga-sync-singals correct. If you use them, you probably won't get a picture and perhaps will fry your tv and/or vga-card. Does anyone know of a shop (in Europe, better Germany) selling the correct cables? 2. Are there any disadvantages in buying these cables? a) I would guess, that most of the cables do not have plugs for audio next to the VGA plug, so that I will need to either use an amplifier or have to modify the cable and solder some wires to the SCART-plug. ¹ With around 10 € for a 5 meter cable they do not seem to be that much expensive. [1] http://www.linuxtv.org/pipermail/vdr/2008-July/017347.html [2] http://www.vdr-portal.de/board/thread.php?postid=742945#post742945 Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [OT] development infrastructur for VGA2SCART patch set
Dear Thomas, thanks for your answer. Am Mittwoch, den 25.02.2009, 15:49 +0100 schrieb Thomas Hilber: On Wed, Feb 25, 2009 at 01:35:01PM +0100, Paul Menzel wrote: Is there a homepage for the VGA2SCART patch set with information about it? A repository? due to lack of time and interest I do not yet run a full blown homepage. But at least I started to collect the plain patches here [3]. That is what I thought. So maybe other people who are not good or intersted in coding could help set up this web site and repository. Would you be willing to use this. Do you have a favorite system for SCM (Git, Subversion, …)? @Tobi: Could the patches be hosted on projects.vdr-developers.org? Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [OT] development infrastructur for VGA2SCART patch set
Am Donnerstag, den 26.02.2009, 19:47 +0100 schrieb Thomas Hilber: On Thu, Feb 26, 2009 at 09:12:36AM +0100, Paul Menzel wrote: due to lack of time and interest I do not yet run a full blown homepage. But at least I started to collect the plain patches here [3]. That is what I thought. So maybe other people who are not good or intersted in coding could help set up this web site and repository. Would you be willing to use this. Do you have a favorite system for SCM At least somebody must start such a page.. For the moment it takes less time for me to answer questions in the corresponding threads on easy-vdr.de and vdr-portal.de directly. I would be willing to begin to start such a page. But I wanted to know your preferences, so that chances are high, that you will feel comfortable with it. I will ask the owners of projects.vdr-developers.org again. Why don't you just use the easy-vdr install script I mentioned above which already has been proven successful? I just checked it out. But the main problem in distribution is, that everyone has to register to be able to download attachments. If you are interested in what's happening behind the scenes - no problem. The script builds all VGA2SCART + FRC relevant things from source. I just took a look. On quick look at the homepage and the Wiki I could not find any information on [1] on what Easy VDR does and on what distro it is based. Looking at the script it looks like it is based on Debian Etch. There is no better way to document an installation than a working shell script:-) Of course, but if one has to register at a forum to get the files it will prevent people from getting it and to contributing to the project. That is why I think a repository would be helpful. Then everything relating to the code would be in one place and work does not have to be done twice because one did not see that thread were someone else already implemented this. I find it very difficult to jump through all the threads of the forum and reads through all the posts and most of the time read it several times. Thanks a lot, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [OT] development infrastructur for VGA2SCART patch set
Am Sonntag, den 01.03.2009, 00:29 +0100 schrieb Tobi: Paul Menzel wrote: @Tobi: Could the patches be hosted on projects.vdr-developers.org? In general I would have no objections against this. What kind of patches is this all about? I haven't followed this VGA2SCART thing, but a quick lookup showed, that this involves patching XOrg stuff and xineliboutput. That is correct. It requires several programs to be patched. If this is the case, then a single Git repository might not be appropriate. Right. Creating a directory for each individual program might not be the best solution. Let us wait, what Thomas will answer. Thanks for your reply, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [OT] development infrastructur for VGA2SCART patch set
Am Montag, den 02.03.2009, 17:26 +0100 schrieb Thomas Hilber: On Mon, Mar 02, 2009 at 01:19:53PM +0100, Paul Menzel wrote: Concerning the wiki: I would prefer a neutral domain Sure. I had no other domain handy. Your domain name could also be used, if you set up DNS this way (vga2scart.lowbyte.de) or we register some free domain name vga2scart.de.vu or vga2scart.eu.org? something like vga2scart.eu.org sounds good. Though our project is not limited to vga2scart. In the meantime I successfully use a modified version of the vga-sync-fields patch on DVI/HDMI interface also. Providing me high quality 576i over DVI/HDMI on intel i9xx machines with SDVO ports. Originating from SDTV our project could be important for HDTV also. Everyone, could please brainstorm about a name for this project [5]. or even better http://www.linuxtv.org/wiki/ for this. If you are fine with that, great. My reasoning choosing ikiwiki is, that I would expect it to save you (and others) time. I wonder why nobody else joins our discussion. […] You can setup a repos with current source found in vga-sync-fields package at anytime. Everybody is invited to test and contribute. I don't consider it as 'my' project. I just will contribute the initial idea behind frame rate control and a sample implementation for it. And of course I will continue to develop as time permits. […] As said, I don't consider it as my project. Everybody is invited to improve the project status. There are left many ideas and features still not implemented. As written in my other message I continued to set up ikiwiki for the project [5]. If something else will be better for the project, please say so and we can change that. I consider the most important thing right to get someone to publish detailed instruction on how a VGA2SCART cable can be assembled. For me a circuit diagram is not good enough for an inexperienced user in soldering as myself. (Do I attach/fix the resistors on a board or just between the wires? Where can I get the parts? …) I already wrote a to-do list with issues of lesser priority. But features that would improve things a lot. - like writing a tool similar to powerstrip. Which lets you adjust overscan and other parameters in real time by pressing cursor keys. or - derive xine's masterclock from graphics card frame rate. This would provide almost instant sync after a channel switch. The idea for this was published by 'durchflieger' [3] There are still left many things to do. As often in life it's not a matter of ideas but a matter of time:) I added those two to the TODO list of the website [6]. Thanks, Paul [1] http://vdr-wiki.de/wiki/index.php/Hauptseite [2] http://www.linuxtv.org/vdrwiki [3] http://www.vdr-portal.de/board/thread.php?postid=796538#post796538 [4] http://www.easy-vdr.de/forum/index.php?topic=6072.msg51320#msg51320 [5] http://vga2scart.gw90.de/ [6] http://vga2scart.gw90.de/todo/ signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [OT] development infrastructur for VGA2SCART patch set
Dear everyone, Am Donnerstag, den 05.03.2009, 20:51 +0100 schrieb Luca Olivetti: En/na Timothy D. Lenz ha escrit: Mail should be text and any code should be limited to files that are in no way run by the mail program. […] Do the world a favour and use a real email program, or stop complaining about well formed messages. Although I agree, I want to thank Timothy for at least answering me. Thanks Timothy, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Clients with graphical output over USB (was: Re: A new possibility for lower power high performance VDR)
Dear Mika, Am Sonntag, den 08.03.2009, 10:53 +0200 schrieb Mika Laitio: I have myself thinked about the possibility of running vdr/xineliboutput client on low end systems that just have usb 2.0 but not any graphic cards or free pci slots available. So, does that mean, those boards do not have a graphic chip of any kind? Has anybody experiences from the usb vga or usb dvi graphic card adapters like these? Sorry, I do not. Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [VGA sync field] question to fb-radeon-intel.patch
Dear Thomas, 1. In your patchset the patch fb-radeon-intel.patch [1] does include changes to drivers/video/intelfb/intelfbhw.c although in the install instructions [2] it is stated that intel drivers do not need to be modified. The changelog in 0.11 includes these two items. - patch against intelfb (kernel 2.6.26) to allow for PAL/SCART video timings. You now can use a regular SCART CRT as display for linux console. - fixed a bug in intelfb initialization which sporadically setup video timing with weirdous values I guess the installation instructions need to be updated for release 0.11. If this is correct I would update the instructions. 2. Well I was going to ask this question on linux-fbdev-devel but did not do so until I get a reply to my other message. a) Why is MIN_CLOCK set to 25000 in intelfbhw.h [3]? What would be the downside of setting it to 1? b) Where do I get information about the registers, like what DPLL_A and DPLL_VCO_ENABLE is? In the header file some values are assigned to them, but where is it documented what they mean? DPLL_A VCO for interlaced mode 800x...@50i\n); OUTREG(DPLL_A, INREG(DPLL_A) ~DPLL_VCO_ENABLE); Thanks, Paul [1] http://git.hellersdorfer-jugendchor.de/?p=vga2scart.git;a=blob;f=patches/fb-radeon-intel.patch;h=6292c031f8ab67ac0fc7f2d031870fe994eed57a;hb=f560a83274cf13f7fe99a9f4d9e9ef1ccf69b0c4 [2] http://vga2scart.gw90.de/install/ (last section) [3] http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.28.y.git;a=blob;f=drivers/video/intelfb/intelfbhw.h;h=0b076bac321b82559b2240105503751e843b1cc3;hb=HEAD signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [VGA sync field] question to fb-radeon-intel.patch
Am Donnerstag, den 12.03.2009, 19:08 +0100 schrieb Thomas Hilber: On Thu, Mar 12, 2009 at 06:31:47PM +0100, Thomas Hilber wrote: a) Why is MIN_CLOCK set to 25000 in intelfbhw.h [3]? What would be the downside of setting it to 1? MIN_CLOCK is set to 12000 by the patch. What allows for SCART suitable dotclocks. I don't know why the original driver denies such low clock frequencies. I forgot to say patching the intelfb is only needed if you even want to run the linux console in VGA2SCART mode. For the Xserver in VGA2SCART+FRC mode it's not needed. Thanks. I figured that after reading a lot of threads. (And thanks for your other answer.) I hope, you have seen my message to linux-fbdev-devel [1]. I will try to do what Krzysztof suggested, but will have to read more about that. Maybe we get it into Linux kernel 2.6.30. Should we continue discussion about this on linux-fbdev-devel, that means, can subscribe there? Thanks, Paul [1] http://sourceforge.net/mailarchive/forum.php?thread_name=1236701836.4068.85.camel%40mattotaupa.wohnung.familie-menzel.netforum_name=linux-fbdev-devel signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [VGA sync field] question to fb-radeon-intel.patch
Am Donnerstag, den 12.03.2009, 18:31 +0100 schrieb Thomas Hilber: On Wed, Mar 11, 2009 at 06:15:04PM +0100, Paul Menzel wrote: 1. In your patchset the patch fb-radeon-intel.patch [1] does include changes to drivers/video/intelfb/intelfbhw.c although in the install instructions [2] it is stated that intel drivers do not need to be modified. sorry, install instructions are not up to date for the Intel version of the patch. The changelog in 0.11 includes these two items. - patch against intelfb (kernel 2.6.26) to allow for PAL/SCART video timings. You now can use a regular SCART CRT as display for linux console. - fixed a bug in intelfb initialization which sporadically setup video timing with weirdous values I guess the installation instructions need to be updated for release 0.11. right. as said installation instructions have not been touched since a while. I just included the plain Intel patches into the package. There was not yet too much interest in the patches anyway. So I did not want to waste my time for documentation:-) If this is correct I would update the instructions. thank you for that. Done (commit 89ddb9af67be949be3be01f795f964926728f45a). Not much, but I hope alright. Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [FRC] Why are patches for framebuffer not needed anymore in release 0.1.0?
Dear Thomas, you released version 0.1.0 [1]. Could you please explain to me, why the framebuffer patches (intelfb, radeonfb) are not needed anymore? Thanks a lot, Paul [1] http://lowbyte.de/vga-sync-fields/vga-sync-fields/ signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] OT: Germany/IPTV: Watching private stations on PC?
Dear everyone, some German providers offer IPTV. Public stations are broadcasted using DVB IPTV/multicast(?) [1][2] and I can watch them using a special port of the provided modem and for example mplayer. Do you know if it is possible to watch also private stations on the computer? Using the provided Set-Top-Box and a smartcard(?) it is possible to watch those and even stream movies from a videothek. I did not find any information or tutorials on the Web. The thought behind this is, if I could not do this, if it would be useful to build a PVR with vdr, if I was not able to play those stations¹. One way solution would be to use DVB-T. But I would like to circumvent that. Thanks in advance, Paul ¹ Sure, it still has advantages like the possibility to surf the Web and to set up everything to my need. But the main point is still to watch TV. [1] http://www.ard-digital.de/14026_1 [2] http://www.unternehmen.zdf.de/index.php?id=248 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] OT: Germany/IPTV: Watching private stations on PC?
Am Donnerstag, den 02.04.2009, 07:20 +0200 schrieb Steffen Barszus: Paul Menzel schrieb: Dear everyone, some German providers offer IPTV. Public stations are broadcasted using DVB IPTV/multicast(?) [1][2] and I can watch them using a special port of the provided modem and for example mplayer. [1] http://www.ard-digital.de/14026_1 [2] http://www.unternehmen.zdf.de/index.php?id=248 Looks like you are searching for the iptv plugin: http://www.saunalahti.fi/~rahrenbe/vdr/iptv/ http://www.vdr-wiki.de/wiki/index.php/Iptv-plugin Thanks. I had read about it before. But I cannot see how it should help in accessing the private stations. Does anyone have the IP addresses? According to this thread, at least for T-Home Entertain, those channels are encrypted and only accessible with the provided streaming device/set-top-box [3]. Is there a way to circumvent this? Thanks, Paul [3] http://www.vdr-portal.de/board/thread.php?threadid=80314 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] OT: Germany/IPTV: Watching private stations on PC?
Dear Artem, Am Donnerstag, den 02.04.2009, 22:54 +0200 schrieb Artem Makhutov: On Thu, Apr 02, 2009 at 04:11:02PM +0200, Paul Menzel wrote: Am Donnerstag, den 02.04.2009, 07:20 +0200 schrieb Steffen Barszus: Paul Menzel schrieb: Dear everyone, some German providers offer IPTV. Public stations are broadcasted using DVB IPTV/multicast(?) [1][2] and I can watch them using a special port of the provided modem and for example mplayer. [1] http://www.ard-digital.de/14026_1 [2] http://www.unternehmen.zdf.de/index.php?id=248 Looks like you are searching for the iptv plugin: http://www.saunalahti.fi/~rahrenbe/vdr/iptv/ http://www.vdr-wiki.de/wiki/index.php/Iptv-plugin Thanks. I had read about it before. But I cannot see how it should help in accessing the private stations. Does anyone have the IP addresses? According to this thread, at least for T-Home Entertain, those channels are encrypted and only accessible with the provided streaming device/set-top-box [3]. Is there a way to circumvent this? You can use Alice HomeTV to watch private stations. They are not encrypted. Great news. Do you know what the IP addresses for the stations are? Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] only get DVB-related messages from linux-media (was: Re: Compilation issues with recent DVB header files vs libc6)
Am Donnerstag, den 09.04.2009, 09:35 +0200 schrieb Klaus Schmidinger: On 04/09/09 09:25, Niels Wagenaar wrote: Op Do, 9 april, 2009 08:29, schreef Matthias Becker: According to my information (a message on the linux-dvb mailinglist), the old mailinglists (V4L and DVB) are now merged into linux-media. what does merged mean? Are Posts on the old list replicated to the new one? No. Merge as in combined to one and/or a replacement for the old V4L/DVB mailinglists. Messages send to the 'old' mailinglists will not automaticly be available on the linux-media mailinglist. That is, if you don't count a CC as a replication method ;-) Well, so what is the preferred method of making the DVB driver developers aware of bugs, if one doesn't want to suffer from all the traffic on the linux-media list? I did initially subscribe to that list, but after a few days I unsubscribed again, because there was way too much non DVB related stuff there. I conclude your current situation is, that right now you do not get any dvd-related messages, since you are not subscribed. I propose, that you subscribe, and do one of the following. • Either configure your list options to not receive any messages. That way you can send messages to report bugs and maybe ask to CC you. • Or set up a filter in your mail program to delete all messages from this list except they have [DVB] or so in the subject line and make sure the subject of your messages contains this word. […] Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.4 memory leak?
Am Sonntag, den 12.04.2009, 16:30 +0200 schrieb Klaus Schmidinger: On 04/12/09 16:20, marti...@embl.de wrote: I have setup an HTPC based on oxine + vdr It has 2gigs of RAM and another 2gigs of Swap space Upon booting it uses about 300megs of RAM. 5 hours later (running vdr all this time) I notice most of the ram is in use. Is this a known memory leak or a design feature? Neither one ;-) If a known memory leak is there a patch for it or we need to wait for 1.7.5? I have released version 1.7.5 earlier today. Please test if it happens with this one, too. top - 16:15:00 up 45 min, 2 users, load average: 1.06, 1.34, 1.45 Tasks: 113 total, 1 running, 112 sleeping, 0 stopped, 0 zombie Cpu(s): 21.2%us, 2.5%sy, 0.2%ni, 76.2%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 1811916k total, 1765156k used,46760k free,15640k buffers Swap: 2096472k total, 4972k used, 2091500k free, 1449112k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 6486 root 20 0 203m 59m 19m S 16 3.4 5:18.98 oxine 6699 root 20 0 172m 11m 5680 S 14 0.7 5:06.00 vdr 6133 root 20 0 94144 50m 32m S9 2.9 1:21.67 Xorg 6721 root 15 -5 000 S2 0.0 0:37.73 cx88[0] dvb 6330 root 20 0 63672 2324 1752 S1 0.1 0:16.44 CCcam.x86 6702 root 15 -5 000 S1 0.0 0:12.24 kdvb-ad-0-fe-0 1 root 20 0 3056 1900 576 S0 0.1 0:01.60 init I dont' see a problem here. Can you post the same info when the problem actually happens? Maybe you can sort it by memory usage (shift + m). Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] test material to evaluate image quality on TV set
Dear list, I searched for all variants of test material for ff-card or full featured tv set vdr test material on the WWW to no avail. I only found [1] which also voices this wish. Could you please tell me where I could get some video files to test the quality of my setup/system. I remember sometimes there is some test images on the TV broadcasted by the TV station if there is an error(?). Thanks a lot, Paul [1] http://www.mail-archive.com/vdr@linuxtv.org/msg09256.html signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [xineliboutput] [PATCH] [README] Fix typos and give whole command for consistency.
Signed-off-by: Paul Menzel paulepan...@users.sourceforge.net CC: Petri Hintukainen phint...@users.sourceforge.net --- README | 12 ++-- 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/README b/README index 9e4a176..7d79bdc 100644 --- a/README +++ b/README @@ -154,20 +154,20 @@ Using remote frontends with vdr-??fe --help. Frontend should find server automatically (from local subnet) - and negoate best available transport. If frontend does not + and negotiate best available transport. If frontend does not find server (or specific transport should be used), mrl must be given on command line. Examples: Search for VDR (xineliboutput) server, connect to it and -negoatite best available transport. Use best available audio +negotiate best available transport. Use best available audio and video driver. vdr-fbfe or vdr-sxfe -Connect to 192.168.1.3 default port and negoate best available transport +Connect to 192.168.1.3 default port and negotiate best available transport vdr-fbfe xvdr://192.168.1.3 Connect to 192.168.2.100, port 12550 and use TCP transport @@ -179,8 +179,8 @@ Using remote frontends vdr-fbfe --udp Available transports for video/audio - pipe Use local pipe; server and front-end must be running in -same machine + pipe Use local pipe; server and front-end must be running on +same machine. rtp Use RTP/UDP multicast for data and TCP for control. Multiple frontends can receive same stream. udp Use UDP unicast for data and TCP for control. @@ -206,7 +206,7 @@ Using remote frontends --video xvmc:127.0.0.1:1.0 With framebuffer frontend (vdr-fbfe): ---video [fb | DirectFB | sdl | vidixfb | dxr3 | aadxr3 | none [:fb_device]] +vdr-fbfe --video [fb | DirectFB | sdl | vidixfb | dxr3 | aadxr3 | none [:fb_device]] Examples: --video DirectFB --video fb:/dev/fb/1 -- 1.6.2.4 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [iptv] [input_vdr] No data in 8 seconds, queuing no signal image
Dear list, I am trying to set up IPTV for German public stations. They provide the multicast addresses [1]. I have to use the Hansenet ones. They also provide playlists for VLC and MPlayer [2]. I used VLC to watch some channels and that worked quite OK, if the modem has synced correctly(?), i. e. has a good connection. With VLC it stuttered every 5 seconds with some channels. I followed [3] and the README.Debian of the vdr-plugin-iptv package from [4]. I came up with the following. $ cat /etc/vdr/channels.conf […] :@1000 New channels Das-Erste;IPTV:10:IPTV|S0P0|EXT|vlc2iptv|1:P:0:2:3:0:0:1:0:0:0 $ cat /etc/vdr/plugins/iptv/vlcinput/Das-Erste.conf URL=rtp://233.51.128.19:1234 VPID=2 APID=3 SPID=4 I start VDR with the following command. $ sudo vdr -P iptv -P xineliboutput -l3 Then I get a black screen with the information/sender name IPTV. After some more seconds I get a NO STREAM/SIGNAL screen. You can find the output written to syslog at the end of this message. I use the following versions of the sofware. $ vdr --version vdr (1.6.0-2/1.6.0) - The Video Disk Recorder iptv (0.2.5) - Experience the IPTV xineliboutput (1.0.90-cvs) - X11/xine-lib output plugin Can you give me a hint on what I made wrong or what might be the problem. Maybe I messed up some syntax in the configurations files. Thanks a lot, Paul [1] http://www.ard-digital.de/index.php?id=14029languageid=1 [2] http://www.ard-digital.de/index.php?id=14028languageid=1 [3] http://www.saunalahti.fi/~rahrenbe/vdr/iptv/ [4] http://www.e-tobi.net/repositories/repositories.html May 2 14:07:38 mattotaupa vdr: [18648] switching to channel 1000 May 2 14:07:38 mattotaupa vdr: [18818] [input_vdr] BLANK in middle of stream! bufs queue 0 , video_fifo 8 May 2 14:07:38 mattotaupa vdr: [19126] receiver on device 9 thread started (pid=18648, tid=19126) May 2 14:07:38 mattotaupa vdr: [19128] IPTV streamer thread started (pid=18648, tid=19128) May 2 14:07:38 mattotaupa vdr: [19125] transfer thread started (pid=18648, tid=19125) May 2 14:07:44 mattotaupa vdr: [18773] [vdr-fe]Keypress: XKeySym u May 2 14:07:45 mattotaupa vdr: [18773] [vdr-fe]Keypress: XKeySym u May 2 14:07:45 mattotaupa vdr: [19125] transfer thread ended (pid=18648, tid=19125) May 2 14:07:45 mattotaupa vdr: [18648] buffer stats: 0 (0%) used May 2 14:07:45 mattotaupa vdr: [18648] replay /var/lib/video.00/@IPTV/2009-05-02.11.24.50.99.rec May 2 14:07:45 mattotaupa vdr: [18648] playing '/var/lib/video.00/@IPTV/2009-05-02.11.24.50.99.rec/001.vdr' May 2 14:07:45 mattotaupa vdr: [19292] dvbplayer thread started (pid=18648, tid=19292) May 2 14:07:45 mattotaupa vdr: [19293] non blocking file reader thread started (pid=18648, tid=19293) May 2 14:07:45 mattotaupa vdr: [19128] IPTV streamer thread ended (pid=18648, tid=19128) May 2 14:07:45 mattotaupa vdr: [19126] receiver on device 9 thread ended (pid=18648, tid=19126) May 2 14:07:45 mattotaupa vdr: [19293] non blocking file reader thread ended (pid=18648, tid=19293) May 2 14:07:45 mattotaupa vdr: [19292] dvbplayer thread ended (pid=18648, tid=19292) May 2 14:07:46 mattotaupa vdr: [18648] switching to channel 1000 May 2 14:07:46 mattotaupa vdr: [18818] [input_vdr] BLANK in middle of stream! bufs queue 0 , video_fifo 0 May 2 14:07:46 mattotaupa vdr: [19294] transfer thread started (pid=18648, tid=19294) May 2 14:07:46 mattotaupa vdr: [19295] receiver on device 9 thread started (pid=18648, tid=19295) May 2 14:07:46 mattotaupa vdr: [19297] IPTV streamer thread started (pid=18648, tid=19297) May 2 14:07:46 mattotaupa vdr: [18773] [vdr-fe]Keypress: XKeySym Alt_L May 2 14:07:54 mattotaupa vdr: [18818] [input_vdr] No data in 8 seconds, queuing no signal image May 2 14:07:54 mattotaupa vdr: [18818] [input_vdr] using custom no signal image /usr/share/libxine1-xvdr/nosignal.mpg signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] e-tobi.net Debian packages: vdrdevel for Debian Sid/Unstable?
Dear list, does anyone know, how I can get the vdrdevel packages for Debian Sid/Unstable? I searched for »vdrdevel e-tobi sources.list sid«, but only found [1][2], where I did not get any information for vdrdevel on [1] and for Debian Sid on [2]. Can I simply use the packages for Lenny? Thanks, Paul [1] http://www.e-tobi.net/blog/pages/vdr-repository [2] http://www.vdr-portal.de/board/thread.php?threadid=86433sid=f5e26c74c628343fbeccea7d60bb7c9a signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [solved] [iptv] [input_vdr] No data in 8 seconds, queuing no signal image
Am Sonntag, den 03.05.2009, 12:16 +0300 schrieb Antti Seppälä: Paul Menzel wrote: Am Samstag, den 02.05.2009, 21:24 +0300 schrieb Antti Seppälä: Do you know what encoding format your provider uses for the streams? Play it with mplayer -v rtp://233.51.128.19:1234 to see the information. TRIED UP TO POSITION 321104, FOUND 47, packet_size= 188, SEEMS A TS? 1 Mplayer detects that your stream is transport stream, which is what vdr requires. PARSE_PMT(28106 INDEX 0), STREAM: 0, FOUND pid=0x30 (48), type=0x1005, ES_DESCR_LENGTH: 0, bytes left: 28 ...descr id: 0xa, len=4 Language Descriptor: deu PARSE_PMT(28106 INDEX 1), STREAM: 1, FOUND pid=0x31 (49), type=0x50, ES_DESCR_LENGTH: 6, bytes left: 17 ...descr id: 0x56, len=10 PARSE_PMT(28106 INDEX 2), STREAM: 2, FOUND pid=0x34 (52), type=0x, ES_DESCR_LENGTH: 12, bytes left: 0 This is the pid information vdr also requires in the channels.conf entry. Searching for picture parameter set... H264: 0x128 OK! This means that the stream is using h264 encoding. I tried it with S0P0 and there was only a black screen shown and I could see the VDR menu on top of it. I also noticed the the following line was added to channels.conf. I do not know how it got there. Das Erste;ARD:10:IPTV|S0P0|UDP|233.51.128.19|1234:P:0:0:49=deu:52:0:28106:1:1019:0 The line was added by vdr when it detected that the stream is in the format it supports. (Though I wonder if it shouldn't happen when disabling sid scanning with S0.) It also means that iptv plugin is working and the stream in rtp format is really supported. The entry contains 0 as the video pid which means that the channel is treated like a radio channel. Changing to this channel with the up key, I could hear the audio, but instead of the video some kind of animation was shown. Those you can set up in your media players and which move to the audio. This is what xineliboutput does when viewing a radio channel. It's called the goom plugin. I think you are only missing h264 support from vdr core which could be the reason why the video pid of the channel is set to zero. A patch for adding h264 support to vdr 1.6 -series is included in this mailing list post: http://www.linuxtv.org/pipermail/vdr/2008-March/016227.html It's the vdr-1.5.18-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff.bz2 and it works for 1.6 even though the name suggests 1.5 version. Vdr 1.7.x includes h264 support by default. I just wanted to confirm that you were right all the way. I get video with VDR 1.7.7 (although I will have to tweak my system to get it fluent). Thanks a million for your great and fast replies. Bests, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] e-tobi.net Debian packages: vdrdevel for Debian Sid/Unstable?
Am Montag, den 11.05.2009, 09:05 +0200 schrieb Thomas Creutz: Paul Menzel schrieb: Can I simply use the packages for Lenny? yes, normally the lenny packages should work very well with sid, give it a try ;-) Tobias answered me off-list. See my other message for a conclusion. Am Dienstag, den 05.05.2009, 20:10 +0200 schrieb Tobias Grimm: Ich schätze die Lenny-Pakete würden auch nicht so ohne weiteres unter Sid funktionieren. Translation I guess the Lenny packages would not work out of the without any further manual adaptations. Bests, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [solved] e-tobi.net Debian packages: vdrdevel for Debian Sid/Unstable?
Dear list, thanks to Tobias Grimm and Thomas Günther her comes the solution. Am Sonntag, den 03.05.2009, 17:30 +0200 schrieb Paul Menzel: does anyone know, how I can get the vdrdevel packages for Debian Sid/Unstable? Right now there are not vdrdevel packages for Debian Sid/Unstable. […] Can I simply use the packages for Lenny? Probably not. But nobody tried. But the sources build without problems. Thomas Günther gave the following instructions with one correction by Tobias. Am Mittwoch, den 06.05.2009, 00:57 +0200 schrieb Thomas Günther: […] echo deb-src http://e-tobi.net/vdr-experimental lenny base backports addons vdr-multipatch /etc/apt/sources.list sudo apt-get update sudo apt-get build-dep vdr PATCHVARIANT=multipatch SPECIAL_VDR_SUFFIX=devel apt-get source -b vdr sudo dpkg -i vdrdevel-dev_* sudo apt-get build-dep vdr-plugin-epgsearch SPECIAL_VDR_SUFFIX=devel apt-get source -b vdr-plugin-epgsearch […] These packages run without any problem under Debian Sid/Unstable. Thanks, Paul [1] http://www.e-tobi.net/blog/pages/vdr-repository [2] http://www.vdr-portal.de/board/thread.php?threadid=86433sid=f5e26c74c628343fbeccea7d60bb7c9a signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] test material to evaluate image quality on TV set
Dear list, Am Freitag, den 24.04.2009, 17:11 +0200 schrieb Paul Menzel: […] Could you please tell me where I could get some video files to test the quality of my setup/system. I remember sometimes there is some test images on the TV broadcasted by the TV station if there is an error(?). Vesa Solonen gave me a great resource with test material for testing TV output display quality [1]. Thanks, Paul [1] http://www.kingcot.eclipse.co.uk/unichrome/tvoutTest.html signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [OT] What about the VIA VX855?
Dear list, there has been some talk about the new ION chipset from NVIDIA on this list [1]. Intel also published a board which is said to be very promising for SD (standard definition) material [2] (at least with the FRC (frame rate control) patches [3]. So what about the VIA VX855 chipset [4] as the basis for a multimedia platform? VIA publishes the docs and it looks like it will even be supported by coreboot [5][6]. I know it depends on what you need (SD or HD and so on). But I searched for »vx855 vdr«, »vx855 xbmc«, »vx855 mythtv« on the WWW and did not get meaningfull results. Or is the problem, that there are no boards available yet? What do you think? Thanks, Paul [1] http://linuxtv.org/pipermail/vdr/2009-May/020457.html [2] http://www.vdr-portal.de/board/thread.php?threadid=86810 [3] http://frc.easy-vdr.de/ [4] http://www.tomshardware.com/news/Via-VX855-chipset,7261.html [5] http://www.coreboot.org/ [6] http://www.coreboot.org/pipermail/coreboot/2009-May/048829.html signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Any really working HD video output systems for VDR?
Am Freitag, den 05.06.2009, 15:42 +0200 schrieb Thomas Hilber: On Fri, Jun 05, 2009 at 11:17:54AM +0200, jori.hamalai...@teliasonera.com wrote: It would mean that no judder and studder on HD-quality. With VDPAU the problem still might be 50Hz vs 50.02Hz -thing so you cannot get frame accurate display. With every 5 seconds you might have duplicated display of frame or dropped frame. This is not acceptable by my I fully agree. The *only* way to overcome this is by synchronizing VGA video timing to DVB-stream clock. I realized this for some ATI-Radeon and Intel-GMA hardware. Even the brandnew Intel D945GSEJT now is fully supported with VGA/SCART/DVI/HDMI output. Could you test your boards with HD-material, for example some movie trailers? Could you please share your results, what resolutions are possible to play and how much the system usage is doing so? I found the following on VDR-Portal. Your mpstat results for playing SD material [2] and x.264 encoded material [3] from [8]. [4] has a row »HDTV Video Wiedergabe« which says non-fluent playback. [5] claims to be playing 1080p HD material on an ASUS EeePC 901. Specifications for the GMA 950 from Intel state »HDTV 480i/p, 576i/p, 720i/p and 1080i/p display resolution support« [7]. [6] says something similar. So is the following summary correct? The hardware is capable to play certain HDTV resolutions, but the xf86-video-intel driver does not support it yet. Thanks, Paul [1] http://www.vdr-portal.de/board/thread.php?postid=816759#post816759 [2] http://www.vdr-portal.de/board/thread.php?postid=816443#post816443 [3] http://www.vdr-portal.de/board/attachment.php?attachmentid=22074 [4] http://www.minitechnet.de/asus-n10_5.html [5] http://www.youtube.com/watch?v=JVf3PtNF-j0 [6] http://www.intel.com/design/intarch/applnots/DSS_Appnote_r5.pdf [7] http://www.intel.com/products/chipsets/gma950/index.htm [8] http://www.vdr-portal.de/board/thread.php?postid=816831#post816831 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [OT] Boot time of Intel D945GSEJT (Johnstown)
Dear list, can a knowledgeable person please write how long the BIOS takes to do its stuff until the boot loader or the operating system boots. And just to have a random figure, how long does the operating system take to get to the login screen? I know it depends a lot on the hardware and software configuration, so please mention this to (storage, distribution, Linux kernel version). Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [OT] Quality and us of DLNA feature of television sets
Dear list, some new TV sets seem to have an Ethernet port and support DLNA streaming. For example Philips Cineos 32PFL9613D [1]. I found some information VDR and UPnP/DLNA [2][3][4]. So my question is, how does the quality compare to other possibilities to connect the TV to a VDR client or server using HDMI or VGA? I did not find any information regarding this on the Web. Thanks, Paul [1] http://www.trustedreviews.com/tvs/review/2009/03/02/Philips-Cineos-32PFL9613D-32in-LCD-TV/p1 [2] http://www.linuxtv.org/pipermail/vdr/2008-April/thread.html#16684 [3] http://www.vdr-wiki.de/wiki/index.php/UPnP [4] http://www.vdrportal.de/board/thread.php?threadid=88192 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Patches for VGA timing not matching up with the TV (was: HD output - your current favourites)
Dear list, Am Samstag, den 15.08.2009, 14:41 +0300 schrieb Pasi Kärkkäinen: On Thu, Aug 13, 2009 at 10:35:11PM +0100, Gavin Hamill wrote: […] Most of the content is still SD, and I am a real pedant about smooth video / interlaced output for scrolling text / live sports. Any time that I've played with vdr-xine or xineliboutput over my years with VDR, it's always been a bit juddery due to VGA timing not matching up with the TV.. is that improved any in the world of HD / HDMI? Take a look at these patches: http://lowbyte.de/vga-sync-fields/ I believe they are useful also for HDMI/HD stuff. I haven't tried them yet myself. Original announcement: http://www.linuxtv.org/pipermail/vdr/2008-July/017347.html For Intel: http://www.linuxtv.org/pipermail/vdr/2009-January/019330.html the Web site with more information is: http://frc.easy-vdr.de/ Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Fast compact distro for vdr
Am Sonntag, den 30.08.2009, 17:02 +0100 schrieb scott: On Fri, 28 Aug 2009 22:51:15 +0200, Diego Pierotto vdr_ml...@tiscali.it wrote: Damien Bally ha scritto: gimli a écrit : […] I'd like a system booting in a few seconds. A few years back when I built my car pc, one of the things that got my boot time down significantly was using LinuxBios. If you are counting seconds it might be worth a look. LinuxBIOS was renamed coreboot [1] over a year ago. Bests, Paul [1] http://www.coreboot.org/ signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Fast compact distro for vdr
Dear Damien, Am Freitag, den 28.08.2009, 18:32 +0200 schrieb Damien Bally: […] Sorry if my mail is out of topic. I'm looking for a linux distro for my vdr box. I'd like a light system (without X11 since I use a dxr3 card) that boots fast. In my opinion you can set up a system with a small boot time with any distribution. So I would take a distribution you are familiar with and optimize it. For Debian you can take a look at [1][2]. As Scott wrote, coreboot would be nice to have too. And last but not least the boot partition should be located on a SSD drive, if I remember correctly. Good luck with your project. Maybe you can share your results, when you are done setting it up. I am looking forward to it. Thanks, Paul [1] http://lists.alioth.debian.org/pipermail/debian-eeepc-devel/2009-June/002308.html [2] http://www.debian-administration.org/article/Booting_Debian_in_14_seconds signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [OT] ARM based devices for VDR server and client
Am Dienstag, den 03.11.2009, 09:49 +0200 schrieb Michael Stepanov: IMHO nVidia Ion is much better option. Did you try both options or is this just your point of view from reading the specs? Especially for HDTV. As far as I know the Beagle Board is supposed to play 720p without any problems. See for example [1]. The NVIDIA ION is supposed to do 1080p with VDPAU, but I think I do not need it yet. + The Beagle Board should use less power. - More people run and test x86 hardware. • Both use proprietary drivers. Thanks, Paul [1] http://www.youtube.com/watch?v=BdnDpH3543Q signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [OT] ARM based devices for VDR server and client
Am Sonntag, den 01.11.2009, 21:43 +0100 schrieb Helge Lenz: As far as I know uses the reel NetClient an ARM core but I am not shure which one and if there is an additional graphics processor onboard. As long as nobody buys this box and opens it, we won't know. As far as I know all used components are known. To quote from for example Wikipedia [1] it uses a TI OMAP3530 Processor, and has a Imagination Technologies PowerVR SGX 2D/3D graphics processor integrated for HD material. This is the same technology used in the Intel Poulsbo design, so the DRM drivers(?) are unfortunately proprietary. Thanks, Paul [1] http://en.wikipedia.org/wiki/BeagleBoard [2] http://beagleboard.org/ [3] http://en.wikipedia.org/wiki/Texas_Instruments_TMS320 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [OT] ARM based devices for VDR server and client
Dear list, Am Samstag, den 31.10.2009, 09:28 +0100 schrieb Paul Menzel: I searched the Web but could not find a lot of reviews or tests about ARM based VDR systems. just a small update. I posted on the Beagle Board mailing list [3] and found also a post [4] where someone had run VDR successfully on a Beagle Board but has problems with the OSD. […] Thanks, Paul [1] http://en.wikipedia.org/wiki/BeagleBoard [2] http://beagleboard.org/ [3] http://en.wikipedia.org/wiki/Texas_Instruments_TMS320 [4] http://groups.google.com/group/beagleboard/browse_thread/thread/369302c3018b9634 [5] http://groups.google.com/group/beagleboard/browse_thread/thread/b7bec30fd5783fd8 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Shutting a system down. (was: vdr shutdownskript - wrong time)
Am Donnerstag, den 24.12.2009, 20:00 -0800 schrieb VDR User: On Wed, Dec 23, 2009 at 5:55 AM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: At some point the shutdown mechanism apparently became rocket science and I decided to no longer touch it (especially since I don't even use it myself). ;) Personally I don't see any real reason to ever shut down/wakeup feature. Maybe that's useful for guys running VDR on laptops or old pc's that consume a lot of power(?). I only use VDR in my living room as my main tv/media source, and on a test box for messing around with but that's it. I don't actually watch tv on a computer monitor. Sorry, I do not get your reasoning. Do you mean if a system uses less than 5 – or a different number – watts it does not need to be shut down? signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Shutting a system down.
Am Freitag, den 25.12.2009, 13:38 -0800 schrieb VDR User: […] However, in my case since VDR is my main tv/media source, it would be annoying to have to boot the computer every time someone wanted to watch/listen to something, therefore the box stays on 24/7. Thus, never having use for shutting down. Well, I guess energy prices are still too low. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Shutting a system down.
Am Samstag, den 26.12.2009, 07:53 +0200 schrieb Lauri Tischler: Paul Menzel wrote: Am Freitag, den 25.12.2009, 13:38 -0800 schrieb VDR User: […] However, in my case since VDR is my main tv/media source, it would be annoying to have to boot the computer every time someone wanted to watch/listen to something, therefore the box stays on 24/7. Thus, never having use for shutting down. Well, I guess energy prices are still too low. Really stupid comment, maybe you also believe that food is too cheap if people can afford to eat. Sorry, I will not insult you, but I do not understand your analogy. Of course I do not believe that. I did not write, energy prices are too low because people can afford to run electrical systems. I will not write anything further regarding this topic because that does not belong to this list. If you want to we can discuss this off-list. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] FRC + HDMI with Radeon 9200 SE
Am Sonntag, den 20.12.2009, 20:12 +0200 schrieb kompu: I have tried to get FRC + HDMI working with my Radeon 9200 SE Without success... :) I have installed all those patches like instructed on http://vga2scart.gw90.de/install/ Just a note for future references and search engines. Although it has the same content, the correct URL is [1]. […] Thanks, Paul [1] http://frc.easy-vdr.de/ signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] FRC + HDMI with Radeon 9200 SE
Dear kompu, let us start over from the beginning. Am Sonntag, den 20.12.2009, 20:12 +0200 schrieb kompu: I have tried to get FRC + HDMI working with my Radeon 9200 SE Is the Radeon 9200 SE connected to your monitor with a HDMI cable? Without success... :) I have installed all those patches like instructed on http://frc.easy-vdr.de/install/ Using Debian Lenny. That means xserver-xorg-video-ati_6.9.0-1+lenny4_i386.deb. From your Xorg.0.log from [1] you are using a SHARP HDMI monitor. Is (II) RADEON(0): Monitor name: SHARP HDMI Can you tell us the exact model please? The most important question I forgot to ask previously is, is the unpatched driver working? As far as I know FRC just gets activated when your are playing a video file. Beforehand you have to configure everything using modelines(?). […] Thanks, Paul [1] http://www.linuxtv.org/pipermail/vdr/2009-December/021909.html signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [OT] mini-PCIE with Broadcom Crystal HD Hardware Decoder (BCM970012) for HD playback with free drivers
Dear list, I just share something I read on the XBMC [1] Web site. The Broadcom Crystal HD Hardware Decoder (BCM970012) seems to be an alternative for HD playback with free drivers [2]. You can get it at as an mini-PCIE card at eBay for 22 $ [3]. If this is all true in my opinion these are fantastic news. Thanks, Paul [1] http://www.xbmc.org/ [2] http://www.xbmc.org/davilla/2009/12/29/broadcom-crystal-hd-its-magic/ [3] http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItemitem=320436937576#ht_2174wt_1167 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] VDR available as package in O penEmbedded and in Ångström
Dear VDR users, VDR 1.7.10 is now also available as a package in OpenEmbedded (OE), a build framework for embedded Linux [1][2]. I thank Henning Heinold who did most of the work to get VDR included and the OE developers to answer my questions on the openembedded-devel mailing list [3]. Around a week ago, Koen Kooi added VDR also to Ångström [4][5][6], a distribution using OE heavily. With `opkg install vdr` it is now as easy as on other distributions to install VDR and get it running on embedded devices which because of their energy efficiency and form factors, e. g. BeagleBoard [7], are predestined for use as a VDR server. The next steps are going to be to improve the packaging in OE and to send some patches to upstream VDR to adapt it for cross compilation [8]. As always especially the developers do not have much time, so help with testing and writing patches is very welcomed. You should ask on the list or on IRC before starting any work though. Since some patches are still pending hopefully it can be avoided that work is done twice. It would be great to get the plugins also included into OE soon. I am thinking about to create a project on projects.vdr-developer.org [9] so I could publish a branch for OE to push from. (I hope this will be more successful than my attempt with the FRC project. It will be revived. ;-)) A short page is available in the German VDR Wiki already [10]. It would be great if someone could add that to the English VDR Wiki [11] too. In my opinion this should be kept short with links to already available information on the Web. Thanks again to everyone and happy testing, Paul [1] http://www.openembedded.org/ [2] http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/vdr/ [3] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel [4] http://www.angstrom-distribution.org/ [5] http://www.angstrom-distribution.org/repo/?pkgname=vdr [6] http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=dfa0d36cac88fd6f3a451cc7bc9433629f4a2df0 [7] http://beagleboard.org/ [8] http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-January/016213.html [9] http://projects.vdr-developer.org/ [10] http://vdr-wiki.de/wiki/index.php/Ångström [11] http://www.linuxtv.org/vdrwiki/index.php/Main_Page [12] http://projects.vdr-developer.org/projects/show/frc ___ Openembedded-devel mailing list openembedded-de...@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [Makefile] `-fPIC` not added to externally defined `C[XX]FLAGS` of PLUGINS if `Make.config` not available
Dear VDR users,
in `Make.config.template` [1] which if renamed to `Make.config` gets
included in all Makefiles there is
ifdef PLUGIN
CFLAGS += -fPIC
CXXFLAGS += -fPIC
DEFINES += -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE
endif
which just gets included if `PLUGIN` is defined, which is normally done
in the Makefile of a plugin as for example in `Makefile` [3] belonging
to the plugin hello [2].
Additionally in each Makefile of a plugin `C[XX]FLAGS` is set to
CXXFLAGS ?= -fPIC -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
if it has not been defined yet for example in the environment.
As far as I understand plugins have to be compiled with the `-fPIC`
flag, so that the VDR can be linked against them [4]. Otherwise it would
give an error message as the following example.
ld: hello.o: relocation R_ARM_MOVW_ABS_NC against `a local symbol' can
not be used when making a shared object; recompile with -fPIC
hello.o: could not read symbols: Bad value
The problem now is, that if `Make.config` does not contain the snippet
from the top and `C[XX]FLAGS` are defined before without `-fPIC`
building the plugins fails. This scenario is typical in cross
compilation [5].
I do not know if the `DEFINES` from above are required, so I just
concentrate on the `-fPIC` issue because this flag is needed for a
successful build.
I thought of two solutions. Maybe you see something better.
1. Each `Makefile` of a plugin gets rewritten to always append `-fPIC`
to `C[XX]FLAGS`. Here is an example for the plugin hello.
diff --git a/PLUGINS/src/hello/Makefile b/PLUGINS/src/hello/Makefile
index ea5b806..a02d6c2 100644
--- a/PLUGINS/src/hello/Makefile
+++ b/PLUGINS/src/hello/Makefile
@@ -18,7 +18,8 @@ VERSION = $(shell grep 'static const char \*VERSION
*=' $(PLUGIN).c | awk '{ pri
### The C++ compiler and options:
CXX ?= g++
-CXXFLAGS ?= -fPIC -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
+CXXFLAGS ?= -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
+CXXFLAGS += -fPIC
### The directory environment:
2. If `DEFINES` from the beginning is also needed, that we should factor
the snippet out into a file `Make.plugins` and every plugin has to
include it in its Makefile.
What do you think? What alternative is preferable? When this is decided
I would create a patch to change that in VDR.
Thanks,
Paul
[1] http://git.gekrumbel.de/vdr.git?p=vdr.git;a=blob;f=Make.config.template
[2] http://git.gekrumbel.de/vdr.git?p=vdr.git;a=tree;f=PLUGINS/src/hello
[3]
http://git.gekrumbel.de/vdr.git?p=vdr.git;a=blob;f=PLUGINS/src/hello/Makefile#l31
[4] http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1chap=3
[5]
http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-January/016213.html
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [Makefile] `-fPIC` not added to externally defined `C[XX]FLAGS` of PLUGINS if `Make.config` not available
Am Dienstag, den 26.01.2010, 10:34 +0100 schrieb Frank Schmirler: On Mon, 25 Jan 2010 23:43:11 +0100, Paul Menzel wrote 1. Each `Makefile` of a plugin gets rewritten to always append `- fPIC` to `C[XX]FLAGS`. Here is an example for the plugin hello. 2. If `DEFINES` from the beginning is also needed, that we should factor the snippet out into a file `Make.plugins` and every plugin has to include it in its Makefile. What do you think? What alternative is preferable? When this is decided I would create a patch to change that in VDR. This has already been discussed during the last months, I just didn't take the time yet to propose a fix: http://www.linuxtv.org/pipermail/vdr/2009-July/020977.html http://www.linuxtv.org/pipermail/vdr/2009-December/021807.html Thank you for the links. I could not figure out what alternativ is preferred though. If you tell me, I could prepare a patch. Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH v2] Gather necessary options for build in Make.global and include it.
Without this patch, if some options in `Makefile` were set outside `Makefile`
and no `Make.config` existed with the necessary options, builds could fail.
[1][2][3]
Therefore include strictly necessary options in `Make.global` and include this
in all the Makefiles before `Make.config`.
This patch does not delete the those options which were factored out into
`Make.global` to make it easier for people to understand the Makefile and what
options are needed.
[1] http://www.linuxtv.org/pipermail/vdr/2009-July/020977.html
[2] http://www.linuxtv.org/pipermail/vdr/2009-December/021807.html
[3] http://www.linuxtv.org/pipermail/vdr/2010-January/022235.html
v2: Use `include` instead of `-include` to get a warning/error if it is not
present. [4]
[4] http://www.gnu.org/software/make/manual/make.html#Include
Signed-off-by: Paul Menzel paulepan...@users.sourceforge.net
---
Make.config.template |6 --
Make.global | 14 ++
Makefile |1 +
PLUGINS/src/dvbsddevice/Makefile |4
PLUGINS/src/hello/Makefile |4
PLUGINS/src/osddemo/Makefile |4
PLUGINS/src/pictures/Makefile|4
PLUGINS/src/servicedemo/Makefile |4
PLUGINS/src/skincurses/Makefile |4
PLUGINS/src/status/Makefile |4
PLUGINS/src/svdrpdemo/Makefile |4
11 files changed, 47 insertions(+), 6 deletions(-)
create mode 100644 Make.global
diff --git a/Make.config.template b/Make.config.template
index 758fc14..3296992 100644
--- a/Make.config.template
+++ b/Make.config.template
@@ -16,12 +16,6 @@ CFLAGS = -g -O2 -Wall
CXX = g++
CXXFLAGS = -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
-ifdef PLUGIN
-CFLAGS += -fPIC
-CXXFLAGS += -fPIC
-DEFINES += -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-endif
-
### The directory environment:
#DVBDIR = /usr/src/v4l-dvb/linux
diff --git a/Make.global b/Make.global
new file mode 100644
index 000..5ef70f0
--- /dev/null
+++ b/Make.global
@@ -0,0 +1,14 @@
+#
+# Strictly necessary Makefile options for the Video Disk Recorder
+#
+# See the main source file 'vdr.c' for copyright information and
+# how to reach the author.
+
+# Plugins need to be compiled with position independent code, otherwise linking
+# VDR against it will fail.
+ifdef PLUGIN
+CFLAGS += -fPIC
+CXXFLAGS += -fPIC
+endif
+
+DEFINES += -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
diff --git a/Makefile b/Makefile
index e13ea5e..faa36e7 100644
--- a/Makefile
+++ b/Makefile
@@ -32,6 +32,7 @@ CONFDIR = $(VIDEODIR)
DOXYGEN = /usr/bin/doxygen
DOXYFILE = Doxyfile
+include Make.global
-include Make.config
SILIB= $(LSIDIR)/libsi.a
diff --git a/PLUGINS/src/dvbsddevice/Makefile b/PLUGINS/src/dvbsddevice/Makefile
index 8ef273c..a3854a5 100644
--- a/PLUGINS/src/dvbsddevice/Makefile
+++ b/PLUGINS/src/dvbsddevice/Makefile
@@ -20,6 +20,10 @@ VERSION = $(shell grep 'static const char \*VERSION *='
$(PLUGIN).c | awk '{ pri
CXX ?= g++
CXXFLAGS ?= -fPIC -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
+### Make sure that necessary options are included:
+
+include $(VDRDIR)/Make.global
+
### The directory environment:
VDRDIR = ../../..
diff --git a/PLUGINS/src/hello/Makefile b/PLUGINS/src/hello/Makefile
index ea5b806..1132cc9 100644
--- a/PLUGINS/src/hello/Makefile
+++ b/PLUGINS/src/hello/Makefile
@@ -20,6 +20,10 @@ VERSION = $(shell grep 'static const char \*VERSION *='
$(PLUGIN).c | awk '{ pri
CXX ?= g++
CXXFLAGS ?= -fPIC -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
+### Make sure that necessary options are included:
+
+include $(VDRDIR)/Make.global
+
### The directory environment:
VDRDIR = ../../..
diff --git a/PLUGINS/src/osddemo/Makefile b/PLUGINS/src/osddemo/Makefile
index 1b1c622..54dc1e0 100644
--- a/PLUGINS/src/osddemo/Makefile
+++ b/PLUGINS/src/osddemo/Makefile
@@ -18,6 +18,10 @@ VERSION = $(shell grep 'static const char \*VERSION *='
$(PLUGIN).c | awk '{ pri
CXX ?= g++
CXXFLAGS ?= -fPIC -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
+### Make sure that necessary options are included:
+
+include $(VDRDIR)/Make.global
+
### The directory environment:
VDRDIR = ../../..
diff --git a/PLUGINS/src/pictures/Makefile b/PLUGINS/src/pictures/Makefile
index 46a262f..6f95238 100644
--- a/PLUGINS/src/pictures/Makefile
+++ b/PLUGINS/src/pictures/Makefile
@@ -20,6 +20,10 @@ VERSION = $(shell grep 'static const char \*VERSION *='
$(PLUGIN).c | awk '{ pri
CXX ?= g++
CXXFLAGS ?= -fPIC -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
+### Make sure that necessary options are included:
+
+include $(VDRDIR)/Make.global
+
### The directory environment:
VDRDIR = ../../..
diff --git a/PLUGINS/src/servicedemo/Makefile b/PLUGINS/src/servicedemo/Makefile
index ea7e66a..e36757a 100644
--- a/PLUGINS/src/servicedemo/Makefile
+++ b/PLUGINS/src/servicedemo/Makefile
@@ -20,6 +20,10
Re: [vdr] [PATCH v2] Gather necessary options for build in Make.global and include it.
Dear Frank, Am Freitag, den 29.01.2010, 10:04 +0100 schrieb Frank Schmirler: […] 1) from VDR's Makefile, remove the line DEFINES += -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE It is already included from Make.global 2) in all plugin Makefiles, remove -fPIC from the line CXXFLAGS ?= -fPIC -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses It will be added by Make.global anyway My reasoning was that someone reading the Makefile would have it easier to see what options are needed. I will change it now. I will also remove the line `DEFINES += -D_FILE …` in there too because it should be added by `Make.global` too. 3) in Make.config.template, remove only the line DEFINES += -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE The lines with += -fPIC are still necessary, as Make.config resets CFLAGS/CXXFLAGS. Correct. 4) Script newplugin needs to be modified, too. I did not know about `newplugin`. Thanks for the review. I will send a new version of the patch, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH v3] Gather necessary options for build in Make.global and include it.
Without this patch, if some options in `Makefile` were set outside `Makefile`
and no `Make.config` existed with the necessary options, builds could fail.
[1][2][3]
Therefore include strictly necessary options in `Make.global` and include this
in all the Makefiles before `Make.config`.
[1] http://www.linuxtv.org/pipermail/vdr/2009-July/020977.html
[2] http://www.linuxtv.org/pipermail/vdr/2009-December/021807.html
[3] http://www.linuxtv.org/pipermail/vdr/2010-January/022235.html
v2: Use `include` instead of `-include` to get a warning/error if it is not
present. [4]
v3: Change according to Frank’s comments [5].
• Delete options set in `Make.global` from other Makefiles.
• Leave adding `-fPIC` to `C[XX]FLAGS` in `Make.config.template` as the flags
get reset including `Make.config`.
• Modify `newplugin`.
[4] http://www.gnu.org/software/make/manual/make.html#Include
[5] http://www.linuxtv.org/pipermail/vdr/2010-January/022243.html
Signed-off-by: Paul Menzel paulepan...@users.sourceforge.net
---
Make.config.template |1 -
Make.global | 14 ++
Makefile |3 +--
PLUGINS/src/dvbsddevice/Makefile |8 +---
PLUGINS/src/hello/Makefile |6 +-
PLUGINS/src/osddemo/Makefile |6 +-
PLUGINS/src/pictures/Makefile|6 +-
PLUGINS/src/servicedemo/Makefile |6 +-
PLUGINS/src/skincurses/Makefile |6 +-
PLUGINS/src/status/Makefile |6 +-
PLUGINS/src/svdrpdemo/Makefile |6 +-
newplugin|8 +---
12 files changed, 60 insertions(+), 16 deletions(-)
create mode 100644 Make.global
diff --git a/Make.config.template b/Make.config.template
index 758fc14..6fffa0e 100644
--- a/Make.config.template
+++ b/Make.config.template
@@ -19,7 +19,6 @@ CXXFLAGS = -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
ifdef PLUGIN
CFLAGS += -fPIC
CXXFLAGS += -fPIC
-DEFINES += -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
endif
### The directory environment:
diff --git a/Make.global b/Make.global
new file mode 100644
index 000..5ef70f0
--- /dev/null
+++ b/Make.global
@@ -0,0 +1,14 @@
+#
+# Strictly necessary Makefile options for the Video Disk Recorder
+#
+# See the main source file 'vdr.c' for copyright information and
+# how to reach the author.
+
+# Plugins need to be compiled with position independent code, otherwise linking
+# VDR against it will fail.
+ifdef PLUGIN
+CFLAGS += -fPIC
+CXXFLAGS += -fPIC
+endif
+
+DEFINES += -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
diff --git a/Makefile b/Makefile
index e13ea5e..a2659be 100644
--- a/Makefile
+++ b/Makefile
@@ -32,6 +32,7 @@ CONFDIR = $(VIDEODIR)
DOXYGEN = /usr/bin/doxygen
DOXYFILE = Doxyfile
+include Make.global
-include Make.config
SILIB= $(LSIDIR)/libsi.a
@@ -60,8 +61,6 @@ DEFINES += -DLIRC_DEVICE=\$(LIRC_DEVICE)\
-DRCU_DEVICE=\$(RCU_DEVICE)\
DEFINES += -D_GNU_SOURCE
-DEFINES += -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-
DEFINES += -DVIDEODIR=\$(VIDEODIR)\
DEFINES += -DCONFDIR=\$(CONFDIR)\
DEFINES += -DPLUGINDIR=\$(PLUGINLIBDIR)\
diff --git a/PLUGINS/src/dvbsddevice/Makefile b/PLUGINS/src/dvbsddevice/Makefile
index 8ef273c..345543e 100644
--- a/PLUGINS/src/dvbsddevice/Makefile
+++ b/PLUGINS/src/dvbsddevice/Makefile
@@ -18,7 +18,11 @@ VERSION = $(shell grep 'static const char \*VERSION *='
$(PLUGIN).c | awk '{ pri
### The C++ compiler and options:
CXX ?= g++
-CXXFLAGS ?= -fPIC -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
+CXXFLAGS ?= -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
+
+### Make sure that necessary options are included:
+
+include $(VDRDIR)/Make.global
### The directory environment:
@@ -45,8 +49,6 @@ INCLUDES += -I$(VDRDIR)/include
DEFINES += -D_GNU_SOURCE -DPLUGIN_NAME_I18N='$(PLUGIN)'
-DEFINES += -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-
### The object files (add further files here):
OBJS = $(PLUGIN).o dvbsdffdevice.o dvbsdffosd.o
diff --git a/PLUGINS/src/hello/Makefile b/PLUGINS/src/hello/Makefile
index ea5b806..1ec3170 100644
--- a/PLUGINS/src/hello/Makefile
+++ b/PLUGINS/src/hello/Makefile
@@ -18,7 +18,11 @@ VERSION = $(shell grep 'static const char \*VERSION *='
$(PLUGIN).c | awk '{ pri
### The C++ compiler and options:
CXX ?= g++
-CXXFLAGS ?= -fPIC -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
+CXXFLAGS ?= -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
+
+### Make sure that necessary options are included:
+
+include $(VDRDIR)/Make.global
### The directory environment:
diff --git a/PLUGINS/src/osddemo/Makefile b/PLUGINS/src/osddemo/Makefile
index 1b1c622..2a7f836 100644
--- a/PLUGINS/src/osddemo/Makefile
+++ b/PLUGINS/src/osddemo/Makefile
@@ -16,7 +16,11 @@ VERSION = $(shell grep 'static const char \*VERSION *='
$(PLUGIN).c | awk '{ pri
### The C++ compiler and options:
CXX ?= g
Re: [vdr] [PATCH] Gather necessary options for build in Make.global and include it.
Am Samstag, den 30.01.2010, 11:57 +0100 schrieb Udo Richter: Am 28.01.2010 22:52, schrieb Ville Skyttä: On Thursday 28 January 2010, Paul Menzel wrote: Therefore include strictly necessary options in `Make.global` and include this in all the Makefiles before `Make.config`. If these options are strictly necessary, shouldn't the leading - be dropped from all -include $(VDRDIR)/Make.global lines? In this case, yes, but many cross-version plugins will need to be more flexible here, either by doing a messy VDR version check, or by simply just using -inlcude anyway. Sorry, I do not know if I understood you correctly. Do you mean that some other plugins (which are not shipped with VDR, i. e. the patch does not need to be changed in that regard) need to use `-include $(VDRDIR)/Make.global` instead of `include $(VDRDIR)/Make.global`? Do the authors of those plugins generally know about that kind of stuff or does this have to be documented somewhere? Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH v3] Gather necessary options for build in Make.global and include it.
Am Samstag, den 06.02.2010, 12:29 +0100 schrieb Klaus Schmidinger: On 29.01.2010 15:19, Paul Menzel wrote: Without this patch, if some options in `Makefile` were set outside `Makefile` and no `Make.config` existed with the necessary options, builds could fail. [1][2][3] Therefore include strictly necessary options in `Make.global` and include this in all the Makefiles before `Make.config`. [1] http://www.linuxtv.org/pipermail/vdr/2009-July/020977.html [2] http://www.linuxtv.org/pipermail/vdr/2009-December/021807.html [3] http://www.linuxtv.org/pipermail/vdr/2010-January/022235.html v2: Use `include` instead of `-include` to get a warning/error if it is not present. [4] v3: Change according to Frank’s comments [5]. • Delete options set in `Make.global` from other Makefiles. • Leave adding `-fPIC` to `C[XX]FLAGS` in `Make.config.template` as the flags get reset including `Make.config`. • Modify `newplugin`. [4] http://www.gnu.org/software/make/manual/make.html#Include [5] http://www.linuxtv.org/pipermail/vdr/2010-January/022243.html Signed-off-by: Paul Menzel paulepan...@users.sourceforge.net ... Is it safe to assume that this is the final version everybody has agreed upon? I think so, since nobody commented on this anymore, it can be applied. Frank told me I should submit it to you. Great that you were faster. I do not know when you will release the 1.7.13. If it is still some days away then maybe we can set a limit of seven days to give everyone a chance again to comment on this patch and you can apply it afterward. Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH v3] Gather necessary options for build in Make.global and include it.
Am Samstag, den 06.02.2010, 13:00 +0100 schrieb Klaus Schmidinger: On 06.02.2010 12:43, Paul Menzel wrote: […] I do not know when you will release the 1.7.13. If it is still some days away then maybe we can set a limit of seven days to give everyone a chance again to comment on this patch and you can apply it afterward. I'm either applying it today, or ignore it altogether ;-) I believe there has been enough time for complaints. Then please apply it. Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH v4] Gather necessary options for build in Make.global and include it.
Without this patch, if some options in `Makefile` were set outside `Makefile`
and no `Make.config` existed with the necessary options, builds could fail.
[1][2][3]
Therefore include strictly necessary options in `Make.global` and include this
in all the Makefiles before `Make.config`.
[1] http://www.linuxtv.org/pipermail/vdr/2009-July/020977.html
[2] http://www.linuxtv.org/pipermail/vdr/2009-December/021807.html
[3] http://www.linuxtv.org/pipermail/vdr/2010-January/022235.html
v2: Use `include` instead of `-include` to get a warning/error if it is not
present. [4]
v3: Change according to Frank’s comments [5].
• Delete options set in `Make.global` from other Makefiles.
• Leave adding `-fPIC` to `C[XX]FLAGS` in `Make.config.template` as the flags
get reset including `Make.config`.
• Modify `newplugin`.
v4: Actually provide a working patch. Thanks to Klaus [6].
• Only use `$(VDRDIR)` after it has been defined.
• Escape `$` in Perl script `newplugin`.
[4] http://www.gnu.org/software/make/manual/make.html#Include
[5] http://www.linuxtv.org/pipermail/vdr/2010-January/022243.html
[6] http://www.linuxtv.org/pipermail/vdr/2010-February/022325.html
Signed-off-by: Paul Menzel paulepan...@users.sourceforge.net
---
Make.config.template |1 -
Make.global | 14 ++
Makefile |3 +--
PLUGINS/src/dvbsddevice/Makefile |8 +---
PLUGINS/src/hello/Makefile |6 +-
PLUGINS/src/osddemo/Makefile |6 +-
PLUGINS/src/pictures/Makefile|6 +-
PLUGINS/src/servicedemo/Makefile |6 +-
PLUGINS/src/skincurses/Makefile |6 +-
PLUGINS/src/status/Makefile |6 +-
PLUGINS/src/svdrpdemo/Makefile |6 +-
newplugin|8 +---
12 files changed, 60 insertions(+), 16 deletions(-)
create mode 100644 Make.global
diff --git a/Make.config.template b/Make.config.template
index 758fc14..6fffa0e 100644
--- a/Make.config.template
+++ b/Make.config.template
@@ -19,7 +19,6 @@ CXXFLAGS = -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
ifdef PLUGIN
CFLAGS += -fPIC
CXXFLAGS += -fPIC
-DEFINES += -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
endif
### The directory environment:
diff --git a/Make.global b/Make.global
new file mode 100644
index 000..5ef70f0
--- /dev/null
+++ b/Make.global
@@ -0,0 +1,14 @@
+#
+# Strictly necessary Makefile options for the Video Disk Recorder
+#
+# See the main source file 'vdr.c' for copyright information and
+# how to reach the author.
+
+# Plugins need to be compiled with position independent code, otherwise linking
+# VDR against it will fail.
+ifdef PLUGIN
+CFLAGS += -fPIC
+CXXFLAGS += -fPIC
+endif
+
+DEFINES += -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
diff --git a/Makefile b/Makefile
index 01408cb..fea4ebe 100644
--- a/Makefile
+++ b/Makefile
@@ -32,6 +32,7 @@ CONFDIR = $(VIDEODIR)
DOXYGEN = /usr/bin/doxygen
DOXYFILE = Doxyfile
+include Make.global
-include Make.config
SILIB= $(LSIDIR)/libsi.a
@@ -60,8 +61,6 @@ DEFINES += -DLIRC_DEVICE=\$(LIRC_DEVICE)\
-DRCU_DEVICE=\$(RCU_DEVICE)\
DEFINES += -D_GNU_SOURCE
-DEFINES += -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-
DEFINES += -DVIDEODIR=\$(VIDEODIR)\
DEFINES += -DCONFDIR=\$(CONFDIR)\
DEFINES += -DPLUGINDIR=\$(PLUGINLIBDIR)\
diff --git a/PLUGINS/src/dvbsddevice/Makefile b/PLUGINS/src/dvbsddevice/Makefile
index 8ef273c..07e820f 100644
--- a/PLUGINS/src/dvbsddevice/Makefile
+++ b/PLUGINS/src/dvbsddevice/Makefile
@@ -18,7 +18,7 @@ VERSION = $(shell grep 'static const char \*VERSION *='
$(PLUGIN).c | awk '{ pri
### The C++ compiler and options:
CXX ?= g++
-CXXFLAGS ?= -fPIC -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
+CXXFLAGS ?= -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
### The directory environment:
@@ -26,6 +26,10 @@ VDRDIR = ../../..
LIBDIR = ../../lib
TMPDIR = /tmp
+### Make sure that necessary options are included:
+
+include $(VDRDIR)/Make.global
+
### Allow user defined options to overwrite defaults:
-include $(VDRDIR)/Make.config
@@ -45,8 +49,6 @@ INCLUDES += -I$(VDRDIR)/include
DEFINES += -D_GNU_SOURCE -DPLUGIN_NAME_I18N='$(PLUGIN)'
-DEFINES += -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-
### The object files (add further files here):
OBJS = $(PLUGIN).o dvbsdffdevice.o dvbsdffosd.o
diff --git a/PLUGINS/src/hello/Makefile b/PLUGINS/src/hello/Makefile
index ea5b806..2f755c0 100644
--- a/PLUGINS/src/hello/Makefile
+++ b/PLUGINS/src/hello/Makefile
@@ -18,7 +18,7 @@ VERSION = $(shell grep 'static const char \*VERSION *='
$(PLUGIN).c | awk '{ pri
### The C++ compiler and options:
CXX ?= g++
-CXXFLAGS ?= -fPIC -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
+CXXFLAGS ?= -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
### The directory environment:
@@ -26,6 +26,10 @@ VDRDIR
Re: [vdr] [PATCH v3] Gather necessary options for build in Make.global and include it.
Am Samstag, den 06.02.2010, 13:25 +0100 schrieb Klaus Schmidinger: On 06.02.2010 13:23, Paul Menzel wrote: Am Samstag, den 06.02.2010, 13:00 +0100 schrieb Klaus Schmidinger: On 06.02.2010 12:43, Paul Menzel wrote: […] I do not know when you will release the 1.7.13. If it is still some days away then maybe we can set a limit of seven days to give everyone a chance again to comment on this patch and you can apply it afterward. I'm either applying it today, or ignore it altogether ;-) I believe there has been enough time for complaints. Then please apply it. I was just about to do that, when I came across a problem while testing it. See my posting just a few minutes ago. Sorry about that. I just resend a working patch which you can apply. Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH v3] Gather necessary options for build in Make.global and include it.
Am Samstag, den 06.02.2010, 13:17 +0100 schrieb Klaus Schmidinger:
On 29.01.2010 15:19, Paul Menzel wrote:
[…]
--- a/PLUGINS/src/dvbsddevice/Makefile
+++ b/PLUGINS/src/dvbsddevice/Makefile
@@ -18,7 +18,11 @@ VERSION = $(shell grep 'static const char \*VERSION *='
$(PLUGIN).c | awk '{ pri
### The C++ compiler and options:
CXX ?= g++
-CXXFLAGS ?= -fPIC -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
+CXXFLAGS ?= -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
+
+### Make sure that necessary options are included:
+
+include $(VDRDIR)/Make.global
...
This fails when doing
make clean-plugins
make[1]: Entering directory `/home/kls/vdr/VDR/PLUGINS/src/dvbsddevice'
Makefile:25: /Make.global: No such file or directory
make[1]: *** No rule to make target `/Make.global'. Stop.
make[1]: Leaving directory `/home/kls/vdr/VDR/PLUGINS/src/dvbsddevice'
Apparently $(VDRDIR) is not yet defined at that point.
Fixed.
...
diff --git a/newplugin b/newplugin
index 52ef72e..6c9be35 100755
--- a/newplugin
+++ b/newplugin
@@ -77,7 +77,11 @@ VERSION = \$(shell grep 'static const char \\*VERSION
*=' \$(PLUGIN).c | awk '{
### The C++ compiler and options:
CXX ?= g++
-CXXFLAGS ?= -fPIC -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
+CXXFLAGS ?= -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses
+
+### Make sure that necessary options are included:
+
+include $(VDRDIR)/Make.global
I assume this last line should read
+include \$(VDRDIR)/Make.global
Fixed.
Please provide a revised (and tested ;-) patch.
I sent the revised and tested (`make`, `make plugins`, `make
clean-plugins`) patch to the list.
[vdr] [PATCH v4] Gather necessary options for build in Make.global and include
it.
Sorry for the inconvenience. Thanks,
Paul
[1] http://www.linuxtv.org/pipermail/vdr/2010-February/022333.html
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Linux in the living room
Am Dienstag, den 23.02.2010, 07:19 +0100 schrieb Stefan Hußfeldt: Oliver Endriss schrieb: I just checked my archives and found that VDR replaced my analogue SAT receiver around July 2002. From the beginning it was the most useful linux application I ever tried. And it is still the only one which made it into the living room. That's not true for me at all. My LCD TV is running Linux and has sshd, ftpd, nfs, etc. ;) Sounds great! What model is that? Of course VDR is running for a much longer time in the living room. Does your LCD TV act directly as a VDR client too? Thanks, Paul signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Adapt Make.config.template to VDR 1.7.13
Am Sonntag, den 28.03.2010, 14:36 +0200 schrieb Klaus Schmidinger: On 27.03.2010 18:11, Joachim Wilke wrote: I was just wondering, if ifdef PLUGIN CFLAGS += -fPIC CXXFLAGS += -fPIC endif can now be removed from Make.config.template, as the new Make.global cares for -fPIC since VDR 1.7.13. I guess you're right - changed for version 1.7.15. Frank pointed the following out back then [1]. Am Freitag, den 29.01.2010, 10:04 +0100 schrieb Frank Schmirler: 3) in Make.config.template, remove only the line DEFINES += -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE The lines with += -fPIC are still necessary, as Make.config resets CFLAGS/CXXFLAGS. Thanks, Paul [1] http://linuxtv.org/pipermail/vdr/2010-January/022243.html signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] Do not override externally defined `INCLUDES`.
In some environments, i. e. when cross building, include files are not located in the standard path like `/usr/includes/freetype2`. Make it possible to provide the correct path without needing to patch `Makefile`. Signed-off-by: Paul Menzel paulepan...@users.sourceforge.net --- Makefile |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/Makefile b/Makefile index 31f05b0..c7af79c 100644 --- a/Makefile +++ b/Makefile @@ -21,7 +21,7 @@ MANDIR = $(PREFIX)/share/man BINDIR = $(PREFIX)/bin LOCDIR = ./locale LIBS = -ljpeg -lpthread -ldl -lcap -lrt -lfreetype -lfontconfig -INCLUDES = -I/usr/include/freetype2 +INCLUDES ?= -I/usr/include/freetype2 PLUGINDIR= ./PLUGINS PLUGINLIBDIR= $(PLUGINDIR)/lib -- 1.7.0.3 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR and uClibc
Dear VDR folks, I am trying to compile VDR with uClibc [1] using OpenEmbedded [2] and get the following error. thread.o: In function `cRwLock::Lock(bool, int)': /oe/angstrom-dev/work/armv7a-angstrom-linux-uclibceabi/vdr-1.7.15-r0/vdr-1.7.15/thread.c:164: undefined reference to `pthread_rwlock_timedwrlock' /oe/angstrom-dev/work/armv7a-angstrom-linux-uclibceabi/vdr-1.7.15-r0/vdr-1.7.15/thread.c:166: undefined reference to `pthread_rwlock_timedrdlock' collect2: ld returned 1 exit status The problem seems to exist since 2004 [3][4] and those function do not seem to be implemented in uClibc [5]. Judging from the comment in Gentoo bug #201718 I hoped that this has been resolved somehow. But I could not find any patches regarding this issue in the Gentoo archive. Did anyone solve this problem? Thanks, Paul [1] http://www.uclibc.org/ [2] http://wiki.openembedded.net/index.php/Main_Page [3] http://www.linuxtv.org/mailinglists/vdr/2004/07-2004/msg00089.html [4] http://www.linuxtv.org/mailinglists/vdr/2004/12-2004/msg01061.html [5] http://www.linuxtv.org/mailinglists/vdr/2004/12-2004/msg01077.html [6] http://bugs.gentoo.org/show_bug.cgi?id=201718#c1 [7] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/media-video/vdr/files/ signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Alternate-Channel-Patch
Dear Rainer, Am Freitag, den 30.07.2010, 21:48 +0200 schrieb Rainer Blickle: there was the alternate channel patch (http://www.vdr-wiki.de/wiki/index.php/Alternative_channel-patch). This patch provides alternative channels for timers, if the programmed channel was not available. Is there any patch providing this functionality for live-tv, too ? sorry, I do not know. If not, i would like to develop such a functionality. Does anybody knows why the patch doesn't get integrated ? Klaus decides what goes into VDR. I do not know if he knows about the patch or if it was sent to this list. Is such a functionality unwanted ? I recommend, that you send this patch to this list to get it reviewed. I guess Klaus will comment on it if he has time. What is the workflow to parcipiate in developing the vdr ? As far as I know, you create a patch and you send it to this list or to Klaus directly. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Advice on new motherboard, xineliboutput, vdpau, hdmi video audio, etc.
Dear VDR folks, Am Sonntag, den 15.08.2010, 21:59 +0300 schrieb Seppo Ingalsuo: My old HTPC motherboard died and I'm now looking for a new one to become a vdr-sxfe thin client. The old Silverstone case is for normal ATX board but I no more need PCI slots so a smaller one, even a Mini-ITX would do. Since the PC runs 24/7 I'm interested in low-power motherboards with Atom CPU. There should be VDPAU support for MPEG-2 SDTV decoding + high-quality de-interlacing. I'm watching also sometimes H.264 HDTV channels from satellite. There should be 1080p50 video + up 7.1ch multi-channel PCM audio over HDMI. I'd like to get rid of SPDIF connection to AV-receiver. My HTPC box has a home-brew LIRC receiver that connected to motherboard (Asus style) COM port heading. If COM ports are history I could change to Bluetooth remote control with a PS3 Blu-Ray remote. Therefore integrated BT support would be nice (otherwise some USB-BT dongle). WLAN is not mandatory since I stream from vdr server over gigabit ethernet. Are there still issues with some ethernet chipsets and Linux? I found some options such as Asus AT3IONT-I DELUXE, Asus AT3IONT-I, Asus AT5IONT-I. I would be happy to hear experiences about these motherboards with Linux and Xine. Are there problems with some motherboard features? Other recommendations are welcome too! is there really no recommendation for a board not using Nvidia graphics components? It would really be great to not depend on proprietary drivers. The VIA chipset VX855 was supposed to have support 1080p support build in. But those devices do not seem to be available in non Asian regions. AMD/ATI or Intel should also over some products fitting your need. And I heard the drivers matured quite a bit (besides Intel Poulsbo). Unfortunately I do not own such systems. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Advice on new motherboard, xineliboutput, vdpau, hdmi video audio, etc.
Am Dienstag, den 17.08.2010, 19:06 +0300 schrieb Seppo Ingalsuo: is there really no recommendation for a board not using Nvidia graphics components? It would really be great to not depend on proprietary drivers. The VIA chipset VX855 was supposed to have support 1080p support build in. But those devices do not seem to be available in non Asian regions. AMD/ATI or Intel should also over some products fitting your need. And I heard the drivers matured quite a bit (besides Intel Poulsbo). Unfortunately I do not own such systems. I installed vdr-sxfe to Poulsbo/GMA500 netbook but there is no Xv and VA API is not supported by xine-lib. There is mplayer support but I don't know if deintelacing is good. I haven't tried. An unscaled window works but fullscreen is horrible. The real Intel graphics stuff is likely better but I have no experience about that. What driver did you use? Anyway, »besides Intel Poulsbo« meant this chip is using closed drivers and is not supported by xf86-video-intel and so it does not fit into my wish list. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Advice on new motherboard, xineliboutput, vdpau, hdmi video audio, etc.
Am Dienstag, den 17.08.2010, 09:48 -0700 schrieb VDR User: On Tue, Aug 17, 2010 at 8:13 AM, Paul Menzel paulepan...@users.sourceforge.net wrote: is there really no recommendation for a board not using Nvidia graphics components? It would really be great to not depend on proprietary drivers. Just wondering why you even care about this... The Nvidia drivers work well for me and honestly that's all I care about. Good for you. As I wrote I do not want to start a flame war. But you asked. ;-) Everyone should decide for himself what he wants. I am on the side of Free Software and believe that it has more advantages than just »it works«. For example I believe supporting hardware requiring non-free software puts more work to the distributions and people working on those because they have to answer a lot of support request when people contact them and not Nvidia and they cannot fix problems because they do not have access to the code. Secondly I guess you will find a lot of requests for fixes the Nvidia driver which have not been accomplished. I think you will find a lot of information about this whole issue on the Internet and others can lay down the points better than I can. But as I said, it is just an axiom, so you cannot argue what is right or wrong. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VGA2SCART: circuit diagram with audio pins (was: VDR with 50Hz clock output)
Am Montag, den 23.08.2010, 09:28 +0200 schrieb martinez: Looking at the circuit diagram for the vga2scart cable. at http://vga2scart.gw90.de/cable/vga2scart/ What pins need to be mapped on the scart to include also sound (for a complete vga+ stereo out SCART cable) I found an updated diagram at [1]. I hope it is what you wanted. Thanks, Paul [1] http://crashme.cx/vdr-portal-picts/VGA_SCART_RGB_NEWER.png signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Xorg displaying 50 Hz but uses 60 Hz with Nvidia driver (was: Advice on new motherboard, xineliboutput, vdpau, hdmi video audio, etc.)
Am Donnerstag, den 26.08.2010, 16:16 +0200 schrieb Thomas Hilber: On Thu, Aug 26, 2010 at 03:06:51PM +0100, Tony Houghton wrote: Are you aware of the interaction between DynamicTwinView and XRandR? The no. But if Xorg.0.log tells me (in the bad case): (II) NVIDIA(0): Validating Mode 1920x1080: (II) NVIDIA(0): 1920 x 1080 @ 50 Hz (II) NVIDIA(0): For use as DFP backend. (II) NVIDIA(0): Mode Source: EDID (II) NVIDIA(0): Pixel Clock : 148.50 MHz (II) NVIDIA(0): HRes, HSyncStart : 1920, 2448 (II) NVIDIA(0): HSyncEnd, HTotal : 2492, 2640 (II) NVIDIA(0): VRes, VSyncStart : 1080, 1084 (II) NVIDIA(0): VSyncEnd, VTotal : 1089, 1125 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. [...] (II) NVIDIA(0): 1920x1080_50 : 1920 x 1080 @ 50.0 Hz (from: EDID) [...] (II) NVIDIA(0): Config Options in the README. (II) NVIDIA(0): Setting mode 1920x1080_50 and it uses a 60Hz modeline though this is clearly a Xserver bug for me. Do you know if it has been reported to Nvidia? I think the X.org people would not look at it, since you use the proprietary driver. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Xorg displaying 50 Hz but uses 60 Hz with Nvidia driver
Am Donnerstag, den 26.08.2010, 17:13 +0200 schrieb Thomas Hilber: On Thu, Aug 26, 2010 at 04:31:28PM +0200, Paul Menzel wrote: Do you know if it has been reported to Nvidia? I think the X.org people would not look at it, since you use the proprietary driver. I dont't know if especially this problem has been reported to nVidia. There are heaps of error reports of that kind reported to nVidia that all sound quite similar. I got the same answer from Aaron as Tony told us. Am Donnerstag, den 26.08.2010, 13:58 -0700 schrieb Aaron Plattner: It's not a bug, please see the README: ftp://download.nvidia.com/XFree86/Linux-x86/256.44/README/faq.html#WhyIsTheRefreshdcf0a Thomas, having just VertRefresh 50.0 in your `xorg.conf`, did you measure the 60 Hz directly at the output or were you just saying the tools reported 60 Hz? Thanks, Paul signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Arabic language EPG is inappropriately displayed
Dear Sami, [please just post normal plain/text messages [1–3].] Am Mittwoch, den 08.09.2010, 22:48 +0300 schrieb semsem85 sami: I am using Yavdr 0.2 with VDR 1.7.15 and the EPG or EIT for arabic language is inappropriately displayed in VDR. Using the arabic ISO-8859-6 in etc/default/vdr now the letters are shown correctly but they appear disjointed and are read from from left to right[whereas normally Arabic is read from right to left and the letters should be connected to each other to give a word and these words give a sentence ]. Is there any way to make the EPG readable in Arabic? Thanks alot. 1. Has it ever worked for you or is it the first time you are trying VDR? 2. Do other programs, e. g. VLC, work correctly? 3. Do you know other people having the same problems or did you find other reports on the WWW regarding the same problem? 4. Could you attach a screenshot so that the developers know what is going wrong exactly, please. 5. Could you attach `/etc/default/vdr`, please. 6. Could you please upload a test example somewhere so that developers can try to reproduce your issue and test fixes themselves. Unfortunately I do not know how to capture such an example though. 7. Are you using Arabic language for the menu of VDR too? Is it displayed correctly there? Thanks, Paul [1] http://www.asciiribbon.org/ [2] http://email.about.com/od/hotmailtips/qt/et_plain_text.htm [3] http://www2.cit.cornell.edu/computer/elist/text/hotmail.html signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Arabic language EPG is inappropriately displayed
Am Montag, den 13.09.2010, 20:05 +0300 schrieb semsem85 sami: @Mr.Tux, could you please Add me on MSN @ sami8519 at hotmail dot com What do you mean? Do you want to be subscribed to the list? If that is true, please take a look at [1] which is also present in the automatically added footer. Thanks, Paul [1] http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR Portal down?
Dear Achim, Am Freitag, den 19.11.2010, 09:46 +0100 schrieb Achim Tuffentsammer: www.vdr-portal.de seems to be down (yesterday evening and today)? Anyone else experience this? I can confirm this. It does not load for me either. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Include Path in Makefile (VDR =1.7.15)
Am Sonntag, den 12.12.2010, 16:29 +0100 schrieb Klaus Schmidinger: On 20.11.2010 11:39, Joachim Wilke wrote: 2010/11/19 Hans-Peter Jansen h...@urpla.net: The HISTORY file states: Include paths are now added instead of overwriting INCLUDES in the Makefile However, in the Makefile changes: -INCLUDES = -I/usr/include/freetype2 +INCLUDES ?= -I/usr/include/freetype2 Shouldn't that be += instead of ?=. No, the conditional variable assignment operator ?= allows one to replace this variable via command line/environment. Thats not what the HISTORY reads. Either the Makefile or the HISTORY should be changed. This change was posted here on the list by Paul Menzel on 2010-04-05. The link to the message in the archive is [1]. I guess the phrase Include paths are now added instead of overwriting... in the HISTORY was my fault. @Paul: would it be ok with you to make this INCLUDES += -I/usr/include/freetype2 instead of INCLUDES ?= -I/usr/include/freetype2 Reading my commit message, In some environments, i. e. when cross building, include files are not located in the standard path like `/usr/includes/freetype2`. Make it possible to provide the correct path without needing to patch `Makefile`. I would say that it would not work when cross compiling. I am no expert though. I would recommend to change the entry in HISTORY and I will ask on openembedded-devel what they suggest. Thanks, Paul [1] http://www.linuxtv.org/pipermail/vdr/2010-April/022831.html signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Include Path in Makefile (VDR =1.7.15)
Am Sonntag, den 12.12.2010, 16:46 +0100 schrieb Paul Menzel: Am Sonntag, den 12.12.2010, 16:29 +0100 schrieb Klaus Schmidinger: On 20.11.2010 11:39, Joachim Wilke wrote: 2010/11/19 Hans-Peter Jansen h...@urpla.net: The HISTORY file states: Include paths are now added instead of overwriting INCLUDES in the Makefile However, in the Makefile changes: -INCLUDES = -I/usr/include/freetype2 +INCLUDES ?= -I/usr/include/freetype2 Shouldn't that be += instead of ?=. No, the conditional variable assignment operator ?= allows one to replace this variable via command line/environment. Thats not what the HISTORY reads. Either the Makefile or the HISTORY should be changed. This change was posted here on the list by Paul Menzel on 2010-04-05. The link to the message in the archive is [1]. I guess the phrase Include paths are now added instead of overwriting... in the HISTORY was my fault. @Paul: would it be ok with you to make this INCLUDES += -I/usr/include/freetype2 instead of INCLUDES ?= -I/usr/include/freetype2 Reading my commit message, In some environments, i. e. when cross building, include files are not located in the standard path like `/usr/includes/freetype2`. Make it possible to provide the correct path without needing to patch `Makefile`. I would say that it would not work when cross compiling. I am no expert though. I would recommend to change the entry in HISTORY and I will ask on openembedded-devel what they suggest. My message already got an answer [2] which advises to use `pkg-config`. IMO you should use pkg-config or freetype-config instead, e.g.: INCLUDES ?= `pkg-config --cflags freetype2` or better, instead of using INCLUDES at all: FREETYPE_CFLAGS ?= `pkg-config --cflags freetype2` CFLAGS += $(FREETYPE_CFLAGS) This will work in most environments. Thanks, Paul [1] http://www.linuxtv.org/pipermail/vdr/2010-April/022831.html [2] http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-December/027801.html signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] Makefile: pass `LDFLAGS` to compiler
Dear Jörg, Am Samstag, den 25.09.2010, 13:15 +0200 schrieb Joerg Bornkessel: […] we have an open bug [1] to all versions of VDR on gentoo we changed any weeks befor our default profiles to use LDFLAGS on compile prozesses. snipp news-info about this from 2010-08-01 -Wl,--as-needed has been added to the default profile's LDFLAGS. This option optimizes the linking process, only linking binaries to libraries that are trully needed. This way, fewer libraries are loaded at runtime and fewer packages need to be rebuilt after library updates. /snap For more information on --as-needed, read [2]. Plz. let us check is it possible to add a fix generally to the Makefile to respect the LDFLAGS or should i fixed always localy on gentoo Disti. fixed should it be in this part of Makefile -# The main program: - -vdr: $(OBJS) $(SILIB) -$(CXX) $(CXXFLAGS) -rdynamic $(OBJS) $(LIBS) $(LIBDIRS) $(SILIB) -o vdr +# The main program: + +vdr: $(OBJS) $(SILIB) +$(CXX) $(CXXFLAGS) -rdynamic $(LDFLAGS) $(OBJS) $(LIBS) $(LIBDIRS) $(SILIB) -o vdr [1] http://bugs.gentoo.org/show_bug.cgi?id=333493 [2] http://www.gentoo.org/proj/en/qa/asneeded.xml Should `LDFLAGS` also be passed to the compiler when building the plugins? I made a patch from your message which does not include any changes to the plugins. Thanks, Paul 88 Date: Sun, 12 Dec 2010 18:19:42 +0100 Some distributions pass special flags to the linker [1][2]. Respect those by using `LDFLAGS`. [1] http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/vdr/vdr-1.7.10/linkerflags.patch [2] http://www.linuxtv.org/pipermail/vdr/2010-September/023623.html Signed-off-by: Paul Menzel paulepan...@users.sourceforge.net --- Makefile |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/Makefile b/Makefile index cca4d55..e12e2b2 100644 --- a/Makefile +++ b/Makefile @@ -95,7 +95,7 @@ $(DEPFILE): Makefile # The main program: vdr: $(OBJS) $(SILIB) - $(CXX) $(CXXFLAGS) -rdynamic $(OBJS) $(LIBS) $(LIBDIRS) $(SILIB) -o vdr + $(CXX) $(CXXFLAGS) -rdynamic $(LDFLAGS) $(OBJS) $(LIBS) $(LIBDIRS) $(SILIB) -o vdr # The libsi library: -- 1.7.2.3 signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Request: E parameter in channels.conf for epg scan
Am Sonntag, den 12.12.2010, 09:33 -0800 schrieb VDR User: On Sun, Dec 12, 2010 at 9:21 AM, Steffen Barszus steffenbpu...@googlemail.com wrote: Having epg in a DB (sqlite,mysql) might also be nice. You are going to find a lot of opposition to this. Thinking of sql, I don't recall ever hearing anyone suggest VDR using it would be a good idea but I have heard people will look into other options if it ever did go that route (as mythtv uses currrently). That is why Steffen wrote to make it a plugin. Thanks, Paul signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] tools.h: include `stdarg.h` to fix `error: 'va_list' has not been declared` with uClibc
From a94d15b582df5d1464cec8bc7dd68be46e1bf937 Mon Sep 17 00:00:00 2001
From: Paul Menzel paulepan...@users.sourceforge.net
Date: Sun, 12 Dec 2010 19:21:25 +0100
Subject: [PATCH] tools.h: include `stdarg.h`
For some reason using uClibc `tools.h` needs to have `stdarg.h` included
explicitly. Otherwise it fails with the following error. Using Libc or EGLIBC
this error does not surface.
NOTE: package vdr-1.7.16-r0: task do_distribute_sources: Succeeded
ERROR: TaskFailed event exception, aborting
ERROR: Build of /oe/openembedded/recipes/vdr/vdr_1.7.16.bb do_compile
failed
ERROR: Task 11 (/oe/openembedded/recipes/vdr/vdr_1.7.16.bb, do_compile)
failed with 256
ERROR: Function do_compile failed
NOTE: Task failed: ('function do_compile failed',
'/oe/build-minimal-uclibc/minimal-uclibc-dev/work/armv7a-oe-linux-uclibceabi/vdr-1.7.16-r0/temp/log.do_compile.8011')
ERROR: Logfile of failure stored in:
/oe/build-minimal-uclibc/minimal-uclibc-dev/work/armv7a-oe-linux-uclibceabi/vdr-1.7.16-r0/temp/log.do_compile.8011
Log data follows:
| NOTE: make -j4 -e MAKEFLAGS=
INCLUDES=-I/oe/build-minimal-uclibc/minimal-uclibc-dev/sysroots/armv7a-oe-linux-uclibceabi/usr/include/freetype2
| arm-oe-linux-uclibceabi-g++ -march=armv7-a -mtune=cortex-a8
-mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb
-isystem/oe/build-minimal-uclibc/minimal-uclibc-dev/sysroots/armv7a-oe-linux-uclibceabi/usr/include
-fexpensive-optimizations -fomit-frame-pointer -frename-registers -Os
-fpermissive -fvisibility-inlines-hidden -c -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DREMOTE_KBD
-DLIRC_DEVICE=\/dev/lircd\ -DRCU_DEVICE=\/dev/ttyS1\ -D_GNU_SOURCE
-DVIDEODIR=\/video\ -DCONFDIR=\/video\ -DPLUGINDIR=\./PLUGINS/lib\
-DLOCDIR=\./locale\
-I/oe/build-minimal-uclibc/minimal-uclibc-dev/sysroots/armv7a-oe-linux-uclibceabi/usr/include/freetype2
audio.c
| arm-oe-linux-uclibceabi-g++ -march=armv7-a -mtune=cortex-a8
-mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb
-isystem/oe/build-minimal-uclibc/minimal-uclibc-dev/sysroots/armv7a-oe-linux-uclibceabi/usr/include
-fexpensive-optimizations -fomit-frame-pointer -frename-registers -Os
-fpermissive -fvisibility-inlines-hidden -c -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DREMOTE_KBD
-DLIRC_DEVICE=\/dev/lircd\ -DRCU_DEVICE=\/dev/ttyS1\ -D_GNU_SOURCE
-DVIDEODIR=\/video\ -DCONFDIR=\/video\ -DPLUGINDIR=\./PLUGINS/lib\
-DLOCDIR=\./locale\
-I/oe/build-minimal-uclibc/minimal-uclibc-dev/sysroots/armv7a-oe-linux-uclibceabi/usr/include/freetype2
channels.c
| arm-oe-linux-uclibceabi-g++ -march=armv7-a -mtune=cortex-a8
-mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb
-isystem/oe/build-minimal-uclibc/minimal-uclibc-dev/sysroots/armv7a-oe-linux-uclibceabi/usr/include
-fexpensive-optimizations -fomit-frame-pointer -frename-registers -Os
-fpermissive -fvisibility-inlines-hidden -c -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DREMOTE_KBD
-DLIRC_DEVICE=\/dev/lircd\ -DRCU_DEVICE=\/dev/ttyS1\ -D_GNU_SOURCE
-DVIDEODIR=\/video\ -DCONFDIR=\/video\ -DPLUGINDIR=\./PLUGINS/lib\
-DLOCDIR=\./locale\
-I/oe/build-minimal-uclibc/minimal-uclibc-dev/sysroots/armv7a-oe-linux-uclibceabi/usr/include/freetype2
ci.c
| arm-oe-linux-uclibceabi-g++ -march=armv7-a -mtune=cortex-a8
-mfpu=neon -mfloat-abi=softfp -mthumb-interwork -mno-thumb
-isystem/oe/build-minimal-uclibc/minimal-uclibc-dev/sysroots/armv7a-oe-linux-uclibceabi/usr/include
-fexpensive-optimizations -fomit-frame-pointer -frename-registers -Os
-fpermissive -fvisibility-inlines-hidden -c -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DREMOTE_KBD
-DLIRC_DEVICE=\/dev/lircd\ -DRCU_DEVICE=\/dev/ttyS1\ -D_GNU_SOURCE
-DVIDEODIR=\/video\ -DCONFDIR=\/video\ -DPLUGINDIR=\./PLUGINS/lib\
-DLOCDIR=\./locale\
-I/oe/build-minimal-uclibc/minimal-uclibc-dev/sysroots/armv7a-oe-linux-uclibceabi/usr/include/freetype2
config.c
| In file included from i18n.h:14:0,
| from config.h:19,
| from channels.h:13,
| from ci.h:15,
| from ci.c:10:
| tools.h:176:43: error: 'va_list' has not been declared
| In file included from audio.h:14:0,
| from audio.c:10:
| tools.h:176:43: error: 'va_list' has not been declared
| In file included from i18n.h:14:0,
| from config.h:19,
| from config.c:10:
| tools.h:176:43: error: 'va_list' has not been declared
| In file included from i18n.h:14:0,
| from config.h:19,
| from channels.h:13,
| from channels.c:10:
| tools.h:176:43: error: 'va_list' has not been declared
| make: *** [audio.o] Error 1
| make
[vdr] [RFC] [PATCH] tools.c: use C++ headers instead of deprecated C headers
Looking at Henning Heinhold’s patch [1] he changed the includes to the C++
headers instead of the C headers. At least Wikipedia says [2], that the C
headers are deprecated.
C++ provides this functionality in the header cstdarg; the C header, though
permitted, is deprecated in C++.
Is it desirable to change the includes in all files? If yes, is there a tool
which would accomplish this, since after the substitution a reordering is
needed?
[1]
http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/vdr/files/cplusplus.patch?id=97e1b707d6504343f02e683f49eb2cb6db2cc091
[2] https://secure.wikimedia.org/wikipedia/en/wiki/Stdarg.h
Signed-off-by: Paul Menzel paulepan...@users.sourceforge.net
---
tools.c | 10 +-
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/tools.c b/tools.c
index 3ce12ec..9a400a8 100644
--- a/tools.c
+++ b/tools.c
@@ -8,9 +8,12 @@
*/
#include tools.h
-#include ctype.h
+#include cctype
+#include cerrno
+#include cstdarg
+#include cstdlib
+#include ctime
#include dirent.h
-#include errno.h
extern C {
#ifdef boolean
#define HAVE_BOOLEAN
@@ -18,11 +21,8 @@ extern C {
#include jpeglib.h
#undef boolean
}
-#include stdarg.h
-#include stdlib.h
#include sys/time.h
#include sys/vfs.h
-#include time.h
#include unistd.h
#include utime.h
#include i18n.h
--
1.7.2.3
signature.asc
Description: This is a digitally signed message part
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] tools.h: include `stdarg.h` to fix `error: 'va_list' has not been declared` with uClibc
Am Montag, den 13.12.2010, 00:18 +0100 schrieb Klaus Schmidinger: On 12.12.2010 23:03, Paul Menzel wrote: From a94d15b582df5d1464cec8bc7dd68be46e1bf937 Mon Sep 17 00:00:00 2001 From: Paul Menzel paulepan...@users.sourceforge.net Date: Sun, 12 Dec 2010 19:21:25 +0100 Subject: [PATCH] tools.h: include `stdarg.h` For some reason using uClibc `tools.h` needs to have `stdarg.h` included explicitly. Otherwise it fails with the following error. Using Libc or EGLIBC this error does not surface. Since tools.h uses va_list you're apparently right. I wonder which one of the other header files tools.h includes pulls in that declaration (apparently unnecessarily). Sorry I have no idea. ... This change was made by Henning Heinhold when packaging VDR 1.7.10 for OpenEmbedded [1]. [1] http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/vdr/files/cplusplus.patch So I'll mention Henning in the CONTRIBUTORS file then, if that's ok with you. That would be fine. Signed-off-by: Paul Menzel paulepan...@users.sourceforge.net CC: Henning Heinold hein...@inf.fu-berlin.de --- tools.h |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/tools.h b/tools.h index 95c35ff..1fbe005 100644 --- a/tools.h +++ b/tools.h @@ -17,6 +17,7 @@ #include iconv.h #include math.h #include poll.h +#include stdarg.h #include stddef.h #include stdint.h #include stdio.h The '#include stdarg.h' can then also be removed from tools.c, and apparently it's included unnecessarily in osd.c and receiver.c. Good catches. Thank you for your fast response and analysis, Paul signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] Makefile: pass `LDFLAGS` to compiler
Am Montag, den 13.12.2010, 11:29 +0100 schrieb Paul Menzel: Am Montag, den 13.12.2010, 00:29 +0100 schrieb Joerg Bornkessel: Am Samstag, den 25.09.2010, 13:15 +0200 schrieb Joerg Bornkessel: […] [2] http://www.gentoo.org/proj/en/qa/asneeded.xml Should `LDFLAGS` also be passed to the compiler when building the plugins? We have this fixed global on Gentoo for all plugins. All plugin Makefile's are sed'ed/patched to use the LDFLAGS. Sorry, I do not know Gentoo’s build system. I found the patch for VDR [1] and the ebuild file [2]. I was wondering why skincurses had no patch applied or change regarding `LDFLAGS` [3] and for example vdr-burn [4] has a separate patch. Then I found `vdr-plugin.eclass` [5] where the replacement is done using `sed`. I made a patch from your message which does not include any changes to the plugins. I dont know, what distri you use, I am using the OpenEmbedded framework [6]. one way would be to fix this in the make.global ( used up from vdr-1.7.(not shure yet)) and inherit this in the plugin Makefile. Should be standard in the vdr-1.7.x adapted plugin Makefiles That is what my patch is for. I will send an updated patch. One question left. Why does not `LDFLAGS` need to be passed in the implicit rules? ### Implicit rules: %.o: %.c $(CXX) $(CXXFLAGS) $(LDFLAGS) -c $(DEFINES) $(INCLUDES) $ Thanks, Paul [1] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/media-video/vdr/files/vdr-1.6.0-ldflags.patch?view=markup [2] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/media-video/vdr/vdr-1.6.0_p2-r5.ebuild?view=markup [3] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/media-plugins/vdr-skincurses/ChangeLog?view=markup [4] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/media-plugins/vdr-burn/files/vdr-burn-0.2.0_beta1_ldflags.diff?revision=1.1view=markup [5] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/eclass/vdr-plugin.eclass?view=markup [6] http://www.openembedded.org/ signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH v2] Makefile: pass `LDFLAGS` to compiler
Am Montag, den 13.12.2010, 11:56 +0100 schrieb Paul Menzel: Am Montag, den 13.12.2010, 11:29 +0100 schrieb Paul Menzel: Am Montag, den 13.12.2010, 00:29 +0100 schrieb Joerg Bornkessel: Am Samstag, den 25.09.2010, 13:15 +0200 schrieb Joerg Bornkessel: […] [2] http://www.gentoo.org/proj/en/qa/asneeded.xml Should `LDFLAGS` also be passed to the compiler when building the plugins? We have this fixed global on Gentoo for all plugins. All plugin Makefile's are sed'ed/patched to use the LDFLAGS. Sorry, I do not know Gentoo’s build system. I found the patch for VDR [1] and the ebuild file [2]. I was wondering why skincurses had no patch applied or change regarding `LDFLAGS` [3] and for example vdr-burn [4] has a separate patch. Then I found `vdr-plugin.eclass` [5] where the replacement is done using `sed`. I made a patch from your message which does not include any changes to the plugins. I dont know, what distri you use, I am using the OpenEmbedded framework [6]. one way would be to fix this in the make.global ( used up from vdr-1.7.(not shure yet)) and inherit this in the plugin Makefile. Should be standard in the vdr-1.7.x adapted plugin Makefiles That is what my patch is for. I will send an updated patch. One question left. Why does not `LDFLAGS` need to be passed in the implicit rules? ### Implicit rules: %.o: %.c $(CXX) $(CXXFLAGS) $(LDFLAGS) -c $(DEFINES) $(INCLUDES) $ I guess that no linking is happening here? Please find below an updated patch. It would be great if you could add your Signed-off-by line or acknowledge it in some why, so Klaus can apply it. Thanks, Paul [1] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/media-video/vdr/files/vdr-1.6.0-ldflags.patch?view=markup [2] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/media-video/vdr/vdr-1.6.0_p2-r5.ebuild?view=markup [3] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/media-plugins/vdr-skincurses/ChangeLog?view=markup [4] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/media-plugins/vdr-burn/files/vdr-burn-0.2.0_beta1_ldflags.diff?revision=1.1view=markup [5] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/eclass/vdr-plugin.eclass?view=markup [6] http://www.openembedded.org/ 88 Date: Sun, 12 Dec 2010 18:19:42 +0100 Subject: [PATCH v2] Makefile: pass `LDFLAGS` to compiler Some distributions pass special flags to the linker [1][2]. Respect those by using `LDFLAGS`. Instead of [1] this patch was made using the following command based on `vdr-plugin.eclass` [3]. find PLUGINS -name Makefile | xargs sed -i '/LDFLAGS/!s:-shared:$(LDFLAGS) -shared:' Additionally the main Makefile was changed too. The changes have been present in OpenEmbedded and Gentoo for a while already and can be assumend tested. The implicit rules are not changed. This could been done easily using the following command. $ find PLUGINS -name Makefile | xargs sed -i 's/$(CXX) $(CXXFLAGS) -c $(DEFINES) $(INCLUDES) $/$(CXX) $(CXXFLAGS) $(LDFLAGS) -c $(DEFINES) $(INCLUDES) $/' [1] http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/vdr/vdr-1.7.10/linkerflags.patch [2] http://www.linuxtv.org/pipermail/vdr/2010-September/023623.html [3] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/eclass/vdr-plugin.eclass?view=markup (code line 232) Signed-off-by: Paul Menzel paulepan...@users.sourceforge.net --- Makefile |2 +- PLUGINS/src/dvbsddevice/Makefile |2 +- PLUGINS/src/hello/Makefile |2 +- PLUGINS/src/osddemo/Makefile |2 +- PLUGINS/src/pictures/Makefile|2 +- PLUGINS/src/servicedemo/Makefile |4 ++-- PLUGINS/src/skincurses/Makefile |2 +- PLUGINS/src/status/Makefile |2 +- PLUGINS/src/svdrpdemo/Makefile |2 +- 9 files changed, 10 insertions(+), 10 deletions(-) diff --git a/Makefile b/Makefile index 26f54ea..48e3309 100644 --- a/Makefile +++ b/Makefile @@ -95,7 +95,7 @@ $(DEPFILE): Makefile # The main program: vdr: $(OBJS) $(SILIB) - $(CXX) $(CXXFLAGS) -rdynamic $(OBJS) $(LIBS) $(LIBDIRS) $(SILIB) -o vdr + $(CXX) $(CXXFLAGS) -rdynamic $(LDFLAGS) $(OBJS) $(LIBS) $(LIBDIRS) $(SILIB) -o vdr # The libsi library: diff --git a/PLUGINS/src/dvbsddevice/Makefile b/PLUGINS/src/dvbsddevice/Makefile index 32d0f50..afc801b 100644 --- a/PLUGINS/src/dvbsddevice/Makefile +++ b/PLUGINS/src/dvbsddevice/Makefile @@ -99,7 +99,7 @@ i18n: $(I18Nmsgs) $(I18Npot) ### Targets: libvdr-$(PLUGIN).so: $(OBJS) - $(CXX) $(CXXFLAGS) -shared $(OBJS) -o $@ + $(CXX) $(CXXFLAGS) $(LDFLAGS) -shared $(OBJS) -o $@ @cp --remove-destination $@ $(LIBDIR)/$...@.$(APIVERSION) dist: clean diff --git a/PLUGINS/src/hello/Makefile b/PLUGINS/src/hello
Re: [vdr] [PATCH] Makefile: pass `LDFLAGS` to compiler
Am Montag, den 13.12.2010, 23:03 +0100 schrieb Joerg Bornkessel: Am Montag, den 13.12.2010, 00:29 +0100 schrieb Joerg Bornkessel: Am Samstag, den 25.09.2010, 13:15 +0200 schrieb Joerg Bornkessel: I was wondering why skincurses had no patch applied or change regarding `LDFLAGS` [3] and for example vdr-burn [4] has a separate patch. Then I found `vdr-plugin.eclass` [5] where the replacement is done using `sed`. some plugins (just a handfull) create beside on the plugin lib a helper lib or bin. to fix the makefile in this part will not fixed by the vdr-plugin.eclass. See this depended bug for vdr-burn http://bugs.gentoo.org/show_bug.cgi?id=339328 http://bugs.gentoo.org/attachment.cgi?id=249154 Thanks, actually I read that ticket before sending my message. It is great that you confirmed my guess. Could you reply to my »PATCH v2« if you have time please so that Klaus knows it is ready to be committed. I am using the OpenEmbedded framework [6]. hmm, sounds interresting, On what Hardware will this run, then? I am planning on using the BeagleBoard [8] which is ARM Cortex A8 based. T. Brinkmann is working on getting VDR to run on the BeagleBoard too [9], but there are some problems to use it as the output device. Thanks, Paul [7] http://www.vdr-wiki.de/wiki/index.php/Ångström [8] http://beagleboard.org/ [9] http://groups.google.com/group/beagleboard/msg/1b3fabd83fa9190e signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH v3] Makefile: pass `LDFLAGS` to compiler
Date: Sun, 12 Dec 2010 18:19:42 +0100 Some distributions pass special flags to the linker [1][2]. Respect those by using `LDFLAGS`. Instead of [1] this patch was made using the following command based on `vdr-plugin.eclass` [3]. find PLUGINS -name Makefile | xargs sed -i '/LDFLAGS/!s:-shared:$(LDFLAGS) -shared:' Additionally the main Makefile and the script `newplugin` are changed too. The changes have been present in OpenEmbedded and Gentoo for a while already and can be assumend tested. The implicit rules are not changed. This could been done easily using the following command. $ find PLUGINS -name Makefile | xargs sed -i 's/$(CXX) $(CXXFLAGS) -c $(DEFINES) $(INCLUDES) $/$(CXX) $(CXXFLAGS) $(LDFLAGS) -c $(DEFINES) $(INCLUDES) $/' [1] http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/vdr/vdr-1.7.10/linkerflags.patch [2] http://www.linuxtv.org/pipermail/vdr/2010-September/023623.html [3] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/eclass/vdr-plugin.eclass?view=markup (code line 232) Signed-off-by: Paul Menzel paulepan...@users.sourceforge.net Signed-off-by: Joerg Bornkessel m...@websitec.de --- v2 → v3: Change script `newplugin`. Patch submitted by Joerg [4]. [4] http://www.linuxtv.org/pipermail/vdr/2010-December/024068.html --- Makefile |2 +- PLUGINS/src/dvbsddevice/Makefile |2 +- PLUGINS/src/hello/Makefile |2 +- PLUGINS/src/osddemo/Makefile |2 +- PLUGINS/src/pictures/Makefile|2 +- PLUGINS/src/servicedemo/Makefile |4 ++-- PLUGINS/src/skincurses/Makefile |2 +- PLUGINS/src/status/Makefile |2 +- PLUGINS/src/svdrpdemo/Makefile |2 +- newplugin|2 +- 10 files changed, 11 insertions(+), 11 deletions(-) diff --git a/Makefile b/Makefile index 26f54ea..48e3309 100644 --- a/Makefile +++ b/Makefile @@ -95,7 +95,7 @@ $(DEPFILE): Makefile # The main program: vdr: $(OBJS) $(SILIB) - $(CXX) $(CXXFLAGS) -rdynamic $(OBJS) $(LIBS) $(LIBDIRS) $(SILIB) -o vdr + $(CXX) $(CXXFLAGS) -rdynamic $(LDFLAGS) $(OBJS) $(LIBS) $(LIBDIRS) $(SILIB) -o vdr # The libsi library: diff --git a/PLUGINS/src/dvbsddevice/Makefile b/PLUGINS/src/dvbsddevice/Makefile index 32d0f50..afc801b 100644 --- a/PLUGINS/src/dvbsddevice/Makefile +++ b/PLUGINS/src/dvbsddevice/Makefile @@ -99,7 +99,7 @@ i18n: $(I18Nmsgs) $(I18Npot) ### Targets: libvdr-$(PLUGIN).so: $(OBJS) - $(CXX) $(CXXFLAGS) -shared $(OBJS) -o $@ + $(CXX) $(CXXFLAGS) $(LDFLAGS) -shared $(OBJS) -o $@ @cp --remove-destination $@ $(LIBDIR)/$...@.$(APIVERSION) dist: clean diff --git a/PLUGINS/src/hello/Makefile b/PLUGINS/src/hello/Makefile index a5703f6..9e51cf7 100644 --- a/PLUGINS/src/hello/Makefile +++ b/PLUGINS/src/hello/Makefile @@ -99,7 +99,7 @@ i18n: $(I18Nmsgs) ### Targets: libvdr-$(PLUGIN).so: $(OBJS) - $(CXX) $(CXXFLAGS) -shared $(OBJS) -o $@ + $(CXX) $(CXXFLAGS) $(LDFLAGS) -shared $(OBJS) -o $@ @cp --remove-destination $@ $(LIBDIR)/$...@.$(APIVERSION) dist: clean diff --git a/PLUGINS/src/osddemo/Makefile b/PLUGINS/src/osddemo/Makefile index d9ed4c5..eb98160 100644 --- a/PLUGINS/src/osddemo/Makefile +++ b/PLUGINS/src/osddemo/Makefile @@ -72,7 +72,7 @@ $(DEPFILE): Makefile ### Targets: libvdr-$(PLUGIN).so: $(OBJS) - $(CXX) $(CXXFLAGS) -shared $(OBJS) -o $@ + $(CXX) $(CXXFLAGS) $(LDFLAGS) -shared $(OBJS) -o $@ @cp --remove-destination $@ $(LIBDIR)/$...@.$(APIVERSION) dist: clean diff --git a/PLUGINS/src/pictures/Makefile b/PLUGINS/src/pictures/Makefile index 19c6fc6..a573363 100644 --- a/PLUGINS/src/pictures/Makefile +++ b/PLUGINS/src/pictures/Makefile @@ -99,7 +99,7 @@ i18n: $(I18Nmsgs) $(I18Npot) ### Targets: libvdr-$(PLUGIN).so: $(OBJS) - $(CXX) $(CXXFLAGS) -shared $(OBJS) -o $@ + $(CXX) $(CXXFLAGS) $(LDFLAGS) -shared $(OBJS) -o $@ @cp --remove-destination $@ $(LIBDIR)/$...@.$(APIVERSION) dist: clean diff --git a/PLUGINS/src/servicedemo/Makefile b/PLUGINS/src/servicedemo/Makefile index 18bfd26..8cba989 100644 --- a/PLUGINS/src/servicedemo/Makefile +++ b/PLUGINS/src/servicedemo/Makefile @@ -74,11 +74,11 @@ $(DEPFILE): Makefile ### Targets: libvdr-$(PLUGIN1).so: $(PLUGIN1).o - $(CXX) $(CXXFLAGS) -shared $(PLUGIN1).o -o $@ + $(CXX) $(CXXFLAGS) $(LDFLAGS) -shared $(PLUGIN1).o -o $@ @cp --remove-destination $@ $(LIBDIR)/$...@.$(APIVERSION) libvdr-$(PLUGIN2).so: $(PLUGIN2).o - $(CXX) $(CXXFLAGS) -shared $(PLUGIN2).o -o $@ + $(CXX) $(CXXFLAGS) $(LDFLAGS) -shared $(PLUGIN2).o -o $@ @cp --remove-destination $@ $(LIBDIR)/$...@.$(APIVERSION) dist: clean diff --git a/PLUGINS/src/skincurses/Makefile b/PLUGINS/src/skincurses/Makefile index 080c3e6..e1e3ae6 100644 --- a/PLUGINS/src/skincurses/Makefile +++ b/PLUGINS/src/skincurses/Makefile @@ -99,7 +99,7 @@ i18n: $(I18Nmsgs) $(I18Npot) ### Targets: libvdr-$(PLUGIN).so: $(OBJS) - $(CXX
Re: [vdr] [PATCH v2] Makefile: pass `LDFLAGS` to compiler
Dear Jörg, Am Montag, den 13.12.2010, 23:49 +0100 schrieb Joerg Bornkessel: […] is it possible to add the patch/diff attached to the mail? I get the patches always inherited in the mail. Its more ezy to handle by Klaus then. I am used to Git, where it is easy to apply mail messages using the following command. git am /path/to/file I have not tried using `patch` with an mbox file. But it should work too. btw, also it should patched then the script newplugin in the main vdr src dir, see attached file. Thank you. I forgot about that. I hope the third iteration of the patch with your Signed-off-by will be fine [1]. And finaly, if the patch is applyed in the core vdr, plugin developer should be forced to fix this also in her development trees ;) Is there a way to do that. Or is the only option to bug them and send them patches? Thanks, Paul [1] http://www.linuxtv.org/pipermail/vdr/2010-December/024096.html signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] distribution of systemd service file
Dear VDR folks, I just noticed that Davide Cavalca added an systemd [1] service file for VDR to OpenBricks [2]. Is it useful to get this included upstream, so that all distributions can use it? I just found this one comment, that these service files supposed to be uniform between distributions [3]. On the other hand I did not find any init scripts in the VDR source. Thanks, Paul PS: Please do not use this thread to discuss different init systems. [1] http://www.freedesktop.org/wiki/Software/systemd [2] http://hg.openbricks.org/openbricks-next/rev/c532ffce1712 [3] http://bheekly.blogspot.com/2010/08/systemd-in-gentoo.html?showComment=1282939911093#c1286207673641196368 signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [RFC] [PATCH] player.c: fix `(error) Common realloc mistake: 'buffer' nulled but not freed upon failure`
Date: Mon, 14 Feb 2011 14:29:48 +0100
Output of Cppcheck 1.47 [1], VDR 1.7.16:
Checking ./PLUGINS/src/pictures/player.c...
[./PLUGINS/src/pictures/player.c:9]: (debug) Include file:
vdr/remote.h not found.
[./PLUGINS/src/pictures/player.c:10]: (debug) Include file:
vdr/tools.h not found.
[./PLUGINS/src/pictures/player.c:70]: (error) Common realloc mistake:
'buffer' nulled but not freed upon failure
Checking ./PLUGINS/src/pictures/player.c: BIDI...
Checking ./PLUGINS/src/pictures/player.c: DEBUGRINGBUFFERS...
Checking ./PLUGINS/src/pictures/player.c: PLUGIN_NAME_I18N...
Checking ./PLUGINS/src/pictures/player.c: __STL_CONFIG_H...
9/72 files checked 12% done
This patch uses the fix for QEMU [2] as a template and is build tested.
[1] http://cppcheck.sourceforge.net/
[2]
http://meego.gitorious.org/qemu-maemo/qemu/commit/29718712eb2e53c09d28f08e39f6514d690f6fd3
Signed-off-by: Paul Menzel paulepan...@users.sourceforge.net
CC: Klaus Schmidinger klaus.schmidin...@tvdr.de
---
Dear VDR folks,
please advise if the `break` is enough and what kind of error message
would be useful. I would then apply this fix to the whole tree and
submit a final patch.
Thanks,
Paul
---
PLUGINS/src/pictures/player.c |9 -
1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/PLUGINS/src/pictures/player.c b/PLUGINS/src/pictures/player.c
index a0123e4..3f87696 100644
--- a/PLUGINS/src/pictures/player.c
+++ b/PLUGINS/src/pictures/player.c
@@ -60,6 +60,7 @@ void cPicturePlayer::Activate(bool On)
void cPicturePlayer::SetPicture(const char *FileName)
{
+ uchar *new_buffer;
int f = open(FileName, O_RDONLY);
if (f = 0) {
for (;;) {
@@ -67,7 +68,13 @@ void cPicturePlayer::SetPicture(const char *FileName)
if (length 0) {
if (length = size) {
size = size * 3 / 2;
- buffer = (uchar *)realloc(buffer, size);
+ new_buffer = (uchar *)realloc(buffer, size);
+ if (new_buffer == NULL) {
+ free(buffer);
+ LOG_ERROR_STR(realloc);
+ break;
+ }
+ buffer = new_buffer;
lseek(f, 0, SEEK_SET);
continue;
}
--
1.7.2.3
signature.asc
Description: This is a digitally signed message part
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Email problem - who is the postmaster?
Dear Scott, Am Montag, den 14.02.2011, 19:54 + schrieb Scott Waye: What is the postmaster email address for this list? sorry, I do not know. I get some of the messages 7 times 20 minutes apart. I do not experience this problem. Do you have the headers of some of the messages where this happens? Thanks, Paul signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Plugin for MHEG (BBC RedButton service)
Dear John, Am Samstag, den 19.03.2011, 11:49 + schrieb John Williams: I have adapted the standalone redbutton program (http://redbutton.sourceforge.net/) into a plugin for VDR. This allows me to view the Redbutton data service broadcast by the BBC. great to hear that. To everyone as ignorant about MHEG as me please read [1]. John, thank you for the screenshots on your project site. Unfortunately MHEG is not available in Germany according to [1]. This is a preliminary version of the plugin and it is not robust enough for general use, but if anyone would like to experiment with it, the source code can be downloaded from http://pond-weed.com/redbutton/ I could not find a repository on your site. I think it greatly eases the task to provide patches. If you do not want to set one up yourself and you need a host you could use for example [2]. Thanks, Paul [1] https://secure.wikimedia.org/wikipedia/en/wiki/MHEG-5 [2] http://projects.vdr-developer.org/ signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] PLUGINS/src/osddemo/osddemo.c: fix possible null pointer dereference
Date: Sun, 3 Apr 2011 22:53:33 +0200
Cppcheck reports the following.
$ cppcheck --version
Cppcheck 1.47
$ cppcheck .
[…]
Checking ./PLUGINS/src/osddemo/osddemo.c...
[./PLUGINS/src/osddemo/osddemo.c:8]: (debug) Include file: vdr/osd.h
not found.
[./PLUGINS/src/osddemo/osddemo.c:9]: (debug) Include file:
vdr/plugin.h not found.
[./PLUGINS/src/osddemo/osddemo.c:270]: (error) Possible null pointer
dereference: NextPixmap
[…]
`CreateTextPixmap` can indeed assign `NULL` to `NextPixmap` and right before in
line 265 the same check is performed.
Signed-off-by: Paul Menzel paulepan...@users.sourceforge.net
CC: Klaus Schmidinger klaus.schmidin...@tvdr.de
---
PLUGINS/src/osddemo/osddemo.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/PLUGINS/src/osddemo/osddemo.c b/PLUGINS/src/osddemo/osddemo.c
index 2e6a33b..d3ec718 100644
--- a/PLUGINS/src/osddemo/osddemo.c
+++ b/PLUGINS/src/osddemo/osddemo.c
@@ -267,7 +267,9 @@ void cTrueColorDemo::Action(void)
}
Start = cTimeMs::Now();
StartLine = Line;
- Line += NextPixmap-DrawPort().Height();
+ if (NextPixmap) {
+ Line += NextPixmap-DrawPort().Height();
+ }
}
State++;
}
--
1.7.4.1
signature.asc
Description: This is a digitally signed message part
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] PLUGINS/src/dvbsddevice/dvbsdffosd.c: remove superflous variable `Bitmap`
Date: Fri, 4 Feb 2011 14:58:23 +0100
Cppcheck reports the following.
cppcheck: (style) Variable 'Bitmap' is assigned a value that is never
used
Therefore remove the variable `Bitmap` for stylistic reasons since the compiler
probably optimized that out anyway.
Signed-off-by: Paul Menzel paulepan...@users.sourceforge.net
CC: Klaus Schmidinger klaus.schmidin...@tvdr.de
---
PLUGINS/src/dvbsddevice/dvbsdffosd.c |6 ++
1 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/PLUGINS/src/dvbsddevice/dvbsdffosd.c
b/PLUGINS/src/dvbsddevice/dvbsdffosd.c
index 4b60ef5..8be1d25 100644
--- a/PLUGINS/src/dvbsddevice/dvbsdffosd.c
+++ b/PLUGINS/src/dvbsddevice/dvbsdffosd.c
@@ -73,8 +73,7 @@ void cDvbSdFfOsd::SetActive(bool On)
Flush();
}
else if (shown) {
-cBitmap *Bitmap;
-for (int i = 0; (Bitmap = GetBitmap(i)) != NULL; i++) {
+for (int i = 0; GetBitmap(i) != NULL; i++) {
Cmd(OSD_SetWindow, 0, i + 1);
Cmd(OSD_Close);
}
@@ -108,8 +107,7 @@ eOsdError cDvbSdFfOsd::CanHandleAreas(const tArea *Areas,
int NumAreas)
eOsdError cDvbSdFfOsd::SetAreas(const tArea *Areas, int NumAreas)
{
if (shown) {
- cBitmap *Bitmap;
- for (int i = 0; (Bitmap = GetBitmap(i)) != NULL; i++) {
+ for (int i = 0; GetBitmap(i) != NULL; i++) {
Cmd(OSD_SetWindow, 0, i + 1);
Cmd(OSD_Close);
}
--
1.7.4.1
signature.asc
Description: This is a digitally signed message part
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.18
Dear Klaus, thank you for this new release. Am Sonntag, den 17.04.2011, 16:50 +0200 schrieb Klaus Schmidinger: VDR developer version 1.7.18 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.18.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.17-1.7.18.diff I do not know if this has been discussed before, but could you please add the output of `md5sum` or `sha256sum` of the above files to your announcements. […] Thanks, Paul signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] non standard `.c` extension for C++ files
Dear VDR developers,
I am curious why the C++ source files have the extension `.c` and not
`.c{c,pp,xx}`.
I am asking because I tried to use `scan-build` from Clang/LLVM and by
default – and I did not find an option to change that – it treats `.c`
files as C files and not C++.
Running Clang directly on the `.c` files the following message is
displayed.
clang: warning: treating 'c' input as 'c++' when in C++ mode, this
behavior is deprecated
The folks an #llvm helped me and by verifying this putting
#ifndef __cplusplus
#error Not C++
#endif
in a file. Clang can be passed `-x c++` to override that behavior.
In the end I renamed the files and adapted `Makefile` to get
`scan-build` working and it did not find any errors.
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] cppcheck: VDR 1.7.18: [timers.c:53]: (error) snprintf size is out of bounds
Dear VDR folks,
Cppcheck 1.49 [1] reports the following error when run against VDR
1.7.18.
[timers.c:53]: (error) snprintf size is out of bounds
Looking at `timers.c` in `CTimer` `*file = 0` and afterward written to
if I am not mistaken.
[…]
cTimer::cTimer(bool Instant, bool Pause, cChannel *Channel)
{
startTime = stopTime = 0;
lastSetEvent = 0;
recording = pending = inVpsMargin = false;
flags = tfNone;
if (Instant)
SetFlags(tfActive | tfInstant);
channel = Channel ? Channel :
Channels.GetByNumber(cDevice::CurrentChannel());
time_t t = time(NULL);
struct tm tm_r;
struct tm *now = localtime_r(t, tm_r);
day = SetTime(t, 0);
weekdays = 0;
start = now-tm_hour * 100 + now-tm_min;
stop = now-tm_hour * 60 + now-tm_min + Setup.InstantRecordTime;
stop = (stop / 60) * 100 + (stop % 60);
if (stop = 2400)
stop -= 2400;
priority = Pause ? Setup.PausePriority : Setup.DefaultPriority;
lifetime = Pause ? Setup.PauseLifetime : Setup.DefaultLifetime;
*file = 0;
aux = NULL;
event = NULL;
if (Instant channel)
snprintf(file, sizeof(file), %s%s, Setup.MarkInstantRecord ? @
: , *Setup.NameInstantRecord ? Setup.NameInstantRecord : channel-Name());
[…]
Unfortunately I do not know C++ well enough to judge this error message.
Thanks,
Paul
[1] http://cppcheck.sourceforge.net/
signature.asc
Description: This is a digitally signed message part
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Wanted VDR xineliboutput client
Dear JJussi, Am Sonntag, den 16.10.2011, 14:02 +0300 schrieb JJussi: Any suggestions for small, powerful, quiet, FullHD VDR client? So, I search machine what would act as VDR-client, using xineliboutput with FullHD resolution and machine would have DVI or HDMI connection + optical audio. I am not having tested anything. Two things come to my mind if you assemble the system yourself. 1. ASRock E350M1 [1] for around 85 € [2]. (There is a USB3 variant too if you need that.) All you need is RAM and a case. The graphic chipset is powerful enough for FullHD playback. The reason I am recommending this board is it is supported by coreboot [3][4]. So buy one or two backup flash chips, build an image or use a demo image, flash it to the chip using flashrom [5] and enjoy hardware initialization in less than a second. Using a SSD (and systemd [6] (?)) it should be almost an instant on experience. 2. PandaBoard [7]. If you have a little more time to set things up the PandaBoard should be a nice platform. Costing around 170 € it is a little more expensive but it is small but has everything integrated (no RAM needed). I have been told boot up times using the Ȧngström distribution [8] (uses OpenEmbedded framework [9]) with systemd in less than four seconds. The chips on there are powerful enough for FullHD playback even without the proprietary PowerVR stuff. You will probably need to put some effort into getting Xine and xineliboutput to run as it is not packaged for OpenEmbedded yet. Of course remote control is needed too! ;-) Can’t you use your old one? Otherwise I am not having any suggestions. I heard the MSCE remotes are supported quite well though. Thanks, Paul [1] http://www.asrock.com/mb/overview.asp?Model=E350M1 [2] http://www.cyberport.de/?DEEP=2310-18RAPID=1 [3] http://coreboot.org/ [4] http://www.youtube.com/watch?v=IntsDeX_s1M [5] http://flashrom.org/ [6] http://freedesktop.org/wiki/Software/systemd/ [7] http://www.pandaboard.org/ [8] http://www.angstrom-distribution.org/ [9] http://www.openembedded.org/ signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] OT: Patches posted to support interlaced modes in intel-gfx
Dear VDR folks, there is a request for testing on the intel-gfx list for patches enabling interlaced modes [1]. After porting the driver to KMS interlaced modes did not work anymore and the patches enable support again. So Intel hardware seems to even more suited for a HTPC. 15:48 danvet yeah, together with libva an recent intel gpu should make a nice htpc 15:49 danvet although we don't support tv-out on ilk and later 15:49 danvet but iirc rodrigo vivi is working on that Daniel Vetter told me to remind you that these patches are experimental though and will (only) land in Linux 3.4. So to test them you will have to build the Linux kernel yourself. Maybe frame rate control patches from Thomas Hilber and VGA2SCART will also get upstream in the feature if somebody gets her/his hands dirty porting those. Thanks, Paul [1] http://lists.freedesktop.org/archives/intel-gfx/2012-January/014757.html [2] http://frc.easy-vdr.de/ [Intel-gfx]_[PATCH_0_8]_interlaced_support_v2.mbox Description: application/mbox signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Client/server implementation after VDR 2.0: Do not reinvent the wheel
Dear VDR folks, as you might have noticed in the thread of the announcement for version 1.7.25 there is some ongoing discussion about a client/server implementation for VDR which Klaus said to look at after the VDR 2.0 release. I just want to throw in, that there are several programs already using a client/server approach (MythTV [1], Tvheadend [2], …) and we should not reinvent the wheel when designing the new implementation. That means maybe folks having already used some of the other programs could write down the pros and the cons of their implementation. Maybe even the developers of these programs could be asked to comment on that and to give hints. Just a thought. Thanks, Paul [1] http://www.mythtv.org [2] https://www.lonelycoder.com/tvheadend/ signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Client/server implementation after VDR 2.0: Do not reinvent the whole wheel
Am Donnerstag, den 01.03.2012, 15:31 +0100 schrieb Gero: On Thursday 01 March 2012 - 10:31:37, Paul Menzel wrote: On Thursday 01 March 2012 - 07:03:03, VDR User wrote: I just want to throw in, that there are several programs already using a client/server approach (MythTV [1], Tvheadend [2], …) and we should not reinvent the wheel when designing the new implementation. I'd like to oppose headline and last statement. We can do better, so let's go ahead :) It looks like my message was not clear enough. I meant we should look at what other projects implemented and tried and take the good ideas and use those. So of course the result will probably be better. But cooperation like on using already existing protocols would be a big advantage, because in this way already existing clients or servers can be used to or tested against. […] Thanks, Paul signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR 1.7.28, xineliboutput 1.0.7: Using local frontend gives `No protocol specified`
Dear VDR folks, somehow I am not able to get the local frontend to work. Debian Sid/unstable is installed with $ dpkg -l vdr vdr-plugin-xineliboutput libxineliboutput-sxfe […] ii libxineliboutput-sxfe 1.0.7+cvs20120609.1902-1 Local X-Server frontend for the xineliboutput plugin ii vdr 1.7.28-1 Video Disk Recorder for DVB cards ii vdr-plugin-xineliboutput 1.0.7+cvs20120609.1902-1 VDR plugin for Xine based sofdevice frontends and I try to get the local frontend working but it fails. $ sudo -u vdr vdr -Pxineliboutput --local=sxfe --video=auto --audio=alsa --remote=none No protocol specified No protocol specified No protocol specified Unfortunately I do not know what the problem is as this is the command mentioned in `README` of `xineliboutput`. Usage examples (VDR plugin) If no arguments are given, both X11 and framebuffer frontends are tried. First working frontend is used with best available video driver. Complete list of available command-line arguments can be obtained with vdr --help. Only local frontend, X11/Xv video, alsa audio: vdr -Pxineliboutput --local=sxfe --video=xv --audio=alsa --remote=none Thanks, Paul signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [solved] VDR 1.7.28, xineliboutput 1.0.7: Using local frontend gives `No protocol specified`
Am Freitag, den 15.06.2012, 12:47 +0300 schrieb Petri Hintukainen: On ti, 2012-06-12 at 11:31 +0200, Paul Menzel wrote: somehow I am not able to get the local frontend to work. Debian Sid/unstable is installed with $ dpkg -l vdr vdr-plugin-xineliboutput libxineliboutput-sxfe […] ii libxineliboutput-sxfe 1.0.7+cvs20120609.1902-1 Local X-Server frontend for the xineliboutput plugin ii vdr 1.7.28-1 Video Disk Recorder for DVB cards ii vdr-plugin-xineliboutput 1.0.7+cvs20120609.1902-1 VDR plugin for Xine based sofdevice frontends and I try to get the local frontend working but it fails. $ sudo -u vdr vdr -Pxineliboutput --local=sxfe --video=auto --audio=alsa --remote=none No protocol specified No protocol specified No protocol specified Maybe it has no rights to open X window. Do you see any errors in log ? I did not see any errors printed to the terminal. What log file should I have looked at? Do you start it from X terminal ? Yes. I used GNOME Terminal with GNOME 3 running. Some things to try: - run xhost +si:localuser:vdr or xhost + before starting vdr (note that this opens a security hole) That indeed helped. Both commands work and knowing the solution it of course is the vdr user forbidden to put windows on the X session of a different user. - try starting without su (as current user, or with vdr option --user=vdr) I had tried that before and the problem is that the video directory is owned by the vdr user and it looks like starting `vdr` from a normal user and passing `--user=vdr` cannot change the user. That is why I tried it with `sudo`. […] Thanks a million, Paul signature.asc Description: This is a digitally signed message part ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
