Re: [linux-dvb] Empire DVB Dual Pen - New hardware
On 3/17/08, Maurizio [EMAIL PROTECTED] wrote: Hello. I just buyed an Empire USB 2.0 Pen Dual TV that is in supported USB DVB-T devices list. Too bad I discover now that apparently there is a new version of this hardware: same name than before but a different id (6000:eaec for my model). It doesn't work with current CVS compiled neither DVB-T nor Analogical (google give me no page about that id, so I don't know anything about the hardware itself). Is there anything I can do to help developers before I bring back this card to the shop and change it with something working? :-) what does usbview show up? I think it is already supported actually. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Elgato EyeTV Hybrid
On 3/13/08, Craig Marshall [EMAIL PROTECTED] wrote: Hi, Does anyone know if it's possible to use the Elgato EyeTV Hybrid (a mac device) with Linux? The device should be supported as far as I know, it's an Empiatech based device. Go to mcentral.de for further information. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] illegal bandwith value, driver for Terratec Cinergy DT usb XS
Hi Derk, On 3/10/08, Derk Dukker [EMAIL PROTECTED] wrote: Thank you very much Markus!! Do you also have any idea how to get the Cinergy CI usb working? I live in Holland and most of the channels are encrypted, so I need to use the Cinergy CI usb but I can't find drivers/information anywhere. I bought this in the firstplace for my playstation 3 with linux on it, I knew that support for CI was hard, but they said it would work with eyetv. So I thought, if it isn't working on linux it will on mac with eyetv. Everything works on my mac with eyetv except the CI usb :( there's no support for this CI device at this time. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Going though hell here, please provide how to for Pinnacle PCTV Hybrid Pro Stick 330e
I spent several hours again to see if I could get it working on Debian sid. I got a little bit further bit still got compilation errors. Can you please look at my attachments. CC [M] /home/jelle/em28xx-userspace2/em2880-dvb.o In file included from /home/jelle/em28xx-userspace2/em28xx.h:42, from /home/jelle/em28xx-userspace2/em2880-dvb.c:33: include/sound/core.h:281: error: 'SNDRV_CARDS' undeclared here (not in a function) ok this seems to come from a cleanup patch to remove some warnings. I reverted that change again. Can you download em28xx-userspace2 again and try to recompile it. thanks, Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] how can I create a czap config file without an sample config file for my environment
On Fri, Feb 29, 2008 at 4:03 PM, Markus Rechberger [EMAIL PROTECTED] wrote: Hi Jelle, On Fri, Feb 29, 2008 at 3:52 PM, Jelle de Jong [EMAIL PROTECTED] wrote: Hello all, I wanted to create the channel config files for my environment, but there is no scan example configuration that works for my environment, I do have the websites with tabels of the frequencys. How do i create my channel.conf sudo apt-get install dvb-utils # dvb-c channels: firefox http://www.upc.nl/frequencies_gm.php?GM=0493 I haven't had a look at that link first, this seems to be an analogue TV frequency list and not DVB-C. http://mcentral.de/wiki/index.php5/Tvtime you might try to install this tvtime version, it's patched to work with your device and autodetect the corresponding audio device. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] how can I create a czap config file without an sample config file for my environment
Hi Jelle,
On Fri, Feb 29, 2008 at 3:52 PM, Jelle de Jong
[EMAIL PROTECTED] wrote:
Hello all,
I wanted to create the channel config files for my environment, but
there is no scan example configuration that works for my environment, I
do have the websites with tabels of the frequencys. How do i create my
channel.conf
sudo apt-get install dvb-utils
# dvb-c channels:
firefox http://www.upc.nl/frequencies_gm.php?GM=0493
# dvb-t channels:
firefox http://www.digitenne.nl/pagina_49.html
# make directorys to store channel configurations
mkdir --verbose ~/.{t,c}zap
scan --help
sudo scan -A 1/usr/share/doc/dvb-utils/examples/scan/dvb-t/.
~/.tzap/channels.conf
sudo scan -A 2 /usr/share/doc/dvb-utils/examples/scan/dvb-c/
~/.czap/channels.conf
In case you want to use DVB-C, the Pinnacle Hybrid Pro 330e does NOT
support DVB-C, only analogue TV.
This device only supports DVB-T and analogue TV (which has nothing to
do with DVB-C or DVB-S)
You might try kaffeine for scanning for DVB-T channels.
for creating a custom scanfile you need some information about the
dvb-t transponder.
T 48200 8MHz 2/3 NONE QAM16 8k 1/4 NONE
T 76200 8MHz 2/3 NONE QAM16 8k 1/4 NONE
the Pinnacle 330e is capable of autodetecting everything beside the
first 2 entries (frequency, bandwidth)
There are tools available for creating scanfiles and running the
bruteforce method:
http://www.johannes-bauer.com/dvbt/
look at Schritt 4, or tar xfvj dvbt-scanaid-0.03.tar.bz2
http://www.johannes-bauer.com/dvbt/dvbt-scanaid-0.03.tar.bz2
Markus
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Going though hell here, please provide how to for Pinnacle PCTV Hybrid Pro Stick 330e
On Fri, Feb 29, 2008 at 4:10 PM, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: I spent several hours again to see if I could get it working on Debian sid. I got a little bit further bit still got compilation errors. Can you please look at my attachments. CC [M] /home/jelle/em28xx-userspace2/em2880-dvb.o In file included from /home/jelle/em28xx-userspace2/em28xx.h:42, from /home/jelle/em28xx-userspace2/em2880-dvb.c:33: include/sound/core.h:281: error: 'SNDRV_CARDS' undeclared here (not in a function) ok this seems to come from a cleanup patch to remove some warnings. I reverted that change again. Can you download em28xx-userspace2 again and try to recompile it. thanks, Markus Thank you it is now compiling, however when loading the drivers after rebooting the pc (also before rebooting) i get the following errors. See the attachments, Kind regards, Jelle usb 5-3: new high speed USB device using ehci_hcd and address 5 usb 5-3: configuration #1 chosen from 1 choice em28xx: disagrees about version of symbol video_unregister_device em28xx: Unknown symbol video_unregister_device em28xx: disagrees about version of symbol video_device_alloc em28xx: Unknown symbol video_device_alloc em28xx: disagrees about version of symbol video_register_device em28xx: Unknown symbol video_register_device em28xx: disagrees about version of symbol video_device_release em28xx: Unknown symbol video_device_release can you also reinstall the linux kernel for your debian distribution? the manual installation of v4l-dvb-experimental from mcentral.de or v4l-dvb repository from linuxtv.org causes this problem. You might try apt-get install --reinstall linux-image-`uname -r` for restoring your kernel You probably have the modules from v4l-dvb-experimental or v4l-dvb installed, but your kernel sources have older versions of those interfaces, and the userspace drivers only build against the original kernel interface. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle PCTV Hybrid Pro Stick 330e - Installation Guide - v0.1.2j
On 2/29/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: Hi Jelle, On 2/29/08, Jelle de Jong [EMAIL PROTECTED] wrote: This message contains the following attachment(s): Pinnacle PCTV Hybrid Pro Stick 330e - Installation Guide - v0.1.2j.txt the correct mailinglist for those devices is em28xx at mcentral dot de I added some comments below and prefixed them with / This message contains the following attachment(s): Pinnacle PCTV Hybrid Pro Stick 330e - Installation Guide - v0.1.2j.txt We will get it working in the next few days, i am already working on a user guide. I will add the comments to the new version, i just thought release as soon as possible, dont want somebody else to spent hours and hours of his day installing your nice driver. Nice, I was working on building tvtime but it gave me errors, libasound2-dev and the linux kernel headers or at least a symlink from /usr/include/linux - kernelroot/include/linux is missing. It would be nice if you can create a howto on mcentral.de! I'm sure it might help some people. My guide only explains how to compile it on a already set up system (and this can differ with every distribution). I will release precompiled packages for the eeePC within the next few days. I just need to package the binaries for it. I added tvtime, gqradio and kaffeine buttons to my eeePC and everything works really well. I'll focus on ATSC devices next week (after the cebit) thanks for the howto so far! Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle PCTV Hybrid Pro Stick 330e - Installation Guide - v0.1.2j
Hi Jelle, On 2/29/08, Jelle de Jong [EMAIL PROTECTED] wrote: This message contains the following attachment(s): Pinnacle PCTV Hybrid Pro Stick 330e - Installation Guide - v0.1.2j.txt the correct mailinglist for those devices is em28xx at mcentral dot de I added some comments below and prefixed them with / This message contains the following attachment(s): Pinnacle PCTV Hybrid Pro Stick 330e - Installation Guide - v0.1.2j.txt #!/bin/bash # Pinnacle PCTV Hybrid Pro Stick 330e - Installation Guide - v0.1.1j.txt # # Copyright 2008 Jelle de Jong [EMAIL PROTECTED] # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, # MA 02110-1301, USA. # to-do: # howto add group for created devices so that all users in that group can use the devices? # notes: # there is less then 10% cpu load on an ASUS eeepc when watching analog tv with xawtv, is there hardware encoding? # how to watch teletext? # no audio yet, need to find out how to channel the audio to my primary soundcard, without lossing sync! /// use tvtime from mcentral.de it runs well on my eeePC and audio is also in sync, I tested it with NTSC, PAL-BG and SECAM. # support: # email the linux-dvb mailinglist // email the em28xx mailinglist! # step 0: only do this if you already tried to compile some linux drivers sudo apt-get remove linux-image-(uname -r) linux-headers linux-source linux-headers-$(uname -r) sudo apt-get autoremove sudo rm -r -f /usr/src/* sudo rm -r -f /lib/modules/* sudo apt-get install atl2-modules-2.6.24-1-686 linux-image-2.6.24-1-686 sudo update-grub # step 1: update your system sudo apt-get clean sudo apt-get update sudo apt-get upgrade sudo apt-get autoremove # step 2: clean your system sudo apt-get remove linux-headers linux-source linux-headers-$(uname -r) sudo apt-get autoremove # step 3: install the necessary tools sudo apt-get install linux-source linux-headers-$(uname -r) build-essential mercurial # step 4: extract the kernel source cd /usr/src sudo tar --bzip2 -xvf linux-source-2.6.*.tar.bz2 cd ~ # step 5: remove old symlinks when present sudo rm /usr/src/linux sudo rm /lib/modules/$(uname -r)/source # step 6: create new sysmlinks, change the kernel to its current version sudo ln -s /usr/src/linux-source-2.6.24 /usr/src/linux sudo ln -s /usr/src/linux-source-2.6.24 /lib/modules/$(uname -r)/source # step 7: copy your orignal config to the kernel source root tree sudo cp --verbose /boot/config-$(uname -r) /usr/src/linux/.config # step 8: check if the symlink and kernel source is there ls -hal /usr/src/ #total 44M #drwxrwsr-x 6 root src 4.0K Feb 29 15:16 . #drwxr-xr-x 11 root root 4.0K Feb 23 00:32 .. #lrwxrwxrwx 1 root src28 Feb 29 15:16 linux - /usr/src/linux-source-2.6.24 #drwxr-xr-x 4 root root 4.0K Feb 29 15:10 linux-headers-2.6.24-1-686 #drwxr-xr-x 18 root root 4.0K Feb 29 15:10 linux-headers-2.6.24-1-common #drwxr-xr-x 3 root root 4.0K Feb 29 15:10 linux-kbuild-2.6.24 #drwxr-xr-x 20 root root 4.0K Feb 29 15:17 linux-source-2.6.24 #-rw-r--r-- 1 root root 44M Feb 11 12:42 linux-source-2.6.24.tar.bz2 # step 9: make sure all these files and locations excist ls -hal /lib/modules/$(uname -r)/source ls -hal /lib/modules/$(uname -r)/source/drivers/media/dvb/dvb-core/dmxdev.h ls -hal /lib/modules/$(uname -r)/source/drivers/media/dvb/dvb-core/dvb_frontend.h ls -hal /lib/modules/$(uname -r)/source/drivers/media/dvb/dvb-core/dvb_demux.h ls -hal /lib/modules/$(uname -r)/source/drivers/media/dvb/dvb-core/dvb_net.h ls -hal /usr/src/linux/drivers/media/dvb/dvb-core/dmxdev.h ls -hal /usr/src/linux/drivers/media/dvb/dvb-core/dvb_frontend.h ls -hal /usr/src/linux/drivers/media/dvb/dvb-core/dvb_demux.h ls -hal /usr/src/linux/drivers/media/dvb/dvb-core/dvb_net.h # step 10: download and build the first driver necessary to build the second one cd ~ sudo rm -r userspace-drivers hg clone http://mcentral.de/hg/~mrec/userspace-drivers cd userspace-drivers sudo ./build.sh cd ~ # step 11: download and build the second driver after you build the first one cd ~ sudo rm -r em28xx-userspace2 hg clone http://mcentral.de/hg/~mrec/em28xx-userspace2 cd em28xx-userspace2 sudo ./build.sh cd ~ # step 12: reboot your
Re: [linux-dvb] Pinnacle PCTV Hybrid Pro Stick 330e - Installation Guide - v0.1.2j
On 2/29/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 2/29/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: Hi Jelle, On 2/29/08, Jelle de Jong [EMAIL PROTECTED] wrote: This message contains the following attachment(s): Pinnacle PCTV Hybrid Pro Stick 330e - Installation Guide - v0.1.2j.txt the correct mailinglist for those devices is em28xx at mcentral dot de I added some comments below and prefixed them with / This message contains the following attachment(s): Pinnacle PCTV Hybrid Pro Stick 330e - Installation Guide - v0.1.2j.txt We will get it working in the next few days, i am already working on a user guide. I will add the comments to the new version, i just thought release as soon as possible, dont want somebody else to spent hours and hours of his day installing your nice driver. Nice, I was working on building tvtime but it gave me errors, libasound2-dev and the linux kernel headers or at least a symlink from /usr/include/linux - kernelroot/include/linux is missing. It would be nice if you can create a howto on mcentral.de! I'm sure it might help some people. My guide only explains how to compile it on a already set up system (and this can differ with every distribution). I will release precompiled packages for the eeePC within the next few days. I just need to package the binaries for it. I added tvtime, gqradio and kaffeine buttons to my eeePC and everything works really well. I'll focus on ATSC devices next week (after the cebit) thanks for the howto so far! Markus I will work on the docu you on the nice code :-p Just one thing how to fix the below? Than we can release a first draft. We need a group that is compatiable with udev and the driver, so that we can do adduser $USER $GROUP to give premissions to use the devices feel free to work on it, if you have some patches to apply for the build.sh scripts just submit them :) # to-do: # howto add group for created devices so that all users in that group can use the devices? oja also i cant get /dev/vdi0 working the vbi interface was only tested with osc which is part of the libzvbi package. There's currently no application available which works with the vbi interface, it needs some more fiddling around with the libzvbi library. This is a topic which has a lower priority since other parts have to be improved first.. Patches in that area are welcome of course. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] need advice to buy supported DVB-T USB device
Hi Jelle, On Thu, Feb 28, 2008 at 3:47 PM, Jelle de Jong [EMAIL PROTECTED] wrote: Hello, I want to buy a device that allows me to watch dvd-t signals under Linux. I want this device to work under linux on my usb port. And i need to buy the device at this store for support: http://www.informatique.nl/cgi-bin/iqshop.cgi?M=ARTG=167 secondary like to haves: - works on 900 MHZ Intel Mobile M (eeepc) - can record and watch at the same time - cost less then 140 euro. - small size - works with an analogue coax cable and digital dvb-t signal I can suggest: http://tvde.terratec.net/modules.php?op=modloadname=Newsfile=articlesid=249 http://www.pinnaclesys.com/PublicSite/us/Products/Consumer+Products/PCTV/PCTV/ http://www.hauppauge.co.uk/pages/products/data_hvr900.html etc. Those devices are tested on the eeePC, first device from Terratec also supports analogue radio (and stereo with analogue TV, pinnacle and hauppauge's devices only support mono TV audio) all of them support analogue TV and DVB-T. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] v4l-dvb-experimental will not compile on debian sid 2.6.24-1-686
Hi Jelle, which device device did you buy? there are 2 different kind of driver available. There's a patch available on the em28xx mailinglist which I haven't added to v4l-dvb-experimental yet (I'll go through it tomorrow) to fix those compatibility issues. Markus On 2/28/08, John Drescher [EMAIL PROTECTED] wrote: On Thu, Feb 28, 2008 at 3:39 PM, Jelle de Jong [EMAIL PROTECTED] wrote: cd $HOME hg clone http://mcentral.de/hg/~mrec/v4l-dvb-experimental cd v4l-dvb-experimental make sudo make install v4l-dvb-experimental will not compile on debian sid 2.6.24-1-686 If you guys need more information i will sent it to the list. Can you post what error you are getting. Also, since this is a live build from the repository there are times when parts of the build will fail. John ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Going though hell here, please provide how to for Pinnacle PCTV Hybrid Pro Stick 330e
On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: This message contains the following attachment(s): Pinnacle PCTV Hybrid Pro Stick 330e.txt Spent my hole day trying to get a dvd-t device up and running, this is device number two I tried. Can somebody please tell me how to get this device working on: 2.6.24-1-686 debian sid and 2.6.22-14-generic ubuntu I have to get some sleep now, because this is getting on my health and that does not happen often Jelle, it's really easy to install it actually. http://www.mail-archive.com/em28xx%40mcentral.de/msg00750.html this is the correct howto for it. You need the linux kernel sources for your kernel, if you experience any problems just post them to the em28xx ML. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Going though hell here, please provide how to for Pinnacle PCTV Hybrid Pro Stick 330e
On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: This message contains the following attachment(s): Pinnacle PCTV Hybrid Pro Stick 330e.txt Spent my hole day trying to get a dvd-t device up and running, this is device number two I tried. Can somebody please tell me how to get this device working on: 2.6.24-1-686 debian sid and 2.6.22-14-generic ubuntu I have to get some sleep now, because this is getting on my health and that does not happen often Jelle, it's really easy to install it actually. http://www.mail-archive.com/em28xx%40mcentral.de/msg00750.html this is the correct howto for it. You need the linux kernel sources for your kernel, if you experience any problems just post them to the em28xx ML. Markus Hi Markus, I tried that two times, The seconds build blows up in my face, I need specified dependecies to be able to compile the seconds driver... there are not so many dependencies, just submit the errors you get. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Going though hell here, please provide how to for Pinnacle PCTV Hybrid Pro Stick 330e
On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: This message contains the following attachment(s): Pinnacle PCTV Hybrid Pro Stick 330e.txt Spent my hole day trying to get a dvd-t device up and running, this is device number two I tried. Can somebody please tell me how to get this device working on: 2.6.24-1-686 debian sid and 2.6.22-14-generic ubuntu I have to get some sleep now, because this is getting on my health and that does not happen often Jelle, it's really easy to install it actually. http://www.mail-archive.com/em28xx%40mcentral.de/msg00750.html this is the correct howto for it. You need the linux kernel sources for your kernel, if you experience any problems just post them to the em28xx ML. Markus Hi Markus, I tried that two times, The seconds build blows up in my face, I need specified dependecies to be able to compile the seconds driver... there are not so many dependencies, just submit the errors you get. Markus Here you go, lets see I will try it for 40 more minutes with your help [EMAIL PROTECTED]:~$ hg clone http://mcentral.de/hg/~mrec/em28xx-userspace2 destination directory: em28xx-userspace2 requesting all changes adding changesets adding manifests adding file changes added 21 changesets with 65 changes to 20 files 18 files updated, 0 files merged, 0 files removed, 0 files unresolved [EMAIL PROTECTED]:~$ cd em28xx-userspace2 [EMAIL PROTECTED]:~/em28xx-userspace2$ sudo ./build.sh if [ -f ../userspace-drivers/kernel/Module.symvers ]; then \ grep v4l_dvb_stub_attach ../userspace-drivers/kernel/Module.symvers Module.symvers; \ fi make -C /lib/modules/2.6.22-14-generic/build SUBDIRS=/home/jelle/em28xx-userspace2 modules make[1]: Entering directory `/usr/src/linux-headers-2.6.22-14-generic' CC [M] /home/jelle/em28xx-userspace2/em2880-dvb.o In file included from /home/jelle/em28xx-userspace2/em2880-dvb.c:33: /home/jelle/em28xx-userspace2/em28xx.h:33:20: error: dmxdev.h: No such file or directory /home/jelle/em28xx-userspace2/em28xx.h:34:23: error: dvb_demux.h: No such file or directory /home/jelle/em28xx-userspace2/em28xx.h:35:21: error: dvb_net.h: No such file or directory /home/jelle/em28xx-userspace2/em28xx.h:36:26: error: dvb_frontend.h: No such file or directory there we go, the linux kernel sources aren't installed for your system. apt-get install linux-source linux-headers-`uname -r` I'm not sure if the kernel sources are decompressed in /usr/src you might have a look at it. /lib/modules/`uname -r`/build should be a symlink to the root of the extracted kernelsources. the root of your kernelsources should also contain a .config file. You can find the config file for your current kernel in /boot /boot/config-`uname -r` copy this file to the kernelroot and rename it to .config Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Going though hell here, please provide how to for Pinnacle PCTV Hybrid Pro Stick 330e
On 2/28/08, Markus Rechberger [EMAIL PROTECTED] wrote: On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: This message contains the following attachment(s): Pinnacle PCTV Hybrid Pro Stick 330e.txt Spent my hole day trying to get a dvd-t device up and running, this is device number two I tried. Can somebody please tell me how to get this device working on: 2.6.24-1-686 debian sid and 2.6.22-14-generic ubuntu I have to get some sleep now, because this is getting on my health and that does not happen often Jelle, it's really easy to install it actually. http://www.mail-archive.com/em28xx%40mcentral.de/msg00750.html this is the correct howto for it. You need the linux kernel sources for your kernel, if you experience any problems just post them to the em28xx ML. Markus Hi Markus, I tried that two times, The seconds build blows up in my face, I need specified dependecies to be able to compile the seconds driver... there are not so many dependencies, just submit the errors you get. Markus Here you go, lets see I will try it for 40 more minutes with your help [EMAIL PROTECTED]:~$ hg clone http://mcentral.de/hg/~mrec/em28xx-userspace2 destination directory: em28xx-userspace2 requesting all changes adding changesets adding manifests adding file changes added 21 changesets with 65 changes to 20 files 18 files updated, 0 files merged, 0 files removed, 0 files unresolved [EMAIL PROTECTED]:~$ cd em28xx-userspace2 [EMAIL PROTECTED]:~/em28xx-userspace2$ sudo ./build.sh if [ -f ../userspace-drivers/kernel/Module.symvers ]; then \ grep v4l_dvb_stub_attach ../userspace-drivers/kernel/Module.symvers Module.symvers; \ fi make -C /lib/modules/2.6.22-14-generic/build SUBDIRS=/home/jelle/em28xx-userspace2 modules make[1]: Entering directory `/usr/src/linux-headers-2.6.22-14-generic' CC [M] /home/jelle/em28xx-userspace2/em2880-dvb.o In file included from /home/jelle/em28xx-userspace2/em2880-dvb.c:33: /home/jelle/em28xx-userspace2/em28xx.h:33:20: error: dmxdev.h: No such file or directory /home/jelle/em28xx-userspace2/em28xx.h:34:23: error: dvb_demux.h: No such file or directory /home/jelle/em28xx-userspace2/em28xx.h:35:21: error: dvb_net.h: No such file or directory /home/jelle/em28xx-userspace2/em28xx.h:36:26: error: dvb_frontend.h: No such file or directory there we go, the linux kernel sources aren't installed for your system. apt-get install linux-source linux-headers-`uname -r` I'm not sure if the kernel sources are decompressed in /usr/src you might have a look at it. /lib/modules/`uname -r`/build should be a symlink to the root of the extracted kernelsources. the root of your kernelsources should also contain a .config file. You can find the config file for your current kernel in /boot /boot/config-`uname -r` copy this file to the kernelroot and rename it to .config oh wait someone already provided precompiled packages for that device for the same ubuntu version as you use. http://mcentral.de/pipermail/em28xx/2008-February/001277.html Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Going though hell here, please provide how to for Pinnacle PCTV Hybrid Pro Stick 330e
On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: This message contains the following attachment(s): Pinnacle PCTV Hybrid Pro Stick 330e.txt Spent my hole day trying to get a dvd-t device up and running, this is device number two I tried. Can somebody please tell me how to get this device working on: 2.6.24-1-686 debian sid and 2.6.22-14-generic ubuntu I have to get some sleep now, because this is getting on my health and that does not happen often Jelle, it's really easy to install it actually. http://www.mail-archive.com/em28xx%40mcentral.de/msg00750.html this is the correct howto for it. You need the linux kernel sources for your kernel, if you experience any problems just post them to the em28xx ML. Markus Hi Markus, I tried that two times, The seconds build blows up in my face, I need specified dependecies to be able to compile the seconds driver... there are not so many dependencies, just submit the errors you get. Markus Here you go, lets see I will try it for 40 more minutes with your help [EMAIL PROTECTED]:~$ hg clone http://mcentral.de/hg/~mrec/em28xx-userspace2 destination directory: em28xx-userspace2 requesting all changes adding changesets adding manifests adding file changes added 21 changesets with 65 changes to 20 files 18 files updated, 0 files merged, 0 files removed, 0 files unresolved [EMAIL PROTECTED]:~$ cd em28xx-userspace2 [EMAIL PROTECTED]:~/em28xx-userspace2$ sudo ./build.sh if [ -f ../userspace-drivers/kernel/Module.symvers ]; then \ grep v4l_dvb_stub_attach ../userspace-drivers/kernel/Module.symvers Module.symvers; \ fi make -C /lib/modules/2.6.22-14-generic/build SUBDIRS=/home/jelle/em28xx-userspace2 modules make[1]: Entering directory `/usr/src/linux-headers-2.6.22-14-generic' CC [M] /home/jelle/em28xx-userspace2/em2880-dvb.o In file included from /home/jelle/em28xx-userspace2/em2880-dvb.c:33: /home/jelle/em28xx-userspace2/em28xx.h:33:20: error: dmxdev.h: No such file or directory /home/jelle/em28xx-userspace2/em28xx.h:34:23: error: dvb_demux.h: No such file or directory /home/jelle/em28xx-userspace2/em28xx.h:35:21: error: dvb_net.h: No such file or directory /home/jelle/em28xx-userspace2/em28xx.h:36:26: error: dvb_frontend.h: No such file or directory there we go, the linux kernel sources aren't installed for your system. apt-get install linux-source linux-headers-`uname -r` I'm not sure if the kernel sources are decompressed in /usr/src you might have a look at it. /lib/modules/`uname -r`/build should be a symlink to the root of the extracted kernelsources. the root of your kernelsources should also contain a .config file. You can find the config file for your current kernel in /boot /boot/config-`uname -r` copy this file to the kernelroot and rename it to .config Markus sudo apt-get install linux-source linux-headers-`uname -r` Reading package lists... Done Building dependency tree Reading state information... Done linux-source is already the newest version. linux-headers-2.6.22-14-generic is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. [EMAIL PROTECTED]:~/em28xx-userspace2$ ls -hal /lib/modules/`uname -r`/build lrwxrwxrwx 1 root root 40 2007-10-21 18:19 /lib/modules/2.6.22-14-generic/build - /usr/src/linux-headers-2.6.22-14-generic [EMAIL PROTECTED]:~/em28xx-userspace2$ /boot/config-`uname -r` bash: /boot/config-2.6.22-14-generic: Permission denied [EMAIL PROTECTED]:~/em28xx-userspace2$ sudo /boot/config-`uname -r` sudo: /boot/config-2.6.22-14-generic: command not found [EMAIL PROTECTED]:~/em28xx-userspace2$ sudo ls /boot/config-`uname -r` /boot/config-2.6.22-14-generic [EMAIL PROTECTED]:~/em28xx-userspace2$ sudo cp --verbose /boot/config-2.6.22-14-generic /usr/src/linux/.config `/boot/config-2.6.22-14-generic' - `/usr/src/linux/.config' still all the same problems ! it's just one problem actually, the kernel sources aren't installed or not installed correctly. You need to have /usr/src/linux/drivers/media/dvb/dvb-core/dmxdev.h /usr/src/linux/drivers/media/dvb/dvb-core/dvb_frontend.h /usr/src/linux/drivers/media/dvb/dvb-core/dvb_demux.h /usr/src/linux/drivers/media/dvb/dvb-core/dvb_net.h those are part of the ubuntu linux source package. look up the source package for 2.6.22 with apt-cache apt-cache search linux-source | grep -i 2.6.22 or something like that and install it. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Going though hell here, please provide how to for Pinnacle PCTV Hybrid Pro Stick 330e
On 2/28/08, Markus Rechberger [EMAIL PROTECTED] wrote: On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: This message contains the following attachment(s): Pinnacle PCTV Hybrid Pro Stick 330e.txt Spent my hole day trying to get a dvd-t device up and running, this is device number two I tried. Can somebody please tell me how to get this device working on: 2.6.24-1-686 debian sid and 2.6.22-14-generic ubuntu I have to get some sleep now, because this is getting on my health and that does not happen often Jelle, it's really easy to install it actually. http://www.mail-archive.com/em28xx%40mcentral.de/msg00750.html this is the correct howto for it. You need the linux kernel sources for your kernel, if you experience any problems just post them to the em28xx ML. Markus Hi Markus, I tried that two times, The seconds build blows up in my face, I need specified dependecies to be able to compile the seconds driver... there are not so many dependencies, just submit the errors you get. Markus Here you go, lets see I will try it for 40 more minutes with your help [EMAIL PROTECTED]:~$ hg clone http://mcentral.de/hg/~mrec/em28xx-userspace2 destination directory: em28xx-userspace2 requesting all changes adding changesets adding manifests adding file changes added 21 changesets with 65 changes to 20 files 18 files updated, 0 files merged, 0 files removed, 0 files unresolved [EMAIL PROTECTED]:~$ cd em28xx-userspace2 [EMAIL PROTECTED]:~/em28xx-userspace2$ sudo ./build.sh if [ -f ../userspace-drivers/kernel/Module.symvers ]; then \ grep v4l_dvb_stub_attach ../userspace-drivers/kernel/Module.symvers Module.symvers; \ fi make -C /lib/modules/2.6.22-14-generic/build SUBDIRS=/home/jelle/em28xx-userspace2 modules make[1]: Entering directory `/usr/src/linux-headers-2.6.22-14-generic' CC [M] /home/jelle/em28xx-userspace2/em2880-dvb.o In file included from /home/jelle/em28xx-userspace2/em2880-dvb.c:33: /home/jelle/em28xx-userspace2/em28xx.h:33:20: error: dmxdev.h: No such file or directory /home/jelle/em28xx-userspace2/em28xx.h:34:23: error: dvb_demux.h: No such file or directory /home/jelle/em28xx-userspace2/em28xx.h:35:21: error: dvb_net.h: No such file or directory /home/jelle/em28xx-userspace2/em28xx.h:36:26: error: dvb_frontend.h: No such file or directory there we go, the linux kernel sources aren't installed for your system. apt-get install linux-source linux-headers-`uname -r` I'm not sure if the kernel sources are decompressed in /usr/src you might have a look at it. /lib/modules/`uname -r`/build should be a symlink to the root of the extracted kernelsources. the root of your kernelsources should also contain a .config file. You can find the config file for your current kernel in /boot /boot/config-`uname -r` copy this file to the kernelroot and rename it to .config Markus sudo apt-get install linux-source linux-headers-`uname -r` Reading package lists... Done Building dependency tree Reading state information... Done linux-source is already the newest version. linux-headers-2.6.22-14-generic is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. [EMAIL PROTECTED]:~/em28xx-userspace2$ ls -hal /lib/modules/`uname -r`/build lrwxrwxrwx 1 root root 40 2007-10-21 18:19 /lib/modules/2.6.22-14-generic/build - /usr/src/linux-headers-2.6.22-14-generic [EMAIL PROTECTED]:~/em28xx-userspace2$ /boot/config-`uname -r` bash: /boot/config-2.6.22-14-generic: Permission denied [EMAIL PROTECTED]:~/em28xx-userspace2$ sudo /boot/config-`uname -r` sudo: /boot/config-2.6.22-14-generic: command not found [EMAIL PROTECTED]:~/em28xx-userspace2$ sudo ls /boot/config-`uname -r` /boot/config-2.6.22-14-generic [EMAIL PROTECTED]:~/em28xx-userspace2$ sudo cp --verbose /boot/config-2.6.22-14-generic /usr/src/linux/.config `/boot/config-2.6.22-14-generic' - `/usr/src/linux/.config' still all the same problems ! it's just one problem actually, the kernel sources aren't installed or not installed correctly. You need to have /usr/src/linux/drivers/media/dvb/dvb-core/dmxdev.h /usr/src/linux/drivers/media/dvb/dvb-core/dvb_frontend.h /usr/src/linux/drivers/media/dvb/dvb-core/dvb_demux.h /usr/src/linux/drivers/media/dvb/dvb-core/dvb_net.h those are part of the ubuntu linux source package. look up the source package for 2.6.22 with apt-cache apt-cache search linux-source | grep -i 2.6.22 or something like that and install it. if you have an instant messenger
Re: [linux-dvb] Going though hell here, please provide how to for Pinnacle PCTV Hybrid Pro Stick 330e
On 2/29/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: This message contains the following attachment(s): Pinnacle PCTV Hybrid Pro Stick 330e.txt Spent my hole day trying to get a dvd-t device up and running, this is device number two I tried. Can somebody please tell me how to get this device working on: 2.6.24-1-686 debian sid and 2.6.22-14-generic ubuntu I have to get some sleep now, because this is getting on my health and that does not happen often Jelle, it's really easy to install it actually. http://www.mail-archive.com/em28xx%40mcentral.de/msg00750.html this is the correct howto for it. You need the linux kernel sources for your kernel, if you experience any problems just post them to the em28xx ML. Markus Hi Markus, I tried that two times, The seconds build blows up in my face, I need specified dependecies to be able to compile the seconds driver... there are not so many dependencies, just submit the errors you get. Markus Here you go, lets see I will try it for 40 more minutes with your help [EMAIL PROTECTED]:~$ hg clone http://mcentral.de/hg/~mrec/em28xx-userspace2 destination directory: em28xx-userspace2 requesting all changes adding changesets adding manifests adding file changes added 21 changesets with 65 changes to 20 files 18 files updated, 0 files merged, 0 files removed, 0 files unresolved [EMAIL PROTECTED]:~$ cd em28xx-userspace2 [EMAIL PROTECTED]:~/em28xx-userspace2$ sudo ./build.sh if [ -f ../userspace-drivers/kernel/Module.symvers ]; then \ grep v4l_dvb_stub_attach ../userspace-drivers/kernel/Module.symvers Module.symvers; \ fi make -C /lib/modules/2.6.22-14-generic/build SUBDIRS=/home/jelle/em28xx-userspace2 modules make[1]: Entering directory `/usr/src/linux-headers-2.6.22-14-generic' CC [M] /home/jelle/em28xx-userspace2/em2880-dvb.o In file included from /home/jelle/em28xx-userspace2/em2880-dvb.c:33: /home/jelle/em28xx-userspace2/em28xx.h:33:20: error: dmxdev.h: No such file or directory /home/jelle/em28xx-userspace2/em28xx.h:34:23: error: dvb_demux.h: No such file or directory /home/jelle/em28xx-userspace2/em28xx.h:35:21: error: dvb_net.h: No such file or directory /home/jelle/em28xx-userspace2/em28xx.h:36:26: error: dvb_frontend.h: No such file or directory there we go, the linux kernel sources aren't installed for your system. apt-get install linux-source linux-headers-`uname -r` I'm not sure if the kernel sources are decompressed in /usr/src you might have a look at it. /lib/modules/`uname -r`/build should be a symlink to the root of the extracted kernelsources. the root of your kernelsources should also contain a .config file. You can find the config file for your current kernel in /boot /boot/config-`uname -r` copy this file to the kernelroot and rename it to .config Markus sudo apt-get install linux-source linux-headers-`uname -r` Reading package lists... Done Building dependency tree Reading state information... Done linux-source is already the newest version. linux-headers-2.6.22-14-generic is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. [EMAIL PROTECTED]:~/em28xx-userspace2$ ls -hal /lib/modules/`uname -r`/build lrwxrwxrwx 1 root root 40 2007-10-21 18:19 /lib/modules/2.6.22-14-generic/build - /usr/src/linux-headers-2.6.22-14-generic [EMAIL PROTECTED]:~/em28xx-userspace2$ /boot/config-`uname -r` bash: /boot/config-2.6.22-14-generic: Permission denied [EMAIL PROTECTED]:~/em28xx-userspace2$ sudo /boot/config-`uname -r` sudo: /boot/config-2.6.22-14-generic: command not found [EMAIL PROTECTED]:~/em28xx-userspace2$ sudo ls /boot/config-`uname -r` /boot/config-2.6.22-14-generic [EMAIL PROTECTED]:~/em28xx-userspace2$ sudo cp --verbose /boot/config-2.6.22-14-generic /usr/src/linux/.config `/boot/config-2.6.22-14-generic' - `/usr/src/linux/.config' still all the same problems ! it's just one problem actually, the kernel sources aren't installed or not installed correctly. You need to have /usr/src/linux/drivers/media/dvb/dvb-core/dmxdev.h /usr/src/linux/drivers/media/dvb/dvb-core/dvb_frontend.h /usr/src/linux/drivers/media/dvb/dvb-core/dvb_demux.h /usr/src/linux/drivers/media/dvb/dvb-core/dvb_net.h those are part of the ubuntu linux source package. look up the source package for 2.6.22 with apt-cache apt-cache search linux-source | grep -i 2.6.22 or something like that and install it. Markus I did a complete clean-up of the system tried again checked
Re: [linux-dvb] Going though hell here, please provide how to for Pinnacle PCTV Hybrid Pro Stick 330e
On 2/29/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 2/28/08, Markus Rechberger [EMAIL PROTECTED] wrote: On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 2/28/08, Jelle de Jong [EMAIL PROTECTED] wrote: This message contains the following attachment(s): Pinnacle PCTV Hybrid Pro Stick 330e.txt Spent my hole day trying to get a dvd-t device up and running, this is device number two I tried. Can somebody please tell me how to get this device working on: 2.6.24-1-686 debian sid and 2.6.22-14-generic ubuntu I have to get some sleep now, because this is getting on my health and that does not happen often Jelle, it's really easy to install it actually. http://www.mail-archive.com/em28xx%40mcentral.de/msg00750.html this is the correct howto for it. You need the linux kernel sources for your kernel, if you experience any problems just post them to the em28xx ML. Markus Hi Markus, I tried that two times, The seconds build blows up in my face, I need specified dependecies to be able to compile the seconds driver... there are not so many dependencies, just submit the errors you get. Markus Here you go, lets see I will try it for 40 more minutes with your help [EMAIL PROTECTED]:~$ hg clone http://mcentral.de/hg/~mrec/em28xx-userspace2 destination directory: em28xx-userspace2 requesting all changes adding changesets adding manifests adding file changes added 21 changesets with 65 changes to 20 files 18 files updated, 0 files merged, 0 files removed, 0 files unresolved [EMAIL PROTECTED]:~$ cd em28xx-userspace2 [EMAIL PROTECTED]:~/em28xx-userspace2$ sudo ./build.sh if [ -f ../userspace-drivers/kernel/Module.symvers ]; then \ grep v4l_dvb_stub_attach ../userspace-drivers/kernel/Module.symvers Module.symvers; \ fi make -C /lib/modules/2.6.22-14-generic/build SUBDIRS=/home/jelle/em28xx-userspace2 modules make[1]: Entering directory `/usr/src/linux-headers-2.6.22-14-generic' CC [M] /home/jelle/em28xx-userspace2/em2880-dvb.o In file included from /home/jelle/em28xx-userspace2/em2880-dvb.c:33: /home/jelle/em28xx-userspace2/em28xx.h:33:20: error: dmxdev.h: No such file or directory /home/jelle/em28xx-userspace2/em28xx.h:34:23: error: dvb_demux.h: No such file or directory /home/jelle/em28xx-userspace2/em28xx.h:35:21: error: dvb_net.h: No such file or directory /home/jelle/em28xx-userspace2/em28xx.h:36:26: error: dvb_frontend.h: No such file or directory there we go, the linux kernel sources aren't installed for your system. apt-get install linux-source linux-headers-`uname -r` I'm not sure if the kernel sources are decompressed in /usr/src you might have a look at it. /lib/modules/`uname -r`/build should be a symlink to the root of the extracted kernelsources. the root of your kernelsources should also contain a .config file. You can find the config file for your current kernel in /boot /boot/config-`uname -r` copy this file to the kernelroot and rename it to .config Markus sudo apt-get install linux-source linux-headers-`uname -r` Reading package lists... Done Building dependency tree Reading state information... Done linux-source is already the newest version. linux-headers-2.6.22-14-generic is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. [EMAIL PROTECTED]:~/em28xx-userspace2$ ls -hal /lib/modules/`uname -r`/build lrwxrwxrwx 1 root root 40 2007-10-21 18:19 /lib/modules/2.6.22-14-generic/build - /usr/src/linux-headers-2.6.22-14-generic [EMAIL PROTECTED]:~/em28xx-userspace2$ /boot/config-`uname -r` bash: /boot/config-2.6.22-14-generic: Permission denied [EMAIL PROTECTED]:~/em28xx-userspace2$ sudo /boot/config-`uname -r` sudo: /boot/config-2.6.22-14-generic: command not found [EMAIL PROTECTED]:~/em28xx-userspace2$ sudo ls /boot/config-`uname -r` /boot/config-2.6.22-14-generic [EMAIL PROTECTED]:~/em28xx-userspace2$ sudo cp --verbose /boot/config-2.6.22-14-generic /usr/src/linux/.config `/boot/config-2.6.22-14-generic' - `/usr/src/linux/.config' still all the same problems ! it's just one problem actually, the kernel sources aren't installed or not installed correctly. You need to have /usr/src/linux/drivers/media/dvb/dvb-core/dmxdev.h /usr/src/linux/drivers/media/dvb/dvb-core/dvb_frontend.h /usr/src/linux/drivers/media/dvb/dvb-core/dvb_demux.h /usr/src/linux/drivers/media/dvb/dvb-core/dvb_net.h those are part of the ubuntu linux source package. look up the source package for 2.6.22 with apt-cache apt-cache search linux-source | grep -i 2.6.22 or something like that and install it. if you have an instant
Re: [linux-dvb] Going though hell here, please provide how to for Pinnacle PCTV Hybrid Pro Stick 330e
On 2/29/08, Nicolas Will [EMAIL PROTECTED] wrote: hmmm... guys. First thing: on a Debian or Ubuntu system, I never needed the full Linux sources to compile a v4l-dvb tree. The headers were always enough. Second thing: when you compile a v4l-dvb tree on the side, I do not think that it is adding anything in the headers. So, if you subsequently need to compile a driver that needs stuff from a recent v4l-dvb tree, it won't find it. Third thing: That weird driver of yours is probably looking for its stuff either int the headers (were there will not be anything good to find because of the point made above) or in an available kernel source tree (where it will probably not find anything that will make it happy because your recent v4l-dvb tree is elsewhere). May I suggest to get a kernel source tree (from the appropriate package), incorporate the v4l-dvb tree in it, then try to compile your weird driver against this. Getting rid of the headers may help. When you compile the v4l-dvb or v4l-dvb-experimental tree it will update your whole v4l and dvb subsystem. As soon as you do so it won't work to install any other external media drivers anymore, beside that v4l-dvb is much bigger than the snipped out em28xx driver. em28xx-userspace2 and userspace-drivers only contains the drivers for em28xx based devices and won't affect any other drivers on the system. Since the uvc driver is also out of tree it won't break compiling/using the uvc driver against the current running kernel. The kernel sources are needed because some internal headers are needed for the em28xx to build an alternative tuning system for hybrid radio/analogue TV/DTV devices. It should work flawlessly with older kernel releases where v4l-dvb already fails to compile. It's also easier to keep backward compatibility while not breaking any other drivers on the system that way (and this is seriously needed) Beside all that: There's a .deb package available I posted the link very early already compiling from source can always introduce some mess so you better know what you do otherwise you have to learn how it works... The build scripts already do alot work there for several different distributions Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle Hybrid Pro Stick 330e - DVB - Micronas DRX3975D/DRX3977D based
Hi, 2008/2/24 Salvatore De Astis [EMAIL PROTECTED]: Hi, I bouth the hardware in object and I would like support to use it for digital tv. Anyone can help me? this device is already supported, please have a look at the em2880 projectsite on mcentral.de. If you have any questions regarding it please use the em28xx ML on mcentral.de. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] experimental drivers and 2.6.24 kernel
Hey Ondrej, 2008/2/24 Ondrej Holecek [EMAIL PROTECTED]: hello, i have problems with compiling experimental drivers from http://mcentral.de/hg/~mrec/v4l-dvb-experimental/ with kernel 2.6.24 i need it for my eb1a:e323 eMPIA Technology, Inc. (digivox a/d II) I'll try to get that device next week for adding full support for it. I don't think that there's proper support in v4l-dvb-experimental for that device anyway. Best for you would be to sign up at the mailinglist on mcentral.de I'll post further news about it when I'm done with it. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Start thinking about potential Google Summer of Code Projects we could run
Steven Toth wrote: Hans Verkuil wrote: On Wednesday 19 December 2007 17:26:35 CityK wrote: Hi folks, Google summer of code will be rolling around in a couple of months. Now I know we've talked a little bit about it before, but I don't recall what the thoughts on it were. In any regard, on the surface of things, it would seem a perfect opportunity for the LinuxTV Project to leverage -- i.e. enslave a few students to get some desperately needed tasks, components, apps, drivers or whatever done. Side benefit -- it might hopefully attact a few more developers to the project too -- get some new blood, stir up the pot, chase after nagging/long-time bugs etc, etc. So, I suggest we start thinking about or, better yet, discussing ideas/projects for which we could make use of the GSOC. (I, of course, was kidding about the enslavement part) Pity, that was my favorite part ;) I think that this might be an ideal opportunity to develop a v4l2 library that can be used by applications to access v4l devices. Something like that is sorely missing and nobody has the time to really work on it. I've always thought that this is a good project for something like GSOC. Why stop at a v4l2 library, why not include digital to complete the TV experience? A unified library that protects the kernel (at the expense of a newer more flexible userland API/ABI). How about a concise library for analog/digital channels worldwide? A concrete and reliable set of frequencies, country by country, video/audio standards, bandwidths etc so userland apps can stop having to care about internal channel tables? This is a good idea, I would say this is necessary in the end to avoid inconsistency in the end. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [Em28xx] kernel crash with Terratec Cinergy XS
[80208ce4] default_idle+0x0/0x3d [8020c136] do_IRQ+0x6c/0xd6 [88003e4d] :processor:acpi_processor_idle+0x0/0x48b [8020a141] ret_from_intr+0x0/0xa EOI [88003dc6] :processor:acpi_safe_halt+0x28/0x39 [88003ff9] :processor:acpi_processor_idle+0x1ac/0x48b [88003e4d] :processor:acpi_processor_idle+0x0/0x48b [80208ce4] default_idle+0x0/0x3d [80208daf] cpu_idle+0x8e/0xb1 [805d077b] start_kernel+0x2cf/0x2db [805d0148] _sinittext+0x148/0x14c Code: c6 85 88 00 00 00 03 48 c7 45 50 00 00 00 00 e8 a8 95 1d f8 RIP [8811d20a] :ehci_hcd:end_unlink_async+0x22/0xed RSP 80624e48 crash On Thursday 06 December 2007 23:00:05 you wrote: Hi all, I recently bought a Terratec Cinergy XS in France. I tried driver from http://mcentral.de/hg/~mrec/v4l-dvb-experimental and followed instructions from here http://www.techjp.net/suse_103_terratec_cartetv_tnt I modprobed with and without em28xx device_mode=17. Scanning in kaffeine starts, but after a while (around 30%) the system locks up and the kernel crashes. I use opensuse kernel 2.6.22.13-0.3-default. I tried different Firmware, e.g. from here http://www.techjp.net/UserFile/File/articles/OpenSuse103/firmware.tgz. Any idea what could go wrong or how I could provide more info e.g. kernel stack trace? Chris - Linux video capture interface: v2.00 em28xx v4l2 driver version 0.0.1 loaded em28xx new video device (0ccd:005e): interface 0, class 255 em28xx: device is attached to a USB 2.0 bus em28xx: you're using the experimental/unstable tree from mcentral.de em28xx: there's also a stable tree available but which is limited to em28xx: linux =2.6.19.2 em28xx: it's fine to use this driver but keep in mind that it will move em28xx: to http://mcentral.de/hg/~mrec/v4l-dvb-kernel as soon as it's em28xx: proved to be stable em28xx #0: Alternate settings: 8 em28xx #0: Alternate setting 0, max size= 0 em28xx #0: Alternate setting 1, max size= 0 em28xx #0: Alternate setting 2, max size= 1448 em28xx #0: Alternate setting 3, max size= 2048 em28xx #0: Alternate setting 4, max size= 2304 em28xx #0: Alternate setting 5, max size= 2580 em28xx #0: Alternate setting 6, max size= 2892 em28xx #0: Alternate setting 7, max size= 3072 input: em2880/em2870 remote control as /class/input/input7 em28xx-input.c: remote control handler attached attach_inform: eeprom detected. em28xx #0: i2c eeprom 00: 1a eb 67 95 cd 0c 5e 00 d0 12 5c 03 9e 40 de 1c em28xx #0: i2c eeprom 10: 6a 34 27 57 46 07 01 00 00 00 00 00 00 00 00 00 em28xx #0: i2c eeprom 20: 46 00 01 00 f0 10 31 00 b8 00 14 00 5b 1e 00 00 em28xx #0: i2c eeprom 30: 00 00 20 40 20 6e 02 20 10 01 00 00 00 00 00 00 em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00 34 03 54 00 65 00 em28xx #0: i2c eeprom 70: 72 00 72 00 61 00 54 00 65 00 63 00 20 00 45 00 em28xx #0: i2c eeprom 80: 6c 00 65 00 63 00 74 00 72 00 6f 00 6e 00 69 00 em28xx #0: i2c eeprom 90: 63 00 20 00 47 00 6d 00 62 00 48 00 00 00 40 03 em28xx #0: i2c eeprom a0: 43 00 69 00 6e 00 65 00 72 00 67 00 79 00 20 00 em28xx #0: i2c eeprom b0: 48 00 79 00 62 00 72 00 69 00 64 00 20 00 54 00 em28xx #0: i2c eeprom c0: 20 00 55 00 53 00 42 00 20 00 58 00 53 00 20 00 em28xx #0: i2c eeprom d0: 28 00 32 00 38 00 38 00 32 00 29 00 00 00 1c 03 em28xx #0: i2c eeprom e0: 30 00 37 00 30 00 38 00 30 00 32 00 30 00 30 00 em28xx #0: i2c eeprom f0: 33 00 38 00 34 00 33 00 00 00 00 00 00 00 00 00 EEPROM ID= 0x9567eb1a Vendor/Product ID= 0ccd:005e AC97 audio (5 sample rates) 500mA max power Table at 0x27, strings=0x409e, 0x1cde, 0x346a tuner 1-0061: chip found @ 0xc2 (em28xx #0) attach inform (default): detected I2C address c2 /home/christian/v4l-dvb-experimental/v4l/tuner-core.c: setting tuner callback tuner 0x61: Configuration acknowledged /home/christian/v4l-dvb-experimental/v4l/tuner-core.c: setting tuner callback /home/christian/v4l-dvb-experimental/v4l/xc3028-tuner.c: attach request! /home/christian/v4l-dvb-experimental/v4l/tuner-core.c: xc3028 tuner successfully loaded attach_inform: tvp5150 detected. tvp5150 1-005c: tvp5150am1 detected. Loading base firmware: xc3028_init0.i2c.fw Loading default analogue TV settings: xc3028_BG_PAL_A2_A.i2c.fw xc3028-tuner.c: firmware 2.7 ANALOG TV REQUEST em28xx #0: V4L2 VBI device registered as /dev/vbi0 em28xx #0: V4L2 device registered as /dev/video0 em28xx #0: Found Terratec Hybrid XS (em2882) usbcore: registered new interface driver em28xx em28xx-audio.c: probing for em28x1 non standard usbaudio em28xx-audio.c: Copyright (C) 2006 Markus Rechberger Em28xx: Initialized (Em28xx Audio Extension) extension em2880-dvb.c: DVB
Re: [linux-dvb] Anybody who used snd-usb-audio to play tv audio, please help me.
On Nov 30, 2007 6:01 AM, kevin liu [EMAIL PROTECTED] wrote: Dear, Now I found that my tv card have a usb audio class compliant audio stream interface. Linux's audio class driver snd-usb-driver finds my audio device, and the relative device nodes under /dev have been created successfully. And I am also using adevice option to give mplayer correct alsa device, when I play tv program, I cat /proc/asound/card1/stream0, streaming status is running, but I still can not get any sound. I have no experience to config snd-usb-audio, if you have it, would you like to give me some clues. you might have to toggle some input selector bits in your main driver (eg. to switch audio from composite to TV input or so) Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Trying to get Hauppauge WinTV HVR 950 to work
On 11/29/07, Meryl Silverburgh [EMAIL PROTECTED] wrote: Hi, Can you please tell me if someone can get Hauppauge WinTV HVR 950 to work under Ubuntu 7.10 with both audio and video? I can only get video but no audio. You can have a look at: http://mcentral.de/wiki/index.php/Em2880 regards, Markus Thank you for any pointers. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- http://www.couchsurfing.com/people/mrec ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem about snd-usb-audio
On 11/29/07, kevin liu [EMAIL PROTECTED] wrote: Dear, My usb device controller has an audio stream isoc interface. When my tv card was plugged in, the audio stream isoc interface is found by the snd-usb-audio. I think snd-usb-audio.ko is Linux USB audio class driver, but why saa7134 project maintain its own sound card driver. which sound card can snd-usb-audio successfully drive? snd-usb-audio supports devices which are conform to the usb audio specification. If your device provides endpoints which are conform that driver can handle the datatransfer to userspace for you. You might still have to set up the audio source using the videointerface. The em28xx also has an extra audio driver for non usb audio compatible interfaces. The same for the saa7134, the way how the audio data gets transferred is just not specified in a generic specification for it that's why it needs a special driver for it. hope that helps, Markus Thanks. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- http://www.couchsurfing.com/people/mrec ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Has anyone met the same problem with me?
On 11/28/07, kevin liu [EMAIL PROTECTED] wrote: Dear, /** I attached one of my video frame, please help me to examine it. **/ I am testing my sweet tv card on my Ubuntu with self-developed driver, until yesterday, I got some bad effect video frame. It seems that the video data correctly received and correctly copied to buffer outqueue because I could watch the tv program with a bad effect. But I wonder why mplayer gives video frame a green background. Anyone has met the same problem, give me some advice please, thank you. could also be a bad reception and that the video is shifted by 1 or 2 bytes to the wrong direction, maybe you forgot to strip of the headers of your frame (just a guess though) RGB would look differently. YUYV uses 4 bytes for 2 pixels, RGB 3 bytes for 1 pixel (so the video would very likely be bigger). It seems like that you're displaying the whole videocontent already so have a closer look at stripping off a few bytes. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle PCTV HD Ultimate Stick
On 11/15/07, Michael Krufky [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 11/15/07, Michael Krufky [EMAIL PROTECTED] wrote: Jeff Rosenberg wrote: I just purchase the PCTV HD Ultimate Stick. I decided upon this since it supported clear QAM and had flash space for recording to the stick in addition to the hardrive. I read that the PCTV HD Pro Stick was supported with the latest Experimental build based on the em2883 chipset. I took the risk and went with the Ultimate instead of the Pro. [snip] Any chance that there will be support for this newly released USB stick ? You wont find native support for this in any Linux Distribution's native kernel anytime soon. Your best bet, in this case, is to look at Markus' experimental repository. I don't think that he has support for this exact device yet, but he does have most of the pieces required. #1) You need em2880-dvb support, which is not yet in the master v4l-dvb development branch #2) (I think) you'll need an xc5000 driver, also not yet merged into the v4l-dvb master branch. You might be able to assemble the right pieces of code together, but I don't know where you'll find it all at this time. Given a few months (or weeks, in a perfect world) time, the situation may become clearer. Michael, this is no em28xx based device, I guess it's a dibcom one. Ah, OK. Thanks, Markus. In which case, bridge-wise, it may be a bit easier (or more difficult, depending) than I thought. Jeff, it might be helpful if you could crack open the device and tell us all of the chips featured inside. Hi-res digital photos are always helpful :-) If you can take photos, please post them to a website (like bttv-gallery) and post links here. I think that's not really necessary, my one is already open (I could take a foto if not already available) although I think Patrick already has a driver for it? The usb device includes a hub and shows up 2 more usbids on the host, one is a storage device, the other one is the dibcom tuner as far as I remember. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle PCTV HD Ultimate Stick
On 11/15/07, Michael Krufky [EMAIL PROTECTED] wrote: Jeff Rosenberg wrote: I just purchase the PCTV HD Ultimate Stick. I decided upon this since it supported clear QAM and had flash space for recording to the stick in addition to the hardrive. I read that the PCTV HD Pro Stick was supported with the latest Experimental build based on the em2883 chipset. I took the risk and went with the Ultimate instead of the Pro. [snip] Any chance that there will be support for this newly released USB stick ? You wont find native support for this in any Linux Distribution's native kernel anytime soon. Your best bet, in this case, is to look at Markus' experimental repository. I don't think that he has support for this exact device yet, but he does have most of the pieces required. #1) You need em2880-dvb support, which is not yet in the master v4l-dvb development branch #2) (I think) you'll need an xc5000 driver, also not yet merged into the v4l-dvb master branch. You might be able to assemble the right pieces of code together, but I don't know where you'll find it all at this time. Given a few months (or weeks, in a perfect world) time, the situation may become clearer. Michael, this is no em28xx based device, I guess it's a dibcom one. regards, Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle PCTV HD Ultimate Stick
On 11/15/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Markus Rechberger wrote: I think that's not really necessary, my one is already open (I could take a foto if not already available) although I think Patrick already has a driver for it? The usb device includes a hub and shows up 2 more usbids on the host, one is a storage device, the other one is the dibcom tuner as far as I remember. Interesting... In which case, then I'm probably wrong, and it's not an xc5000. Do you know WHICH dibcom tuner? Is it a 7070? I have no idea last time when I looked at it was around 6 months ago. I'll check it when I'm at home. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle PCTV HD Ultimate Stick
On 11/15/07, CityK [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: Jeff Rosenberg wrote: The Pinnacle PCTV HD Ultimate stick just came out (a couple of weeks ago). I looked in the Windoze .inf files and it appears that the drivers used are the same for the PCTV HD Pro and PCTV HD Ultimate. I looked in the developmental build of DVB and saw that in the file em288x-cards.c there was the correct USB_DEVICE # of 0x2304 but the next value was not 0x0233. I changed it and recompiled. When the driver loads it now has the following message in the kernel buffer log: FIXME:em28xx_i2c_send_bytes(c2): write failed: Any ideas ? I am pretty sure the correct driver is the em28xx. As both Patrick and Markus explained, this device is not empia hardware, and the code that supports it is located inside dib0700_devices.c -- you'll want to edit dvb-usb-ids.h Also, please do not top-post. However, Jeff will still need xc5000 support the dib0700 is purely the usb bridge while, I'm guessing that the stick uses a xc5000, I believe that it is indeed a pretty safe bet (given other factors) Interesting... In which case, then I'm probably wrong, and it's not an xc5000. Do you know WHICH dibcom tuner? Is it a 7070? It definitely won't be from Dibicom --- no support for ATSC Hi-res digital photos are always helpful :-) If you can take photos, please post them to a website (like bttv-gallery) and post links here. Jeff, if you take a photo, could you please up load it to the LinuxTV wiki: http://www.linuxtv.org/wiki/index.php/Special:Upload (Please also use an appropriate filename) If you wish to submit it too bttv-gallery too, go ahead, but i) as was noted on the m/l last month, Gunther (bttv-gallery's proprietor) hasn't been around for ages ii) doing so alone would continue the trend of a fractured distribution of information regarding Linux PC tvtuners. Linuxtv should become the one stop shop. We don't need to compete with ourselves, so lets make requests for photos to the wiki please. The outcome is it's an Empiatech device with completly new components on it. It's hard to programm... although they'll submit the specs (NDA) as soon as I'm done with the current project. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] xc3028 tuner development status?
On 11/13/07, aldebaran [EMAIL PROTECTED] wrote: Hi! I noticed that a few commits concerning tuner xc3028 have started to be done in the mercurial tree. Is the support for this tuner already usable (at least for testing purposes)? One month ago I was told in this mailing list that you were still working on the firmware part but apart from that the work had already been done. Any news? I own an HP/Hauppauge WinTv885 mod 77001 with cx23885 and xc3028 chipsets. The xc3028 is implemented for several cx88 and saa7134 devices on mcentral.de for analogue TV, radio and DVB-T. the installation is just the same for the cx23885 devices: http://mcentral.de/wiki/index.php/Em2880#Installation Markus I'm looking forward to this chipset being supported and wish you all a good work (on it)! ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- http://www.couchsurfing.com/people/mrec ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] xc3028 tuner development status?
On 11/13/07, James Klaas [EMAIL PROTECTED] wrote: On 11/13/07, Markus Rechberger [EMAIL PROTECTED] wrote: On 11/13/07, aldebaran [EMAIL PROTECTED] wrote: Hi! I noticed that a few commits concerning tuner xc3028 have started to be done in the mercurial tree. Is the support for this tuner already usable (at least for testing purposes)? One month ago I was told in this mailing list that you were still working on the firmware part but apart from that the work had already been done. Any news? I own an HP/Hauppauge WinTv885 mod 77001 with cx23885 and xc3028 chipsets. The xc3028 is implemented for several cx88 and saa7134 devices on mcentral.de for analogue TV, radio and DVB-T. How well does this get along with the rest of the linux-dvb/video4linux drivers? I've found in the past that I cannot run both the mecentral.de drivers with the v4l/linux-dvb drivers, so I'm limited to using one or the other and I have stuff that I have to run under the v4l drivers. what are you missing? Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] MSI DigiVOX mini II v2.0
On 11/10/07, pat [EMAIL PROTECTED] wrote: Hello, I've searched for information about *subject* and found that there's not a driver for it. Is it true or did I missed something? I'm also a bit confused by the product naming of those DigiVox mini devices, can you post the output of usbview (you can usually copy the content by selecting the content and pushing the middle mousebutton (or in case of 2 button mice the left and the right mousebutton at the same time)). regards, Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Help. VIDIOC_S_FMT
Hello Kevin, On 11/8/07, kevin liu [EMAIL PROTECTED] wrote: Dear everyone: I wonder why v4l2 driver cancel all the urbs in VIDIOC_S_FMT and then reinit all the urbs to submit. VIDIOC_S_FMT only negotiate frame format with application like mplayer and has nothing to do with our v4l2 driver. there are several ways how you can deal with that, one way would be that you set up the framebuffers again for a different framesize using VIDIOC_S_FMT. While doing that setup the mode needs to be switched on the device depending on the device. When doing so you might bring it into an unstable state if you just change it while the isoc or bulk transfers are still running in the background. http://www.thedirks.org/v4l2/v4l2dev.htm The size of the buffers often depends on the format of the data. For example, the size of capture buffers is determined by the capture image format set by the VIDIOC_S_FMT ioctl. Hope this clears up your questions, if not let me know. And in my driver I follow the way most drivers have taken, but when I use usb_submit_urb() in VIDIOC_S_FMT to submit all the urbs successfully reinited, my Ubuntu crashes. Caps and Scroll flash during my Ubuntu crashes. I can't get any value message from my syslog. Could somebody help me with this issue? Thank you in advance! you very likely have a bad pointer in your driver, if you can publish the code somewhere someone could have a look. regards, Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-S2 API vs. HVR4000: When?
On 11/2/07, Markus Rechberger [EMAIL PROTECTED] wrote: On 11/1/07, Nico Sabbi [EMAIL PROTECTED] wrote: Il Thursday 01 November 2007 20:36:36 Steven Toth ha scritto: Ian Bonham wrote: Steve, Does this mean you will be working on an alternative to MultiProto? As an HVR4000 user I am following this thread closely as you might imagine. Ian Most likely yes. - Steve I really hope there won't be too many ( 1 ) APIs around: right now I'd be very embarassed regarding the API choose API to extend dvbstream and mplayer... I wonder many people are around blindly overall within the whole linuxtv project. Community should mean that people support other ones. Either visible on the Mailinglist uppon valid topics or providing sourcecode. What I've seen here is just forcing and pushing developers who don't agree with a small amount of people (since most others are independent and almost noone is involved with specific topics which are covered by individuals). Sooner or later this will draw back since the freedom is gone that way. Ah well I just read what's going on with Mandriva at the moment this makes me thinking about linuxtv again. While this crowd is playing a shitty game against each other, in Windows _everything's_ available. Now planing to replace around 17.000 copies of Linux with Windows at one side seriously has a positive impact of supported hardware at least. Ah well continue to play against each other. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-S2 API vs. HVR4000: When?
On 11/1/07, Nico Sabbi [EMAIL PROTECTED] wrote: Il Thursday 01 November 2007 20:36:36 Steven Toth ha scritto: Ian Bonham wrote: Steve, Does this mean you will be working on an alternative to MultiProto? As an HVR4000 user I am following this thread closely as you might imagine. Ian Most likely yes. - Steve I really hope there won't be too many ( 1 ) APIs around: right now I'd be very embarassed regarding the API choose API to extend dvbstream and mplayer... I wonder many people are around blindly overall within the whole linuxtv project. Community should mean that people support other ones. Either visible on the Mailinglist uppon valid topics or providing sourcecode. What I've seen here is just forcing and pushing developers who don't agree with a small amount of people (since most others are independent and almost noone is involved with specific topics which are covered by individuals). Sooner or later this will draw back since the freedom is gone that way. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [RFC] merged tree with newer patch series
On 10/30/07, Mauro Carvalho Chehab [EMAIL PROTECTED] wrote: Looking at tuner-xc2028.c, there seem to be some issues: a) priv-count is initialized to zero by the first user. This would result in priv either being freed prematurely or never freed at all. b) If priv is freed, it doesn't seem to be removed from the global xc2028_list list, meaning that this list is left containing dangling pointers that will be followed the next time xc2028_attach is called. Of course, unless there's more than one user of the same tuner, these would mostly cancel each other, leaving nothing but a slight memory leak. Thanks for the finding, Aidan! I've wrote a patch fixing it. I've already merged all the patch series, including the fix, at v4l-dvb. A good news is that I had some time to make HVR-950 (Analog part) to work with tuner-xc2028. I don't like the idea of using a reverse engineered xc2028 driver with the em28xx driver. * any reversed xc2028/3028 driver will not work properly for all countries (this includes my current driver which is available on mcentral.de) * as for the chip reset which is slightly different between certain firmware versions having that part reversed is not good either (eg. power consumption might have a negative impact - as it's the case at the moment). * radio support is far away from the xc2028 for many devices with such a driver (especially because of the firmware - driver hw/API) Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] XC5000/XC3028 tuner dvb support?
On 10/24/07, CityK [EMAIL PROTECTED] wrote: Steven Toth wrote: Chaogui Zhang wrote: Hi, everyone, I bought a Pinnacle PCTV HD 800i card recently and I am trying to add support for the card. It has the following chips on board: 1. CX23883 (supported already) 2. Samsung S5H1409 (supported already) 3. Cirrus 5340 ADC (not seen on the I2C bus) 4. ATMEL eeprom (forgot the part no., but probably not needed anyway) 5. Xceive XC5000 or XC3028 tuner. (Not visible, mentioned in the windows driver inf file.) Great! Take some decent PCB and silicon pictures and make them available via a website so we can all see the board. :) A website?? See, the correct answer should be the LinuxTV wiki but it doesn't matter, as this has already been done: http://www.linuxtv.org/wiki/index.php/Pinnacle_PCTV_HD_Card_%28800i%29 And speaking of things that have already been done, there already was a discussion on this card just a FEW DAYS AGO. See: http://www.linuxtv.org/pipermail/linux-dvb/2007-October/021380.html since Marcus has taken his toys and gone home so to speak if anything important is missing there let me know. several repositories have been made available before I went for a trip to sweden. Markus The windows inf file refers to Xceive XC5000 as the tuner in the *comment*, but there is NO mentioning of it anywhere else, while XC3028 is referenced a few more times (firmware, tuner type comment etc). I am pasting the relevant parts of the inf file below. Based on the windows driver information, is it safe to say that it may contain the XC5000 hardware, Yes, it is the XC5000 -- hence the overall ability of the card to support 256-QAM, as the XC3028 no can provide such (XC3028 can serve up 64-QAM source to the demod, but not 256-QAM). It is possible that Pinnacle also developed a similar card based on the XC3028 -- which would make it, by virtue of component constitution, similar to some other cards on the market (like KWorld ATSC 120, Geniatech X8000a, DViCO F5 nano PCI, maybe others..) -- and hence the presence of the XC3028 stuff in the .inf file, but has only released the XC5000 based board instead. I also noticed that on the i2c bus, it seems like the tuner is at 0x64 (there are only 3 visible addresses: 0x19 (s5h1409), 0x50 (eeprom), and 0x64). However, the windows inf file refers to TunerI2CAddress at 0xC2 (which corresponds to 0x61 == (0xC21)). I am puzzled by the discrepancy here I'd hazard a guess that the info in the inf only applies to a XC3028 based board, and not a XC5000 based board. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- http://www.couchsurfing.com/people/mrec ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] XC5000/XC3028 tuner dvb support? (an apology)
Hi James, On 10/24/07, James Klaas [EMAIL PROTECTED] wrote: I apologize, Markus, for making that rather rude comment. But, from a user's perspective the split between you and the rest of the v4l/dvb community is extrordinarily frustrating and my comment reflects that. I think both sides are responsible for the split to varying degrees. Your work has been invaluable to many people including myself, but I think pulling your code down so abruptly has caused a pretty big loss in goodwill and respect, even from some of your supporters. I have also become a little uneasy with some aspects of this split. It appears to my untrained eye, Markus, that you still depend quite a bit on the dvb/v4l community to provide a working structure for your code and for users to provide information on various hardware. This is not to belittle your amazing work, but it seems odd that (it appears) you depend so much on the community you've so roundly criticised. In all, it wouldn't be so frustrating for the users who depend on both projects if they got along in the kernel at the same time. Obviously, I'm not sure this is practicable, or even possible, but that would alleviate some of the tension. I see technical limitations for several parts that's why I'm continuing with the BSD project which aims at compatibility with the linux project in the end. I really need the time which I spent with noway discussions previously for other (nonlinux) things, so I'll just do whatever I promised some people and the rest I don't mind anymore. There are business interests behind what I need to finish, if the community wants to finish hacked alternative drivers they should do so. Markus James On 10/24/07, Markus Rechberger [EMAIL PROTECTED] wrote: since Marcus has taken his toys and gone home so to speak if anything important is missing there let me know. several repositories have been made available before I went for a trip to sweden. Markus -- http://www.couchsurfing.com/people/mrec -- http://www.couchsurfing.com/people/mrec ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] XC5000/XC3028 tuner dvb support?
On 10/23/07, Chaogui Zhang [EMAIL PROTECTED] wrote: Hi, everyone, I bought a Pinnacle PCTV HD 800i card recently and I am trying to add support for the card. It has the following chips on board: 1. CX23883 (supported already) 2. Samsung S5H1409 (supported already) 3. Cirrus 5340 ADC (not seen on the I2C bus) 4. ATMEL eeprom (forgot the part no., but probably not needed anyway) 5. Xceive XC5000 or XC3028 tuner. (Not visible, mentioned in the windows driver inf file.) I can provide the xc5000 driver which I'm using with my latest devices here. It directly includes the firmware. Markus The windows inf file refers to Xceive XC5000 as the tuner in the *comment*, but there is NO mentioning of it anywhere else, while XC3028 is referenced a few more times (firmware, tuner type comment etc). I am pasting the relevant parts of the inf file below. I searched the archive and noticed that Steven Toth mentioned in August about writing a driver for XC5000. At the same time, there is an existing xc3028.c file in the v4l-dvb tree (which probably needs some work before it can be used for this card, since it depends on em28xx as mentioned in the comment of that file). Based on the windows driver information, is it safe to say that it may contain the XC5000 hardware, but that is also backward-compatible with XC3028? I also noticed that on the i2c bus, it seems like the tuner is at 0x64 (there are only 3 visible addresses: 0x19 (s5h1409), 0x50 (eeprom), and 0x64). However, the windows inf file refers to TunerI2CAddress at 0xC2 (which corresponds to 0x61 == (0xC21)). I am puzzled by the discrepancy here. If necessary, I can post the i2cdump result from the eeprom and tuner later when I get home. BTW, I have patched the tree to the point that S-Video and composite input works without any problem. Of course, the missing tuner piece prevents analog/dvb from functioning. Thanks for any help! -PCTV800i.inf- [Pinnacle.NTamd64] ;--- ; PG583Q Hybrid ATSC/Global TV Tuner Card , Analog TV/DVB-T using SAMSUNG s5h1409 demod with XCevie XC5000 tuner ;--- %PCTV800i.PG583%=OmniTV.XcevieSamsung, %PCI\VEN_14F1DEV_8800SUBSYS_005111BD %PCTV800i.Audio.null%=NullSection, %PCI\VEN_14F1DEV_8801SUBSYS_005111BD %PCTV800i.TS.null%=NullSection, %PCI\VEN_14F1DEV_8802SUBSYS_005111BD [Pinnacle] ;--- ; PG583Q Hybrid ATSC/Global TV Tuner Card , Analog TV/DVB-T using SAMSUNG s5h1409 demod with XCevie XC5000 tuner ;--- %PCTV800i.PG583%=OmniTV.XcevieSamsung, %PCI\VEN_14F1DEV_8800SUBSYS_005111BD %PCTV800i.Audio.null%=NullSection, %PCI\VEN_14F1DEV_8801SUBSYS_005111BD %PCTV800i.TS.null%=NullSection, %PCI\VEN_14F1DEV_8802SUBSYS_005111BD ... [OmniTV.XcevieSamsung.NT] Include=ks.inf, kscaptur.inf, ksfilter.inf, wdmaudio.inf, bda.inf Needs= KS.Registration,KSCAPTUR.Registration.NT,MSPCLOCK.Installation,WDMAUDIO.Registration,BDA.Registration,bda.Installation.NT AddReg= AvSim.AddReg,XcevieSamsung.AddReg,XBAR.AddReg,CXTS.AddReg CopyFiles= AvSim.CopyDrivers,DSFilters.CopyFiles,Xc3028Rom.CopyFile RegisterDlls=DSFilters.RegDLL ... [XcevieSamsung.AddReg] HKR,DriverData,TunerType,0x00010001, 0x1A, 0x00, 0x00, 0x00 HKR,DriverData,DemodType,0x00010001, 0x00, 0x00, 0x00, 0x00 HKR,DriverData,TunerI2CAddress,0x00010001, 0xC2, 0x00, 0x00, 0x00 HKR,DriverData,Tuner2IFAddress,0x00010001, 0x86, 0x00, 0x00, 0x00 HKR,DriverData,TunerModel,0x00010001, 0xA8,0x00,0x00,0x00 HKR,DriverData,UseFreqOffsetDVBT,0x00010001, 0x00, 0x00, 0x00, 0x00 ; Tuner Type: ; 1A = XCeive 3028 ; TunerModel: ; 0xA8(168) = XCevie 3028 + Samsung S5h1409 ; 0x9e(158) = MT3121 + Samsung S5h1409 ;NEC standard HKR,DriverData,IRStandard,0x00010001, 0x01, 0x00, 0x00, 0x00 HKR,DriverData,VideoStandard,0x00010001, 0x00,0x01,0x00,0x00 HKR,DriverData,ColorKillEnable,0x00010001, 0x00,0x00,0x00,0x00 ; Country code is Unite State = 0x1 HKR,DriverData,WWAudioCountryCode,0x00010001, 0x01,0x00,0x00,0x00 HKR,DriverData,WWAudioLineInToI2sIn,0x00010001, 0x01,0x00,0x00,0x00 HKR,DriverData,BlackbirdType,0x00010001, 0x00,0x00,0x00,0x00 ; these registry keys for TS filter HKR,DriverData,dwTS_GEN_CNTRL,0x00010001, 0x04,0x00,0x00,0x00 HKR,DriverData,dwIsTSStream,0x00010001, 0x00,0x00,0x00,0x00 HKR,DriverData,dwTP_PACKET_SIZE,0x00010001, 0xBC,0x00,0x00,0x00 ... -- Chaogui Zhang ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- http://www.couchsurfing.com/people/mrec ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] dvb driver revisions
On 10/11/07, Markus Rechberger [EMAIL PROTECTED] wrote: Hi, On 10/11/07, Halim Sahin [EMAIL PROTECTED] wrote: hi, how can I checkout an older version of the hg stuff? Do I need a revision number or is it possible to give a date? Please give me an example. Thanks $ hg clone http://linuxtv.org/hg/v4l-dvb of course you have to jump into the v4l-dvb directory. $ cd v4l-dvb $ hg log changeset: 6316:33244fbdcd5f tag: tip user:Trent Piepho [EMAIL PROTECTED] date:Wed Oct 10 01:37:43 2007 -0700 summary: Change list_for_each+list_entry to list_for_each_entry changeset: 6315:991e9a4acbb4 user:Trent Piepho [EMAIL PROTECTED] date:Wed Oct 10 01:37:42 2007 -0700 summary: pvrusb2: Change list_for_each+list_entry to list_for_each_entry etc. $ hg up 6315 # for jumping back to that specific revision. Markus -- Markus Rechberger ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Fwd: [PATCH] Aver TV Hybrid A16D
Hi, Miroslav Bobal submitted a patch to get DVB work with his AverTV Hybrid A16D and the repository which is available on mcentral.de. http://mcentral.de/hg/~mrec/v4l-dvb-experimental/ As for radio I can give you the hint to try the pinnacle firmware... http://mcentral.de/firmware/firmware_pinnacle.tgz I used the radio tool (which is part of xawtv .. and uses v4l1 commands?) for testing the radio functionality. thanks alot for the contribution, Markus -- Forwarded message -- From: Miroslav Bobal [EMAIL PROTECTED] Date: Tue, 9 Oct 2007 16:06:16 +0200 Subject: [PATCH] Aver TV Hybrid A16D To: Markus Rechberger [EMAIL PROTECTED] Hello, I make some changes to Aver TV Hybrid A16D work. Analog, Digital and IR works. Radio doesn't work. Dmesg error: tuner 2-0061: tuner has no way to set radio frequency (used head revision) cheers Miroslav Bobal ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Future of Multiproto
Manu Abraham wrote: Steven, Steven Toth wrote: Johannes / Manu, I'm actually pretty sad about the whole situation. The HVR4000 has been done for over a year, probably much more. Support for this product in the main v4l-dvb repository is stuck behind the multiproto tree, and that's going nowhere. People have been using the HVR4000 and multiproto patches with success, although more widespread thorough testing is always a good thing. Manu, First of all, as a backgrounder, i am no more interested in the politics that which Johannes is fostering as of late. (Removed CC) That said, i do respect Johannes for what he had done in the past, but i am against his policies, ideas and concepts that he has been fostering and cherishing as of late. I will explain why, too. I've pinged and pushed you on a number of occasions to publish an updated tree via hg on linuxtv and for various political reasons this has never happened. I think you made yourself pretty clear via private communications, and via the public DVB API thread.Without re-visiting (or-reigniting) those flames and bad feelings, I think it's clear to me that the future of multiproto being maintained and managed in the linuxtv/hg tree is not going to happen. (Addressing your question on the DVB API thread) The DVB API thread is in the light that the broken things in the API should be fixed. (Some people like to state that those aren't broken) Well, i am not going to use the broken stuff and hence the thread. Now you might be interested to do that, because the cx24116 blindly does that, but as i can see the issues, i am not blindly following what someone states. (Addressing your comment on tree location) when you mean linuxtv/hg tree, there is just only one tree which is called thus http://linuxtv.org/hg/v4l-dvb/ Do you have write access to the repository ? Now, only one single person has access to this tree, so obviously you can't develop in that tree. What you mean to say linuxtv.org/hg, i believe you mean individual developer repositories such as ~stoth/ ~manu/ What difference does it make, if the tree is there elsewhere ? (what advantage does it get you other than you are allowed to have some space for storage at linuxtv.org) In fact having a tree elsewhere makes it easy for tree maintenance. Ok, that said you might suggest, still one should put all their code at linuxtv.org, for that community warmth. This can happen of course, but i have my requests also if that needs to be done, the current workflow needs to be changed. Please feel free to address that thread which exists on the v4l-dvb-maintainer ML, as it was discussed earlier as what is wrong with the workflow as it is, in case you would like to address them. (Basically i don't like those people who steal credits and or people wanking into code that which others do maintain and thus making it broken. Johannes earlier said slap such people, but these days he states that they do for your good. I don't see how that is good except that it brings me in larger headaches. True though it is good for person who is watching the spectacular events) Currently, there is no workflow defined. Right now the concept is, i take your code and i do whatever i want with it. I don't agree to that workflow. This is NOT the OSS philosophy I've offered to help by performing the merge, organizing testing and pushing the work to conclusion (final merge), but that doesn't appease you. I'm not writing this email from spite, I'm simply trying to help you, me and the rest of the community. But, either you have different plans for the patches or you'll give me the OK - here in this thread - to take your patches and begin working on them freely via linuxtv.org/hg (On your statement of a merge) A merge should happen when things are considered stable. At least as far as i can say, it needs some more efforts from my side. I am not for merging something that which needs more work and tests (Anyone who thinks different is in fact creating politics, why ? Generally we have the idea that release when done an not before is the general OSS philosophy. Now why is some people like Johannes creating a politics, whenever he get's the chance ?) First fix your code, then you merge, this is on a general note. if you see such merges/attitudes have only led to a rise of the largely broken code and or drivers. This attitude has to change, merge should happen on complete stuff. (On your statement, of me giving you Ok to do whatever you feel like) This is exactly what anyone would detest. This brings in just broken code/concepts only. Also this does mean that i have stopped working on it and thrown it away. Why is it that you think thus, i don't understand. Unless this happens, I repeat, I cannot see a future where the multiproto patches will be merged
[linux-dvb] Fwd: making af9005 on ubuntu gutsy with 2.6.22-12-generic
-- Forwarded message -- From: Joachim Neu [EMAIL PROTECTED] Date: Sat, 06 Oct 2007 11:01:23 +0200 Subject: making af9005 on ubuntu gutsy with 2.6.22-12-generic To: linux-dvb@linuxtv.org Cc: [EMAIL PROTECTED] -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi everybody, i tried to make the af9005 on ubuntu gutsy (comes with 2.6.22-12-generic) but i got an error in /af9005/v4l/dvb_net.c on line 186. In function 'dvb_net_eth_type_trans': error: 'struct sk_buff' has no member named 'mac' i fixed the problem by just commenting out this line. after that it worked! maybe someone can fix this inside the source? thank you, you're doing a great job! alpha1650 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHB07j7awBpSuN1JIRAqNiAJ9iwVp7xLuCP+1pQ/xAndozShi+AQCfS6EG 7PkKOeBYHysCEO24fxkB4uc= =1O9S -END PGP SIGNATURE- -- Markus Rechberger begin:vcard fn:Joachim Neu n:Neu;Joachim adr;quoted-printable:;;;M=C3=BCnchen;Bayern;;Deutschland email;internet:[EMAIL PROTECTED] x-mozilla-html:FALSE url:http://www.joachim-neu.de version:2.1 end:vcard ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] New card for http://www.bttv-gallery.de/
On 10/5/07, Aidan Thornton [EMAIL PROTECTED] wrote: On 10/5/07, David Campbell [EMAIL PROTECTED] wrote: The whole XP driver kit is at http://www.aaa.net.au/campbell/driver.zip but it may support other devices so unsure what bits are actually relevant: -rw-rw-r-- 1 dcampbel dcampbel 4697 2005-08-06 15:27 EMAUDIO.INF -rw-rw-r-- 1 dcampbel dcampbel 20736 2005-07-08 17:43 emAudio.sys -rw-rw-r-- 1 dcampbel dcampbel 48335 2005-11-14 20:29 EMBDA.INF -rw-rw-r-- 1 dcampbel dcampbel 209664 2005-11-14 20:30 emBDA.sys -rw-rw-r-- 1 dcampbel dcampbel 17152 2005-11-14 20:29 emOEM.sys (strings indicates it to be an MT2060 driver) -rw-rw-r-- 1 dcampbel dcampbel 32768 2005-11-14 20:29 emPRP.ax Interesting. The driver finds it but doesn't seem to recognise one of the i2c devices:em28xx #0: found i2c device @ 0x16 [???] That's the ZL10353. I think it's the analog code that's not detecting it; it's the digital part of the driver that handles this i2c device, and it doesn't auto-detect. Actually this unrecognised device shows itself at different i2c addresses different times you plug it in. See below for what I've seen. em28xx #0: found i2c device @ 0x26 [???] em28xx #0: found i2c device @ 0xa0 [eeprom] em28xx #0: found i2c device @ 0xc2 [tuner (analog)] em28xx #0: found i2c device @ 0x16 [???] em28xx #0: found i2c device @ 0xa0 [eeprom] em28xx #0: found i2c device @ 0xc2 [tuner (analog)] em28xx #0: found i2c device @ 0x32 [???] em28xx #0: found i2c device @ 0xa0 [eeprom] em28xx #0: found i2c device @ 0xc2 [tuner (analog)] I'm guessing it's probably bogus, then. it's not really bogus, toggled gpio values are capable of changing what you can see here. So either by reloading the driver or replugging the devices you can change the output. The dirtiest fallback for devicedetection is to recognize the device by those i2c addresses. If nothing works out the enduser has to fall back to the card module parameter - anyway I try to avoid that the user has to set up any module parameters.. it's just a pain if a user plugs in his device the first time and has to fiddle around with some settings for a device. Any better idea on devicedetection with same usbids is welcome. I find that if I do the following, the device gets registered, and it is saying something about an LG chip but I'm not familiar enough with the depths of the driver to know whether this output below is actually the driver detecting the tuner chipset, or something that the driver has been forced to believe. Can you comment? modprobe em28xx card=8 i2c_scan=1 device_mode=1 Table at 0x04, strings=0x226a, 0x, 0x tuner 1-0061: chip found @ 0xc2 (em28xx #0) attach inform (default): detected I2C address c2 tuner 0x61: Configuration acknowledged tuner 1-0061: type set to 37 (LG PAL (newer TAPC series)) em28xx #0: found i2c device @ 0x26 [???] em28xx #0: found i2c device @ 0xa0 [eeprom] em28xx #0: found i2c device @ 0xc2 [tuner (analog)] em28xx #0: V4L2 device registered as /dev/video0 em28xx #0: Found Pinnacle PCTV USB 2 You're basically forcing the driver to assume that your tuner is that particular one. I'm guessing the LG tuner it's set to is a can tuner, which is far too big to be in a USB device. I'd suggest that Terratec Cinergy T XS (MT2060) or Pinnacle PCTV DVB-T would be a better choice. Yes, I also think so, although as mentioned the GPIO values might differ. but subsequently loading the em2880-dvb device doesn't work I don't know whether I'm doing the right thing here by attempting to load this: em2880-dvb.c: DVB Init em2880-dvb.c: unsupported device em2880-dvb.c: failed initializing zl10353 DVB-T demodulator em2880-dvb.c: retrying with mt352 DVB-T demodulator FIXME:em28xx_i2c_send_bytes(1e): write failed: === 7f mt352_read_register: readreg error (reg=127, ret==-19) em2880-dvb.c: no luck with mt352 demodulator, not attaching em2880-dvb em2880-dvb.c: DVB-T demodulator not reachable, did you try modprobe em28xx device_mode=1 Em28xx: Initialized (Em2880 DVB Extension) extension That's because you're telling the driver that your device is one that doesn't support DVB-T; I'm not sure why it even tries to load. (The fact that it doesn't do the right GPIO-twiddling doesn't help either.) Aidan Markus Rechberger wrote: This device requires a gpio setup for enabling the zl10353 on the i2c bus. Does your driver already do that for some devices? How difficult is it going to be to convince it for this one? It's not that hard (in theory); it just requires booting into Windows and running a USB sniffer to find out what the Windows driver sends. It's just that it's different for different devices. I'm sure Markus will tell you more. There are 2 wiki sites available: http://mcentral.de/wiki/index.php/USBVideo http
Re: [linux-dvb] RE : Frontend device disappearing with HauppaugeWinTVNOVA-T-500
On 9/21/07, Thierry Lelegard [EMAIL PROTECTED] wrote: Hello, Unfortunately, after just one single day, the problem occured again. Note that this is not 24 hours of continuous TV watching. This is a test lab and I stop and start the tests quite frequently. From dmesg: usb 8-1: USB disconnect, address 2 After the problem, the command 'lsusb' hangs. I forgot to mention that in my previous report. A 'kill -9' of the lsusb process does not remove the process. Its state is 'D' using ps (must hang somewhere in the kernel). I cannot unload the DVB modules. Under v4l source tree: $ make unload scripts/rmmod.pl unload found 209 modules /sbin/rmmod dib3000mc ERROR: Module dib3000mc is in use /sbin/rmmod dibx000_common ERROR: Module dibx000_common is in use by dib3000mc /sbin/rmmod mt2060 ERROR: Module mt2060 is in use $ I found no other solution than rebooting the system again ! Do you see any further information with dmesg? Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiB0700 firmware - next try
On 9/22/07, David Harvey [EMAIL PROTECTED] wrote: Thanks Soeren, I'm just working out how I can free up my single epia pci slot (currently running my sata card) so I can persue the pci dvb solution... Is there anything recommended with solid support? (as I mistakenly thought nova-t in all its incarnations worked so don't want to make the same mistake twice!) I've been messing about with my freecom and nova-t usb sticks for so long now that I can't wait to stop tinkering (which is something I thought I'd never say! :) ) If you're looking for a stable hardware usb solution I can say that solutions from Empiatech just work fine in most cases :-) (the exceptions will be cleared up within the next few months) http://mcentral.de/wiki/index.php/Em2880 mailinglist: http://mcentral.de/pipermail/em28xx/ (just avoid to buy the devices which are in question there, although _all_ empia devices will experience a great improvement in future) Beside just writing about that. Empia has customers who are interested in Linux support and Empia itself is interested in getting those customers satisfied. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB API update
I cannot resist ;-) since I stumbled over the RCU documentation I seriously would like to invite several linuxtv people (especially Steven Stoth, Mauro Chehab, Michael Krufky, Manu Abraham last but not least myself [but I read already it] ;-) to read about RCU... RCU is a synchronization mechanism that was added to the Linux kernel during the 2.5 development effort that is optimized for read-mostly situations. Although RCU is actually quite simple once you understand it, getting there can sometimes be a challenge. Part of the problem is that most of the past descriptions of RCU have been written with the mistaken assumption that there is one true way to describe RCU. Instead, the experience has been that different people must take different paths to arrive at an understanding of RCU. This document provides several different paths, as follows http://www.rdrop.com/users/paulmck/RCU/whatisRCU.html these few lines exactly cover a similar situation (but probably worse) about linuxtv which covers analogue and digital TV. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB API update
On 9/20/07, Steven Toth [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 9/19/07, hermann pitton [EMAIL PROTECTED] wrote: Am Dienstag, den 18.09.2007, 19:07 +0400 schrieb Manu Abraham: Mauro Carvalho Chehab wrote: Em Ter, 2007-09-18 às 18:33 +0400, Manu Abraham escreveu: Mauro Carvalho Chehab wrote: I'm just interested on see things moving forward. Please stop with your flame wars. If you are not interested on serious discussions, you shouldn't have started the thread. (bla, bla, bla) If you can't technically argue about DVB API, but just want to play politics, you don't deserve any attention on that thread. Missing context: You don't have to try for that. See the userspace thread as well, where you were misappropriating credits. So my case was not an isolated case. My, my, you and Markus would have exactly _nothing_ without the prior work done by others. If you don't feel referenced enough by some lines from you currently, likely only by running on NDAs first, just make it clear and you get _your_ credit! there should be another thread called Ongoing internal flamewars and the first line of that mail should be idiots who cannot work together and disagree whenever it's possible. I completely agree. It's much easier to burn the barn down than to rebuild it, and we have a lot of arsonists in linuxtv. I don't think that there are any arsonists .. I think it's better for all parties to go their own way now since there's no agreement and the communication is still on a bad level between certain people. This will at least keep everything calm. A bit competition shouldn't hurt after all... As someone pointed out earlier if someone disagrees with something try to build your own way around it to not cross each other's way. It might not always be the best way but it keeps projects running since it's only about drivers only support for various devices count. As for projects which are not included in the kernel and for people who do not get along with Mauro, the code can be submitted to the LKML and Andrew, Greg, Linus or someone else can also pick up the sourcecode. People need to get over previous flame wars and get back to doing the one thing that brought them into the linuxtv community in the first place, community development. It always requires 2 and more people .. I don't think that someone will start a flamewar if there wouldn't be so many disagreements. Although it's not worth to send flame mails around in the end.. Anything else is a waste of everyones time and only demonstrates to the rest of the world how fragmented many of the linuxtv devs really are. maybe it's best to keep it more fragmented for a few years... a few people might stop their participation and newer people might join .. the only advice I'd give here is to accept what newer people do. Nobody here is perfect and some suggestions can be kept as suggestions without forcing them over someone if there's no serious technical reason about it... if people are willing to do something let them do.. Everyone should draw their mental line under their own personal hangups and move on. definitelly yes. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB API update
On 9/19/07, hermann pitton [EMAIL PROTECTED] wrote: Am Dienstag, den 18.09.2007, 19:07 +0400 schrieb Manu Abraham: Mauro Carvalho Chehab wrote: Em Ter, 2007-09-18 às 18:33 +0400, Manu Abraham escreveu: Mauro Carvalho Chehab wrote: I'm just interested on see things moving forward. Please stop with your flame wars. If you are not interested on serious discussions, you shouldn't have started the thread. (bla, bla, bla) If you can't technically argue about DVB API, but just want to play politics, you don't deserve any attention on that thread. Missing context: You don't have to try for that. See the userspace thread as well, where you were misappropriating credits. So my case was not an isolated case. My, my, you and Markus would have exactly _nothing_ without the prior work done by others. If you don't feel referenced enough by some lines from you currently, likely only by running on NDAs first, just make it clear and you get _your_ credit! there should be another thread called Ongoing internal flamewars and the first line of that mail should be idiots who cannot work together and disagree whenever it's possible. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] problems in em28xx-video.c
On 9/19/07, kevin liu [EMAIL PROTECTED] wrote:
Dear Markus:
In em28xx-video.c, when you design memory map function,
You used this state:
for(i=0; idev-num_frames; i++){
if(dev-frame[i].buf.m.offset PAGE_SHIFT == vma-pgoff)
break;
}
Why dev-frame[i].buf.m.offPAGE_SHIFT == vma-pgoff;
it's just a check if vma-pgoff is out of range or not
I see the mmap function implemented in Linux device driver3, it is like
this:
if(remap_pfn_range(vma, vma_start, vm-vm_pgoff, vma_size,
vma-vm_page_prot))
return -EAGAIN;
..
..
And where did the frame[i].buf come from?
/* frames */
struct em28xx_frame_t {
void *bufmem;
struct v4l2_buffer buf;
enum em28xx_frame_state state;
struct list_head frame;
unsigned long vma_use_count;
int top_field;
int fieldbytesused;
};
Could you please give me some explanation?
You hit the first part of the book which isn't uptodate anymore :-)
http://groups.google.de/group/linux.kernel/browse_thread/thread/d5cdcf4d9212178f/965817de9083403e?hl=delnk=stq=remap_pfn_range+vm_insert_pagernum=4#965817de9083403e
Markus
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] V4L Patches to add DVB support for AVerMedia E506
Hi all, Ed submitted a patch for adding the outstanding DVB support of the Avermedia E506 device. So now radio, DVB-T and Analog TV seems to be supported, it would be nice if you guys could test the functionality of that driver. http://mcentral.de/wiki/index.php/AverMedia_Cardbus_Hybrid_TV_FM_E506R So thanks go out to Vadim Dyadkin who went to Dresden with his device so that we could enable analogue TV and a few weeks after for meeting him again in Berlin and adding support for Radio, and finally Ed for DVB and improving Radio :-) Markus On 9/18/07, Ed G [EMAIL PROTECTED] wrote: Markus, I have attached a raw patch file as well as the output from hg export. I ran make commit which seems to cleanup whitespace and add extra changes to the export file. I used the patch file on your latest V4L-experimental tree and checked it all works. Let me know if you still have problems. Regards, Ed. - Original Message - From: Markus Rechberger [EMAIL PROTECTED] To: Ed G [EMAIL PROTECTED] Subject: Re: V4L Patches to add DVB support for AVerMedia E506 Date: Mon, 17 Sep 2007 14:22:46 +0200 Hi Ed, your patch doesn't apply against the latest v4l-dvb-experimental tree. Could you try to apply and test it against the latest tree? thanks alot for your work, I'm sure many users will love it :) Markus On 9/17/07, Ed G [EMAIL PROTECTED] wrote: Marcus Please find attached patches for your V4L-Experimental project. The patches work for me and also fix some problems with switching between TV and Radio. An outstanding issue is that at times the tuner takes a minute or two to properly lock-in to analogue channels. Please let me know if there is anything else you need to publish the patches. Keep up the good work. Regards, Ed. -- Markus Rechberger -- We've Got Your Name @ www.mail.com!!! Get a FREE E-mail Account Today - Choose From 100+ Domains -- Markus Rechberger ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Fwd: V4L Patches to add DVB support for AVerMedia E506
since the mail didn't seem to get through... -- Forwarded message -- From: mimo [EMAIL PROTECTED] Date: Wed, 19 Sep 2007 18:47:23 +0100 Subject: Re: V4L Patches to add DVB support for AVerMedia E506 To: Markus Rechberger [EMAIL PROTECTED] Cc: Ed G [EMAIL PROTECTED], linux-dvb@linuxtv.org, [EMAIL PROTECTED], German Gomez [EMAIL PROTECTED], [EMAIL PROTECTED], dimon-ltd [EMAIL PROTECTED], Carlo Cassinelli [EMAIL PROTECTED], Giovanni Lopedote [EMAIL PROTECTED], Virág János [EMAIL PROTECTED], Vadim Dyadkin [EMAIL PROTECTED] Hi all DVB-T works brilliantly. Thanks a lot to everybody for all your work! mimo On Tuesday 18 September 2007 17:36:48 Markus Rechberger wrote: Hi all, Ed submitted a patch for adding the outstanding DVB support of the Avermedia E506 device. So now radio, DVB-T and Analog TV seems to be supported, it would be nice if you guys could test the functionality of that driver. http://mcentral.de/wiki/index.php/AverMedia_Cardbus_Hybrid_TV_FM_E506R So thanks go out to Vadim Dyadkin who went to Dresden with his device so that we could enable analogue TV and a few weeks after for meeting him again in Berlin and adding support for Radio, and finally Ed for DVB and improving Radio :-) Markus On 9/18/07, Ed G [EMAIL PROTECTED] wrote: Markus, I have attached a raw patch file as well as the output from hg export. I ran make commit which seems to cleanup whitespace and add extra changes to the export file. I used the patch file on your latest V4L-experimental tree and checked it all works. Let me know if you still have problems. Regards, Ed. - Original Message - From: Markus Rechberger [EMAIL PROTECTED] To: Ed G [EMAIL PROTECTED] Subject: Re: V4L Patches to add DVB support for AVerMedia E506 Date: Mon, 17 Sep 2007 14:22:46 +0200 Hi Ed, your patch doesn't apply against the latest v4l-dvb-experimental tree. Could you try to apply and test it against the latest tree? thanks alot for your work, I'm sure many users will love it :) Markus On 9/17/07, Ed G [EMAIL PROTECTED] wrote: Marcus Please find attached patches for your V4L-Experimental project. The patches work for me and also fix some problems with switching between TV and Radio. An outstanding issue is that at times the tuner takes a minute or two to properly lock-in to analogue channels. Please let me know if there is anything else you need to publish the patches. Keep up the good work. Regards, Ed. -- Markus Rechberger -- We've Got Your Name @ www.mail.com!!! Get a FREE E-mail Account Today - Choose From 100+ Domains -- Markus Rechberger ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem when unplugging Cinergy T^2
Hi Tomi, On 9/18/07, Tomi Orava [EMAIL PROTECTED] wrote: Hi, with my Cinergy T^2 there is a problem when I unplug the device. Top shows that khubd uses 100% CPU. My system uses Kernel 2.6.21.1 + latest v4l-dvb modules from http://linuxtv.org/hg/v4l-dvb. With the original kernel modules there is no problem. How can I help to fix the problem? Unfortunately I don't have a fix for you, but in case you would be interested to try a modified version of that driver, here is the patch. The patch modifies the existing Cinergy T^2 driver to fit into dvb-usb framework, although it is very experimental in nature (seems to work quite ok, although no remote controller handling for now). if you need some inspiration for the remote control handling: http://mcentral.de/hg/~mrec/v4l-dvb-experimental/file/ecb561ab9a4d/linux/drivers/media/video/em28xx/em28xx-input.c this might be useful, although if you have some better ideas I'd be interested to improve that code as well :-) Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Userspace tuner
On 9/18/07, Jelle Foks [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 9/14/07, Alan Cox [EMAIL PROTECTED] wrote: On Fri, Sep 14, 2007 at 01:17:05AM +0200, Markus Rechberger wrote: what stops vendors of using the current existing code to achieve that goal. They could provide binary drivers with the existing API. If you feel lucky about the GPL What stops companies to intercept the ioctl calls and overriding some I2C commands? The GPL - derivative work is the boundary not code linkage. Possibly a userspace tuner hack would probably fit this too. Especially if a specific vendor is producing both bits together and trying to claim they are independant. How about proprietary video formats, would you also place the decoding algorithms in kernel just to force companies to release their code for it? No, I would assume they'd provide a proprietary conversion library that no nobody would use (just like their hw). We keep format conversion firmly seperated from hardware I/O processing. In general there are known formats available, the drawback is that every TV application deals with it in a non-unified way at the moment, meaning alot code duplication in userspace since there's no library available at the moment which does the videoconversion from one to another format. Such a library is beeing developed at the moment which gets plugged infront of accessing the devicenodes. IMHO... The reason why there is no single 'format conversion library' that everybody uses is because of the large differences between requirements for such a thing. The line between 'format conversion' and things such as a video codec, or image processing is very vague. For example: Some apps just want compressed video format output. Would video compression be part of such a 'format conversion library'? If so, then which compressed video formats? Proprietary ones too? If not all formats that exist are supported, it would not be complete for some or many apps, and maybe not even useful at all (because integrating any necessary pixel-format conversion into the compression routines may be more efficient than making multiple passes over the data with separate libraries). Will the library include resizing? If so, which resampling algorithms? Then how about rotation? Then maybe geometrical mapping (games could want that)? Will the library be able to adjust brightness/contrast/saturation in software? If so, then what about noise filtering (which algorithms?), etc... perhaps the library should go all the way, bind to port 80 and serve-up a live video stream 'youtube-style'? ok, now that would definitely go too far... The question is: Where exactly to put the boundary? good statement, the absolute goal should be that enduser applications can handle videostreams as easy as possible. This is currently not given. For example I have devices which work with ekiga, and some devices which don't work with ekiga. Why so? Ekiga already uses a rather big library for handling videodevices. Another point is why doesn't tvtime support digital audio? People have to run sox in the background to get any sound piped from the corresponding dsp node to the soundcard, and also this is no general way. So first people have to look up what the correct audio node of their TV device is... (there are small scripts available which lets the users select) But I also think this should happen automatically. There are many devices out there which don't even include all ioctl calls which are documented in the specs. And since sometimes the API needs to be updated a library could handle this in a better way. I see the whole v4l-dvb project as half way done at the moment because of the unflexibility of the whole system. My point is that format conversion is not a video capture driver issue. Sure, it is convenient for apps to be able to use standard libraries that perform certain functions with optimized code, etc, but for the purpose of capturing video (media) it's not always necessary to convert the output into something different before the data is useful for an app. this is just a thought, I think a pluggable mechanism would be nice for that. The library could query the device about it's capabilities and if it returns a non standard videoformat just add a mechanism for loading the corresponding videocodec if available. Certain format conversions can be done very efficiently inside video cards, for example, and an app may prefer to use that. If a video card has such functionality, access to it should be part of its driver. yes, this would always be the optimal way Applications needing format conversions would benefit tremendously from a good, powerful, flexible, efficient, etc, library that removes the necessity for each application to choose between using a video-card accelerator, or MMX code, or SSE code, or another method to do the work. Maybe it should allow applications
Re: [linux-dvb] DVB API update
Hi, On 9/18/07, Manu Abraham [EMAIL PROTECTED] wrote: Felix Domke wrote: Manu Abraham wrote: I'm not against mmap, I'm against using development resources for implementing it. I can't see the big show-stopper in this issue. So, seriously: Is there anybody here who *needs* this, based on his own experience? If yes, I'll might change my mind. I think it would be nice to have it. Yes, it would be nice. But do you NEED it? Is it a show-stopper for you? Do you have a scenario which doesn't work because of THIS? It is definitely not a show stopper, but as i said: It is a nice feature to be incorporated in to. No, not throwing away anything, see my reply to Rainer. The newer features will not be available with the older apps, that's all. You can use the same drivers too. Backward compatibility is achieved by keeping an additional set of ioctl's, so the old stuff will work as it is. Will older hardware drivers be compatible with a new dvb-core (more than maybe changing some identifiers)? As it is, without any change. I think Johannes did the great job of confusing people. Don't get personal. Unstable driver APIs are a huge issue for non-mainstream hardware. Let's do our best to keep devices without active maintainers supported. V4 would have killed them, so i only want to be sure that your api updates won't. My approach is to add a DMX_ADD_PID ioctl, similar to DMX_SET_FILTER. [...] This sounds fine to me. Great. * The current API doesn't allow you to do simple TS filters. Again, in http://www.spinics.net/lists/linux-dvb/msg09258.html I came up with my solution, however people noted that this might break FF cards due. This can probably be avoided by using a better value for DMX_TAP_TS. Note that the dvb-core implementation is trivial, as hardware drivers are already supporting TS filtering. It's just not exposed to userspace. Mostly USB devices, afaik. Any other devices that you would like to mention ? I don't understand this sentence. Any device not ignoring (a not-set) TS_PAYLOAD_ONLY-flag should be compatible. I was thinking what all hardware would be having builtin hardware filters. * The current API doesn't allow you to tune into -S2 transponders. We have solved this one already, drivers also exists, people watch S2 What i pushed out last, is out here: http://jusst.de/manu/04-Jul-07/stb0899.tar.bz2 ok. I don't like any part of the API (FE_SET_FRONTEND) to be obsoleted, but ok, I can live with it. Please specify a bit more explictely which parts of the API are mutually exclusive (FE_SET_FRONTEND vs. DVBFE_SET_PARAMS). why are some IOCTLs called DVBFE_ and others FE_? BTW, this doesn't hold my backward compatibility request - if an application wants to tune a dvb-s transponder with the new api (DVBFE_SET_PARAMS), it won't run against an old api (which only implements FE_SET_FRONTEND, but could technically tune). But it seems that nobody else cares about this. The other option what i can think is to do a version check in the new app, to selectively call the relevant ioctl. Why don't abstract the dvb layer from enduser applications and put a general library infront which does that version check and tries to keep things consistend to the end applications? The enduser applications would have to implement that API one time but it would help to keep unnecessary changes away from those applications and even allow to clean up things lateron without breaking all the applications... it's just a thought though.. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB API update
On 9/18/07, Manu Abraham [EMAIL PROTECTED] wrote: Markus Rechberger wrote: Hi, Why don't abstract the dvb layer from enduser applications and put a general library infront which does that version check and tries to keep things consistend to the end applications? It is a nice idea, yes. Two things, looking at http://linuxtv.org/hg/dvb-apps/file/4bca5d49c9bd/lib/libdvbapi/dvbfe.c * This idea of using multiple API 's was thought (It is effective , yes) You can use multiple API's in there * The down side is that user applications need to use this library Someone could ask, why the hell should we use your library. Well, that causes the headaches. people who use alsa also use the provided alsa API, it makes alot sense to stop applications to directly access those nodes. libdvbapi seems to be the right way to start over with. The enduser applications would have to implement that API one time but it would help to keep unnecessary changes away from those applications and even allow to clean up things lateron without breaking all the applications... it's just a thought though.. Yes, that's how it would work in the ideal case, i doubt whether we can force applications to use the library. I would spend some time to implement such a library in enduser applications. Although first I need to get my devices work and into the kernel and fix some nasty bugs in my driver... Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB API update
On 9/18/07, Manu Abraham [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 9/18/07, Manu Abraham [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 9/18/07, Manu Abraham [EMAIL PROTECTED] wrote: Markus Rechberger wrote: Hi, Why don't abstract the dvb layer from enduser applications and put a general library infront which does that version check and tries to keep things consistend to the end applications? It is a nice idea, yes. Two things, looking at http://linuxtv.org/hg/dvb-apps/file/4bca5d49c9bd/lib/libdvbapi/dvbfe.c * This idea of using multiple API 's was thought (It is effective , yes) You can use multiple API's in there * The down side is that user applications need to use this library Someone could ask, why the hell should we use your library. Well, that causes the headaches. people who use alsa also use the provided alsa API, it makes alot sense to stop applications to directly access those nodes. libdvbapi seems to be the right way to start over with. If one can get applications to get going with it, it would be a start. Someone jokingly said a name for it ALDA. But many times, you can't force things to users. I just looked at it again, is there any official documentation available? There's nothing such as a libdvbapi.doc/txt. But the important parts were documented in the headers.*.h files I would say that's the reason why almost noone uses it. It would deserve some more documentation on linuxtv.org Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB API update
On 9/18/07, Manu Abraham [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 9/18/07, Manu Abraham [EMAIL PROTECTED] wrote: Markus Rechberger wrote: Hi, Why don't abstract the dvb layer from enduser applications and put a general library infront which does that version check and tries to keep things consistend to the end applications? It is a nice idea, yes. Two things, looking at http://linuxtv.org/hg/dvb-apps/file/4bca5d49c9bd/lib/libdvbapi/dvbfe.c * This idea of using multiple API 's was thought (It is effective , yes) You can use multiple API's in there * The down side is that user applications need to use this library Someone could ask, why the hell should we use your library. Well, that causes the headaches. people who use alsa also use the provided alsa API, it makes alot sense to stop applications to directly access those nodes. libdvbapi seems to be the right way to start over with. If one can get applications to get going with it, it would be a start. Someone jokingly said a name for it ALDA. But many times, you can't force things to users. I just looked at it again, is there any official documentation available? Markus The enduser applications would have to implement that API one time but it would help to keep unnecessary changes away from those applications and even allow to clean up things lateron without breaking all the applications... it's just a thought though.. Yes, that's how it would work in the ideal case, i doubt whether we can force applications to use the library. I would spend some time to implement such a library in enduser applications. Although first I need to get my devices work and into the kernel and fix some nasty bugs in my driver... Markus -- Markus Rechberger ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB API update
On 9/18/07, Manu Abraham [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 9/18/07, Manu Abraham [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 9/18/07, Manu Abraham [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 9/18/07, Manu Abraham [EMAIL PROTECTED] wrote: Markus Rechberger wrote: Hi, Why don't abstract the dvb layer from enduser applications and put a general library infront which does that version check and tries to keep things consistend to the end applications? It is a nice idea, yes. Two things, looking at http://linuxtv.org/hg/dvb-apps/file/4bca5d49c9bd/lib/libdvbapi/dvbfe.c * This idea of using multiple API 's was thought (It is effective , yes) You can use multiple API's in there * The down side is that user applications need to use this library Someone could ask, why the hell should we use your library. Well, that causes the headaches. people who use alsa also use the provided alsa API, it makes alot sense to stop applications to directly access those nodes. libdvbapi seems to be the right way to start over with. If one can get applications to get going with it, it would be a start. Someone jokingly said a name for it ALDA. But many times, you can't force things to users. I just looked at it again, is there any official documentation available? There's nothing such as a libdvbapi.doc/txt. But the important parts were documented in the headers.*.h files I would say that's the reason why almost noone uses it. It would deserve some more documentation on linuxtv.org Looking at the function names and what it does, it resembles the in kernel operations 1:1 also there is documentation in the headers. Also example applications, test applications, real working applications all exists in dvb-apps itself. You still think it needs more documentation ? An abstract documentation and/or tutorial would still be better I think. For example http://equalarea.com/paul/alsa-audio.html It seems like people first have to ask in IRC or on the ML to get some info about that library (well now people can also search that thread, although an official documentation would be preferred I guess :) Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB API update
On 9/18/07, Aidan Thornton [EMAIL PROTECTED] wrote: On 9/18/07, Markus Rechberger [EMAIL PROTECTED] wrote: On 9/18/07, Manu Abraham [EMAIL PROTECTED] wrote: Markus Rechberger wrote: Hi, Why don't abstract the dvb layer from enduser applications and put a general library infront which does that version check and tries to keep things consistend to the end applications? It is a nice idea, yes. Two things, looking at http://linuxtv.org/hg/dvb-apps/file/4bca5d49c9bd/lib/libdvbapi/dvbfe.c * This idea of using multiple API 's was thought (It is effective , yes) You can use multiple API's in there * The down side is that user applications need to use this library Someone could ask, why the hell should we use your library. Well, that causes the headaches. people who use alsa also use the provided alsa API, it makes alot sense to stop applications to directly access those nodes. libdvbapi seems to be the right way to start over with. I'm not sure ALSA is a good example - it's always felt a bit hairy to me. Part of the reason that people have to use alsalib is that important bits are in userland, and they tend to break in interesting ways. For example, I found that if a program using ALSA launches another program without closing the file descriptors correctly, sound playback breaks when the first program exits due to the odd way software mixing is done. There's various other annoying and non-intuitive ways that software mixing can break too. (I also get the impression that ALSA uses the library as an excuse to break kernel-userspace ABI compatibility, to the annoyance of distro maintainers. I can certainly recall several complaints about it on Diego Flameeyes Pettenò's blog back when he maintained ALSA on Gentoo.) Besides, it's a bit late to try and do this now... alsa is just an example in case of documentation and since it seems like that the DVB API won't be stable in future either such a way would be better. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Userspace tuner
On 9/15/07, Bernard Jungen [EMAIL PROTECTED] wrote: On Sat, Sep 15, 2007 at 11:04:42AM -0300, Mauro Carvalho Chehab wrote: With respect to your kernel-userspace API for xc3028, you made something that seemed to be a dream: there's a consensus: not a single developer believed that this is the better way; nobody seems that this is the better approach. So, or you are the only media developer with good sense in the face of the Earth, or you're incapable of understand the obvious: you're wrong with this approach. IMO, the answer is quite obvious. Yes, as a newbie observer on the v4l list, the answer is obvious to me, at last, and the reason is not entirely technical. I can't read so many bogus arguments on so few lines without reacting. Rephrasing Mauro: Not a single developer out of a few SEEMS to believe that it is the BETTER approach, so since the FEW represent ALL media developers in the world, and since there is only ONE RIGHT way to do things, and since the GROUP is always RIGHT and always knows better than the individual, then YOU're WRONG and I'm right. Conform to the group and do as the group says, whatever the consequences! Geeks are decidedly as prone as others to blindly accept travelling on the slippery road of herd mentality and obvious conclusions based on appearances. Is this OPEN source development or a dictatorship or what? So in the end Mauro will be right. And Markus will continue to develop and defend his stuff as HE sees fit. He knows his own work better than anyone else. It will be HIS way or nothing with his own stuff, it's his inalienable right. And don't be naive, if there's no solution more viable than Markus' one, then the latter will eventually be widely adopted somehow, sometime, whatever the amount of grumbling from the establishment. No dictatorship/forced consensus can decide future's direction, nor improve its already low own viability. I see it exactly the same way. Well I will continue to provide an alternative stack with alternative drivers. The peer review shows that it doesn't work too well without people participating fixing problems, the initial drivers were inkernel based and due some updates in modules which are used by the em28xx some devices which previously worked don't work anymore in the kernel. As for the em28xx the driver will use userspace i2c based tuners, decoders and demodulators. The userspace modules will use unaltered sample drivers which are provided by several companies, which also saves alot time in future for that project. Those drivers will also officially be provided and recommended by the manufacturing company of those devices, including the proper firmware. Personally I won't spend any time on reinventing the wheel and fixing drivers which get broken by not taking care of it. Beside that people are welcome to contribute without having to fear a political overhead of discussing requirements and other issues when changing the corresponding alternative core code. The project and how it will/should go on is documented at mcentral.de. I also see that as a good way for the community, that way the linuxtv guys have to prove that they can be open to other people without adding too much noise and overhead otherwise people will contribute to the alternative project as some already do. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Userspace tuner
On 9/15/07, Johannes Stezenbach [EMAIL PROTECTED] wrote: On Sat, Sep 15, 2007, Markus Rechberger wrote: it gets me thinking. Some core developers who I met during the last few weeks (kernel summit, suse conference in czech) told me to go on with it actually because the final plan isn't that bad.. I was referring to your code you posted for merging on linux-dvb, and which got rejected. Anyway, it's easy to agree with you if one has just heard _your_ version -- the purpose of this thread is to give people an alternate version of the story to complement yours, which would allow the people you talked to to think it over and change their mind. See if you can get of those people you talked to to post here to support you. Everyone knows that there are some issues even some internal ones which I'm not part of. Not sure if you met some other kernel developers recently, all you can hear is those crazy media guys (which just includes everyone who works with media related drivers) Beside that I'm just curious how much did you contribute during the last 2 years to the lkml/linux kernel, and how much do you want to contribute in future? (also from my side talk is cheap (even for me) but getting something done costs quite some time and feedback from other people) IOW you say if I don't write code I should shut up? Is that also what you tell users on your em28xx list when they dare to disagree with you? Nice... This is a free world you can write whatever you want, but if you want me to change my code you need to convince me that I should acknowlidge your ideas. And by not acknowlidging my requirements don't expect that I will go back to the start and try to reinvent the wheel. After almost 2 years I'm quite into those things and I know what I want for my project and what I'll try to achieve with what I'm doing. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Userspace tuner
On 9/15/07, Mauro Carvalho Chehab [EMAIL PROTECTED] wrote: Everyone knows that there are some issues even some internal ones which I'm not part of. With respect to your kernel-userspace API for xc3028, you made something that seemed to be a dream: there's a consensus: not a single developer believed that this is the better way; nobody seems that this is the better approach. Not a single developer out of 3-5 people? Seems fine with me, because people didn't agree with anything else before either and tried to point me to wrong solutions. http://threebit.net/mail-archive/video4linux/msg07548.html So, or you are the only media developer with good sense in the face of the Earth, or you're incapable of understand the obvious: you're wrong with this approach. IMO, the answer is quite obvious. that for you don't have to use it. http://mcentral.de/wiki/index.php/Userspace_tuner#Advantages I'm off for the weekend now so have a nice one :-) Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Userspace tuner
On 9/14/07, Steven Toth [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 9/13/07, Steven Toth [EMAIL PROTECTED] wrote: Also there is to consider a non technical aspect, whether vendors will misuse this interface for binary only, undermining the efforts put in for OSS drivers. What holds companies for using the current available code putting it into an rpm or deb package and releasing such code now? The Avermedia example I pointed out to is a good example already. As from my side I won't release binary drivers. Although on the other side: * are drivers from vendors which work through several kernel versions that bad? * Why did someone duallicense videodev2 with BSD/GPL? I would appreciate if someone else on the list could also comment the reason that drivers should all be included in the linuxkernel just because forcing the companies to release binary drivers because of that. My opinion about that is if a company wants to go opensource they will do so, if not they will either not release a driver or release nothing. I know for certain that adding a userland API tuner/demod interface to the kernel, allowing non-caring opportunistic silicon or board vendors to developer closed source proprietary drivers, will have a negative effect on the community and we'd set back linuxtv 3-5 years. I know for certain that it would happen. Trust me. I've told you this countless times and you're not hearing me. Hauppauge have some leverage with Conexant and NXP to release public datasheets. If they just have to release a demod.so (or similar) loadable, they'll defer to the board vendors and we'll see the certain board vendors 'locking other board vendors' out of their drivers. We'll see embedded firmware, not shared between drivers. Except, it won't stop at demod.so. It will extend into unfixable bugs for VendorB's board, because VendorA doesn't want to release a new demod.so, and VendorB has no linux resources. What happens next? For financial reasons - demod.so will begin to include checks to see if specific PCI or USB devices are present in the system, and will fail to work properly (if at all) when they're not being used with the preferred products. Steven, what stops vendors of using the current existing code to achieve that goal. They could provide binary drivers with the existing API. Because the good people in this mailing list are keeping them honest. Give any board or silicon company the ability to protect their IP, even in the smallest way and they'll do it, and for no good technical reason. It's a cut throat market and it's not clear that everyone understands just how thin sales margins really are. That means Hauppauge potentially releasing a binary driver, because it's much easier than seeking silicon vendor permission for a public diver. The net result of that would mean I'd have to leave the company and find another company that practices the one thing I truly care about open source and open development groups. well you could already release binary drivers if you would be concerned about it, so again all that seems to be no reason for me. What stops Hauppauge in implementing drivers another way? For example the USB drivers completly in userspace. I'm keeping Hauppauge honest with their Linux involvement and I'm not alone. Other devs in other linux subsystems in other companies are doing the same thing. For example the UIO thing, accessing MMIO through userspace, also accessing usb control messages from userspace. Because of that reason since it is already possible to provide binary drivers your reason is again not valid. The code which the userspace tuners are connected to is GPL so what. Beside that Hauppauge is not the only company out there although I also have contacts there at Hauppauge Europe. Binary drivers (or binary components) leads Linux back in time. I can't believe your so passionate about protecting secrets. Please point me to the part where I am passionated about protecting any of my opensource code which is currently available. I have other arguments why to put that part into userspace. What stops companies to intercept the ioctl calls and overriding some I2C commands? Why would a company want to do that? Companies don't do that, hackers do that. just to achieve what you're trying to argue with that companies could use some odd constructs which could be used to publish their drivers as binary only. I don't see the problem there if they want to do so. Since you know about windows drivers (at least I think that you know about it) you might know about the limitations of the v4l/dvb API in general the reason just put as much code as possible into the kernel just for forcing companies to release code under GPL doesn't seem to be valid. It seems perfectly valid to me. How about proprietary video formats, would you also
Re: [linux-dvb] [PATCH] Userspace tuner
On 9/14/07, Manu Abraham [EMAIL PROTECTED] wrote: Joerg Roedel wrote: On Fri, Sep 14, 2007 at 11:57:59AM +0400, Manu Abraham wrote: What do you think about IOMMU? Just because AMD or INTEL want to invent some whizzy new technology it doesn't say anything about the TV card development and retail business. Intel and AMD have teams of Linux engineers helping operating system developers bring their ideas and technologies to new platforms. That's a million miles away from any of the TV board vendors I know of, who have little or NO fulltime linux developers and consider the 5% market fringe at best. it helps to virtualize devices and introduces newer features for that. Some interesting projects could be derrived out of that, there are quite a few interesting papers floating around how drivers could be handled in future. IOMMU can be considered similar to the AGP GART, which is similar, remapping the Addresses, as far as i understand. Common new IOMMUs have only very few in common with the AGP GART. In fact, with current modern IOMMU hardware it will be possible to implement secure userspace device drivers that are even able to do DMA. This is not possible with the GART. Though you get a physical to virtual translation, what about interrupts, Modern IOMMUs are able to remap interrupts. This will solve the problem with PCI interrupt sharing. What CPU's are we talking about ? upcoming x86-64 processors from the AMD side. I'm not into what Intel is doing in that area at the moment. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Userspace tuner
On 9/14/07, Alan Cox [EMAIL PROTECTED] wrote: On Fri, Sep 14, 2007 at 01:17:05AM +0200, Markus Rechberger wrote: what stops vendors of using the current existing code to achieve that goal. They could provide binary drivers with the existing API. If you feel lucky about the GPL What stops companies to intercept the ioctl calls and overriding some I2C commands? The GPL - derivative work is the boundary not code linkage. Possibly a userspace tuner hack would probably fit this too. Especially if a specific vendor is producing both bits together and trying to claim they are independant. How about proprietary video formats, would you also place the decoding algorithms in kernel just to force companies to release their code for it? No, I would assume they'd provide a proprietary conversion library that no nobody would use (just like their hw). We keep format conversion firmly seperated from hardware I/O processing. In general there are known formats available, the drawback is that every TV application deals with it in a non-unified way at the moment, meaning alot code duplication in userspace since there's no library available at the moment which does the videoconversion from one to another format. Such a library is beeing developed at the moment which gets plugged infront of accessing the devicenodes. Although in the long run I'm looking forward to reuse the userspace tuners with such a library infront of everything by using i2c-dev. This would also make it easy to reuse the sample code of several companies, without having to cut out several features of the drivers and to rewrite them to an inkernel format. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Userspace tuner
On 9/14/07, Johannes Stezenbach [EMAIL PROTECTED] wrote: On Fri, Sep 14, 2007, Markus Rechberger wrote: On 9/14/07, Steven Toth [EMAIL PROTECTED] wrote: If you care about LinuxTV you'll work with the core subsystem developers to bring your em28xx tree inline. If you don't care then why are you here? It doesn't really work out to work with those 3-5 core people who are active there. It starts at the point where RFCs are submitted and not answered, discussions are avoided and finally some people start to complain. In case of pointing people to wrong or bad solutions, one Maintainer pointed out it would be like manipulating others work ... this exactly happened with the em28xx project. It's not only about the current implementation, as from my side I also take upcoming products into account and how long it would take to get something which isn't supported by the API fixed.. it's just something that is too hard and I don't want to debate about things where I know that the outcome is that I have to wait till someone of those 3-5 core people come up with an own idea. Maybe you still don't realize how tiresome it is to talk to you. What you present as linuxtv people block my contributions is IMHO linuxtv people got fed up talking to you. Because when people disagree with you, you keep rambling on and on instead of just accepting it. See, working with an Open source community requires that you don't piss everyone off, but instead find ways to _motivate_ them to help you fix the problems which prevent your code from being merged. When people are doing software development _for fun_, then it should be a _pleasure_ for them to work with you, and not a pain in the ass. Johannes, people do contribute to the em28xx project. If noone keeps finding solutions for requirements I will of course go on to find my own way. Although upcoming and even the current requirements are not met by the existing API. It's worth nothing to merge what's available now since I'm not even ok with how several issues are solved with the driver itself at the moment. I'm going forward step by step with it now. there's also an active and even problem solving oriented ML available: http://mcentral.de/pipermail/em28xx/ Also if you look at the mercurial code you'll see several people contributing to that project. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Userspace tuner
On 9/14/07, Mauro Carvalho Chehab [EMAIL PROTECTED] wrote: Markus, Maybe you still don't realize how tiresome it is to talk to you. What you present as linuxtv people block my contributions is IMHO linuxtv people got fed up talking to you. Because when people disagree with you, you keep rambling on and on instead of just accepting it. See, working with an Open source community requires that you don't piss everyone off, but instead find ways to _motivate_ them to help you fix the problems which prevent your code from being merged. When people are doing software development _for fun_, then it should be a _pleasure_ for them to work with you, and not a pain in the ass. Johannes, people do contribute to the em28xx project. If noone keeps finding solutions for requirements I will of course go on to find my own way. Although upcoming and even the current requirements are not met by the existing API. It's worth nothing to merge what's available now since I'm not even ok with how several issues are solved with the driver itself at the moment. I'm going forward step by step with it now. there's also an active and even problem solving oriented ML available: http://mcentral.de/pipermail/em28xx/ Also if you look at the mercurial code you'll see several people contributing to that project. Solutions for your requirements can be reachable via a kernelspace solution: - The hybrid tuner support, that where your requirement, when all those discussions started, were already added to the subsystem. So now, an hybrid tuner can be accessed by both DVB and V4L devices; It's far more complex as the thing which is implemented there. The only thing that has been implemented is that one moduleformat can be loaded by the v4l and by the dvb framework nothing else at the moment. I told you at the kernel summit about that and I think you knew about that before. Just to quote some text: Right now, a separate instance of the driver is used for analog / digital tuning. In order to use a single instance, we will have to store a pointer to the dvb_frontend structure on the bridge level, but there are various other prerequisites that must be dealt with before we get to that point. We _will_ get there though, eventually. - Audio standard selection is already possible via S_STD (it is already working for a few standards, like NTSC/M JP and NTSC/M KR). Maybe more standards should be needed, but hey, we still have 34 bits available at std mask. Let me quote some text where you've been in CC and which didn't get far enough to get a solution implemented. (Michael Schimek) xc3028_BG_PAL_A2_A.i2c FW_78 B/G PAL A2 Group delay: See RecITU-R BT.470-6 p.21 Response A xc3028_BG_PAL_A2_A_MTS.i2c FW_78_MTS B/G PAL A2 ZWEITON xc3028_BG_PAL_A2_B.i2c FW_78 B/G PAL A2 Group delay: See RecITU-R BT.470-6 p.21 Response B xc3028_BG_PAL_A2_B_MTS.i2c FW_78_MTS B/G PAL A2 ZWEITON xc3028_BG_PAL_NICAM_A.i2c FW_78 B/G PAL NICAM Group delay: See RecITU-R BT.470-6 p.21 Response A xc3028_BG_PAL_NICAM_A_MTS.i2c FW_78_MTS B/G PAL FM xc3028_BG_PAL_NICAM_B.i2c FW_78 B/G PAL NICAM Group delay: See RecITU-R BT.470-6 p.21 Response B xc3028_BG_PAL_NICAM_B_MTS.i2c FW_78_MTS B/G PAL FM We cannot add new standards for each of these files because only six bits are unassigned in the lower half of v4l2_std_id. It seems unecessary too, please correct me if I'm wrong. (Well the driver could define its own video standards for each of the firmwares and put them into the upper 32 bits of v4l2_std_id, which were set aside for this purpose. But adding standards to the API also has its advantages. Maybe it's time to reserve bits 40-55 for future expansion.) I suppose you choose firmwares with IF or baseband sound output depending on the design of the card? The point is: there's no technical need for userspace. This will just add userless complexity. However, you insist with your selfish idea that every other solution, except the one you're proposing are bogus. This is not the way Open Source development works. You should listen to people. I pointed out a few requirements which didn't get commented at all, and I explained why things where done in a particular way. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Userspace tuner
On 9/14/07, Alex Deucher [EMAIL PROTECTED] wrote: On 9/14/07, Markus Rechberger [EMAIL PROTECTED] wrote: On 9/14/07, Manu Abraham [EMAIL PROTECTED] wrote: Joerg Roedel wrote: On Fri, Sep 14, 2007 at 11:57:59AM +0400, Manu Abraham wrote: What do you think about IOMMU? Just because AMD or INTEL want to invent some whizzy new technology it doesn't say anything about the TV card development and retail business. Intel and AMD have teams of Linux engineers helping operating system developers bring their ideas and technologies to new platforms. That's a million miles away from any of the TV board vendors I know of, who have little or NO fulltime linux developers and consider the 5% market fringe at best. it helps to virtualize devices and introduces newer features for that. Some interesting projects could be derrived out of that, there are quite a few interesting papers floating around how drivers could be handled in future. IOMMU can be considered similar to the AGP GART, which is similar, remapping the Addresses, as far as i understand. Common new IOMMUs have only very few in common with the AGP GART. In fact, with current modern IOMMU hardware it will be possible to implement secure userspace device drivers that are even able to do DMA. This is not possible with the GART. Though you get a physical to virtual translation, what about interrupts, Modern IOMMUs are able to remap interrupts. This will solve the problem with PCI interrupt sharing. What CPU's are we talking about ? upcoming x86-64 processors from the AMD side. I'm not into what Intel is doing in that area at the moment. All AMD64 chips have an IOMMU. Only Intel's most recent chips do. It's not available yet, you can read more about it in the following article: http://developer.amd.com/articlex.jsp?id=101 If you're interested in it I can put together some more information about it. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Userspace tuner
On 9/14/07, Johannes Stezenbach [EMAIL PROTECTED] wrote: On Fri, Sep 14, 2007, Markus Rechberger wrote: people do contribute to the em28xx project. ... there's also an active and even problem solving oriented ML available: http://mcentral.de/pipermail/em28xx/ Also if you look at the mercurial code you'll see several people contributing to that project. Of course, people who own such a device and want to use it with Linux have no choice but to work with you. And you do a good job for your users, you support them well and in return they contribute info and patches to support new devices. But the thing is that at mcentral.de you're the man at the top, and your users will hardly disagree with you on core technical questions. (Well, admittedly I'm speculating here as I don't read your em28xx list.) they can. Put technical issues infront of everything also see the whole picture that userspace tv applications have to support all the codecs which are available. On for drivers/media/ OTOH you are just one developer among others, and some of them choose to disagree with you. Even worse, IIRC there wasn't even _a single_ other developer willing to ACK your offending patch. there was not a single developer of the old crufted developers who didn't bring the project forward during the last 2 years. yes you're right. Now, doesn't _that_ get you thinking? it gets me thinking. Some core developers who I met during the last few weeks (kernel summit, suse conference in czech) told me to go on with it actually because the final plan isn't that bad.. I don't expect anyone of the old crufted v4l/dvb (well many of them already left the party) will join the game... (I'll leave that open here) spend some time read the whole history of this thread and it will show up what this all is targeting at. I'll answer your questions with technical reasons why I'm doing all that stuff that way if you'll just ask. Someone told me during the last 2 weeks but v4l2 was about to solve all those problems it didn't. (point) and I think I explained good enough why all that crap still goes on as it is. Beside that I'm just curious how much did you contribute during the last 2 years to the lkml/linux kernel, and how much do you want to contribute in future? (also from my side talk is cheap (even for me) but getting something done costs quite some time and feedback from other people) Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Userspace tuner
On 9/14/07, Johannes Stezenbach [EMAIL PROTECTED] wrote: On Fri, Sep 14, 2007, Markus Rechberger wrote: people do contribute to the em28xx project. ... there's also an active and even problem solving oriented ML available: http://mcentral.de/pipermail/em28xx/ Also if you look at the mercurial code you'll see several people contributing to that project. Of course, people who own such a device and want to use it with Linux have no choice but to work with you. And you do a good job for your users, you support them well and in return they contribute info and patches to support new devices. But the thing is that at mcentral.de you're the man at the top, why is it mcentral.de at the moment? I started several discussions about the whole topic. The thing which is in v4l-dvb on linuxtv does not satisfy any requirements, also further additions will be hard to achieve with it. and your users will hardly disagree with you on core technical questions. (Well, admittedly I'm speculating here as I don't read your em28xx list.) they can disagree, I even pointed out to design flaws lately when some users posted bugreports. On for drivers/media/ OTOH you are just one developer among others, and some of them choose to disagree with you. Even worse, IIRC there wasn't even _a single_ other developer willing to ACK your offending patch. the current patch isn't offending anymore, see it as a chance I'm giving you the chance to acknowlidge what has been done now from my side. The main discussion in this thread was about drivers in userspace are bad because the API will allow binary drivers. The guy who works for Hauppauge (again I also have good contacts at Hauppauge Europe) writes it's bad - for no technical reason. If someone points out that it is bad (after reading the whole thread) why don't we put X.org, bash, well everything into the kernel? GPL is the saviour seems to be the saviour for some people in this world, but in the end it's still if people want to go that way. Much work has been done by other people before, my work is also just an additional contribution and I (again) don't intend to release binary drivers. (also keep in mind that ubuntu takes everything which makes things work - this matters to the enduser) Hey I can also write I can help you to get things right with some other people, and I can financially support people by giving away hardware and even specs for free in some cases. Who is able to do that from the old crufted v4l/dvb guys? Manu throws his drivers over the wall to the OSS community, although I don't mind. Mauro is copying the logic of my code and writes I told him I'm ok with taking my code without just adding a single line of how his driver got developed. (I still wonder why he skipped some significant parts of the driver .. because he used the existing one as logic template) http://linuxtv.org/hg/~mchehab/tm6000-new/log/14352ab89146/linux/drivers/media/video/tuner-xc2028.c (not looking at the specific changeset but he copied the firmware loading instructions without taking care about the copyright?) Now, doesn't _that_ get you thinking? oh yes. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Dazzle* TV Stick supported?
On 9/14/07, Pepe [EMAIL PROTECTED] wrote: En Wed, 12 Sep 2007 23:56:25 +0200, Pepe [EMAIL PROTECTED] escribió: I've just bought a dvb-t usb stick (Dazzle* TV Stick, identified in windows as Pinnacle PCTV 71e). Is this device supported on linux? I can't find anything about it. So nobody knows if this is supported? If it's not supported I still have time to return it to the store. I'm not sure let me try to get more information about it next week from pinnacle. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Userspace tuner
Hi, On 9/13/07, Johannes Stezenbach [EMAIL PROTECTED] wrote: On Thu, Sep 13, 2007, Markus Rechberger wrote: We currently have an implementation that works, although it works by downloading several firmwares for several devices or even several countries. This is not what I want to have in future since it's not needed and it's also hard to manage for distributors. All those differences could be adjusted by software even without module parameter hacks. This argument doesn't hold water. The unpleasant point for users and distributors isn't the binary-only thing, it's the no right to distribute problem. And that's the same for firmware blobs or binary-only userspace blobs. IOW, if you can get the right to redistribute a binary-only userspace blob which incudes the firmware inside, why shouldn't you be able to get the right to redistribute just the firmware? In particular xceive based drivers provide a numerous set of features which cannot be implemented into the kernel because the API (both V4L and DVB) are limited. Since to me it seriously has the impression that the project especially the core of the project is closed to the outside world (just how someone stated it out recently he licked the butts of others to get his stuff accepted) Or the other way round: Do you think your binary-only software will be important enough so distributors will go through all the trouble of trying to get a license to include it in their distribution? If so, why wouldn't they do the same for the plain firmware blobs for in-kernel drivers? I don't have any binary only software just as all the time before. I am also allowed to publish firmware for several drivers (not only the em28xx driver). Although as mentioned earlier already the current existing driver is not really manageable due the firmware mess and that driver will change completly and include templates for several other bridge drivers. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Userspace tuner
On 9/13/07, Johannes Stezenbach [EMAIL PROTECTED] wrote: On Thu, Sep 13, 2007, Markus Rechberger wrote: Let's add the LKML to this. On 9/13/07, Markus Rechberger [EMAIL PROTECTED] wrote: On 9/12/07, Mauro Carvalho Chehab [EMAIL PROTECTED] wrote: I don't see any technical reason why tuner drivers should be moved to userspace. Looking at xc3028 device, the driver is very simple and doesn't require any special treatment that it isn't possible to be done at kernel. There are already some implementations on kernelspace that works fine. As from my side to support the xceive driver properly it needs a rewrite and a proper API description. Since it's not possible to discuss any API changes Not possible? We're doing it all the time... Then ask Mauro about the audio standard discussion which I had with him. However, your ideas were rejected in this discussion, and you can't seem to get over it. As for future projects I see other people having the same problems if they want to join the project. If deeper requirements and/or ideas will come up some particular people will try to run their own game. If I'm doing something wrong technically then state it out show me the bugs that I can understand what I did wrong or what I am doing wrong. As for design changes if someone thinks he has to deny something he has to state out _why_ and not only some overall nontechnical statements which do not help anyone. don't get me wrong but the existing community is rather small and kicking off people who are interested in changing things. IMHO there is a lack of openness caused by people being burned in past flamewars. This makes it a bit difficult to see through what happens and why, and to participate. However, I think it is completely wrong to say that the community is kicking off people. You identified it already the right way in one mail much earlier. It's a messup caused by many people and not only by one single person. And that's also how I see it. I'm against how the project works out at the moment and how it worked out in history. Exactly this way will kick off companies to be interested in future like Avermedia. A driver can easily be written within a few weeks and I've been struggling with it for 2 years(!!!) now just for nothing finally telling me that some guys want to steal my code and move it to kernelspace although it would raise more complications with upcoming and current devices which have even more requirements. Oh dear, there we go again... more flame bait... I reality, 95% of your driver code could have been merged without problems, but you refused to take the small, objectionable part out of the picture. the driver itself still evolves, so the main point is in getting those incomplete APIs to support further requirements. Instead of acknowlidging and seriously discussing the solutions of others all that's beeing done now is to redo things hundred times and splitting development one side beeing more open (which is the userspace work) and the other part beeing more closed to a few people only (the inkernel work). It's not my task to convince myself to rewrite the base of something which I don't think that it would be valueable. The one who wants me that I spend days in changing my code should try to convince me to change my mind on that, unless he can provide patches which demonstrate that his changes are definitelly an advantage over what has been done from my side. I will for sure acknowlidge everything that will seriously improve the work which has been done. (For those interested: http://mcentral.de/~mrec/patches/v4l-dvb/hg_v4l-dvb-experimental_01.patch The patch changed the internal tuner API and required changes to all tuner drivers.) The main problem is moreover that the RFC didn't get discussed properly, afterwards people wondered what happened, even though the sources were also available all the time in a public repository. Your all-or-nothing approach didn't work out. well we got far enough that I end up to step away and preparing the sources to be able to get submitted beside linuxtv since I don't/didn't get any useful technical feedback there. Convince me that my work is welcome then I might start to submit smaller patches, I already spent days for exporting patches in history and it all end up nowhere but in unfriendly discussions - which also turned me to be unfriendly to some people (which I've been told that I should ignore them recently and also not continue to to argue on a nontechnical level .. althought as mentioned I'm not the only one who made mistakes :-) Out of curiosity: How does your userspace approach solve the hybrid (analog/digital TV) tuner problem which was the only objectionable part of your work? And why are the kernel parts of your new interface now less objectionable? What changed? It's only a step in development, I do not intend to keep
Re: [linux-dvb] [PATCH] Userspace tuner
On 9/13/07, Manu Abraham [EMAIL PROTECTED] wrote: It's only a step in development, I do not intend to keep the kernel stub in the end, but I do intend to keep and use the userspace drivers with i2c-dev in the long run, this requires a v4l/dvb library at the front of everything. Well, this was what adq and myself did with libdvbapi and mti, (much before UIO was announced at LK.) It is not tied to I2C either. I2C is the main communication path for it, although there are callback mechanisms available which add the possibility for different configuration paths. But, according to your statements (with regards to i2c-dev) you can handle only some I2C based devices, which is in fact a subset of a subset. Also not to forget that hardly a few I2C devices are in fact truly I2C compatible. In fact many variables to be considered. The analogue tuner core is also only for i2c only devices which most devices rely on. Also there is to consider a non technical aspect, whether vendors will misuse this interface for binary only, undermining the efforts put in for OSS drivers. What holds companies for using the current available code putting it into an rpm or deb package and releasing such code now? The Avermedia example I pointed out to is a good example already. As from my side I won't release binary drivers. Although on the other side: * are drivers from vendors which work through several kernel versions that bad? * Why did someone duallicense videodev2 with BSD/GPL? I would appreciate if someone else on the list could also comment the reason that drivers should all be included in the linuxkernel just because forcing the companies to release binary drivers because of that. My opinion about that is if a company wants to go opensource they will do so, if not they will either not release a driver or release nothing. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Userspace tuner
On 9/13/07, Manu Abraham [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 9/13/07, Manu Abraham [EMAIL PROTECTED] wrote: It's only a step in development, I do not intend to keep the kernel stub in the end, but I do intend to keep and use the userspace drivers with i2c-dev in the long run, this requires a v4l/dvb library at the front of everything. Well, this was what adq and myself did with libdvbapi and mti, (much before UIO was announced at LK.) It is not tied to I2C either. I2C is the main communication path for it, although there are callback mechanisms available which add the possibility for different configuration paths. Sorry, i must say that what you said is wrong. The example implementation in libdvbapi/mti is I2C only with a STV0299 on the TTPCI, if that was what you meant. But if you need examples for every possible interface, then probably you are out of luck. I didn't comment the libdvbapi/mti driver. I'm quite confident that non I2C protocols can be handled by a callback function. In the end it's either a usb control command or pci mmio writes in the current usual cases and such calls could be handled behind a callback function which is implemented in the driver. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Userspace tuner
On 9/13/07, Steven Toth [EMAIL PROTECTED] wrote: Also there is to consider a non technical aspect, whether vendors will misuse this interface for binary only, undermining the efforts put in for OSS drivers. What holds companies for using the current available code putting it into an rpm or deb package and releasing such code now? The Avermedia example I pointed out to is a good example already. As from my side I won't release binary drivers. Although on the other side: * are drivers from vendors which work through several kernel versions that bad? * Why did someone duallicense videodev2 with BSD/GPL? I would appreciate if someone else on the list could also comment the reason that drivers should all be included in the linuxkernel just because forcing the companies to release binary drivers because of that. My opinion about that is if a company wants to go opensource they will do so, if not they will either not release a driver or release nothing. I know for certain that adding a userland API tuner/demod interface to the kernel, allowing non-caring opportunistic silicon or board vendors to developer closed source proprietary drivers, will have a negative effect on the community and we'd set back linuxtv 3-5 years. I know for certain that it would happen. Trust me. I've told you this countless times and you're not hearing me. Hauppauge have some leverage with Conexant and NXP to release public datasheets. If they just have to release a demod.so (or similar) loadable, they'll defer to the board vendors and we'll see the certain board vendors 'locking other board vendors' out of their drivers. We'll see embedded firmware, not shared between drivers. Except, it won't stop at demod.so. It will extend into unfixable bugs for VendorB's board, because VendorA doesn't want to release a new demod.so, and VendorB has no linux resources. What happens next? For financial reasons - demod.so will begin to include checks to see if specific PCI or USB devices are present in the system, and will fail to work properly (if at all) when they're not being used with the preferred products. Steven, what stops vendors of using the current existing code to achieve that goal. They could provide binary drivers with the existing API. What stops companies to intercept the ioctl calls and overriding some I2C commands? Since you know about windows drivers (at least I think that you know about it) you might know about the limitations of the v4l/dvb API in general the reason just put as much code as possible into the kernel just for forcing companies to release code under GPL doesn't seem to be valid. How about proprietary video formats, would you also place the decoding algorithms in kernel just to force companies to release their code for it? What do you think about the existing usbfs implementation, which allows to implement usb drivers completly in userspace? What do you think about IOMMU? please answer those questions. thanks, Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Userspace tuner
On 9/12/07, Mauro Carvalho Chehab [EMAIL PROTECTED] wrote: Markus, Em Ter, 2007-08-14 às 16:31 +0200, Markus Rechberger escreveu: Following patch adds the possibility to implement tuner drivers in userspace. As you asked me about userspace driver, at Linux Conf Europe, let me give you my feedback about it. On Linux, userspace-to-kernelspace APIs are meant to be forever. This means that, once a newer API is created, this should remain supported for all future versions. So, such APIs should be carefully analyzed and accepted by the community, before going to mainstream. The V4L and DVB API is stable at the moment because it's at a stage which is sufficient for older devices but not sufficient for newer devices anymore. To support newer device it needs a change. I don't see any technical reason why tuner drivers should be moved to userspace. Looking at xc3028 device, the driver is very simple and doesn't require any special treatment that it isn't possible to be done at kernel. There are already some implementations on kernelspace that works fine. As from my side to support the xceive driver properly it needs a rewrite and a proper API description. Since it's not possible to discuss any API changes I will work around at least for those devices which I can support for. On the other hand, a TV driver without a tuner is a broken driver. With parts of the driver being at userspace, this means to add undesired complexity at the drivers architecture, while not bringing any benefit. If you look at V4L history, the first drivers started at userspace, being migrated to kernelspace, where we have the proper scenario for managing those devices. Another aspect that should be analyzed is what is desired by the community: don't get me wrong but the existing community is rather small and kicking off people who are interested in changing things. I recently had a talk with someone and I've been told that I'm kicking off people. Guess why I kick off people? - because they do not contribute in a productive way which also means submitting patches. Optical useless changes don't make any difference at the functionality in the end. And my requirements are ignored constantly here. kernelspace tuners or userspace tuners. Keeping support for both at long term doesn't seem reasonable. The Linux community should decide what is the better way. Currently, only you are pushing for userspace tuners, mainly due to non-technical reasons. read the project site and you will see the reasons. http://mcentral.de/wiki/index.php/Userspace_tuner#Advantages Another advantage is that I have cygwin based code here which I can easily reuse with all that work I'm not going to reinvent the wheel even for newer devices which I work on. Almost all the other developers are comfortable with kernelspace tuners. So, creating an userspace interface just to make you happy is not the way we should go. I'm afraid of giving the people which are against what I submitted the responsibility over the project. Initially there was an RFC which didn't get commented either (well there was one useless comment, I tried to discuss it on IRC before with the same guy) after I implemented exactly what I proposed there I got the first non technical comments - also keep in mind that working on something costs alot of time and talking about something unknown is rather cheap. A final aspect is that having an userspace driver for tuner will mean that the kernel driver will depend on an userspace counterpart in order to work. This will allow a vendor with bad intentions to release a partially broken userspace driver, with limited capabilities, and a closed source driver for full support. This model is likely to occur, if you take a look at the past. For example: ATI and Nvidia closed source drivers, several soft modem drivers, some network drivers, ... Please go forward and discuss the UIO driver with Greg Kroah Hartmann and the fuse driver with the other people. If companies want to release binary drivers they can easily use the existing code put it into an RPM or DEB package and Ubuntu will pick it up. With all those issues, I'm against to add an userspace interface for tuners. I'm against how the project works out at the moment and how it worked out in history. Exactly this way will kick off companies to be interested in future like Avermedia. A driver can easily be written within a few weeks and I've been struggling with it for 2 years(!!!) now just for nothing finally telling me that some guys want to steal my code and move it to kernelspace although it would raise more complications with upcoming and current devices which have even more requirements. I spent more time in rewriting and discussing everything than to get any of those requirements done. Look at the dvb hotplug patch which came from my side, also look at device node locking where the Hauppauge guy submitted a patch which doesn't work properly because
Re: [linux-dvb] Dazzle* TV Stick supported?
Hi, On 9/12/07, Pepe [EMAIL PROTECTED] wrote: I've just bought a dvb-t usb stick (Dazzle* TV Stick, identified in windows as Pinnacle PCTV 71e). Is this device supported on linux? I can't find anything about it. what does lsusb and usbview (just copy the content of the window) show up? Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Userspace tuner
Let's add the LKML to this. On 9/13/07, Markus Rechberger [EMAIL PROTECTED] wrote: On 9/12/07, Mauro Carvalho Chehab [EMAIL PROTECTED] wrote: Markus, Em Ter, 2007-08-14 às 16:31 +0200, Markus Rechberger escreveu: Following patch adds the possibility to implement tuner drivers in userspace. As you asked me about userspace driver, at Linux Conf Europe, let me give you my feedback about it. On Linux, userspace-to-kernelspace APIs are meant to be forever. This means that, once a newer API is created, this should remain supported for all future versions. So, such APIs should be carefully analyzed and accepted by the community, before going to mainstream. The V4L and DVB API is stable at the moment because it's at a stage which is sufficient for older devices but not sufficient for newer devices anymore. To support newer device it needs a change. I don't see any technical reason why tuner drivers should be moved to userspace. Looking at xc3028 device, the driver is very simple and doesn't require any special treatment that it isn't possible to be done at kernel. There are already some implementations on kernelspace that works fine. As from my side to support the xceive driver properly it needs a rewrite and a proper API description. Since it's not possible to discuss any API changes I will work around at least for those devices which I can support for. On the other hand, a TV driver without a tuner is a broken driver. With parts of the driver being at userspace, this means to add undesired complexity at the drivers architecture, while not bringing any benefit. If you look at V4L history, the first drivers started at userspace, being migrated to kernelspace, where we have the proper scenario for managing those devices. Another aspect that should be analyzed is what is desired by the community: don't get me wrong but the existing community is rather small and kicking off people who are interested in changing things. I recently had a talk with someone and I've been told that I'm kicking off people. Guess why I kick off people? - because they do not contribute in a productive way which also means submitting patches. Optical useless changes don't make any difference at the functionality in the end. And my requirements are ignored constantly here. kernelspace tuners or userspace tuners. Keeping support for both at long term doesn't seem reasonable. The Linux community should decide what is the better way. Currently, only you are pushing for userspace tuners, mainly due to non-technical reasons. read the project site and you will see the reasons. http://mcentral.de/wiki/index.php/Userspace_tuner#Advantages Another advantage is that I have cygwin based code here which I can easily reuse with all that work I'm not going to reinvent the wheel even for newer devices which I work on. Almost all the other developers are comfortable with kernelspace tuners. So, creating an userspace interface just to make you happy is not the way we should go. I'm afraid of giving the people which are against what I submitted the responsibility over the project. Initially there was an RFC which didn't get commented either (well there was one useless comment, I tried to discuss it on IRC before with the same guy) after I implemented exactly what I proposed there I got the first non technical comments - also keep in mind that working on something costs alot of time and talking about something unknown is rather cheap. A final aspect is that having an userspace driver for tuner will mean that the kernel driver will depend on an userspace counterpart in order to work. This will allow a vendor with bad intentions to release a partially broken userspace driver, with limited capabilities, and a closed source driver for full support. This model is likely to occur, if you take a look at the past. For example: ATI and Nvidia closed source drivers, several soft modem drivers, some network drivers, ... Please go forward and discuss the UIO driver with Greg Kroah Hartmann and the fuse driver with the other people. If companies want to release binary drivers they can easily use the existing code put it into an RPM or DEB package and Ubuntu will pick it up. With all those issues, I'm against to add an userspace interface for tuners. I'm against how the project works out at the moment and how it worked out in history. Exactly this way will kick off companies to be interested in future like Avermedia. A driver can easily be written within a few weeks and I've been struggling with it for 2 years(!!!) now just for nothing finally telling me that some guys want to steal my code and move it to kernelspace although it would raise more complications with upcoming and current devices which have even more requirements. I spent more time in rewriting and discussing everything than to get any of those
Re: [linux-dvb] Problem about the video_mux function.
On 9/13/07, kevin liu [EMAIL PROTECTED] wrote: Dear Markus: I am studying the em28xx source code. But I am puzzled by the function video_mux. It seems that the function does nothing there. Could you explain it ? video_mux is a video input selector in the em28xx. The value usually gets passed forward to the tvp5150 or saa7115. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Userspace tuner
Hi, On 9/13/07, Dâniel Fraga [EMAIL PROTECTED] wrote: Well, I'd like to see Linus' opinion about this, because while programmers keep discussing this, users are waiting forever... so if Markus has a concrete and better solution, why don't use it? And as far as I know, Markus is the programmer who is most interested in this code. I didn't see anybody else in the world doing his work... And I always had a impression that if most of things could be done in user space, than it will be better (for example, devfs - udev). Why do everything in kernel space? Lets put *less* code in the kernel, not more code. And besides that, code in user space can be changed easily. Code in kernel has to wait a long time for Linus to accept (*if* he accepts). It's not only about userspace here, some hardware needs newer features discussing those requirements (as I did with Mauro a while ago through Mail) end up nowhere. It was just about Analogue Audio standards. There are a few ways to solve that problem but in the end nothing came up which would have met that issue, although the solution I proposed didn't seem to be good enough either for him. Regarding binary drivers just read: http://www.linuxtv.org/v4lwiki/index.php/Avermedia it has been like that for years and I expect Avermedia to finally just remove their modules. I don't even see that Avermedia is the evil company by releasing the binary modules here. They are just at a bad position since the tunercode in that driver which comes from another company puts these restrictions onto everything. We currently have an implementation that works, although it works by downloading several firmwares for several devices or even several countries. This is not what I want to have in future since it's not needed and it's also hard to manage for distributors. All those differences could be adjusted by software even without module parameter hacks. The basic idea behind the Userspace drivers is since there's another project which should add a userspace library infront of video4linux devicenodes this library could directly reuse for example the userspace tuning, demodulator or videodecoder code by using for example the i2c-dev infrastructure. This would lateron make the kernelstub which I'm integrating for the em28xx obsolete (which I'm fine with), although such a library could directly reuse the userspace code without any code changes. However the others want to manage their devices I don't want to force anyone to do something although I aim at getting the devices which I received by several vendors last year integrated properly. Those companies are not only focussed in selling their devices in european or american countries only. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] em28xx tv support under linux kernel.
On 9/10/07, kevin liu [EMAIL PROTECTED] wrote:
Dear Mako:
I am studying the em28xx codes under Linux kernel(2.6.20). It
seems that there is no ATSC or NTSC support.
In em28xx-card.c, it defines em28xx_boards array to specify the tv
card the driver can support, struct em28xx_input indicates the tv
input method, but in the em28xx_boards, there is no struct that
includes EM28XX_VMUX_TELEVISION.
I got puzzled by the driver now.
:{
Hi Kevin,
you might have a look at
http://mcentral.de/wiki/index.php/Em2880
after doing some cleanup I will commit some newer code this week
basically the implementation on mcentral.de takes care about alot
extra things.
Anyway the logs which you sent previously does not really show up what
device it is about (it moreover shows up that you own a device which
is supported by dvb_usb)
could you submit an lsusb output?
Markus
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] em28xx tv support under linux kernel.
On 9/10/07, Markus Rechberger [EMAIL PROTECTED] wrote:
On 9/10/07, kevin liu [EMAIL PROTECTED] wrote:
Dear Mako:
I am studying the em28xx codes under Linux kernel(2.6.20). It
seems that there is no ATSC or NTSC support.
In em28xx-card.c, it defines em28xx_boards array to specify the tv
card the driver can support, struct em28xx_input indicates the tv
input method, but in the em28xx_boards, there is no struct that
includes EM28XX_VMUX_TELEVISION.
I got puzzled by the driver now.
:{
Hi Kevin,
you might have a look at
http://mcentral.de/wiki/index.php/Em2880
after doing some cleanup I will commit some newer code this week
basically the implementation on mcentral.de takes care about alot
extra things.
Anyway the logs which you sent previously does not really show up what
device it is about (it moreover shows up that you own a device which
is supported by dvb_usb)
could you submit an lsusb output?
Just as a reference, I'm refering to the mail which got submitted
earlier to the em28xx ML; if it's still about the same device it's not
supported by the em28xx.
http://www.mail-archive.com/linux-dvb%40linuxtv.org/msg24925.html
Markus
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Port of em28xx and xc3028 to new hybrid tuner framework.
On 9/7/07, Michael Krufky [EMAIL PROTECTED] wrote: Aidan Thornton wrote: Hi, In the hope of having a driver that fits better with the v4l-dvb trunk than the currently available options, I've ported the analog parts of Markus Rechberger's em28xx and xc3028 drivers to the new hybrid tuner framework. (The analog bits are similar enough to his framework that this was fairly easy.) It hasn't been tested with anything other than the analog TV in on my HVR-900 (USB ID 2040:6500), so YMMV. The repository is at http://www.makomk.com/hg/v4l-dvb-makomk for anyone feeling brave. Digital is not supported as yet - I haven't even tried to get em2880_dvb working, and the xc3028 support is probably broken. (I'm unsure how to get the bandwidth setting in xc3028 and how to tell if the client wants DVB-T, ATSC or something else.) Any suggestions and comments are welcome. Please take a look at the xc3028-fe.c file in the following patch: http://www.linuxtv.org/~mkrufky/xc-bluebird.patch You can use the logic used in that patch to determine ATSC / DVB-T / etc ...we might want to change this after multiproto is merged (if that happens anytime soon), because better options may be available at that point. I was thinking of redoing that xc3028-fe module to include analog support soon, but if you're going to to work on it instead, it makes life easier for me :-) I acknowlidge what you're doing there although the driver itself will use the userland drivers even for upcoming versions which use different i2c clientchips as the em28xx does at the moment. All the upcoming drivers will be opensourced, just to avoid any doubts. This also has to be concerned about backward compatibility: http://mcentral.de/wiki/index.php/Bugtracker#i2c_dev_problem this is also a problem about the inkernel hybrid design, the em28xx uses the userland implementation since the current xceive reference drivers use floating point algorithms. Since those reference drivers also include sample board configurations for different boards I'll moreover use these ones and work on other things instead of reinventing the wheel. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Kernelspace floating pointer - was Re: Port of em28xx and xc3028 to new hybrid tuner framework.
On 9/8/07, Mauro Carvalho Chehab [EMAIL PROTECTED] wrote: Markus wrote: the em28xx uses the userland implementation since the current xceive reference drivers use floating point algorithms. The usage of FP on DVB drivers is something that have been discussed for quite a long time at the community. I've asked Linus about the possibility of having a kernelspace driver using floating point. This may eventually happen (and, in fact, it already happens on a few drivers). There are, however, two points to consider: a) care should be taken to preserve FP state by the driver, since kernel won't do this by itself. This probably means that this may not be so fast as userspace calculation (although I suspect that it will be faster enough for the current needs); b) FP is processor dependent. So, old 80386 processors without FP instructions shouldn't work (IMO, this is not an issue ). Also, maybe we may have some troubles on a few non-x86 architectures (ARM ?). As you know the userspace tuner framework is capable of solving this and even more problems. http://mcentral.de/wiki/index.php/Userspace_tuner Although I'm waiting for an ack from several companies to reuse their tuner sample drivers without doing much conversion (so far there's an Ack for Quantek tuners) In case of the userspace framework better see the em28xx driver as a field test I won't submit an Ack for something else since I'm doing ongoing support for newer silicons (which are not only limited to Xceive based devices) Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Cinergy HT USB XE
Hi, On 9/3/07, Holger Dehnhardt [EMAIL PROTECTED] wrote: Hello, I buyed a Cinergy HT USB XE stick, because it is mentioned in the wiki as a supported device - but I do not find a way to get it working. I searched this mailing list and after that tried to find the USB id (0ccd:0058 TerraTec Electronic GmbH) in the source code, but I couldn't fint it. So does anyone knows, which driver could work. Is there a possibility to find out, which chip is working inside? I wouldn't hesistate to patch/extend the sources when anyone leads me in the right direction! Maybe you should have a look at: http://ventoso.org/luca/af9005/ Not sure if that driver will work with your device although you might give it a try. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] avermedia e506r mixed success
: AVerMedia Cardbus TV/Radio (E506R) [card=117,insmod option] [12987.77] saa7133[0]: board init: gpio is 222 [12987.897000] saa7133[0]: i2c eeprom 00: 61 14 36 f4 00 00 00 00 00 00 00 00 00 00 00 00 [12987.897000] saa7133[0]: i2c eeprom 10: 00 ff e2 0e ff 20 ff ff ff ff ff ff ff ff ff ff [12987.897000] saa7133[0]: i2c eeprom 20: 01 40 01 02 02 01 01 03 08 ff 00 ff ff ff ff ff [12987.898000] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [12987.898000] saa7133[0]: i2c eeprom 40: ff 65 00 ff c2 1e ff ff ff ff ff ff ff ff ff ff [12987.899000] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [12987.899000] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [12987.899000] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [12988.002000] tuner 0-0061: chip found @ 0xc2 (saa7133[0]) [12988.002000] /home/mimo/e506/v4l-dvb-experimental-20070523/v4l/tuner-core.c: setting tuner callback [12988.002000] tuner 0x61: Configuration acknowledged [12988.002000] /home/mimo/e506/v4l-dvb-experimental-20070523/v4l/tuner-core.c: setting tuner callback [12988.002000] tuner 0x61: Configuration acknowledged [12988.002000] /home/mimo/e506/v4l-dvb-experimental-20070523/v4l/tuner-core.c: setting tuner callback [12988.049000] /home/mimo/e506/v4l-dvb-experimental-20070523/v4l/xc3028-tuner.c: attach request! [12988.049000] /home/mimo/e506/v4l-dvb-experimental-20070523/v4l/tuner-core.c: xc3028 tuner successfully loaded [12988.074000] saa7133[0]: registered device video0 [v4l2] [12988.075000] saa7133[0]: registered device vbi0 [12988.075000] saa7133[0]: registered device radio0 [12988.08] saa7134 ALSA driver for DMA sound loaded [12988.08] saa7133[0]/alsa: saa7133[0] at 0x3c00 irq 11 registered as card -1 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- Markus Rechberger ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- Markus Rechberger ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [RFC] Hybrid tuner refactoring, phase 1
On 8/27/07, Steven Toth [EMAIL PROTECTED] wrote: Steven Toth wrote: MikeW wrote: Michael Krufky mkrufky at linuxtv.org writes: For the past few months, I've been working on refactoring the analog tuner.ko module, such that all I never saw the original RFC posting on the ML. What was the date on this original thread? - Steve Again, I never saw the original message based on this subject, where is it? There's nothing beside this thread here. Everything else is behind the visible scene closed for others. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [patch] dvb_net hotplugging support
On 8/17/07, Oliver Endriss [EMAIL PROTECTED] wrote:
Markus Rechberger wrote:
Since this didn't get commented here, Trent did that patch already 2
months ago but it's not included yet. So I recommend to include his
patch.
http://article.gmane.org/gmane.linux.kernel/543689
Acked-by: Markus Rechberger [EMAIL PROTECTED]
Are you talking about this tiny patch?
yes.
--- a/linux/drivers/media/dvb/dvb-core/dvb_net.c Fri Jun 08 08:58:41 2007
-0300
+++ b/linux/drivers/media/dvb/dvb-core/dvb_net.c Fri Jun 15 15:34:08 2007
-0700
at at -1502,18 +1502,9 at at static int dvb_net_close(struct
inode *i
struct dvb_device *dvbdev = file-private_data;
struct dvb_net *dvbnet = dvbdev-priv;
- if (!dvbdev)
- return -ENODEV;
-
- if ((file-f_flags O_ACCMODE) == O_RDONLY) {
- dvbdev-readers++;
- } else {
- dvbdev-writers++;
- }
-
- dvbdev-users++;
-
- if(dvbdev-users == 1 dvbnet-exit==1) {
+ dvb_generic_release(inode, file);
+
+ if(dvbdev-users == 1 dvbnet-exit == 1) {
fops_put(file-f_op);
file-f_op = NULL;
wake_up(dvbdev-wait_queue);
If yes,
Acked-by: Oliver Endriss [EMAIL PROTECTED]
Btw, why is this patch important? Basically it doesn't change anything.
CU
Oliver
--
VDR Remote Plugin 0.3.9: http://www.escape-edv.de/endriss/vdr/
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
--
Markus Rechberger
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] add device node locking possibility to dvbcore
On 8/17/07, Oliver Endriss [EMAIL PROTECTED] wrote: Steven Toth wrote: Steven Toth wrote: Markus Rechberger wrote: On 8/9/07, Steven Toth [EMAIL PROTECTED] wrote: Markus Rechberger wrote: On 8/9/07, Steven Toth [EMAIL PROTECTED] wrote: Markus Rechberger wrote: Following patch adds a rather primitive way to temporary lock dvb devicenodes, this can be useful for hybrid devices which use the video4linux framework for the analogue TV part and the dvb framework for digital TV if only one mode can be accessed at a time. Signed-off-by: Markus Rechberger [EMAIL PROTECTED] Call me dumb but I don't understand how this patch helps v4l devices. :) Allocation/management of a single card resource doesn't belong inside the dvb framework, these answers need to come from the bridge-frameworks (via callbacks from dvb-core or the analog equivalent) who are better placed to make the decision about hybrid tuners, bus capacity or allocation, in use devices. As a working example, I added similar support in my older HVR3000 tree where two frontends share a single transport bus. The code is old but it demonstrates a solution, much the my earlier patches for shared DVB/Blackbird boards also. I understand how this patch helps the current dvb tree, it stops multiple people opening a device but that's it. ... Or, maybe I've just missed to point. Hi Steve, the bridge framework triggers locking these filehandles. http://mcentral.de/hg/~mrec/v4l-dvb-experimental/file/c0817d73a2a9/linux/drivers/media/video/em28xx/em28xx-video.c line 434 this locks the dvb nodes if someone tries to open the v4l devicenode, it first checks if there's still something active at the DVB side. http://mcentral.de/hg/~mrec/v4l-dvb-experimental/file/f9f3e6bdd6fc/linux/drivers/media/video/em28xx/em2880-dvb.c Line 471 - 484 if this would go into the dvb core we'd have a callback for locking the device nodes. Your comment about lines 471-484 make sense, but that code is not referenced via a callback (that I can see in the DVB patch) ... which is what I expected to see. To do this cleanly in the dvb-core (or any v4l-core) I suggest requires callbacks into the bridge-frameworks and I didn't see those callbacks clearly defined in either your original patch, or your follow up patches. I was pretty sure I did something similar for the DVB/MpegEncoder shared bus support. Have you seen this? http://linuxtv.org/hg/~stoth/hvr3000/rev/4b846f1d939b Or more importantly this: http://linuxtv.org/hg/~stoth/hvr3000/rev/a619436699cc Can we just re-use that? Since I don't see any move forward from anyone again, can you extract that locking callback and submit it independently? I can work around the issue that the dvb core still tries to access DVB components after a device has been closed, although you might have to verify that issue within your drivers too. Sure, I'll prepare a patch later this evening. The ts_bus_ctrl function pointer / callback is already in the mainline, check dvb_frontend.c for more details. You shouldn't need a patch from me. ACK, should be enough to do this kind of locking. Furthermore, with this callback, the dvb_frontend_active() routine from '[linux-dvb] [PATCH] function for checking if the dvb framework is idle' is not required at all. The callback is aware whether the frontend is running or not... As far as I've seen the callback will be called as soon as the device gets closed, even though the thread might still be spinning in the background and the subsystem might still access DVB components, this is why dvb_frontend_active is still needed. Closing the devicenode and that callback doesn't mean that the device is idle. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Userspace tuner
On 8/17/07, Henk [EMAIL PROTECTED] wrote: There's also some responsibility by the users: Users should THINK before they buy unsupported devices. If possible buy devices that are supported by mainline. This is the only way we can convince manufactures to contribute to the Linux community. On Fri, Aug 17, 2007 at 01:09:19AM -0300, Daniel Fraga wrote: That's the problem. While the developers discuss these things, the users are waiting forever. And i think that if Linux really wants to support well most of the devices, something should be done. And remember: some of these developers do this in their spare time without payment. As a user you cannot make any demands on these people. Otherwise it doesn't make sense the driver development because when it finally is done, the device is obsolete and nobody will be using it. So driver development should always be as fast as possible, because the market (and users) won't wait for Linux developers to code the driver. Also don't blame the developers, blame the companies withholding basic information on how to program these device. I know, I know, it has been done with the good will of some programmers, without help of manufacturers, but we should ask: so why programmers are doing this? What's the objective? - Fun, - unlock extended product features, - long term product support. - Freedom and ownership, a GNU/Linux system will put control in the hands of the user. - Technical advancement of your favorite OS. If it was not by Markus' effort, I couldn't use my Xceive based board, so I support his initiative. And as far as I know, he's the only programmer working on this specific tuner. To sum up: there's no time to waste. Linux needs more code and less discussion. Code development in the Linux framework is basically an effort into bringing humans together into cooperation. I think that Markus is now tied to companies by legal agreements. So even if differences between linuxtv and Marcus get resolved Marcus probably will not be allowed to release source code for some of the chips discussed. That is probably one of the reasons why there's a push for a userspace v4l framework. And we will end up with binary userspace drivers. From a users perspective it is probably good to have the device at least working under Linux, but it would be in my opinion even better if we would have modules in Linux mainline. So the userspace framework is an intermediate solution until we have a better alternatives. The reason is that the linuxtv project depends on people who have their own ideas and do not care about other solutions or temporary solutions to get things done, pulling the drivers to userspace adds more flexibility for upcoming devices. Also it's possible to provide one tuner binary for several distributions and kernel versions (most people grab binaries from debian, redhat, suse or whatever distributions and don't deal with sourcecode). The sourcecode can still be distributed. http://mcentral.de/wiki/index.php/Userspace_tuner#Advantages There has been a inkernel xc3028 driver available for years and it was intended to go to mainline even though it got denied for those years. Still that driver needs a firmware from userspace thus a inkernel driver would just be a dummy for that chip. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] function for checking if the dvb framework is idle
On 8/17/07, Mauro Carvalho Chehab [EMAIL PROTECTED] wrote: Allthough this patch is still in the queue of required patches. I would still like to see that one upstream since it would be required by a few drivers for checking if they're really idle. I agree with Obi, Mkrufky and Christoph. It seems to be better to handle lock control inside your driver. Please analyze mails I sent and review the code afterwards please answer this thread again. There are 2 issues one if the filehandle is closed the DVB thread is sometimes still spinning in the background (eg. if someone runs the DVB scan application) (I'm writing this the 3rd time now!). The other one that Steve's patch immediatelly unlocks the bridge after the node is closed. For me this issue is still open. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Userspace tuner
On 8/17/07, CityK [EMAIL PROTECTED] wrote: Dâniel Fraga wrote: I've been exchanging e-mails with Markus for months and he supported very well my board (cx88 chip with xc2028 tuner). Yes, Markus is very good (exceptionally good in fact) with helping users. But at the same time, I noticed that there's a disagreement between Markus and the maintainers and I think this is counterproductive. As far as I know there's a lot of code to be merged in the kernel and we, the users, are waiting for months to see that. If the maintainers keep discussing everything to death, it won't get any further. So please, let's work together and reach the objective. Markus Rechberger wrote: The reason is that the linuxtv project depends on people who have their own ideas and do not care about other solutions or temporary solutions to get things done Now Markus: a) That comment certainly isn't very cooperative or indicative of good will ... and most certainly not in concert with what many of your supporters wish (i.e. just look at the concluding sentence in Daniel's comment). I previously told you once already, in a private email, that if you have truly moved on from LinuxTV, then leave it at that, and stop with the parting shots/insults. After all, you have yourself asked on several occasions on the mailing list for discussion on the matter to cease. So what's good for the goose should be good for the gander. b) Your comment is highly hypocritical on another level too. Consider comments from the [RFC/PATCHES] xc3028 hybrid tuner, em28xx/em2880-dvb, saa7134, cx88 thread on the mailing list this past May: Quoting M.Krufky ( from: http://www.linuxtv.org/pipermail/linux-dvb/2007-May/018016.html): If we decide to go this route, it will truly be the best compromise -- It will allow us to merge in support for the sixty some-odd devices that Markus is talking about, and it will allow for easy development of newer devices that use this tuner ic. The major benefit of this method is that it _will_ allow for us developers to put our heads together after the fact, and find better ways of supporting hybrid tuners. At that point, the pressure of 'trying to merge support for sixty devices' will be gone. Developers will finally be able to discuss this issue without the pressure of the current pending issues, and we _will_ be able to find a better solution. As far as I can tell, it seems that this is the only way for us to push this through, while not upsetting other developers. I will volunteer to keep up the maintenance of the xc3028-fe module until that proper, better solution is agreed upon. Quoting M. Rechberger (http://www.linuxtv.org/pipermail/linux-dvb/2007-May/018084.html): This is not acceptable for me anymore exactly this is and was not acceptable for me. that code was almost exactly what I've been told after the second approach (the mail you quoted over there). I've been told to not do it like that at the beginning after I submitted the first code and finally after wasting weeks of rewriting and rebasing more code on that I'm getting told to move the code back where it was at the very first beginning? Back then I moreover had the feeling I'm getting pushed around by clueless people (and it definitelly was like that), everyone dreamed about his own ideas. This is the reason why relying on linuxtv is very bad. Sometimes clueless people try to guide people who are looking for a solution, although the people who back then had no clue at the beginning also improved their knowledge as everyone did. I still have logs where I asked those people if there's any solution available logs from the very first beginning where everything was peaceful. The userspace tuners allows developers to add tuners independently of linuxtv and manage them by themself if they don't want to submit them officially, also it opens the possibility that people can do whatever _they_ want in userspace adding more features and taking the advantage of the userspace environment. It will avoid discussions with people who might misguide them (this also happened with me when I first tried to discuss some issues - I enjoyed Johannes statement once which was something like this would mean that the work gets manipulated). Markus As I stated in my last message in this thread, and as others have stated before on several occasions, temporary solutions to get things done were available, only you choose not to follow such courses.Live with that decision and follow your path. But don't pretend it was otherwise. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- Markus Rechberger ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Userspace tuner
anyway it's history; we shouldn't waste more time on discussing what happened .. we could fill weeks by doing that. So to clear up some things: * regarding binary userspace drivers, if someone wants to write binary drivers he can do that already if he has enough knowledge and time, even without that framework. * the userspace drivers look almost the same as the inkernel drivers (in case of function callbacks) * the xceive driver is implemented in userspace and works with em28xx based devices and I currently have a patch for cx88 based devices which is beeing tested now by Daniel and myself... everything is opensource here. Markus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] add device node locking possibility to dvbcore
On 8/17/07, Oliver Endriss [EMAIL PROTECTED] wrote:
Markus Rechberger wrote:
On 8/17/07, Oliver Endriss [EMAIL PROTECTED] wrote:
Steven Toth wrote:
The ts_bus_ctrl function pointer / callback is already in the
mainline,
check dvb_frontend.c for more details. You shouldn't need a patch from
me.
ACK, should be enough to do this kind of locking.
Furthermore, with this callback, the dvb_frontend_active() routine from
'[linux-dvb] [PATCH] function for checking if the dvb framework is idle'
is not required at all. The callback is aware whether the frontend is
running or not...
As far as I've seen the callback will be called as soon as the device
gets closed, even though the thread might still be spinning in the
background and the subsystem might still access DVB components, this
is why dvb_frontend_active is still needed.
Closing the devicenode and that callback doesn't mean that the device is
idle.
Ok, this should be fixed. What about this patch:
diff -r dd58780b6fb4 linux/drivers/media/dvb/dvb-core/dvb_frontend.c
--- a/linux/drivers/media/dvb/dvb-core/dvb_frontend.c Thu Aug 09 16:30:39
2007 +0200
+++ b/linux/drivers/media/dvb/dvb-core/dvb_frontend.c Fri Aug 17 20:07:28
2007 +0200
@@ -596,6 +596,10 @@ restart:
mb();
dvb_frontend_wakeup(fe);
+
+ if (fe-ops.ts_bus_ctrl)
+ fe-ops.ts_bus_ctrl (fe, 0);
+
return 0;
}
as I wrote earlier the thread can be idle/closed even before the node
gets closed (you can test that with kaffeine, and you can test the
other case with the scan utility)
@@ -1101,9 +1105,10 @@ static int dvb_frontend_release(struct i
if ((file-f_flags O_ACCMODE) != O_RDONLY)
fepriv-release_jiffies = jiffies;
-
- if (fe-ops.ts_bus_ctrl)
- fe-ops.ts_bus_ctrl (fe, 0);
+ else {
+ if (fe-ops.ts_bus_ctrl)
+ fe-ops.ts_bus_ctrl (fe, 0);
+ }
can you explain this? to me it doesn't look right. Before it always
called ts_bus_ctrl and afterwards it has a dependency to the access
mode bits?
Markus
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
