How to build I2C_MUX in media_build as rtl28xxu depends on it ?
After recent changes, I cannot build rtl28xxu on systems with linux 2.6.32 or 3.2.0. rtl28xxu is one of the few drivers depending on I2C_MUX. Kconfig.kern lists I2C_MUX (correctly) as not in the kernel of the system. I don't know if it is possible to load a new module for that. Who can help me with this ? Antti Palosaari wrote: We need depend on I2C_MUX as rtl2832 demod used requires it. All error/warnings: warning: (DVB_USB_RTL28XXU) selects DVB_RTL2832 which has unmet direct dependencies (MEDIA_SUPPORT DVB_CORE I2C I2C_MUX) ERROR: i2c_add_mux_adapter [drivers/media/dvb-frontends/rtl2832.ko] undefined! ERROR: i2c_del_mux_adapter [drivers/media/dvb-frontends/rtl2832.ko] undefined! Reported-by: kbuild test robot fengguang...@intel.com Signed-off-by: Antti Palosaari cr...@iki.fi --- drivers/media/usb/dvb-usb-v2/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/media/usb/dvb-usb-v2/Kconfig b/drivers/media/usb/dvb-usb-v2/Kconfig index bfb7378..037e519 100644 --- a/drivers/media/usb/dvb-usb-v2/Kconfig +++ b/drivers/media/usb/dvb-usb-v2/Kconfig @@ -126,7 +126,7 @@ config DVB_USB_MXL111SF config DVB_USB_RTL28XXU tristate Realtek RTL28xxU DVB USB support - depends on DVB_USB_V2 + depends on DVB_USB_V2 I2C_MUX select DVB_RTL2830 select DVB_RTL2832 select MEDIA_TUNER_QT1010 if MEDIA_SUBDRV_AUTOSELECT -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Media_build broken by [PATCH RFC v3 5/5] m5mols: Implement .get_frame_desc subdev callback
);
+
+ return 0;
+}
+
+
static int m5mols_enum_mbus_code(struct v4l2_subdev *sd,
struct v4l2_subdev_fh *fh,
struct v4l2_subdev_mbus_code_enum *code)
@@ -615,6 +660,8 @@ static struct v4l2_subdev_pad_ops m5mols_pad_ops = {
.enum_mbus_code = m5mols_enum_mbus_code,
.get_fmt= m5mols_get_fmt,
.set_fmt= m5mols_set_fmt,
+ .get_frame_desc = m5mols_get_frame_desc,
+ .set_frame_desc = m5mols_set_frame_desc,
};
/**
diff --git a/drivers/media/i2c/m5mols/m5mols_reg.h
b/drivers/media/i2c/m5mols/m5mols_reg.h
index 14d4be7..58d8027 100644
--- a/drivers/media/i2c/m5mols/m5mols_reg.h
+++ b/drivers/media/i2c/m5mols/m5mols_reg.h
@@ -310,6 +310,7 @@
#define REG_JPEG 0x10
#define CAPP_MAIN_IMAGE_SIZE I2C_REG(CAT_CAPT_PARM, 0x01, 1)
+#define CAPP_JPEG_SIZE_MAX I2C_REG(CAT_CAPT_PARM, 0x0f, 4)
#define CAPP_JPEG_RATIO I2C_REG(CAT_CAPT_PARM, 0x17, 1)
#define CAPP_MCC_MODEI2C_REG(CAT_CAPT_PARM, 0x1d, 1)
--
Jan Hoogenraad
Hoogenraad Interface Services
Postbus 2717
3500 GS Utrecht
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Media_build broken by [PATCH RFC v3 5/5] m5mols: Implement .get_frame_desc subdev callback
Thanks. I see several drivers disabled for lower kernel versions in my Kconfig file. I am not sure how this is accomplished, but it would be helpful if the Fujitsu M-5MOLS 8MP sensor support is automatically disabled for kernel 3.6 I fixed it in my version by replacing SZ_1M by (1024*1024). I did not need the driver, but at least it compiled ... Sylwester Nawrocki wrote: Hello Jan, On 10/06/2012 05:24 PM, Jan Hoogenraad wrote: On my ubuntu 10.4 system Linux 2.6.32-43-generic-pae #97-Ubuntu SMP Wed Sep 5 16:59:17 UTC 2012 i686 GNU/Linux this patch breaks compilation of media_build. The constant SZ_1M is not defined in the includes on my system Do you know what can be done about this ? --- /home/jhh/dvb/media_build/v4l/m5mols_core.c: In function 'm5mols_set_frame_desc': /home/jhh/dvb/media_build/v4l/m5mols_core.c:636: error: 'SZ_1M' undeclared (first use in this function) /home/jhh/dvb/media_build/v4l/m5mols_core.c:636: error: (Each undeclared identifier is reported only once /home/jhh/dvb/media_build/v4l/m5mols_core.c:636: error: for each function it appears in.) Thanks for reporting this issue. You most likely don't need the M-5MOLS camera sensor driver on you system so one option is to just disable it at kernel config. Make sure CONFIG_VIDEO_M5MOLS is not set, it can be unselected at menuconfig - Device Drivers - Multimedia - Encoders, decoders, sensors and other helper chips Fujitsu M-5MOLS 8MP sensor support The below patch which is intended to fix this issue won't work for media drivers backport builds on kernels older than 3.6, so m5mols driver should not be built for kernel versions 3.6. 8--- From 3e138ea603c9e5102452554cb14e4b404ce306e0 Mon Sep 17 00:00:00 2001 From: Sylwester Nawrocki sylvester.nawro...@gmail.com Date: Sat, 6 Oct 2012 20:04:40 +0200 Subject: [PATCH] m5mols: Add missing #include linux/sizes.h Include linux/sizes.h header that is missing after commit ab7ef22419927 [media] m5mols: Implement .get_frame_desc subdev callback. It prevents possible build errors due to undefined SZ_1M. Reported-by: Jan Hoogenraad jan-conceptro...@hoogenraad.net Signed-off-by: Sylwester Nawrocki sylvester.nawro...@gmail.com --- drivers/media/i2c/m5mols/m5mols.h |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/media/i2c/m5mols/m5mols.h b/drivers/media/i2c/m5mols/m5mols.h index 4ab8b37..90a6c52 100644 --- a/drivers/media/i2c/m5mols/m5mols.h +++ b/drivers/media/i2c/m5mols/m5mols.h @@ -16,6 +16,7 @@ #ifndef M5MOLS_H #define M5MOLS_H +#include linux/sizes.h #include media/v4l2-subdev.h #include m5mols_reg.h -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: media_build error on header file not present in old linux in ivtv-alsa-pcm.c
Thanks. Ecxuse me for the previous mail. I could have searched the archive first: http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/54099/match=printk+h Andy Walls wrote: Jan Hoogenraad jan-conceptro...@hoogenraad.net wrote: I try to compile the media_build on an old Ubuntu Lucid system. 2.6.32-42-generic-pae #96-Ubuntu SMP Wed Aug 15 19:12:17 UTC 2012 i686 GNU/Linux The make job stops with /home/jhh/dvb/media_build/v4l/ivtv-alsa-pcm.c:29:26: error: linux/printk.h: No such file or directory make[3]: *** [/home/jhh/dvb/media_build/v4l/ivtv-alsa-pcm.o] Error 1 Apparently, this header file was not yet present in this version of linux. It is the only driver requesting this header file. Removing line 29 #include linux/printk.h fixes the problem. All compiles well then. -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Hi Jan, Hans Verkuil already noticed this and submitted a patch to remove the include. Regards, Andy -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
media_build directory error after patch dvb_frontend: implement suspend / resume
I try to compile the media_build on an old Ubuntu Lucid system. 2.6.32-42-generic-pae #96-Ubuntu SMP Wed Aug 15 19:12:17 UTC 2012 i686 GNU/Linux The make job stops with /home/jhh/dvb/media_build/v4l/dvb_usb_core.c: In function 'dvb_usb_data_complete_raw': /home/jhh/dvb/media_build/v4l/dvb_usb_core.c:224: error: implicit declaration of function 'dvb_dmx_swfilter_raw' /home/jhh/dvb/media_build/v4l/dvb_usb_core.c: In function 'dvb_usbv2_suspend': /home/jhh/dvb/media_build/v4l/dvb_usb_core.c:975: error: implicit declaration of function 'dvb_frontend_suspend' /home/jhh/dvb/media_build/v4l/dvb_usb_core.c: In function 'dvb_usbv2_resume_common': /home/jhh/dvb/media_build/v4l/dvb_usb_core.c:994: error: implicit declaration of function 'dvb_frontend_resume' This probably started after http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/52430/match=dvb_frontend_resume The media_build tree is confused with too many files with the same name: find linux -name \*front\* -ls 54788964 24 -rw-r--r-- 1 jhh jhh 12642 Aug 16 05:45 linux/drivers/media/dvb-core/dvb_frontend.h 54788973 80 -rw-r--r-- 1 jhh jhh 71787 Sep 14 05:45 linux/drivers/media/dvb-core/dvb_frontend.c 54397078 20 -rw-r--r-- 1 jhh jhh 12056 Sep 16 20:20 linux/drivers/media/dvb/dvb-core/dvb_frontend.h 54397083 68 -rw-r--r-- 1 jhh jhh 60558 Jun 8 2011 linux/drivers/media/dvb/dvb-core/dvb_frontend.c 5439 24 -rw-r--r-- 1 jhh jhh 13012 Aug 14 05:45 linux/include/linux/dvb/frontend.h The frontend.h and .c chosen in the build are older ones find v4l -name \*front\* -ls 54135379 76 -rw-r--r-- 1 jhh jhh 67636 Sep 21 17:47 v4l/.dvb_frontend.o.cmd 541339200 lrwxrwxrwx 1 jhh jhh50 Sep 21 18:13 v4l/dvb_frontend.h - ../linux/drivers/media/dvb/dvb-core/dvb_frontend.h 541339270 lrwxrwxrwx 1 jhh jhh50 Sep 21 18:13 v4l/dvb_frontend.c - ../linux/drivers/media/dvb/dvb-core/dvb_frontend.c 54136025 184 -rw-r--r-- 1 jhh jhh179558 Sep 21 17:47 v4l/dvb_frontend.o Do you know what to do about this situation ? -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: media_build directory error after patch dvb_frontend: implement suspend / resume
Thanks Antti: Maybe the media_build could clean out the linux subdirectories (e.g. drivers include sound) before the tar x command. Your rtl28xxu driver immediately works, even on this old system ! Thanks for that as well. I will remove the very outdated info I put onto the Wiki pages: http://linuxtv.org/wiki/index.php/Realtek_RTL2831U http://linuxtv.org/wiki/index.php/DVB-T_USB_Devices http://linuxtv.org/wiki/index.php/DVB-T_USB_Devices#Freecom_rev_4_DVB-T_USB_2.0_tuner Antti Palosaari wrote: On 09/21/2012 07:19 PM, Jan Hoogenraad wrote: I try to compile the media_build on an old Ubuntu Lucid system. 2.6.32-42-generic-pae #96-Ubuntu SMP Wed Aug 15 19:12:17 UTC 2012 i686 GNU/Linux The make job stops with /home/jhh/dvb/media_build/v4l/dvb_usb_core.c: In function 'dvb_usb_data_complete_raw': /home/jhh/dvb/media_build/v4l/dvb_usb_core.c:224: error: implicit declaration of function 'dvb_dmx_swfilter_raw' /home/jhh/dvb/media_build/v4l/dvb_usb_core.c: In function 'dvb_usbv2_suspend': /home/jhh/dvb/media_build/v4l/dvb_usb_core.c:975: error: implicit declaration of function 'dvb_frontend_suspend' /home/jhh/dvb/media_build/v4l/dvb_usb_core.c: In function 'dvb_usbv2_resume_common': /home/jhh/dvb/media_build/v4l/dvb_usb_core.c:994: error: implicit declaration of function 'dvb_frontend_resume' This probably started after http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/52430/match=dvb_frontend_resume The media_build tree is confused with too many files with the same name: find linux -name \*front\* -ls 54788964 24 -rw-r--r-- 1 jhh jhh 12642 Aug 16 05:45 linux/drivers/media/dvb-core/dvb_frontend.h 54788973 80 -rw-r--r-- 1 jhh jhh 71787 Sep 14 05:45 linux/drivers/media/dvb-core/dvb_frontend.c 54397078 20 -rw-r--r-- 1 jhh jhh 12056 Sep 16 20:20 linux/drivers/media/dvb/dvb-core/dvb_frontend.h 54397083 68 -rw-r--r-- 1 jhh jhh 60558 Jun 8 2011 linux/drivers/media/dvb/dvb-core/dvb_frontend.c 5439 24 -rw-r--r-- 1 jhh jhh 13012 Aug 14 05:45 linux/include/linux/dvb/frontend.h The frontend.h and .c chosen in the build are older ones find v4l -name \*front\* -ls 54135379 76 -rw-r--r-- 1 jhh jhh 67636 Sep 21 17:47 v4l/.dvb_frontend.o.cmd 541339200 lrwxrwxrwx 1 jhh jhh50 Sep 21 18:13 v4l/dvb_frontend.h - ../linux/drivers/media/dvb/dvb-core/dvb_frontend.h 541339270 lrwxrwxrwx 1 jhh jhh50 Sep 21 18:13 v4l/dvb_frontend.c - ../linux/drivers/media/dvb/dvb-core/dvb_frontend.c 54136025 184 -rw-r--r-- 1 jhh jhh179558 Sep 21 17:47 v4l/dvb_frontend.o Do you know what to do about this situation ? All that is due to drivers/media directory structure re-organization. Could you use clean directory for media_build.git? If you want use exiting media_build.git you should remove manually those old directories. regards Antti -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
media_build error on header file not present in old linux in ivtv-alsa-pcm.c
I try to compile the media_build on an old Ubuntu Lucid system. 2.6.32-42-generic-pae #96-Ubuntu SMP Wed Aug 15 19:12:17 UTC 2012 i686 GNU/Linux The make job stops with /home/jhh/dvb/media_build/v4l/ivtv-alsa-pcm.c:29:26: error: linux/printk.h: No such file or directory make[3]: *** [/home/jhh/dvb/media_build/v4l/ivtv-alsa-pcm.o] Error 1 Apparently, this header file was not yet present in this version of linux. It is the only driver requesting this header file. Removing line 29 #include linux/printk.h fixes the problem. All compiles well then. -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Fwd: 0bda:2838 Ezcap DVB USB adaptor - no device files created / RTL2831U/RTL2832U
This is the same problem why the tree on http://linuxtv.org/hg/~jhoogenraad/rtl2831-r2/ does not work for newer kernels. I have decided AGAINST making it runnable on newer kernels, as there are some people working right now on a new release. Once the status becomes more clear, I'll update http://www.linuxtv.org/wiki/index.php/Realtek_RTL2831U Arthur Marsh wrote: Hi, I bought one of these things having seen the Linux penguin on the box and compiled the code from the http://jms.id.au/wiki/EzcapDvbAdapter web page on a quad core AMD64 machine using 3.0.0-rc5 Linux kernel and GCC 4.6.1 under Debian sid. On boot-up the device is at least partially recognised: [ 1.430924] usb 1-5: New USB device found, idVendor=0bda, idProduct=2838 [ 1.431005] usb 1-5: Product: RTL2838UHIDIR [ 6.245292] IR NEC protocol handler initialized [ 6.284327] IR RC5(x) protocol handler initialized [ 6.338049] IR RC6 protocol handler initialized [ 6.371470] IR JVC protocol handler initialized [ 6.448155] IR Sony protocol handler initialized [ 6.590577] lirc_dev: IR Remote Control driver registered, major 252 [ 6.591144] IR LIRC bridge handler initialized [ 7.085160] usbcore: registered new interface driver dvb_usb_rtl2832u $ lsmod|grep dvb dvb_usb_rtl2832u 111764 0 dvb_usb 18302 1 dvb_usb_rtl2832u dvb_core 77682 1 dvb_usb rc_core 18294 7 dvb_usb,ir_lirc_codec,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_rc5_decoder,ir_nec_decoder i2c_core 23876 7 dvb_usb,max6650,radeon,drm_kms_helper,drm,i2c_algo_bit,i2c_piix4 usbcore 119731 5 dvb_usb_rtl2832u,dvb_usb,ohci_hcd,ehci_hcd but apparently no device files are created (there is no /dev/dvb tree). Any suggestions for things to try to get this working welcome. Regards, Arthur. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Ubuntu 10.04 and trying to install drivers fot TV card Asus My Cinema U3000 hybrid
Ivo: type sudo apt-get install libproc-processtable-perl The message is confusing to say the least. I promised Mauro to update the code to yield better messages, but did not get around to do that. see thread change in build .sh due to Pulseaudio device removal / Yours, Ivo Válek wrote: Hello, acc. to instructions on this internet page http://www.linuxtv.org/wiki/index.php/How_to_install_DVB_device_drivers I tried to install some driver for TV card, but I got an order to contact You. enclosed please see printscreen of my Terminal... Could You help me please? I'm not experienced PC user, especially Linux... thanks! Ivo -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Ubuntu 10.04 and trying to install drivers fot TV card Asus My Cinema U3000 hybrid
Could you re-try with the current media_build ? Jan Hoogenraad wrote: Ivo: type sudo apt-get install libproc-processtable-perl The message is confusing to say the least. I promised Mauro to update the code to yield better messages, but did not get around to do that. see thread change in build .sh due to Pulseaudio device removal / Yours, Ivo Válek wrote: Hello, acc. to instructions on this internet page http://www.linuxtv.org/wiki/index.php/How_to_install_DVB_device_drivers I tried to install some driver for TV card, but I got an order to contact You. enclosed please see printscreen of my Terminal... Could You help me please? I'm not experienced PC user, especially Linux... thanks! Ivo attachment: jan-verisign.vcf
Re: RTL2831U driver updates
Can I put this somewhere in the git archive at the linuxtv site, so that we can share and have version control ? Maxim Levitsky wrote: On Tue, 2011-06-21 at 01:22 +0300, Antti Palosaari wrote: It is Maxim who have been hacking with RTL2832/RTL2832U lately. But I think he have given up since no noise anymore. I have taken now it again up to my desk and have been hacking two days now. Currently I am working with RTL2830 demod driver, I started it from scratch. Take sniffs, make scripts to generate code from USB traffic, copy pasted that to driver skeleton and now I have picture. Just implement all one-by-one until ready :-) I think I will implement it as minimum possible, no any signal statistic counters - lets add those later if someone wants to do that. USB-bridge part is rather OK as I did earlier and it is working with RTL2831U and RTL2832U at least. No remote support yet. I hope someone else would make missing driver for RTL2832U demod still... Fine! In about month, after exams, I hope I will work on this to finish at least RTL2832/FC0012. For reference, this is the code I did so far. Best regards, Maxim Levitsky -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: RTL2831U driver updates
Thanks. Do you know more about this subject ? We do have specs about the chipset, but http://linuxtv.org/downloads/v4l-dvb-apis/remote_controllers.html#Remote_controllers_Intro only mentions lirc, not rc-core. This is about where my knowledge stops, however. rc-core is only mentioned shortly in: http://linuxtv.org/wiki/index.php/Remote_Controllers Steffen Barszus wrote: 2011/6/21 Jan Hoogenraadjan-conceptro...@hoogenraad.net: and add the IR remote interface, based on the LIRC framework. It actually should yield little code, and mainly requires a) understanding of LIRC and b) comparing code tables to that the in-kernel code tables can be re-used. sorry for the noise , but i guess you mean rc-core not Lirc -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: RTL2831U driver updates
Antti: You are great ! So as far as I am concerned, it would be great if one of the others could use up your work on the USB bridge, and add the IR remote interface, based on the LIRC framework. It actually should yield little code, and mainly requires a) understanding of LIRC and b) comparing code tables to that the in-kernel code tables can be re-used. Note that Zdenek Styblik seems to have received updates from Realtek THIS month http://wiki.zeratul.org/doku.php?id=linux:v4l:realtek:start He has posted a Ver 2.2.0 of the driver at: http://www.turnovfree.net/~stybla/linux/v4l-dvb/lv5tdlx/ It supports the RTL2832U and RTL2836 and way more tuners (MT2266 FC2580 TUA9001 and MXL5007T E4000 FC0012 tda18272 fc0013) However, the code is not split up. Antti Palosaari wrote: It is Maxim who have been hacking with RTL2832/RTL2832U lately. But I think he have given up since no noise anymore. I have taken now it again up to my desk and have been hacking two days now. Currently I am working with RTL2830 demod driver, I started it from scratch. Take sniffs, make scripts to generate code from USB traffic, copy pasted that to driver skeleton and now I have picture. Just implement all one-by-one until ready :-) I think I will implement it as minimum possible, no any signal statistic counters - lets add those later if someone wants to do that. USB-bridge part is rather OK as I did earlier and it is working with RTL2831U and RTL2832U at least. No remote support yet. I hope someone else would make missing driver for RTL2832U demod still... Antti -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: change in build .sh due to Pulseaudio device removal /
Mauro: You are completely right. Getting the packages automatically is very user-friendly. Furthermore, this will make media_build a great place to start of users stuck with older kernels. On Ubuntu, the package name is libproc-processtable-perl the command to install it is (on Ubuntu, usually no root user is used, but rather per command invokation). The command for installation will be: sudo apt-get install libproc-processtable-perl There is no /etc/system-release on my system However, there is a file /etc/lsb-release cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=10.04 DISTRIB_CODENAME=lucid DISTRIB_DESCRIPTION=Ubuntu 10.04.2 LTS I will make an updated script in the next week. Mauro Carvalho Chehab wrote: Em 18-06-2011 14:20, Jan Hoogenraad escreveu: Mauro: The change in build.sh http://git.linuxtv.org/media_build.git?a=commitdiff;h=16cf0606fd59484236356e400a89c083e76da64b now requires installation of a Perl package Proc::ProcessTable that is not present in standard Ubuntu systems. I needed to run sudo aptitude install libproc-processtable-perl before I could continue after the change. Is there a way around this ? The media_build requires several packages that may not be present on some installation. The build.sh script has a logic to detect the missing parts and to output what's the missing requirements: echo Checking if the needed tools are present run ./check_needs.pl (I moved right now the perl-specific checks into check_needs.pl script) Unfortunately, package names are distro-specific. So, as I use only Fedora/RHEL here, the only hints it have are for them. From my experiences, between the rpm-based distros, the package names are either equal or very close, so such hints probably are probably good enough for Suse and Mandriva users. From what I understand, the standard Ubuntu repositories already provide a package for Proc::ProcessTable. So, the only thing that it is not ok is the package name hint. Could you please provide us a patch adding the Ubuntu (and likely Debian) package name? IMHO, the better would be to modify the check logic, in order to check what's the system, and provide a hint based on it. If the OS type is not found, then fall back to some default. I think that the LSB default to get the distribution is by reading /etc/system-release. Those are provided on RHEL6 and Fedora (plus, the old way: /etc/redhat-release). So, IMHO, all we need to do is to write a logic for the error report part of the check, that opens /etc/system-release, identify what's the distro, and provide the package name and some instructions on how to install the missing parts to the userspace. The right way for adding such logic would be to install the OS's on some VM with the minimum install, run the script and add the missing parts on it. Cheers, Mauro. -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
change in build .sh due to Pulseaudio device removal /
Mauro:
The change in build.sh
http://git.linuxtv.org/media_build.git?a=commitdiff;h=16cf0606fd59484236356e400a89c083e76da64b
now requires installation of a Perl package Proc::ProcessTable that is
not present in standard Ubuntu systems.
I needed to run
sudo aptitude install libproc-processtable-perl
before I could continue after the change.
Is there a way around this ?
Mauro Carvalho Chehab wrote:
During a long time, the removal of an alsa drivers were a problem
for me, and other developers reported to have the same problem.
With Hans de Goede help, I've got the pulseaudio syntax that allows
releasing an alsa device. With that, I've added a patch to the media
build that will automatically handle it, when make rmmod is
called.
Feel free to test and give some feedback. I suspect that the logic
will need more hacks, as pulseaudio-libs is not capable of detecting
the name of some USB alsa drivers.
The logic there is not optimized: It is basically running pacmd list-sources
and pacmd list-sinks several times, as I didn't have time yet to optimize.
I'll probably do it soon, after finishing some other things.
Enjoy!
Mauro.
From 16cf0606fd59484236356e400a89c083e76da64b Mon Sep 17 00:00:00 2001
From: Mauro Carvalho Chehabmche...@redhat.com
Date: Fri, 17 Jun 2011 16:48:04 -0300
Subject: [PATCH] rmmod.pl: Add a logic to allow removing audio modules with
pulseaudio
Pulseaudio keeps audio devices opened forever. In order to be able to
remove a device, pulseaudio needs to de-allocate the device.
Unfortunately, pulseaudio recognizes alsa drivers as module
(an integer number, not related to the device nodename), and only
allows module removal if running with user matches the console owner.
The logic inside rmmod.pl will now take the above into account. So,
it will detect if pulseaudio is running. If it is, it will:
1) list the pulseaudio modules with pacmd list-sinks
and pacmd list-sources
2) detect if any of the modules there is provided by a v4l device;
3) If they're provided by a video device, it removes the module with:
pactl unload-module 26
Even the above logic is not perfect as, due to a pulseaudio libs bug,
pulseaudio can't detect the name of em28xx-alsa driver, as it uses the
same interface as the video node. Similar hacks will may be needed
for other USB devices, like tm6000 and cx231xx.
Signed-off-by: Mauro Carvalho Chehabmche...@redhat.com
diff --git a/build.sh b/build.sh
index 60d0c26..3cc21f8 100755
--- a/build.sh
+++ b/build.sh
@@ -12,6 +12,8 @@ echo Checking if the needed tools are present
run ./check_needs.pl
echo Checking for Digest::SHA1 (package perl-Digest-SHA1)
run perl -MDigest::SHA1 -e 1
+echo Checking for Proc::ProcessTable (package perl-Proc-ProcessTable)
+run perl -MProc::ProcessTable -e 1
echo
echo
echo * This script will download the latest tarball and build it*
diff --git a/v4l/scripts/rmmod.pl b/v4l/scripts/rmmod.pl
index ed79cbe..53ea451 100755
--- a/v4l/scripts/rmmod.pl
+++ b/v4l/scripts/rmmod.pl
@@ -1,6 +1,8 @@
#!/usr/bin/perl
use strict;
use File::Find;
+use Proc::ProcessTable;
+
my %depend = ();
my %depend2 = ();
@@ -166,6 +168,69 @@ sub insmod ($)
}
}
+my @pulse;
+my $try_pulseaudio = 1;
+
+sub check_pulseaudio()
+{
+ my $t = new Proc::ProcessTable;
+ foreach my $p ( @{$t-table} ) {
+ push @pulse, $p-uid if ($p-cmndline =~m,/pulseaudio ,);
+ }
+ $try_pulseaudio = 0 if (!@pulse);
+
+ print Pulseaudio is running with UUID(s): @pulse\n;
+}
+
+sub unload_pulseaudio($)
+{
+ my $driver_name = shift;
+ my $cur_module;
+
+ return if (!$try_pulseaudio);
+
+ check_pulseaudio() if (!@pulse);
+ return if (!$try_pulseaudio);
+
+ for my $pid (@pulse) {
+# printf LANG=C sudo -u \\\#$pid pacmd list-sources |\n;
+ open IN, LANG=C sudo -u \\\#$pid pacmd list-sources |;
+ while (IN) {
+ $cur_module = $1 if (/^\s*module:\s*(\d+)/);
+
+ if (/^\s*alsa.driver_name\s*=\s*(.*)/) {
+ if ($1 eq $driver_name) {
+ print LANG=C sudo -u \\#$pid pactl
unload-module $cur_module\n;
+ system (LANG=C sudo -u \\#$pid pactl
unload-module $cur_module);
+ }
+ next;
+ }
+
+ # Special case: em28xx sometimes use a Vendor Class at
+ # the same interface as the video node. Pulseaudio can't
+ # get the driver name in this case
+ if (/^\s*alsa.card_name\s*=\s*Em28xx/) {
+ print LANG=C sudo -u \\#$pid pactl unload-module
$cur_module\n;
+ system (LANG=C sudo -u \\#$pid pactl unload-module
$cur_module);
+
dvb_usb symbols from media_build disagree on Linux 2.6.32-32
Trying to compile and install media_build on an Ubuntu Lucid computer Linux 2.6.32-32-generic-pae #62-Ubuntu SMP Wed Apr 20 22:10:33 UTC 2011 i686 GNU/Linux I can compile, but cannot use dvb-usb. With the snapshot of june 11th, I was able to do this with no problem. Can somebody help me ? sudo modprobe dvb-usb yields FATAL: Error inserting dvb_usb (/lib/modules/2.6.32-32-generic-pae/kernel/drivers/media/dvb/dvb-usb/dvb-usb.ko): Unknown symbol in module, or unknown parameter (see dmesg) dmesg [678605.646889] WARNING: You are using an experimental version of the media stack. [678605.646891] As the driver is backported to an older kernel, it doesn't offer [678605.646892] enough quality for its usage in production. [678605.646893] Use it with care. [678605.646893] Latest git patches (needed if you report a bug to linux-media@vger.kernel.org): [678605.646894] 5b5c6e080e7d3b484536fa5c96b78ff53df83e84 [media] marvell-cam: Basic working MMP camera driver [678605.646895] 7788a403987b5557e124f4cd76bfde5ffb804960 [media] marvell-cam: Allocate the i2c adapter in the platform driver [678605.646896] dc10bc206b121fcc6308438826a0c9c147fe5051 [media] marvell-cam: Right-shift i2c slave ID's in the cafe driver [678605.647853] dvb_usb: disagrees about version of symbol rc_register_device [678605.647855] dvb_usb: Unknown symbol rc_register_device [678605.648167] dvb_usb: disagrees about version of symbol rc_free_device [678605.648169] dvb_usb: Unknown symbol rc_free_device [678605.648398] dvb_usb: disagrees about version of symbol rc_allocate_device [678605.648400] dvb_usb: Unknown symbol rc_allocate_device [678605.648862] dvb_usb: disagrees about version of symbol rc_unregister_device [678605.648863] dvb_usb: Unknown symbol rc_unregister_device -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RTL2831U driver updates
Sascha: Thanks for the links Would you know how to contact poma ? http://www.spinics.net/lists/linux-media/msg24890.html I will be getting more info from Realtek soon. I did not realize that they were putting out updated drivers. Once the status becomes more clear, I'll update http://www.linuxtv.org/wiki/index.php/Realtek_RTL2831U Sascha Wüstemann wrote: Thomas Holzeisen wrote: Hi there, I tried to get an RTL2831U dvb-t usb-stick running with a more recent kernel (2.6.38) and failed. The hg respository ~jhoogenraad/rtl2831-r2 aborts on countless drivers, the rc coding seem have to changed a lot since it got touched the last time. The hg respository ~anttip/rtl2831u wont compile as well, since its even older. The recent git respositories for media_tree and anttip dont contain drivers for the rtl2831u. Has this device been abandoned, or is anyone working on it? greetings, Thomas There are still people working on it and there is new sources, e.g. look at http://www.spinics.net/lists/linux-media/msg24890.html at the very bottom. Worked like a charm at my system with kernel 2.6.39. I think, there will be announcements later at http://wiki.zeratul.org/doku.php?id=linux:v4l:realtek:start Greetings from Braunschweig, Germany. Sascha -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Media_build does not compile due to errors in cx18-driver.h, cx18-driver.c and dvbdev.c /rc-main.c
Hans, Mauro:
I have tried to compile the sources at git://linuxtv.org/media_build.git,
using build.sh
At
cx18-driver.h:659:
struct workqueue_struct *out_work_queue;
char out_workq_name[12]; /* cx18-NN-out */
struct workqueue_struct *out_work_queue;
char out_workq_name[12]; /* cx18-NN-out */
cx18-driver.c:718
a similar problem occurs: the following code block is repeated:
static int __devinit cx18_create_out_workq(struct cx18 *cx)
{
snprintf(cx-out_workq_name, sizeof(cx-out_workq_name), %s-out,
cx-v4l2_dev.name);
cx-out_work_queue = create_workqueue(cx-out_workq_name);
if (cx-out_work_queue == NULL) {
CX18_ERR(Unable to create outgoing mailbox handler threads\n);
return -ENOMEM;
}
return 0;
}
static int __devinit cx18_create_out_workq(struct cx18 *cx)
{
snprintf(cx-out_workq_name, sizeof(cx-out_workq_name), %s-out,
cx-v4l2_dev.name);
cx-out_work_queue = create_workqueue(cx-out_workq_name);
if (cx-out_work_queue == NULL) {
CX18_ERR(Unable to create outgoing mailbox handler threads\n);
return -ENOMEM;
}
return 0;
}
Furthermore, there is an error that is present in three sources:
At
./v4l/dvbdev.c:466: twice:
the escape sequence \\ sould be replaced with \
./rc-main.c:1131: twice:
the escape sequence \\ sould be replaced with \
./v4l/v4l2-dev.c:782: twice:
the escape sequence \\ sould be replaced with \
--
Jan Hoogenraad
Hoogenraad Interface Services
Postbus 2717
3500 GS Utrecht
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Media_build does not compile due to errors in cx18-driver.h, cx18-driver.c and dvbdev.c /rc-main.c
Andy: Something along the line of id already defined. I just corrected the code by removing the duplicate lines that are in the sources of the tar. The other 3 files have a bad escape sequence in a line saying that this is the backports. One backslash not removed in a script, I guess. Devin: The version does not matter for the cx18 problem: any compiler complains on duplicate lines. Anyway: 2.6.32-32-generic-pae #62-Ubuntu SMP Wed Apr 20 22:10:33 UTC 2011 i686 GNU/Linux Devin Heitmueller wrote: On Fri, Jun 10, 2011 at 8:34 AM, Andy Wallsawa...@md.metrocast.net wrote: What are the error messages? Tejun Heo made quite a number of workqueue changes, and the cx18 driver got dragged forward with them. So did ivtv for that matter. Just disable the cx18 driver if you don't need it for an older kernel. Regards, Andy Another highly relevant piece of information to know is what kernel Jan is running on. It is probably from before the workqueue changes. Devin -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Media_build does not compile due to errors in cx18-driver.h, cx18-driver.c and dvbdev.c /rc-main.c
Sorry; too fast a reaction; I did not realize that the build script creates a version per kernel, and that my messages thus become hard to trace. The cx18 doubles were clear. The one in the code file may be caused by v2.6.37_dont_use_alloc_ordered_workqueue.patch but I don't see the problem in the header file in that patch. Below the 3 non cx18 offending lines: line in v4l2-dev.c: printk(KERN_ERR WARNING: You are using an experimental version of the media stack.\n\tAs the driver is backported to an older kernel, it doesn't offer\n\tenough quality for its usage in production.\n\tUse it with care.\nLatest git patches (needed if you report a bug to linux-media@vger.kernel.org):\n\t75125b9d44456e0cf2d1fbb72ae33c13415299d1 [media] DocBook: Don't be noisy at make cleanmediadocs\n\t0fba2f7ff0c4d9f48a5c334826a22db32f816a76 Revert \\[media] dvb/audio.h: Remove definition for AUDIO_GET_PTS\\\n\t4f75ad768da3c5952d1e7080045a5b5ce7b0d85d [media] DocBook/video.xml: Document the remaining data structures\n); line in rc-main.c: printk(KERN_ERR WARNING: You are using an experimental version of the media stack.\n\tAs the driver is backported to an older kernel, it doesn't offer\n\tenough quality for its usage in production.\n\tUse it with care.\nLatest git patches (needed if you report a bug to linux-media@vger.kernel.org):\n\t75125b9d44456e0cf2d1fbb72ae33c13415299d1 [media] DocBook: Don't be noisy at make cleanmediadocs\n\t0fba2f7ff0c4d9f48a5c334826a22db32f816a76 Revert \\[media] dvb/audio.h: Remove definition for AUDIO_GET_PTS\\\n\t4f75ad768da3c5952d1e7080045a5b5ce7b0d85d [media] DocBook/video.xml: Document the remaining data structures\n); line in dvbdeb.c: printk(KERN_ERR WARNING: You are using an experimental version of the media stack.\n\tAs the driver is backported to an older kernel, it doesn't offer\n\tenough quality for its usage in production.\n\tUse it with care.\nLatest git patches (needed if you report a bug to linux-media@vger.kernel.org):\n\t75125b9d44456e0cf2d1fbb72ae33c13415299d1 [media] DocBook: Don't be noisy at make cleanmediadocs\n\t0fba2f7ff0c4d9f48a5c334826a22db32f816a76 Revert \\[media] dvb/audio.h: Remove definition for AUDIO_GET_PTS\\\n\t4f75ad768da3c5952d1e7080045a5b5ce7b0d85d [media] DocBook/video.xml: Document the remaining data structures\n); Jan Hoogenraad wrote: Andy: Something along the line of id already defined. I just corrected the code by removing the duplicate lines that are in the sources of the tar. The other 3 files have a bad escape sequence in a line saying that this is the backports. One backslash not removed in a script, I guess. Devin: The version does not matter for the cx18 problem: any compiler complains on duplicate lines. Anyway: 2.6.32-32-generic-pae #62-Ubuntu SMP Wed Apr 20 22:10:33 UTC 2011 i686 GNU/Linux Devin Heitmueller wrote: On Fri, Jun 10, 2011 at 8:34 AM, Andy Wallsawa...@md.metrocast.net wrote: What are the error messages? Tejun Heo made quite a number of workqueue changes, and the cx18 driver got dragged forward with them. So did ivtv for that matter. Just disable the cx18 driver if you don't need it for an older kernel. Regards, Andy Another highly relevant piece of information to know is what kernel Jan is running on. It is probably from before the workqueue changes. Devin attachment: jan-verisign.vcf
Re: rtl2832u support
Could the tree from http://linuxtv.org/hg/~jhoogenraad/rtl2831-r2 which is really just an older version of the same code, go into staging than as well ? For that one, I have the signoff by RealTek already. Mauro Carvalho Chehab wrote: Em 20-11-2010 20:37, Maxim Levitsky escreveu: Do we have a common agreement that this driver can go to staging as-is? If yes, I have patch ready, just need to know where to send it (It is around 1 MB). Yes, if people is interested on later fixing the issues. As Antti said he already broke the driver into more consistent parts, maybe his tree may be an start. I would like to volunteer to clean up the driver for eventual merge. At least I can start right away with low handing fruit. Ok, Seems fine for me. I have took the driver from http://www.turnovfree.net/~stybla/linux/v4l-dvb/lv5tdlx/20101102_RTL2832_2836_2840_LINUX+RC-Dongle.rar And it looks very recent, so that means that Realtek actually continues to develop it. The better would be to try to sync with Realtek to be sure that they'll continue to develop the upstream driver, after having it merged. Otherwise, someone will need to do the manual sync, and this can be very painful. Greg KH, maybe you know how to contact Realteck to figure out the best strategy in handling this code. Meanwhile, lets put that into staging. (The above driver doesn't compile due to changes in RC code, but it can be removed (that what I did for now) or ported to new rc-core which what I will do very soon). Just send the patches. The better is to submit them via linux-media, and say, at a TODO file, that patches for it should be submitted to linux-me...@vger.kernel.org. Something similar to drivers/staging/tm6000/TODO. Cheers, Mauro -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: rtl2832u support
I haven't seen any data sheets. At the other hand, Antti was able to create a separated (tuner vs demod) driver, except for IR. http://linuxtv.org/hg/~anttip/rtl2831u/ http://linuxtv.org/hg/~anttip/qt1010/ I haven't seen a data sheet, but I doubt if it would be of more use than using this example code. My mail contacts (latest in may 2008) focused on getting the code to work and on signing off the code. I'll give my mail contact a try, especially if you have questions that cannot be found in the current code base. Maxim Levitsky wrote: On Mon, 2010-12-06 at 16:45 +0100, Jan Hoogenraad wrote: Could the tree from http://linuxtv.org/hg/~jhoogenraad/rtl2831-r2 which is really just an older version of the same code, go into staging than as well ? Yes, but the problem is that due to shaddy license status of the 'windows' driver, I am afraid to look seriously at it. Up till now, I only experimented with IR code. Jan, since you have contacts with Realtek, maybe it would be possible to get datasheet for their hardware? And the above code is guaraneed not to work on my card because even their 'windows' driver v1.4 doesn't work here. Only 2.0 driver works. And you said that you couldn't seperate demod from bridge? Is that nessesary? I have seen few drivers that don't separate it in v4l source. Tuners are of course another story. Best regards, Maxim Levitsky For that one, I have the signoff by RealTek already. Mauro Carvalho Chehab wrote: Em 20-11-2010 20:37, Maxim Levitsky escreveu: Do we have a common agreement that this driver can go to staging as-is? If yes, I have patch ready, just need to know where to send it (It is around 1 MB). Yes, if people is interested on later fixing the issues. As Antti said he already broke the driver into more consistent parts, maybe his tree may be an start. I would like to volunteer to clean up the driver for eventual merge. At least I can start right away with low handing fruit. Ok, Seems fine for me. I have took the driver from http://www.turnovfree.net/~stybla/linux/v4l-dvb/lv5tdlx/20101102_RTL2832_2836_2840_LINUX+RC-Dongle.rar And it looks very recent, so that means that Realtek actually continues to develop it. The better would be to try to sync with Realtek to be sure that they'll continue to develop the upstream driver, after having it merged. Otherwise, someone will need to do the manual sync, and this can be very painful. Greg KH, maybe you know how to contact Realteck to figure out the best strategy in handling this code. Meanwhile, lets put that into staging. (The above driver doesn't compile due to changes in RC code, but it can be removed (that what I did for now) or ported to new rc-core which what I will do very soon). Just send the patches. The better is to submit them via linux-media, and say, at a TODO file, that patches for it should be submitted to linux-me...@vger.kernel.org. Something similar to drivers/staging/tm6000/TODO. Cheers, Mauro -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Compro VideoMate U90
Peter has found out about this device. It seems to have a qt1010 and rtl2831u in it. He reported some success with the driver from: http://linuxtv.org/hg/~anttip/qt1010/ Giles HEWITT wrote: Hi Jan, I read your reply on the comporo videomate driver thread from over a year ago: http://www.mail-archive.com/linux-media@vger.kernel.org/msg05107.html I have a pair of U80s (without the remote) and am experimenting with Mythbuntu again after lots of frustration with Microsoft Media Centre. lsusb gives id 185b:0150 Compro can you spare the time to let me know if I'm wasting mine ... thanks, Giles. -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: rtl2831-r2 still not working for Compro VideoMate U80
Could you try: http://linuxtv.org/hg/~anttip/qt1010/ Previous users of Compro VideoMate U80 has a qt1010 tuner, which required that branch. Ugnius Soraka wrote: Hi, I'd like to get in touch with driver developers, is there any way I could help make RTL2831U driver work with Compro VideoMate U80. I would like to actively participate. My programming skills are well below required to write kernel modules, so I know I would be no use there. But anything else, testing with VideoMate U80, sending debug logs, I think I could do that. I've tried http://linuxtv.org/hg/~jhoogenraad/rtl2831-r2 driver, it looked promising. U80 device was recognised as VideoMate U90, /dev/dvb entries were created. But when scanning it says there's no signal. Debug gives TPS_NON_LOCK, Signal NOT Present, rtd2830_soft_reset, etc. (I could post message log, if it's any use to somebody). U80 has a led which (on windows) shows if TV stick is tuned in and working, when scanning on linux it's always on. I've also tried to compile http://linuxtv.org/hg/~anttip/rtl2831u/ but for now it's based on old dvb tree and seems to be incompatible with new kernels (mine 2.6.34.7-0.3). Is anttip driver supposed to be included in kernel, but it looks like development is going slow. Thank you, Ugnius -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Confusing dmx_pes_type_t in dmx.h
The file dmx.h declares dmx_pes_type_t which is ONLY used in this header file. It is easy to make mistakes, as its member DMX_PES_OTHER resembles a similar symbol in demux.h from enum dmx_ts_pes: DMX_TS_PES_OTHER One problem was found because of Hans' compiler upgrade. I think it would be safer (because it is easy to make mistakes) to remove dmx_pes_type_t from dmx.h. Who knows more on this driver ? The found bug is fixed in the patch on: http://linuxtv.org/hg/~jhoogenraad/ubuntu-firedtv/rev/44751f6fba2f -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
patches for the Realtek rtl2831
Mauro Carvalho Chehab wrote: A side question: when do you intend to send us the patches for the Realtek rtl2831? Basically, I'm waiting for somebody to take up the task to include IR support in Antti's branches. I don't have the knowledge to do so. In the mean time, I just maintain the code from Realtek on a sync with mainline only base in hg, as the code is really sub-standard. http://www.linuxtv.org/wiki/index.php/Realtek_RTL2831U I have seen that Realtek keeps updating their Windows code, and the v4l port, at least for the RTL2832. I see the recipes to use that on many forums. Cheers, Mauro. -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Several linux-release dependent fixes (new and old)
Douglas: Based on the logs from Hans' builds, I have prepared some updates. Some of these might lead to undesired behavior of v4l on older or newer releases. All of these should reduce the number of warnings or errors in the logs below. Could you promote these changes to the git archive as well, if applicable ? http://linuxtv.org/hg/~jhoogenraad/ubuntu-firedtv/rev/199ff5830453 Hans Verkuil wrote: This message is generated daily by a cron job that builds v4l-dvb for the kernels and architectures in the list below. Results of the daily build of v4l-dvb: date:Wed Sep 29 19:00:10 CEST 2010 path:http://www.linuxtv.org/hg/v4l-dvb changeset: 15164:1da5fed5c8b2 git master: 3e6dce76d99b328716b43929b9195adfee1de00c git media-master: dace3857de7a16b83ae7d4e13c94de8e4b267d2a gcc version: i686-linux-gcc (GCC) 4.4.3 host hardware:x86_64 host os: 2.6.32.5 linux-2.6.32.6-armv5: WARNINGS linux-2.6.33-armv5: OK linux-2.6.34-armv5: WARNINGS linux-2.6.35.3-armv5: WARNINGS linux-2.6.36-rc2-armv5: ERRORS linux-2.6.32.6-armv5-davinci: WARNINGS linux-2.6.33-armv5-davinci: WARNINGS linux-2.6.34-armv5-davinci: WARNINGS linux-2.6.35.3-armv5-davinci: WARNINGS linux-2.6.36-rc2-armv5-davinci: ERRORS linux-2.6.32.6-armv5-ixp: WARNINGS linux-2.6.33-armv5-ixp: WARNINGS linux-2.6.34-armv5-ixp: WARNINGS linux-2.6.35.3-armv5-ixp: WARNINGS linux-2.6.36-rc2-armv5-ixp: ERRORS linux-2.6.32.6-armv5-omap2: WARNINGS linux-2.6.33-armv5-omap2: WARNINGS linux-2.6.34-armv5-omap2: WARNINGS linux-2.6.35.3-armv5-omap2: WARNINGS linux-2.6.36-rc2-armv5-omap2: ERRORS linux-2.6.26.8-i686: WARNINGS linux-2.6.27.44-i686: WARNINGS linux-2.6.28.10-i686: WARNINGS linux-2.6.29.1-i686: WARNINGS linux-2.6.30.10-i686: WARNINGS linux-2.6.31.12-i686: WARNINGS linux-2.6.32.6-i686: WARNINGS linux-2.6.33-i686: WARNINGS linux-2.6.34-i686: WARNINGS linux-2.6.35.3-i686: WARNINGS linux-2.6.36-rc2-i686: ERRORS linux-2.6.32.6-m32r: WARNINGS linux-2.6.33-m32r: OK linux-2.6.34-m32r: WARNINGS linux-2.6.35.3-m32r: WARNINGS linux-2.6.36-rc2-m32r: ERRORS linux-2.6.32.6-mips: WARNINGS linux-2.6.33-mips: WARNINGS linux-2.6.34-mips: WARNINGS linux-2.6.35.3-mips: WARNINGS linux-2.6.36-rc2-mips: ERRORS linux-2.6.32.6-powerpc64: WARNINGS linux-2.6.33-powerpc64: WARNINGS linux-2.6.34-powerpc64: WARNINGS linux-2.6.35.3-powerpc64: WARNINGS linux-2.6.36-rc2-powerpc64: ERRORS linux-2.6.26.8-x86_64: WARNINGS linux-2.6.27.44-x86_64: WARNINGS linux-2.6.28.10-x86_64: WARNINGS linux-2.6.29.1-x86_64: WARNINGS linux-2.6.30.10-x86_64: WARNINGS linux-2.6.31.12-x86_64: WARNINGS linux-2.6.32.6-x86_64: WARNINGS linux-2.6.33-x86_64: WARNINGS linux-2.6.34-x86_64: WARNINGS linux-2.6.35.3-x86_64: WARNINGS linux-2.6.36-rc2-x86_64: ERRORS linux-git-Module.symvers: ERRORS linux-git-armv5: ERRORS linux-git-armv5-davinci: ERRORS linux-git-armv5-ixp: ERRORS linux-git-armv5-omap2: ERRORS linux-git-i686: ERRORS linux-git-m32r: ERRORS linux-git-mips: ERRORS linux-git-powerpc64: ERRORS linux-git-x86_64: ERRORS spec-git: OK sparse: ERRORS Detailed results are available here: http://www.xs4all.nl/~hverkuil/logs/Wednesday.log Full logs are available here: http://www.xs4all.nl/~hverkuil/logs/Wednesday.tar.bz2 The V4L-DVB specification from this daily build is here: http://www.xs4all.nl/~hverkuil/spec/media.html -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html attachment: jan-verisign.vcf
Re: updated make_kconfig.pl for Ubuntu
Douglas:
I have an updated make_kconfig.pl for Ububtu on:
http://linuxtv.org/hg/~jhoogenraad/rtl2831-r2/file/cb34ee1c29fc/v4l/scripts/make_kconfig.pl
Could you test if make allyesconfig actually keeps FIREDTV enabled on a
non-Ubuntu system ?
If so, can you merge this version into the main stream ?
Mauro:
You are very right. I did not look far enough.
The expanded place where I expect the dma.h file would be (as I
/lib/modules/2.6.28-19-generic/build/include/config/ieee1394/dma.h
note that the letters el should be removed from your first expression
$dmahplace=$kernelsrc/include/config/ieee1394/dma.h;
needs to be:
$dmahplace=$kernsrc/include/config/ieee1394/dma.h;
Thanks a lot for helping !
As patch, relative to the diff you sent:
# HG changeset patch
# User Jan Hoogenraad jan-conceptro...@h-i-s.nl
# Date 1285695899 -7200
# Node ID 891128e7c3334e41f6c173ee5c01fddbce493b73
# Parent cb34ee1c29fc8891ad3792b3df76031a72e39b9d
Location fix
From: Jan Hoogenraad jan-conceptro...@h-i-s.nl
Location fix
Priority: normal
Signed-off-by: Jan Hoogenraad jan-conceptro...@h-i-s.nl
diff -r cb34ee1c29fc -r 891128e7c333 v4l/scripts/make_kconfig.pl
--- a/v4l/scripts/make_kconfig.pl Mon Sep 27 20:27:20 2010 +0200
+++ b/v4l/scripts/make_kconfig.pl Tue Sep 28 19:44:59 2010 +0200
@@ -688,10 +688,7 @@
# Check for full kernel sources and print a warning
sub dmahcheck()
{
- my $dmahplace= .$kernsrc;
- $dmahplace =~ s-^/lib/modules/--g;
- $dmahplace =~ s-/.*$--g;
-
$dmahplace=/usr/src/linux-headers-$dmahplace/include/config/ieee1394/dma.h;
+ my $dmahplace=$kernsrc/include/config/ieee1394/dma.h;
if (! -e $dmahplace) {
print EOF2;
Mauro Carvalho Chehab wrote:
Em 27-09-2010 17:45, Jan Hoogenraad escreveu:
Mauro:
On my system, the call to make_kconfig reads:
./scripts/make_kconfig.pl /lib/modules/2.6.28-19-generic/build
/lib/modules/2.6.28-19-generic/build 1
Using $kernelsrc yields the following error:
Global symbol $kernelsrc requires explicit package name at
./scripts/make_kconfig.pl line 694.
Using
$dmahplace=$kernsrc/include/config/ieee1394/dma.h;
yields the following INCORRECT expansion:
/lib/modules/2.6.28-19-generic/build/include/config/ieee1394/dma.h
this is the place where I am building into, which is different from the place
where Ubuntu places the include files from the package
Thus I built an expression to get:
/usr/src/linux-headers-2.6.28-19-generic/include/config/ieee1394/dma.h
as I described in the mail of yesterday.
Huh? Are you sure that Ubuntu doesn't have a symbolic link at
/lib/modules/2.6.28-19-generic/build pointing
to /usr/src/linux-headers-2.6.28-19-generic/?
If it doesn't have, then all compat checks done by make_config_compat.pl would
fail.
Now, I realize that the header files could ALSO be present in the build
directory, so there should be a check on that as well, as otherwise the FIREDTV
is incorrectly disabled on other distros, or source builds.
Yes, and I know all of this is ugly
It is not just ugly. It will break compilation on Ubuntu with:
$ make release DIR=some dir
Cheers,
Mauro
--
Jan Hoogenraad
Hoogenraad Interface Services
Postbus 2717
3500 GS Utrecht
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: updated make_kconfig.pl for Ubuntu
Douglas:
Can you push the updated make_kconfig.pl ?
It is in its own HG tree on:
http://linuxtv.org/hg/~jhoogenraad/ubuntu-firedtv/
Mauro Carvalho Chehab wrote:
Em 28-09-2010 14:48, Jan Hoogenraad escreveu:
Douglas:
I have an updated make_kconfig.pl for Ububtu on:
http://linuxtv.org/hg/~jhoogenraad/rtl2831-r2/file/cb34ee1c29fc/v4l/scripts/make_kconfig.pl
Could you test if make allyesconfig actually keeps FIREDTV enabled on a
non-Ubuntu system ?
If so, can you merge this version into the main stream ?
Ok, now it looks correct on my eyes, and it should not hurt compilation
with make release and with distros that do a good job with their kernel
packages.
I'll let Douglas review and test, as he is the maintainer.
It would be better if you could send him a diff. you may use hg diff to generate
it against an older version, in order to merge all your make_kconfig.pl patches,
or just create a new clone from master and apply it there.
A side question: when do you intend to send us the patches for the Realtek
rtl2831?
Cheers,
Mauro.
--
Jan Hoogenraad
Hoogenraad Interface Services
Postbus 2717
3500 GS Utrecht
# HG changeset patch
# User Jan Hoogenraad jan-conceptro...@h-i-s.nl
# Date 1285703652 -7200
# Node ID c8e14191e48d98a19405c9f899abca30cd89bc18
# Parent 1da5fed5c8b2c626180b1a0983fe1c960b999525
Disable FIREDTV for debian/ubuntu distributions with bad header files
From: Jan Hoogenraad jan-conceptro...@h-i-s.nl
Disable FIREDTV for debian/ubuntu distributions with problems in header files
Priority: normal
Signed-off-by: Jan Hoogenraad jan-conceptro...@h-i-s.nl
diff -r 1da5fed5c8b2 -r c8e14191e48d v4l/scripts/make_kconfig.pl
--- a/v4l/scripts/make_kconfig.pl Sun Sep 19 02:23:09 2010 -0300
+++ b/v4l/scripts/make_kconfig.pl Tue Sep 28 21:54:12 2010 +0200
@@ -597,6 +597,9 @@
disable_config('STAGING_BROKEN');
$intopt { DVB_MAX_ADAPTERS } = 8;
+#check broken Ubuntu headers
+dmahcheck();
+
# Check dependencies
my %newconfig = checkdeps();
@@ -681,3 +684,24 @@
EOF3
sleep 5;
}
+
+# Check for full kernel sources and print a warning
+sub dmahcheck()
+{
+ my $dmahplace=$kernsrc/include/config/ieee1394/dma.h;
+ if (! -e $dmahplace) {
+ print EOF2;
+
+***WARNING:*** File $dmahplace not present.
+This problem is at least present on Ubuntu systems:
+https://bugs.launchpad.net/ubuntu/+source/linux-kernel-headers/+bug/134222
+
+Therefore disabling FIREDTV driver.
+
+EOF2
+
+ disable_config('DVB_FIREDTV');
+
+ }
+ sleep 5;
+}
updated make_kconfig.pl for Ubuntu
I have updated launchpad bug https://bugs.launchpad.net/ubuntu/+source/linux-kernel-headers/+bug/134222 I also created an updated make_kconfig.pl http://linuxtv.org/hg/~jhoogenraad/rtl2831-r2/file/cb34ee1c29fc/v4l/scripts/make_kconfig.pl Unfortunately, I forgot to commit changes to the main archive the first time. I do not know how to make a patch file for this one file, without have all other changes in the two commits as well. I cannot find a hg export command to make a patch for this one file between versions spanning two commits. Douglas: can you help ? Mauro Carvalho Chehab wrote: Em 26-09-2010 13:18, Jan Hoogenraad escreveu: On Linux 2.6.28-19-generic the problem is tackled already: DVB_FIREDTV_IEEE1394: Requires at least kernel 2.6.30 On newer linux versions (I have tried Linux 2.6.32-24-generic) the problem is NOT that the modules dma is not present, it is just that the required header files are not present in /usr/include Another location mighte have been: ls -l /usr/src/linux-headers-2.6.28-19-generic/include/config/ieee1394 This is the right place is whatever pointed on your kernel source alias, like: $ ls -la /lib/modules/2.6.35+/source lrwxrwxrwx. 1 root root 23 Set 26 21:51 /lib/modules/2.6.35+/source - /home/v4l/v4l/patchwork but that only contains: -rw-r--r-- 1 root root0 2010-09-16 18:25 dv1394.h drwxr-xr-x 3 root root 4096 2010-06-15 20:12 eth1394 -rw-r--r-- 1 root root0 2010-09-16 18:25 eth1394.h -rw-r--r-- 1 root root0 2010-09-16 18:25 ohci1394.h -rw-r--r-- 1 root root0 2010-09-16 18:25 pcilynx.h -rw-r--r-- 1 root root0 2010-09-16 18:25 rawio.h -rw-r--r-- 1 root root0 2010-09-16 18:25 sbp2.h -rw-r--r-- 1 root root0 2010-09-16 18:25 video1394.h Can you indicate where following files should be located ? dma.h csr1212.h highlevel.h All of them are at the same place: /lib/modules/2.6.35+/source/drivers/ieee1394/dma.h /lib/modules/2.6.35+/source/drivers/ieee1394/csr1212.h /lib/modules/2.6.35+/source/drivers/ieee1394/highlevel.h In that case checking if the dma.h file is present might be the best way forward. I'll also file an ubuntu bug once I know what is missing where. I could not find an entry in launchpad on this issue yet. This is probably the best thing. A check for dma.h may also work. If you want, do a patch for it and submit to Douglas. Cheers, Mauro -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: updated make_kconfig.pl for Ubuntu
Mauro:
On my system, the call to make_kconfig reads:
./scripts/make_kconfig.pl /lib/modules/2.6.28-19-generic/build
/lib/modules/2.6.28-19-generic/build 1
Using $kernelsrc yields the following error:
Global symbol $kernelsrc requires explicit package name at
./scripts/make_kconfig.pl line 694.
Using
$dmahplace=$kernsrc/include/config/ieee1394/dma.h;
yields the following INCORRECT expansion:
/lib/modules/2.6.28-19-generic/build/include/config/ieee1394/dma.h
this is the place where I am building into, which is different from the
place where Ubuntu places the include files from the package
Thus I built an expression to get:
/usr/src/linux-headers-2.6.28-19-generic/include/config/ieee1394/dma.h
as I described in the mail of yesterday.
Now, I realize that the header files could ALSO be present in the build
directory, so there should be a check on that as well, as otherwise the
FIREDTV is incorrectly disabled on other distros, or source builds.
Yes, and I know all of this is ugly
Mauro Carvalho Chehab wrote:
Em 27-09-2010 15:41, Jan Hoogenraad escreveu:
I have updated launchpad bug
https://bugs.launchpad.net/ubuntu/+source/linux-kernel-headers/+bug/134222
I also created an updated make_kconfig.pl
http://linuxtv.org/hg/~jhoogenraad/rtl2831-r2/file/cb34ee1c29fc/v4l/scripts/make_kconfig.pl
Unfortunately, I forgot to commit changes to the main archive the first time. I
do not know how to make a patch file for this one file, without have all other
changes in the two commits as well.
I cannot find a hg export command to make a patch for this one file between
versions spanning two commits.
You can just do a diff with upstream. Anyway, I'm enclosing the merged patch.
There's one problem on it:
$dmahplace=/usr/src/linux-headers-$dmahplace/include/config/ieee1394/dma.h;
Don't use absolute names here. -hg build system is smart enough to get the
directory
where the kernel is installed, depending on what version you're compiling
against
(you may change it with make release).
Based on sub kernelcheck(), were we have:
my $fullkernel=$kernsrc/fs/fcntl.c;
I suspect that using:
$dmahplace=$kernelsrc/include/config/ieee1394/dma.h;
should work properly.
---
FYI, this is the diff from the master -hg:
diff -r 1da5fed5c8b2 v4l/scripts/make_kconfig.pl
--- a/v4l/scripts/make_kconfig.pl Sun Sep 19 02:23:09 2010 -0300
+++ b/v4l/scripts/make_kconfig.pl Mon Sep 27 16:04:50 2010 -0300
@@ -597,6 +597,9 @@
disable_config('STAGING_BROKEN');
$intopt { DVB_MAX_ADAPTERS } = 8;
+#check broken Ubuntu headers
+dmahcheck();
+
# Check dependencies
my %newconfig = checkdeps();
@@ -681,3 +684,27 @@
EOF3
sleep 5;
}
+
+# Check for full kernel sources and print a warning
+sub dmahcheck()
+{
+ my $dmahplace= .$kernsrc;
+ $dmahplace =~ s-^/lib/modules/--g;
+ $dmahplace =~ s-/.*$--g;
+
$dmahplace=/usr/src/linux-headers-$dmahplace/include/config/ieee1394/dma.h;
+ if (! -e $dmahplace) {
+ printEOF2;
+
+***WARNING:*** File $dmahplace not present.
+This problem is at least present on Ubuntu systems:
+https://bugs.launchpad.net/ubuntu/+source/linux-kernel-headers/+bug/134222
+
+Therefore disabling FIREDTV driver.
+
+EOF2
+
+ disable_config('DVB_FIREDTV');
+
+ }
+ sleep 5;
+}
--
Jan Hoogenraad
Hoogenraad Interface Services
Postbus 2717
3500 GS Utrecht
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Trouble building v4l-dvb
On Linux 2.6.28-19-generic the problem is tackled already: DVB_FIREDTV_IEEE1394: Requires at least kernel 2.6.30 On newer linux versions (I have tried Linux 2.6.32-24-generic) the problem is NOT that the modules dma is not present, it is just that the required header files are not present in /usr/include Another location mighte have been: ls -l /usr/src/linux-headers-2.6.28-19-generic/include/config/ieee1394 but that only contains: -rw-r--r-- 1 root root0 2010-09-16 18:25 dv1394.h drwxr-xr-x 3 root root 4096 2010-06-15 20:12 eth1394 -rw-r--r-- 1 root root0 2010-09-16 18:25 eth1394.h -rw-r--r-- 1 root root0 2010-09-16 18:25 ohci1394.h -rw-r--r-- 1 root root0 2010-09-16 18:25 pcilynx.h -rw-r--r-- 1 root root0 2010-09-16 18:25 rawio.h -rw-r--r-- 1 root root0 2010-09-16 18:25 sbp2.h -rw-r--r-- 1 root root0 2010-09-16 18:25 video1394.h Can you indicate where following files should be located ? dma.h csr1212.h highlevel.h In that case checking if the dma.h file is present might be the best way forward. I'll also file an ubuntu bug once I know what is missing where. I could not find an entry in launchpad on this issue yet. Mauro Carvalho Chehab wrote: Em 17-09-2010 08:08, Jan Hoogenraad escreveu: Thanks ! Indeed, the hack so that make allyesmod not select firedtv would be very helpful. that way, it is also clear that firedtv will not work on debian-like distros. Is there a way I cen help with that ? I have no experience with Kconfig, so it would be a learning experience for me. You don't need to look at Kconfig. there are some scripts under v4l/scripts that will deal with Kconfig dependencies. They are meant to identify kernel versions and features. Those scripts are, mainly: v4l/scripts/make_config_compat.pl - Checks for backported features, enabling workarounds at v4l/compat.h v4l/scripts/make_kconfig.pl - Generates a .config file that will compile with an older kernel v4l/scripts/make_makefile.pl - Generates a Makefile that will build/install/remove the kernel modules Basically, you need to add some intelligence to one of the above scripts (likely make_kconfig) to identify that the kernel has broken firewire headers, and disable its compilation, printing a warning message to the user. You'll find a logic at make_makefile.pl to detect an Ubuntu broken kernel that stores the in-kernel drivers at the wrong install place. I'm not sure if all Ubuntu kernels/versions do the same thing, nor if this is broken for all distro-variants. Perhaps you may use this logic at make_kconfig.pl. The logic assumes that broken distros are the ones that store V4L/DVB files at /lib/modules/\$(KERNELRELEASE)/ubuntu/media. This is probably not true for all broken distros (as Ubuntu clones - and maybe Debian - could have the same problem, but storing the media files on a different place), so you may need to generalize that logic, in order to cover any other distros that don't compile firewire. While you're there, the better is to also disable CONFIG_ALSA on Ubuntu, as the drivers won't work anyway. As we don't want to have complains from users about why driver foo is not compiling for me, IMO, it should be printing a warning message saying that compilation of ALSA/FIREWIRE drivers with that specific kernel version is not possible, due to the back packaging of kernel headers, recommending to the user to get a vanilla upstream kernel, if he needs one of the disabled drivers. Cheers, Mauro -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Trouble building v4l-dvb
I see that the build now succeeded. Ole: this is something that should have been fixed a long time ago, but isn't. make allyesmod should set only those divers that do actually compile. Unfortunately, the FIREDTV driver has bugs for as long as I remember. In the 4vl directory, edit .config and change the line CONFIG_DVB_FIREDTV=m into CONFIG_DVB_FIREDTV=n It should compile fine then. Jan Hoogenraad wrote: Douglas; Could you please check your last putback ? the build is broken. see: http://www.xs4all.nl/~hverkuil/logs/Wednesday.log and the mail [cron job] v4l-dvb daily build 2.6.26 and up: ERRORS Yours, Jan Ole W. Saastad wrote: Trouble building v4l-dvb Asus eee netbook, running EasyPeasy. o...@ole-eee:~$ cat /etc/issue Ubuntu 9.04 \n \l o...@ole-eee:~$ uname -a Linux ole-eee 2.6.30.5-ep0 #10 SMP PREEMPT Thu Aug 27 19:45:06 CEST 2009 i686 GNU/Linux Rationale for building from source: I have bought a USB TV with mpg4 support from Sandberg, Mini DVB-T dongle. I also received an archive with driver routines for this from Sandberg. These should be copied into the v4l-dvd three and just rebuild with make. I have installed the kernel headers: apt-get install mercurial linux-headers-$(uname -r) build-essential Then I have downloaded the v4l-dvb source (assuming this is a stable release): hg clone http://linuxtv.org/hg/v4l-dvb I wanted to try to build before applying the patch from Sandberg. Issuing make yield the following : LIRC: Requires at least kernel 2.6.36 IR_LIRC_CODEC: Requires at least kernel 2.6.36 IR_IMON: Requires at least kernel 2.6.36 IR_MCEUSB: Requires at least kernel 2.6.36 VIDEOBUF_DMA_CONTIG: Requires at least kernel 2.6.31 V4L2_MEM2MEM_DEV: Requires at least kernel 2.6.33 and a few more lines Ignoring these and just continuing : CC [M] /home/ole/work/v4l-dvb/v4l/firedtv-dvb.o CC [M] /home/ole/work/v4l-dvb/v4l/firedtv-fe.o CC [M] /home/ole/work/v4l-dvb/v4l/firedtv-1394.o /home/ole/work/v4l-dvb/v4l/firedtv-1394.c:22:17: error: dma.h: No such file or directory /home/ole/work/v4l-dvb/v4l/firedtv-1394.c:23:21: error: csr1212.h: No such file or directory /home/ole/work/v4l-dvb/v4l/firedtv-1394.c:24:23: error: highlevel.h: No such file or directory and many many more similar errors. After some time the make bails out. I assume this have some connection with the 9.04 being too old. Hints ? Regards, Ole W. Saastad -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Trouble building v4l-dvb
Thanks ! Indeed, the hack so that make allyesmod not select firedtv would be very helpful. that way, it is also clear that firedtv will not work on debian-like distros. Is there a way I cen help with that ? I have no experience with Kconfig, so it would be a learning experience for me. Mauro Carvalho Chehab wrote: Em 17-09-2010 06:35, Jan Hoogenraad escreveu: I see that the build now succeeded. Ole: this is something that should have been fixed a long time ago, but isn't. make allyesmod should set only those divers that do actually compile. Unfortunately, the FIREDTV driver has bugs for as long as I remember. The problem are not related to bugs at firedtv driver, but, instead, due to the fact that the provided firewire drivers and fw-core don't match the drivers that are shipped with the distro kernel. In order words, at Ubuntu (and some other deb-based distros), they're shipping the wrong include files at /lib/modules/`uname -r`/build/. So, there's no way to build and run any module based on that wrong broken headers. Up to a certain amount, the same happens with -alsa files on Ubuntu: although they will compile [1], as the provided headers at /lib/modules/`uname -r`/build/ are from a different version than the alsa modules provided with Ubuntu, the drivers that depend on -alsa will generally compile, but they generally won't load (and, if they load, they'll can cause an OOPS and some other random troubles), as the symbol dependency will not match. While a hack might be added at v4l-dvb -hg tree to make firedtv to compile against a broken header, the firedtv driver will not work anyway. The only real solution for it is to fix this issue at the distro. Cheers, Mauro [1] The v4l-dvb is smart enough to adapt to -alsa API changes that are backported into an older kernel, since it checks for the API symbols that changed, instead of just looking for the kernel version. This works fine with all distros (like Fedora, RHEL, SUSE, OpenSUSE, Mandriva, ...) where the include files for alsa are at the right place: /lib/modules/`uname -r`/build/). -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Trouble building v4l-dvb
Really, the only thing I would do is disable the ones that break compilation. this is ONLY firedtv. I doubt if anyone would read the messages during compilation. I'll have a look at the logic. Mauro Carvalho Chehab wrote: Em 17-09-2010 08:08, Jan Hoogenraad escreveu: Thanks ! Indeed, the hack so that make allyesmod not select firedtv would be very helpful. that way, it is also clear that firedtv will not work on debian-like distros. Is there a way I cen help with that ? I have no experience with Kconfig, so it would be a learning experience for me. You don't need to look at Kconfig. there are some scripts under v4l/scripts that will deal with Kconfig dependencies. They are meant to identify kernel versions and features. Those scripts are, mainly: v4l/scripts/make_config_compat.pl - Checks for backported features, enabling workarounds at v4l/compat.h v4l/scripts/make_kconfig.pl - Generates a .config file that will compile with an older kernel v4l/scripts/make_makefile.pl - Generates a Makefile that will build/install/remove the kernel modules Basically, you need to add some intelligence to one of the above scripts (likely make_kconfig) to identify that the kernel has broken firewire headers, and disable its compilation, printing a warning message to the user. You'll find a logic at make_makefile.pl to detect an Ubuntu broken kernel that stores the in-kernel drivers at the wrong install place. I'm not sure if all Ubuntu kernels/versions do the same thing, nor if this is broken for all distro-variants. Perhaps you may use this logic at make_kconfig.pl. The logic assumes that broken distros are the ones that store V4L/DVB files at /lib/modules/\$(KERNELRELEASE)/ubuntu/media. This is probably not true for all broken distros (as Ubuntu clones - and maybe Debian - could have the same problem, but storing the media files on a different place), so you may need to generalize that logic, in order to cover any other distros that don't compile firewire. While you're there, the better is to also disable CONFIG_ALSA on Ubuntu, as the drivers won't work anyway. As we don't want to have complains from users about why driver foo is not compiling for me, IMO, it should be printing a warning message saying that compilation of ALSA/FIREWIRE drivers with that specific kernel version is not possible, due to the back packaging of kernel headers, recommending to the user to get a vanilla upstream kernel, if he needs one of the disabled drivers. Cheers, Mauro -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
rtl2832 chip driver
Hi Ole: Try vlc or keffeins, and see if they have the same audio problem. Also: try playing a normal sound mp3 file with them. me-tv and rtl2832 havce some problems: https://bugs.launchpad.net/ubuntu/+source/me-tv/+bug/478379 Thanks for the Sandberg link. At: http://www.sandberg.it/support/product.aspx?id=133-59 I found Realtek stuff that looks very familiar to the RTL2831 stuff I put into another HG branch: http://linuxtv.org/hg/~jhoogenraad/rtl2831-r2 This is again code where the frontend and backend have not been separated. Seems realtek has their branch kind of working, based on their windows approach. Antti has set up a new version from scratch at: http://linuxtv.org/hg/~anttip/rtl2831u/ Ole W. Saastad wrote: Thanks for all help so far. I managed to figure out the firetv problem as soon as I discovered the .myconfig file. Including the drivers from Sandberg, for the rtl2832 chip and adding some lines to Makefile, Kconfig and .myconfig it compiles and install. Modules load and Me-TV starts, quality is poor with the small antenna. However, there is no audio. Not even for the DAB radio channels. Maybe this is Me-TV problem? The version supplied with Easy Peasy Ubuntu 9.10 is old, 0.7.16. Regards, Ole W. Saastad -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Trouble building v4l-dvb
Douglas; Could you please check your last putback ? the build is broken. see: http://www.xs4all.nl/~hverkuil/logs/Wednesday.log and the mail [cron job] v4l-dvb daily build 2.6.26 and up: ERRORS Yours, Jan Ole W. Saastad wrote: Trouble building v4l-dvb Asus eee netbook, running EasyPeasy. o...@ole-eee:~$ cat /etc/issue Ubuntu 9.04 \n \l o...@ole-eee:~$ uname -a Linux ole-eee 2.6.30.5-ep0 #10 SMP PREEMPT Thu Aug 27 19:45:06 CEST 2009 i686 GNU/Linux Rationale for building from source: I have bought a USB TV with mpg4 support from Sandberg, Mini DVB-T dongle. I also received an archive with driver routines for this from Sandberg. These should be copied into the v4l-dvd three and just rebuild with make. I have installed the kernel headers: apt-get install mercurial linux-headers-$(uname -r) build-essential Then I have downloaded the v4l-dvb source (assuming this is a stable release): hg clone http://linuxtv.org/hg/v4l-dvb I wanted to try to build before applying the patch from Sandberg. Issuing make yield the following : LIRC: Requires at least kernel 2.6.36 IR_LIRC_CODEC: Requires at least kernel 2.6.36 IR_IMON: Requires at least kernel 2.6.36 IR_MCEUSB: Requires at least kernel 2.6.36 VIDEOBUF_DMA_CONTIG: Requires at least kernel 2.6.31 V4L2_MEM2MEM_DEV: Requires at least kernel 2.6.33 and a few more lines Ignoring these and just continuing : CC [M] /home/ole/work/v4l-dvb/v4l/firedtv-dvb.o CC [M] /home/ole/work/v4l-dvb/v4l/firedtv-fe.o CC [M] /home/ole/work/v4l-dvb/v4l/firedtv-1394.o /home/ole/work/v4l-dvb/v4l/firedtv-1394.c:22:17: error: dma.h: No such file or directory /home/ole/work/v4l-dvb/v4l/firedtv-1394.c:23:21: error: csr1212.h: No such file or directory /home/ole/work/v4l-dvb/v4l/firedtv-1394.c:24:23: error: highlevel.h: No such file or directory and many many more similar errors. After some time the make bails out. I assume this have some connection with the 9.04 being too old. Hints ? Regards, Ole W. Saastad -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: HG has errors on kernel 2.6.32
Douglas: Thanks in advance Douglas Schilling Landgraf wrote: Hi Jan, On Thu, Aug 26, 2010 at 4:54 PM, Jan Hoogenraad jan-conceptro...@hoogenraad.net wrote: Douglas: I see on that http://www.xs4all.nl/~hverkuil/logs/Thursday.log that building linux-2.6.32 yields ERRORS skip_spaces has only been included in string.h starting from linux-2.6.33. Should I have a look on how to fix this, or do you want to do this ? It's up to you. I can fix it, easily. Please: I would have to learn from scratch about the code -- second request: can we do some small changes to avoid the compiler warnings ? I will check on the git tree which patch touch on this and commit it. As backport tree, I cannot commit anything besides on existing source of git tree. Please: I have not installed the git tree. Thanks Douglas -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: dvb_usb_rtl2831u module cause oops on kernel 2.6.32 when loading
causes the used console to hang up as well. Would be great if anyone got a solution for this problem. Best regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
ir_codes_dibusb_table : please make table length a constant
During debugging a driver, I found that at least in linux/drivers/media/dvb/dvb-usb/dibusb-mc.c the length of ir_codes_dibusb_table was referring to an older version. This may have caused memory overrun problems I have fixed this in my branch in linux/drivers/media/dvb/dvb-usb/dibusb.h with a #define IR_CODES_DIBUSB_TABLE_LEN 111 http://linuxtv.org/hg/~jhoogenraad/rtl2831-r2/rev/549b40b69fa4 I agree this is not the nicest solution, but at at least would reduce some problems. I am not sure on how to create a patch for this ? Should I make a new branch in the HG archive ? I suggest to replate the 111-s into IR_CODES_DIBUSB_TABLE_LEN in the files below as well: * drivers/media/dvb/dvb-usb/dibusb-common.c: o line 330 o line 459 * drivers/media/dvb/dvb-usb/dibusb-mb.c: o line 215 o line 299 o line 363 o line 420 * drivers/media/dvb/dvb-usb/dibusb.h, line 127 -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
HG has errors on kernel 2.6.32
Douglas: I see on that http://www.xs4all.nl/~hverkuil/logs/Thursday.log that building linux-2.6.32 yields ERRORS skip_spaces has only been included in string.h starting from linux-2.6.33. Should I have a look on how to fix this, or do you want to do this ? -- second request: can we do some small changes to avoid the compiler warnings ? include the line rc=0; at line 187 of linux/drivers/media/IR/ir-raw-event.c and change static void jpeg_set_qual(u8 *jpeg_hdr, into static __attribute__ (( unused )) void jpeg_set_qual(u8 *jpeg_hdr, at line 152 of linux/drivers/media/video/gspca/jpeg.h Yours, Jan Thomas Holzeisen wrote: Hi Jan, this looks great. At first the checkout did not build throwing me this error: /usr/src/rtl2831-r2/v4l/ir-sysfs.c: In function 'store_protocols': /usr/src/rtl2831-r2/v4l/ir-sysfs.c:137: error: implicit declaration of function 'skip_spaces' /usr/src/rtl2831-r2/v4l/ir-sysfs.c:137: warning: assignment makes pointer from integer without a cast /usr/src/rtl2831-r2/v4l/ir-sysfs.c:178: warning: assignment makes pointer from integer without a cast i replaced the file by an older version from a previous checkout and then it build perfectly. It also gets initialized without a flaw: -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: V4L hg tree fails to compile against kernel 2.6.28
Thanks for your help. I pulled the code Actually, now the function definition in compat.h causes a compilation error: see first text below. I fixed that by inserting #include linux/err.h at line 38 in compat.h in my local branch After that, compilation succeeds. Now, the device will not install, as dvb_usb cannot install anymore. see second text below. Therefore, I have replaced the __kmalloc_track_caller with kmalloc (as it was in dvb_demux.c before the change 2ceef3d75547 at line 49 can you make both changes in the hg branch ? - make[2]: Entering directory `/usr/src/linux-headers-2.6.28-19-generic' CC [M] tuner-xc2028.o In file included from tuner-xc2028.c:19: compat.h: In function 'memdup_user': compat.h:50: error: implicit declaration of function 'ERR_PTR' compat.h:50: warning: return makes pointer from integer without a cast compat.h:54: warning: return makes pointer from integer without a cast In file included from include/linux/fs.h:1891, from include/linux/poll.h:11, from dvbdev.h:27, from dvb_frontend.h:43, from tuner-xc2028.h:10, from tuner-xc2028.c:22: include/linux/err.h: At top level: include/linux/err.h:22: error: conflicting types for 'ERR_PTR' sudo modprobe dvb-usb-rtl2831u ir_protocol=2 WARNING: Error inserting dvb_usb (/lib/modules/2.6.28-19-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb.ko): Unknown symbol in module, or unknown parameter (see dmesg) WARNING: Error inserting dvb_usb_dibusb_common (/lib/modules/2.6.28-19-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb-dibusb-common.ko): Unknown symbol in module, or unknown parameter (see dmesg) FATAL: Error inserting dvb_usb_rtl2831u (/lib/modules/2.6.28-19-generic/kernel/drivers/media/dvb/rtl2831/dvb-usb-rtl2831u.ko): Unknown symbol in module, or unknown parameter (see dmesg) in the system log, I find: dvb_core: Unknown symbol __kmalloc_track_caller dvb_core: Unknown symbol __kmalloc_track_caller Douglas Schilling Landgraf wrote: Hello Jan, On Tue, Aug 24, 2010 at 5:04 PM, Jan Hoogenraad jan-conceptro...@hoogenraad.net wrote: Douglas: On compiling with Linux 2.6.28-19-generic #62-Ubuntu I now get: dvb_demux.c: In function 'dvbdmx_write': dvb_demux.c:1137: error: implicit declaration of function 'memdup_user' dvb_demux.c:1137: warning: assignment makes pointer from integer without a cast This is probably due to changeset 2ceef3d75547 which introduced the use of this function: http://linuxtv.org/hg/v4l-dvb/diff/2ceef3d75547/linux/drivers/media/dvb/dvb-core/dvb_demux.c This function is not available in linux/string.h in kernel 2.6.29 and lower. http://lxr.free-electrons.com/source/include/linux/string.h?v=2.6.28 Could you please advise me on what to do ? For this issue, I have fixed right now, please try again with a updated repository. But since I have commited several patches yesterday, we have another one that probably will reach your compilantion (the kfifo one). I will work to fix this one too. Thanks for the report. Cheers Douglas -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Failure of v4l-dvb daily build against kernel 2.6.28 and others
Douglas: I now see that some more versions have several build errors and/or warnings. Could you, in the process of backporting, try to reduce this as well ? Hans Verkuil wrote: This message is generated daily by a cron job that builds v4l-dvb for the kernels and architectures in the list below. Results of the daily build of v4l-dvb: date:Tue Aug 24 19:00:24 CEST 2010 path:http://www.linuxtv.org/hg/v4l-dvb changeset: 15131:2ceef3d75547 git master: f6760aa024199cfbce564311dc4bc4d47b6fb349 git media-master: 1c1371c2fe53ded8ede3a0404c9415fbf3321328 gcc version: i686-linux-gcc (GCC) 4.4.3 host hardware:x86_64 host os: 2.6.32.5 linux-2.6.32.6-armv5: ERRORS linux-2.6.33-armv5: WARNINGS linux-2.6.34-armv5: WARNINGS linux-2.6.35-rc1-armv5: WARNINGS linux-2.6.32.6-armv5-davinci: ERRORS linux-2.6.33-armv5-davinci: ERRORS linux-2.6.34-armv5-davinci: ERRORS linux-2.6.35-rc1-armv5-davinci: ERRORS linux-2.6.32.6-armv5-ixp: ERRORS linux-2.6.33-armv5-ixp: ERRORS linux-2.6.34-armv5-ixp: ERRORS linux-2.6.35-rc1-armv5-ixp: ERRORS linux-2.6.32.6-armv5-omap2: ERRORS linux-2.6.33-armv5-omap2: ERRORS linux-2.6.34-armv5-omap2: ERRORS linux-2.6.35-rc1-armv5-omap2: ERRORS linux-2.6.22.19-i686: ERRORS linux-2.6.23.17-i686: ERRORS linux-2.6.24.7-i686: ERRORS linux-2.6.25.20-i686: ERRORS linux-2.6.26.8-i686: ERRORS linux-2.6.27.44-i686: ERRORS linux-2.6.28.10-i686: ERRORS linux-2.6.29.1-i686: ERRORS linux-2.6.30.10-i686: ERRORS linux-2.6.31.12-i686: ERRORS linux-2.6.32.6-i686: ERRORS linux-2.6.33-i686: ERRORS linux-2.6.34-i686: ERRORS linux-2.6.35-rc1-i686: ERRORS linux-2.6.32.6-m32r: ERRORS linux-2.6.33-m32r: WARNINGS linux-2.6.34-m32r: WARNINGS linux-2.6.35-rc1-m32r: WARNINGS linux-2.6.32.6-mips: ERRORS linux-2.6.33-mips: WARNINGS linux-2.6.34-mips: WARNINGS linux-2.6.35-rc1-mips: WARNINGS linux-2.6.32.6-powerpc64: ERRORS linux-2.6.33-powerpc64: ERRORS linux-2.6.34-powerpc64: ERRORS linux-2.6.35-rc1-powerpc64: ERRORS linux-2.6.22.19-x86_64: ERRORS linux-2.6.23.17-x86_64: ERRORS linux-2.6.24.7-x86_64: ERRORS linux-2.6.25.20-x86_64: ERRORS linux-2.6.26.8-x86_64: ERRORS linux-2.6.27.44-x86_64: ERRORS linux-2.6.28.10-x86_64: ERRORS linux-2.6.29.1-x86_64: ERRORS linux-2.6.30.10-x86_64: ERRORS linux-2.6.31.12-x86_64: ERRORS linux-2.6.32.6-x86_64: ERRORS linux-2.6.33-x86_64: WARNINGS linux-2.6.34-x86_64: WARNINGS linux-2.6.35-rc1-x86_64: WARNINGS linux-git-armv5: WARNINGS linux-git-armv5-davinci: WARNINGS linux-git-armv5-ixp: WARNINGS linux-git-armv5-omap2: WARNINGS linux-git-i686: WARNINGS linux-git-m32r: OK linux-git-mips: OK linux-git-powerpc64: OK linux-git-x86_64: WARNINGS spec: ERRORS spec-git: OK sparse: ERRORS linux-2.6.16.62-i686: ERRORS linux-2.6.17.14-i686: ERRORS linux-2.6.18.8-i686: ERRORS linux-2.6.19.7-i686: ERRORS linux-2.6.20.21-i686: ERRORS linux-2.6.21.7-i686: ERRORS linux-2.6.16.62-x86_64: ERRORS linux-2.6.17.14-x86_64: ERRORS linux-2.6.18.8-x86_64: ERRORS linux-2.6.19.7-x86_64: ERRORS linux-2.6.20.21-x86_64: ERRORS linux-2.6.21.7-x86_64: ERRORS Detailed results are available here: http://www.xs4all.nl/~hverkuil/logs/Tuesday.log Full logs are available here: http://www.xs4all.nl/~hverkuil/logs/Tuesday.tar.bz2 The V4L-DVB specification from this daily build is here: http://www.xs4all.nl/~hverkuil/spec/media.html -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: V4L hg tree fails to compile against kernel 2.6.28
__kmalloc_track_caller is not avaiable in 2.6.28-19-generic #62-Ubuntu which just passes your cut at 2.6.26. Apparently, the code __kmalloc_track_caller is in the source archive for 2.6.28, but the kernel options were not such that the symbol is available. My guess is that it was changed in 2.6.30, where memory management was changed. Thus, 2.6.28, it needs to stay kmalloc. Douglas Schilling Landgraf wrote: Hello Jan, On Wed, Aug 25, 2010 at 3:26 AM, Jan Hoogenraad jan-conceptro...@hoogenraad.net wrote: Thanks for your help. I pulled the code Actually, now the function definition in compat.h causes a compilation error: see first text below. I fixed that by inserting #include linux/err.h at line 38 in compat.h in my local branch After that, compilation succeeds. Thanks, applied. Now, the device will not install, as dvb_usb cannot install anymore. see second text below. Therefore, I have replaced the __kmalloc_track_caller with kmalloc (as it was in dvb_demux.c before the change 2ceef3d75547 at line 49 can you make both changes in the hg branch ? This one won't be required because the idea is support until kernel 2.6.26. Please check my next email about hg x announcement. Thanks for checking it, your help is appreciate. Cheers Douglas -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
V4L hg tree fails to compile against kernel 2.6.28
Douglas: On compiling with Linux 2.6.28-19-generic #62-Ubuntu I now get: dvb_demux.c: In function 'dvbdmx_write': dvb_demux.c:1137: error: implicit declaration of function 'memdup_user' dvb_demux.c:1137: warning: assignment makes pointer from integer without a cast This is probably due to changeset 2ceef3d75547 which introduced the use of this function: http://linuxtv.org/hg/v4l-dvb/diff/2ceef3d75547/linux/drivers/media/dvb/dvb-core/dvb_demux.c This function is not available in linux/string.h in kernel 2.6.29 and lower. http://lxr.free-electrons.com/source/include/linux/string.h?v=2.6.28 Could you please advise me on what to do ? Douglas Schilling Landgraf wrote: Hello Derek, On Sun, Aug 15, 2010 at 2:22 AM, Douglas Schilling Landgraf dougsl...@gmail.com wrote: Hello Derek, On Sat, Aug 14, 2010 at 12:46 PM, VDR User user@gmail.com wrote: On Wed, Aug 4, 2010 at 10:19 PM, Douglas Schilling Landgraf dougsl...@gmail.com wrote: I am already working to give a full update to hg tree. Sorry this problem. Hi Douglas. Any estimate when this will be fixed? Was hoping it was already since new stable kernel 2.6.35.2 is out now but still the same problem when I tried just now. I am already working on it this weekend. I will reply this thread when finished. 2.6.35 should be working, let me know if not. Now, I need to backport the changes to old kernels and commit other patches in my pending list. Cheers Douglas -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Help wanted on removing dibusb_rc_keys from dvb_usb_rtl2831u module
OK. I found the solution by looking at the sources at: http://lxr.free-electrons.com/source/drivers/media/dvb/dvb-usb/dibusb-common.c What needed was a rename over all sources affected: struct dvb_usb_rc_key dibusb_rc_keys[] = struct dvb_usb_rc_key ir_codes_dibusb_table[] I also fixed missing renaming in dib_usb driver. I have updated http://linuxtv.org/hg/~jhoogenraad/rtl2831-r2/ Jan Hoogenraad wrote: This is probably caused by the current dvb_usb_rtl2831u module using dibusb_rc_keys, which disapperead due to IR changes. Syncing the rtl2831-r2/ tree with the main archive cause compilation problems in v4l/dibusb-mc.c and I suppose rtd2830u.c will not compile anymore either. Can somebody with knowledge on IR help me with updating the code ? $ grep dibusb_rc_keys */*.[ch] v4l/dibusb-mc.c:.rc_key_map = dibusb_rc_keys, v4l/rtd2830u.c:d-props.rc_key_map = dibusb_rc_keys; v4l/rtd2830u.c:.rc_key_map = dibusb_rc_keys, v4l/rtd2830u.c:.rc_key_map = dibusb_rc_keys, I addition, I'd like to get help on how to move the IR code into http://linuxtv.org/hg/~anttip/rtl2831u That (in all other respects much better) version has NO IR support at all at. Adding IR to that driver, and getting it into the kernel would solve all problems. Thomas Holzeisen wrote: Hi, i am using a DVB-T USB-Stick with Realtek RTL2831 chip (14aa:0160) on Debian Lenny having the lastest Backport kernel 2.6.32. $ uname -a Linux xbmc 2.6.32-bpo.5-686 #1 SMP Fri Jun 11 22:20:29 UTC 2010 i686 GNU/Linux For v4l I took the drivers from here: http://linuxtv.org/hg/~jhoogenraad/rtl2831-r2/ The checked out source compile and installs fine. I compiled them starting with make distclean. But when plugging the DVB-Stick this happens: [ 229.524028] usb 4-2: new high speed USB device using ehci_hcd and address 3 [ 229.658591] usb 4-2: New USB device found, idVendor=14aa, idProduct=0160 [ 229.661204] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 229.663841] usb 4-2: Product: DTV Receiver [ 229.666308] usb 4-2: Manufacturer: DTV Receiver [ 229.668826] usb 4-2: SerialNumber: 00067936 [ 229.671609] usb 4-2: configuration #1 chosen from 1 choice [ 230.266960] dvb-usb: found a 'Freecom USB 2.0 DVB-T Device' in warm state. [ 230.270314] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 230.273641] DVB: registering new adapter (Freecom USB 2.0 DVB-T Device) [ 230.277461] DVB: registering adapter 0 frontend 0 (Realtek RTL2831 DVB-T)... [ 230.282081] BUG: unable to handle kernel paging request at 02b65c40 [ 230.285794] IP: [f7c623ba] dvb_usb_remote_init+0x12e/0x209 [dvb_usb] [ 230.291463] *pde = [ 230.293969] Oops: 0002 [#1] SMP [ 230.293969] last sysfs file: /sys/devices/pci:00/:00:06.1/usb4/4-2/bmAttributes [ 230.293969] Modules linked in: dvb_usb_rtl2831u(+) dvb_usb_dibusb_common dvb_usb dib3000mc dibx000_common dvb_ttpci dvb_core saa7146_vv videodev v4l1_compat saa7146 videobuf_dma_sg videobuf_core ttpci_eeprom iscsi_trgt crc32c loop snd_hda_codec_nvhdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq snd_timer snd_seq_device snd tpm_tis soundcore tpm shpchp psmouse wmi serio_raw tpm_bios snd_page_alloc pcspkr pci_hotplug processor evdev button ir_core nvidia(P) lirc_imon i2c_nforce2 i2c_core lirc_dev ext3 jbd mbcache raid1 md_mod usbhid hid sg sr_mod cdrom sd_mod crc_t10dif usb_storage ahci ata_generic libata ehci_hcd ohci_hcd scsi_mod usbcore nls_base forcedeth thermal fan thermal_sys [last unloaded: scsi_wait_scan] [ 230.293969] [ 230.293969] Pid: 3279, comm: modprobe Tainted: P (2.6.32-bpo.5-686 #1) Point of View [ 230.293969] EIP: 0060:[f7c623ba] EFLAGS: 00010246 CPU: 0 [ 230.293969] EIP is at dvb_usb_remote_init+0x12e/0x209 [dvb_usb] [ 230.293969] EAX: 69656148 EBX: f589b000 ECX: c14c18e4 EDX: f589b018 [ 230.293969] ESI: f5904000 EDI: 03b8 EBP: 0077 ESP: f5851e88 [ 230.293969] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 230.293969] Process modprobe (pid: 3279, ti=f585 task=f5cd4400 task.ti=f585) [ 230.293969] Stack: [ 230.293969] f589b018 f5904000 f5904000 f5904864 0001 f7c61945 f5904418 f80bb8d0 [ 230.293969] 0 f5912000 f5b8f800 f80bad88 f80bad88 f5912000 [ 230.293969] 0 f80bb894 f80ba970 f80b886d f80ba960 f5912000 f80c8c98 f591201c [ 230.293969] Call Trace: [ 230.293969] [f7c61945] ? dvb_usb_device_init+0x515/0x51c [dvb_usb] [ 230.293969] [f80b886d] ? rtd2831u_usb_probe+0x19/0x48 [dvb_usb_rtl2831u] [ 230.293969] [f80c8c98] ? usb_probe_interface+0xe7/0x130 [usbcore] [ 230.293969] [c11b2c22] ? driver_probe_device+0x8a/0x11e [ 230.293969] [c11b2cf6] ? __driver_attach+0x40/0x5b [ 230.293969] [c11b2667] ? bus_for_each_dev+0x37/0x5f [ 230.293969] [c11b2af5] ? driver_attach+0x11/0x13 [ 230.293969] [c11b2cb6] ? __driver_attach+0x0/0x5b [ 230.293969
Re: dvb_usb_rtl2831u module cause oops on kernel 2.6.32 when loading
63034 2 dvb_usb,dvb_ttpci saa7146_vv 31312 1 dvb_ttpci saa7146 9911 2 dvb_ttpci,saa7146_vv ttpci_eeprom1224 1 dvb_ttpci i2c_core 12700 8 dvb_usb,dib3000mc,dibx000_common,dvb_ttpci,videodev,ttpci_eeprom,nvidia,i2c_nforce2 usbcore98466 10 dvb_usb_rtl2831u,dvb_usb,lirc_imon,usbhid,usb_storage,ehci_hcd,ohci_hcd When plugging the usb-stick after boot I am able to use it as intend. But when having it inserted during boot the system hangs up. Calling lsusb from console causes the used console to hang up as well. Would be great if anyone got a solution for this problem. Best regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: v4l-dvb unsupported device: Conceptronic CTVDIGUSB2 1b80:d393 (Afatech) - possibly similar to CTVCTVDIGRCU v3.0?
Matteo: If I read this well, CTVDIGUSB2 1b80:d393 (Afatech) is not at all similar to the CTVDIGRCU. The CTVDIGRCU has a Realtek RTL2831U decoder, and is NOT included in the standard dvb list. Conceptronic just packages sticks from other vendors. The fact that the device ID is recognized point towards the afatech driver, and not the Realtek RTL2831U driver. Fot background on the Realtek RTL2831U driver, see: http://www.linuxtv.org/wiki/index.php/Realtek_RTL2831U matteo sisti sette wrote: Hi, I hope this is the right place for reporting this; if not, please forgive and redirect me. My DVB-T USB stick, a Conceptronic USB 2.0 Digital TV Receiver CTVDIGUSB2 doesn't work after succesfully compiling and installing v4l-dvb, and it seems it is not supported according to the device list. The ID is 1b80:d393 The name Conceptronic USB 2.0 is very similar to that of CTVDIGRCU, which _is_ supported and the chipset seems to be indeed an Afatech as the output of lsusb reports: Bus 002 Device 007: ID 1b80:d393 Afatech (or isn't that reliable?) So I wonder whether this is one of the cases where the following applies: The driver has to be aware that it's related to some hardware (typically through the subsystem ID from the USB ID or PCI ID). If the driver doesn't recognize/bind to your particular hardware, then the module will probably load but then proceed to not do anything. In other words, support for your device would have to be added to the driver. If I understand correctly (pleas correct me if I am wrong), IF that is the case (which may be not), then making it work should be just a matter of adding the id of the device to the source code of the driver somewhere and recompiling it and it would work?? If so, is it something I may try following some step-by-step guide? Thanks m. -- Jan Hoogenraad -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: v4l-dvb unsupported device: Conceptronic CTVDIGUSB2 1b80:d393 (Afatech) - possibly similar to CTVCTVDIGRCU v3.0?
I see: apparently the versions earlier than V3.0 of CTVDIGRCU used Realtek RTL2831U. I'll make a note of that on the wiki page. Matteo Sisti Sette wrote: On 06/28/2010 09:48 PM, Jan Hoogenraad wrote: Matteo: If I read this well, CTVDIGUSB2 1b80:d393 (Afatech) is not at all similar to the CTVDIGRCU. The CTVDIGRCU has a Realtek RTL2831U decoder, and is NOT included in the standard dvb list. So is the table at http://linuxtv.org/wiki/index.php/DVB-T_USB_Devices incorrect? It says: Conceptronic USB2.0 DVB-T CTVDIGRCU V3.0 ✔ Yes, in kernel since 2.6.31 1b80:e397 USB2.0 Afatech AF9015 Anyway, I see there are other sticks with chipsets by Afatech. Is there any chance that some of the currently implemented driver would work fine with my chipset if only I forced the driver to recognize the chipset as another one by touching the source code? How could I try that? (if it deserves a try) Thanks m. -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Help with RTL2832U DVB-T dongle (LeadTek WinFast DTV Dongle Mini)
Antti has been working on drivers for the RTL283x. http://linuxtv.org/hg/~anttip/rtl2831u or http://linuxtv.org/hg/~anttip/qt1010/ If you have more information on the RTL2832, I'd be happy to add it at: http://www.linuxtv.org/wiki/index.php/Rtl2831_devices Jan Slaninka wrote: Hi, I'd like to ask for a support with getting LeadTek WindFast DTV Dongle mini running on Linux. So far I was able to fetch latest v4l-dvb from HG, and successfully compiled module dvb_usb_rtl2832u found in 090730_RTL2832U_LINUX_Ver1.1.rar but with no luck. The box says the dongle's TV Tuner is Infineon 396 and Demodulator is RTL2832U. Is there any chance with this one? Any hints appreciated. Thanks, Jan lsmod: Module Size Used by dvb_usb_rtl2832u 94445 0 dvb_usb18655 1 dvb_usb_rtl2832u dmesg output: [ 9283.804050] usb 2-1: new high speed USB device using ehci_hcd and address 9 [ 9283.930504] usb 2-1: New USB device found, idVendor=0413, idProduct=6a03 [ 9283.930507] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 9283.930510] usb 2-1: Product: usbtv [ 9283.930512] usb 2-1: Manufacturer: realtek [ 9283.930610] usb 2-1: configuration #1 chosen from 1 choice lsusb: Bus 002 Device 009: ID 0413:6a03 Leadtek Research, Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0413 Leadtek Research, Inc. idProduct 0x6a03 bcdDevice1.00 iManufacturer 1 realtek iProduct2 usbtv iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 USB2.0-BulkIso bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 5 Bulk-In, Interface Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 bNumConfigurations 2 Device Status: 0x (Bus Powered) -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [linux-dvb] Compro U80 Nearly there???
Please see if there is more information on the tuner in the logging with debugging switched on: sudo modprobe -r dvb-usb-rtl2831u sudo modprobe dvb-usb-rtl2831u debug=1 The ~jhoogenraad/rtl2831-r2 has two tuners hard-coded in the driver (no separation of back-end and front-end), and logs the interactions with those tuners in debug mode. I maintain the wiki with info on the driver: http://www.linuxtv.org/wiki/index.php/Rtl2831_devices Please also try the new driver (alas with no IR remote support) from ~anttip/rtl2831u peter wrote: I'm running Ubuntu Karmic, and have a Compro U80 Device USB ID 185b:0150. To get this close to working I have: 1) Added 50-udev.rules which seem to allow the device to be recognised. 2) Compiled the ~jhoogenraad/rtl2831-r2 version of the driver. This gets me to the point where: - /dev/dvb exists. - my applications recognise the device - In the log I see: [ 14.311735] dvb-usb: found a 'VideoMate U90' in warm state. [ 14.311743] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 14.312131] DVB: registering new adapter (VideoMate U90) [ 14.312420] DVB: registering adapter 0 frontend 0 (Realtek RTL2831 DVB-T)... [ 14.312521] input: IR-receiver inside an USB DVB receiver as /devices/pci:00/:00:02.1/usb1/1-1/input/input5 [ 14.312552] dvb-usb: schedule remote query interval to 300 msecs. [ 14.312558] dvb-usb: VideoMate U90 successfully initialized and connected. [ 14.312589] usbcore: registered new interface driver dvb_usb_rtd2831u So looking good so far. However, if i used scan, or an application like Kaffeine tuning fails. I know that the device works as I can get it to work on windows. So I have been looking at the RTL2831U data sheets which I know from the windows driver that this is based on. (I don't know much about this hardware I am trying to figure it out ). So this chip is just doing the demodulating and the USB interface. It must therefore be paired with tuner. It seems logical to me (but is possibly wrong ) that if the demodulator is working and I cant tune, then the issue is with the tuner part of the driver. The windows drivers refer to both the MT2060 and the QT1010, but I don't know which one is being used. (I have not had the guts to rip the thing apart yet). Docu in the code of for the driver implies that it can support the MT2060 but not the QT1010 so I guess with my luck it is the quantec one. Has any one got any advice as to where I should look next? Has anyone got this to work? It seems to be quite close. I any suggestions would be appreciated. Thanks Peter ___ linux-dvb users mailing list For V4L/DVB development, please use instead linux-media@vger.kernel.org linux-...@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Compro U80
The Realtek driver (a windows-like driver I got from the manufacturer) only supported the mt2060 and mx5005. I have heard of U80 working. Please give the new driver (alas with no IR remote support) from anttip/rtl2831u If there is a different tuner, that driver is set up so that you can incorporate other tuners easily. James Troup wrote: Hi Jan, someone in the chat channel has told me that the driver does not support the qt1010 tuner that I have. Is this correct? I am using the hg clone on your driver rtl2831-r2 James Hi Jan, I bought the Compro U80, compiled the driver, but I don't seem to be able to tune. tuning failed :~$ scan /usr/share/dvb/dvb-t/au-Adelaide ~/Desktop/channels.conf scanning /usr/share/dvb/dvb-t/au-Adelaide using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 22650 1 3 9 3 1 1 0 initial transponder 17750 1 3 9 3 1 1 0 initial transponder 191625000 1 3 9 3 1 1 0 initial transponder 21950 1 3 9 3 1 1 0 initial transponder 56450 1 2 9 3 1 2 0 tune to: 22650:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE WARNING: tuning failed!!! Where is the best place to ask questions for this? -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Compro VideoMate U80 DVB-T USB 2.0 High Definition Digital TV Stick
Can you give us the USB ID (type on the command line: lsusb, and report the output) The U90 has a RTL2831 in it. More info on the driver on: http://www.linuxtv.org/wiki/index.php/Rtl2831_devices drappa wrote: Hi All http://www.comprousa.com/en/product/u80/u80.html I'd be grateful if anyone can tell me if this device is supported yet, and if so, any pointers to getting it working. Thanks Drappa -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Compro VideoMate U80 DVB-T USB 2.0 High Definition Digital TV Stick
So: it is a Realtek 2831 device. Please first check /lib/udev/rules.d/50-udev-default.rules. There seems to be a generic problem with Karmac there. Look at http://ubuntuforums.org/showthread.php?t=1327337 which gives solution for the problem by installing a new rule:- /etc/udev/rules.d/50-udev.rules Under Ubuntu Karmac, I have heard that the anttip/rtl2831u driver works (alas without IR support) with this workaround. Of the jhoogenraad/rtl2831-2 I have no confirmation yet. http://ubuntuforums.org/showthread.php?t=960113 Which one have you downloaded ? drappa wrote: Jan Hoogenraad wrote: Can you give us the USB ID (type on the command line: lsusb, and report the output) The U90 has a RTL2831 in it. More info on the driver on: http://www.linuxtv.org/wiki/index.php/Rtl2831_devices Hi Jan USB ID is : 185b-0150 Compro I built the driver as per the link but the device does not initialise. Tested using an Ubuntu Studio Karmic installation with two afatech 9015 USB devices connected ok Thanks drappa drappa wrote: Hi All http://www.comprousa.com/en/product/u80/u80.html I'd be grateful if anyone can tell me if this device is supported yet, and if so, any pointers to getting it working. Thanks Drappa -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [linux-dvb] Organizing ALL device data in linuxtv wiki
that will display those attributes (and ignore things like firmware or url) The only attributes I'd like to have in all devices are vendor, device and did (Device ID). -henrik PS: As you see from the number of links to widely different pages, a wiki is NOT a good solution for discussions. Just to avoid the impression that wiki's are my new hammer. :-) ___ linux-dvb users mailing list For V4L/DVB development, please use instead linux-media@vger.kernel.org linux-...@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Make file request: default adddepmod instead of allyesmod
I tried to guide a newbie through compiling v4l. v4l did not compile right away, because of a problem in one of the drivers http://ubuntuforums.org/showthread.php?p=8241469#post8241469 a workaroudn was proposed: http://ubuntuforums.org/showthread.php?t=1305228 I myself have not experienced this problem as I have used make alldepmod, where the offending driver was not selected. Can the default config be reprogrammed from all yes (which might easily fail on certain kernel versions) to the all dep config ? That way, new users have more chance to have a succesful make right away. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Trying to compile for kernel version 2.6.28
Thanks a lot. Only syncing my sources every 2 months, I forgot about the make allmodconfig I keep http://linuxtv.org/hg/~jhoogenraad/rtl2831-r2. in sync until Antti's sources have been tested, and IR support is put in, so that these sticks can be supported from the normal kernel. Mauro Carvalho Chehab wrote: Hi Jan, Em Tue, 03 Nov 2009 16:45:15 +0100 Jan Hoogenraad jan-conceptro...@hoogenraad.net escreveu: At this moment, I cannot figure out how to compile v4l with kernel version 2.6.28. I see, however, that the daily build reports: linux-2.6.28-i686: OK Yes, and that's correct. It does compile from scratch with 2.6.28. If you look at v4l/versions.txt, this is already marked to compile only with kernels 2.6.31 or newer. It should be noticed, however, that the building system won't touch at your .config if you just do an hg update (or hg pull -u). You'll need to ask it explicitly to process versions.txt again, by calling one of the alternatives bellow that re-generates a v4l/.config. If you are using a customized config, you'll need to call either one of those: make menuconfig make config make xconfig or make gconfig (in this specific case, just entering there and saving the config is enough - there's no need to touch on any items) Or, at the simple case were you're just building everything, you'll need to do: make allmodconfig A side effect of touching at v4l/.config is that all (selected) drivers will recompile again. Cheers, Mauro -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Trying to compile for kernel version 2.6.28
At this moment, I cannot figure out how to compile v4l with kernel version 2.6.28. I see, however, that the daily build reports: linux-2.6.28-i686: OK I have the same problem as in the old message: http://www.spinics.net/lists/linux-media/msg10047.html I have included the text of that message below. How do I revert the latest changepatch to videobuf-dma-config ? And could somebody preferably put a kernel-version-dependent #if around that changepatch ? --- / / / Then I made it here:/ / / / CC [M] /home/mythbox/Firmware/v4l-dvb/v4l/videobuf-core.o/ / CC [M] /home/mythbox/Firmware/v4l-dvb/v4l/videobuf-dma-sg.o/ / CC [M] /home/mythbox/Firmware/v4l-dvb/v4l/videobuf-dma-contig.o/ / /home/mythbox/Firmware/v4l-dvb/v4l/videobuf-dma-contig.c: In function/ / 'videobuf_dma_contig_user_get':/ / /home/mythbox/Firmware/v4l-dvb/v4l/videobuf-dma-contig.c:164: error:/ / implicit declaration of function 'follow_pfn'/ / make[3]: *** [/home/mythbox/Firmware/v4l-dvb/v4l/videobuf-dma-contig.o] Error 1/ / make[2]: *** [_module_/home/mythbox/Firmware/v4l-dvb/v4l] Error 2/ / make[2]: Leaving directory `/usr/src/linux-headers-2.6.28-15-generic'/ / make[1]: *** [default] Error 2/ / make[1]: Leaving directory `/home/mythbox/Firmware/v4l-dvb/v4l'/ / make: *** [all] Error 2/ / / / Its kinda annoying that a year ago this was super easy.../ / / / I dont really want to bump up to 2.6.31 seeing it just came out a few days ago./ Ok, this is the usual backport issues we have every time we need to backport patches upstream. This should be solved soon, but currently my priority is to merge the pending patches at the tree. Up to then, you may do a: make menuconfig and select only the drivers you need, or just revert the latest changepatch to videobuf-dma-config. Cheers, Mauro -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Rework the RTL2831 remote control handler to reuse dibusb.
, ir_protocol);
@@ -237,47 +199,9 @@
return 1;
}
-static int rtd2831u_rc_key_to_event(struct dvb_usb_device *d,
- u8 keybuf[4], u32 * event, int *state)
-{
- int i;
- struct dvb_usb_rc_key *keymap = d-props.rc_key_map;
- *event = 0;
- *state = REMOTE_NO_KEY_PRESSED;
-
- switch (ir_protocol) {
- case RTL2831U_RC5_TYPE:
- keybuf[0] = (keybuf[0] 0x00);
- keybuf[1] = (keybuf[1] 0x00);
- keybuf[2] = (keybuf[2] 0x00);
- keybuf[3] = (keybuf[3] 0xff);
- break;
- }
-
-/* deb_info(raw key code 0x%02x, 0x%02x, 0x%02x,
0x%02x\n,keybuf[0], keybuf[1], keybuf[2], keybuf[3]); */
- /* See if we can match the raw key code. */
- for (i = 0; i d-props.rc_key_map_size; i++)
- if (keymap[i].custom == keybuf[2]
-keymap[i].data == keybuf[3]) {
- *event = keymap[i].event;
- *state = REMOTE_KEY_PRESSED;
- return 0;
- }
-
- if (*state != REMOTE_KEY_PRESSED) {
- deb_info
- (Unmatched raw key code 0x%02x, 0x%02x, 0x%02x, 0x%02x:
please
try other setting for parameter ir_protocol\n,
-keybuf[0], keybuf[1], keybuf[2], keybuf[3]);
- }
-
- return 0;
-
-}
-
static int rtd2831u_rc_query(struct dvb_usb_device *d, u32 * event, int *state)
{
- u8 key[4];
- u8 b = 0xcc;
+ u8 key[5] = {0xcc, 0, 0, 0, 0};
struct rtl2831u_rc_state *p_rc_state = d-priv;
*event = 0;
@@ -290,21 +214,36 @@
goto error;
}
- if (RTD2831_READ_BYTES(d, RTD2831U_SYS, IRRC_SR, b, 1))
+ if (RTD2831_READ_BYTES(d, RTD2831U_SYS, IRRC_SR, key[0], 1))
goto error;
- if (b 0x01) {
- if (RTD2831_READ_BYTES(d, RTD2831U_SYS, IRRC_RP, key, 4))
+ if (key[0] 0x01) {
+ if (RTD2831_READ_BYTES(d, RTD2831U_SYS, IRRC_RP, key[1], 4))
goto error;
- b = 0x01;
- if (RTD2831_WRITE_BYTES(d, RTD2831U_SYS, IRRC_SR, b, 1))
+ key[0] = 0x01;
+ if (RTD2831_WRITE_BYTES(d, RTD2831U_SYS, IRRC_SR, key[0], 1))
goto error;
if (++p_rc_state-repeat_key_count
p_rc_state-rc_key_repeat_count)
return 0; /*set two events to 1(repeat.) */
- rtd2831u_rc_key_to_event(d, key, event, state);
+ /* in the old code, keybuf was 4 bytes. in the dibusb, keybuf
is 5 bytes.
+ byte 0 is the cmd. bytes 1-4 are bytes 0-3 from the old.
+ so we must switch around some bytes to make the rc5 table
valid.
+ This probably isn't necessary (can just fix the table
instead)
+ but I can't tell without the actual un-switched remote
codes. */
+
+ switch (ir_protocol) {
+ case RTL2831U_RC5_TYPE:
+ key[1] = 0x00; // custom - 0 in rc5 table
+ key[2] = 0xff; // checksum/compliment of keybuf[1]
+ key[3] = (key[4] 0xff); // data (need to move it)
+ key[4] = ~key[3]; // checksum/compliment
+ break;
+ }
+
+ dvb_usb_nec_rc_key_to_event(d, key, event, state);
p_rc_state-repeat_key_count = 0;
/*(prev.line) reset counter to 0*/
}
@@ -412,17 +351,16 @@
.rc_interval = 300,
#ifdef RTL2831U_NEC_PROTOCOL
- .rc_key_map = rtd2831u_nec_keys,
- .rc_key_map_size = ARRAY_SIZE(rtd2831u_nec_keys),
-#else
-#ifdef RTL2831U_RC5_PROTOCOL
+ .rc_key_map = dibusb_rc_keys,
+ .rc_key_map_size = 135,
+#elif defined RTL2831U_RC5_PROTOCOL
.rc_key_map = rtd2831u_rc5_keys,
.rc_key_map_size = ARRAY_SIZE(rtd2831u_rc5_keys),
#elif defined RTL2831U_CONCEPTRONIC_PROTOCOL
.rc_key_map = rtd2831u_conceptronic_keys,
.rc_key_map_size = ARRAY_SIZE(rtd2831u_conceptronic_keys),
#endif
-#endif
+
.rc_query = rtd2831u_rc_query,
.num_device_descs = 8,
@@ -487,17 +425,15 @@
.rc_interval = 300,
#ifdef RTL2831U_NEC_PROTOCOL
- .rc_key_map = rtd2831u_nec_keys,
- .rc_key_map_size = ARRAY_SIZE(rtd2831u_nec_keys),
-#else
-#ifdef RTL2831U_RC5_PROTOCOL
+ .rc_key_map = dibusb_rc_keys,
+ .rc_key_map_size = 135,
+#elif defined RTL2831U_RC5_PROTOCOL
.rc_key_map = rtd2831u_rc5_keys,
.rc_key_map_size = ARRAY_SIZE(rtd2831u_rc5_keys),
#elif defined RTL2831U_CONCEPTRONIC_PROTOCOL
.rc_key_map = rtd2831u_conceptronic_keys,
.rc_key_map_size = ARRAY_SIZE(rtd2831u_conceptronic_keys),
#endif
-#endif
.rc_query = rtd2831u_rc_query,
.num_device_descs = 5,
--
Jan Hoogenraad
Hoogenraad
Re: Ralink RTL2831U
Please note that the current (not split-up) driver was developed by the maker of the hardware. It is the same code that is used in the Windows driver. As far as I have seen, there is only ONE callback from the tuner code to the demodulator. I forgot the name of the routine. Cheers, Jan Antti Palosaari wrote: Moi Jelle, On 06/26/2009 11:26 AM, Jelle de Jong wrote: Question for Antti if he had any luck with the devices (rtl2831-r2) I send? I have been busy with other drivers, but now I have time for this. It was a little bit tricky to take sniffs from Windows because sniffer crashed very easily with this device :o But after testing about all drivers I found and after countless blue-screens I finally got one good sniff. From sniff I see this device is rather simple to program. And device you send have MT2060 tuner. With a any luck and without other summer activities (I am still hoping warm weather and beach activities :) it will not take many days to get picture. After that I will move relevant parts from the current Ralink driver to the new driver... I will keep informed about driver status. regards Antti -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [linux-dvb] Remote af9015 Conceptronic
The IR tables are hardcoded in the driver that can be found at: http://linuxtv.org/hg/~jhoogenraad/rtl2831-r2 It has 3 sets parameters, and by default is set to tthe NEC one. ir_protocol Specify RTL2381 remote: 0=NEC, 1=RC5, 2=Conceptronic (defaults to 0) sudo modprobe -r dvb_usb_rtl2831u sudo modprobe dvb-usb-rtl2831u ir_protocol=2 to be compliant with the Conceptronic IR Daniel Sanchez wrote: Hi, I'm have Conceptronic USB2.0 DVB-T CTVDIGRCU V3.0 and remote not working, In method 'af9015_read_config' set IR mode: 4 and set rc_key_map to NULL; Why I'm read ir_table to set? It's possible follow this instructions? http://linuxtv.org/wiki/index.php/Remote_controllers-V4L#How_to_add_remote_control_support_to_a_card_.28GPIO_remotes.29 Thanks ___ linux-dvb users mailing list For V4L/DVB development, please use instead linux-media@vger.kernel.org linux-...@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- Jan Hoogenraad Hoogenraad Interface Services Postbus 2717 3500 GS Utrecht -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [not working] Conceptronic USB 2.0 Digital TV Receiver - CTVDIGRCU - Device Information
Jelle de Jong wrote: Antti Palosaari wrote: Terve Jelle, On 04/24/2009 04:10 PM, Antti Palosaari wrote: On 04/24/2009 03:25 PM, Jelle de Jong wrote: I got an USB ID 14aa:0160 Conceptronic USB2.0 DVB-T CTVDIGRCU V2.0 but I have no idea what chipsets it contains. Could somebody extract the drivers to be sure? (see my first mail for driver web pages) http://www.conceptronic.net/site/desktopdefault.aspx?tabindex=0tabid=420pc=CTVDIGRCU There is no drivers for device USB-ID 14aa:0160. ; Copyright (C) Wideviewer Corporation, 2005 All Rights Reserved. ; ; USB DVB-T Adapter ; WideViewer DVB-T WT-225U ; The Vendor ID =14AA, and the Product ID =0226 %DevModel.DeviceDesc%=DevModel.Dev,USB\VID_14AAPID_0226MI_00 According to google search it could be Realtek. http://ubuntuforums.org/showthread.php?t=822291page=2 I just got that device from post. I installed driver from: http://linuxtv.org/hg/~jhoogenraad/rtl2831-r2 and it is working :( Driver identifies this device as Freecom USB 2.0 DVB-T Device. I have don't know exactly what's driver status currently - is is only in development tree currently. Could Jan Hoogenraad comment what should do before driver is ready to the master release? regards Antti That is great news, now lets see what is needed to get the code stable in the mainstream kernel code. So it will work out of the box with the upcoming kernel releases. Did you need any proprietary firmware? Does the device work with mplayer does the dvb-t radio work? Cheers, Jelle -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html In kernel integration: I'll re-post my entry of september 16, 2008. This entry is still valid. I have updated working repository rtl2831-r2 on a regular basis, both for syning with the kernel, and updating e.g. USB-IDs. I've posted the same message on a list where there was some other activity, but got no response yet. http://ubuntuforums.org/showthread.php?t=960113page=2 -- The repository at http://linuxtv.org/hg/~jhoogenraad/rtl2831-r2. Thus: hg clone http://linuxtv.org/hg/~jhoogenraad/rtl2831-r2 make make install should be working at all times. I synchronise it once in a while to keep it running. Splitting the code up into front-end and back-end is more of a hassle than I assumed. I'm struggling with the old include files, the data structures (where used) and the linux interface protocols in general. A version that does not even compile (NO USE FOR END USERS !) http://linuxtv.org/hg/~jhoogenraad/rtl2831-sepfront I have synched the version with the version on my harddisk. Part of the code is already recycled into the kernel. As Alistair noticed, this is now blocking for getting the support for the stick into the main line. A pity for the users, Peter Mayer wrote: --- Steven Toth st...@linuxtv.org schrieb am So, 14.9.2008: So, I wonder now what the next steps are to make this driver available in the linux kernel, and when it will probably happen. I gather the tree has some significant merge issues, that's probably why it hasn't been merged. Generally if the drivers are legally clean, code clean they get merged in a couple of weeks. Sorry if I need to ask again, but what does this actually mean with respect to that specific driver rtl2821u? I just wonder. My problem is that in Ubuntu Hardy I managed to make this stick work, but in Debian SID I have no idea how to get it work. When I do hg clone http://linuxtv.org/hg/v4l-dvb make make install the stick is not recognized. The entries in /var/log/syslog are: Sep 15 23:35:55 kernel: usb 3-3: New USB device found, idVendor=14aa, idProduct=0160 Sep 15 23:35:55 kernel: usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 15 23:35:55 kernel: usb 3-3: Product: DTV Receiver Sep 15 23:35:55 kernel: usb 3-3: Manufacturer: DTV Receiver Sep 15 23:35:55 kernel: usb 3-3: SerialNumber: 00010205 When I unpack and make make install rtl2831u_dvb-usb_v0.0.2mod, syslog says: Sep 15 23:40:17 kernel: usb 3-3: new high speed USB device using ehci_hcd and address 3 Sep 15 23:40:17 kernel: usb 3-3: configuration #1 chosen from 1 choice Sep 15 23:40:17 kernel: usb 3-3: New USB device found, idVendor=14aa, idProduct=0160 Sep 15 23:40:17 kernel: usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 15 23:40:17 kernel: usb 3-3: Product: DTV Receiver Sep 15 23:40:17 kernel: usb 3-3: Manufacturer: DTV Receiver Sep 15 23:40:17 kernel: usb 3-3: SerialNumber: 00010205 Sep 15 23:40:17 NetworkManager: debug [1221514817.598859] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/usb_device_14aa_160_00010205'). Sep 15 23:40:17 NetworkManager: debug [1221514817.602281] nm_hal_device_added(): New
