Team for mobile apps
Do you have needs for mobile apps design? We are the one who can help you. We are an India based software company. What we focus is mobile apps development. We have 125 staffs in office and have created over 350 apps so far. We work on many different platforms, such as iOS, Android and others. Please reply if interested, we will send you our portfolios. Thanks, Ray Charles
Apps Design
Do you have needs for mobile apps design? We are the one who can help you. We are an India based software company. What we focus is mobile apps development. We have 125 staffs in office and have created over 350 apps so far. We work on many different platforms, such as iOS, Android and others. Please reply if interested, we will send you our portfolios. Thanks, Ray Charles
Apps Design
Do you have needs for mobile apps design? We are the one who can help you. We are an India based software company. What we focus is mobile apps development. We have 125 staffs in office and have created over 350 apps so far. We work on many different platforms, such as iOS, Android and others. Please reply if interested, we will send you our portfolios. Thanks, Ray Charles
We design apps
Do you have needs for mobile apps design? We are the one who can help you. We are an India based software company. What we focus is mobile apps development. We have 125 staffs in office and have created over 350 apps so far. We work on many different platforms, such as iOS, Android and others. Please reply if interested, we will send you our portfolios. Thanks, Ray Charles
[no subject]
Is there someone willing to assist me in finding out why my video configuration will not work? I am using a Sony HDR-SR11 as a webcam. Camorama does show video. Other video tools recognize it. Skype does not recognize it. Yahoo messenger shows video once I changed the video preference to Composite. The driver I am using is stk1160 on Ubuntu 12.04 In WebRTC (https://appear.in), stk1160 does show in the Firefox drop down menu for camera and microphone, but after I select it, it says it cannot connect. I'd appreciate a helping hand. Just beware I know little to nothing about how a web video is created and sent and what is needed to do that. Thanks and I appreciate your help. Ray -- 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-dib0700-1.20.fw Issues.
I have tried this now on Debian 32 and 64 bit versions with no joy. The sticks are fine as they work on Windows 7 perfectly. Any advice? On 15 January 2014 20:02, Ray Image imagemagi...@gmail.com wrote: I have tried a couple of USB sticks which use the dvb-usb-dib0700-1.20.fw firmware in a number of machines running different linux distros (CentOS, Debian and Raspbian) and I simply can't get them to work. I have put dvb-usb-dib0700-1.20.fw in /lib/firmware. Both USB sticks are recognised and loaded (see dmesg below) but won't tune. I have a PCTV 290e which works perfectly. Can anyone please help? Dmesg for Nova-T (this device fails): [ 850.170729] usb 1-2: Product: Nova-T Stick [ 850.170730] usb 1-2: Manufacturer: Hauppauge [ 850.170731] usb 1-2: SerialNumber: 4027796501 [ 850.181622] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware [ 850.185487] usb 1-2: firmware: agent loaded dvb-usb-dib0700-1.20.fw into memory [ 853.291628] dib0700: firmware started successfully. [ 853.794138] dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state. [ 853.794255] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 853.795277] DVB: registering new adapter (Hauppauge Nova-T Stick) [ 854.350077] DVB: registering adapter 1 frontend 0 (DiBcom 7000PC)... [ 854.359052] MT2060: successfully identified (IF1 = 1220) [ 854.999066] dvb-usb: Hauppauge Nova-T Stick successfully initialized and connected. Dmesg for MyTV.t (this device fails): [ 505.753256] usb 1-1: Product: myTV.t [ 505.753257] usb 1-1: Manufacturer: Eskape Labs [ 505.753258] usb 1-1: SerialNumber: 4030928317 [ 505.861413] dib0700: loaded with support for 21 different device-types [ 510.853328] dvb-usb: found a 'Hauppauge Nova-T MyTV.t' in cold state, will try to load a firmware [ 510.924679] usb 1-1: firmware: agent loaded dvb-usb-dib0700-1.20.fw into memory [ 514.327591] dib0700: firmware started successfully. [ 514.830712] dvb-usb: found a 'Hauppauge Nova-T MyTV.t' in warm state. [ 514.830796] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 514.832785] DVB: registering new adapter (Hauppauge Nova-T MyTV.t) [ 515.335819] DVB: registering adapter 0 frontend 0 (DiBcom 7000PC)... [ 515.789061] DiB0070: successfully identified [ 515.789065] dvb-usb: Hauppauge Nova-T MyTV.t successfully initialized and connected. [ 515.790175] usbcore: registered new interface driver dvb_usb_dib0700 Dmesg for PCTV290e (this device works): [ 314.918928] em28xx: New device PCTV Systems PCTV 290e @ 480 Mbps (2013:024f, interface 0, class 0) [ 314.920018] em28xx #0: chip ID is em28174 [ 315.251613] em28xx #0: Identified as PCTV nanoStick T2 290e (card=78) [ 315.331134] Registered IR keymap rc-pinnacle-pctv-hd [ 315.331262] input: em28xx IR (em28xx #0) as /devices/pci:00/:00:11.0/:02:03.0/usb1/1-1/rc/rc0/input6 [ 315.331726] rc0: em28xx IR (em28xx #0) as /devices/pci:00/:00:11.0/:02:03.0/usb1/1-1/rc/rc0 [ 315.338297] em28xx #0: v4l2 driver version 0.1.3 [ 315.408548] em28xx #0: V4L2 video device registered as video0 [ 315.408572] usbcore: registered new interface driver em28xx [ 315.408573] em28xx driver loaded [ 315.510762] tda18271 0-0060: creating new instance [ 315.540382] TDA18271HD/C2 detected @ 0-0060 [ 316.283833] tda18271 0-0060: attaching existing instance [ 316.283836] DVB: registering new adapter (em28xx #0) [ 316.283838] DVB: registering adapter 0 frontend 0 (Sony CXD2820R (DVB-T/T2))... [ 316.284044] DVB: registering adapter 0 frontend 1 (Sony CXD2820R (DVB-C))... [ 316.284947] em28xx #0: Successfully loaded em28xx-dvb [ 316.284950] Em28xx: Initialized (Em28xx dvb Extension) extension Output of scan for Nova-T and MyTV.t: scanning /usr/share/dvb/dvb-t/uk-Hannington using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 70600 0 3 9 1 0 0 0 initial transponder 650167000 0 2 9 3 0 0 0 initial transponder 626167000 0 2 9 3 0 0 0 initial transponder 674167000 0 3 9 1 0 0 0 initial transponder 658167000 0 3 9 1 0 0 0 initial transponder 634167000 0 3 9 1 0 0 0 tune to: 70600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 70600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 650167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 650167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 626167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64
dvb-usb-dib0700-1.20.fw Issues.
I have tried a couple of USB sticks which use the dvb-usb-dib0700-1.20.fw firmware in a number of machines running different linux distros (CentOS, Debian and Raspbian) and I simply can't get them to work. I have put dvb-usb-dib0700-1.20.fw in /lib/firmware. Both USB sticks are recognised and loaded (see dmesg below) but won't tune. I have a PCTV 290e which works perfectly. Can anyone please help? Dmesg for Nova-T (this device fails): [ 850.170729] usb 1-2: Product: Nova-T Stick [ 850.170730] usb 1-2: Manufacturer: Hauppauge [ 850.170731] usb 1-2: SerialNumber: 4027796501 [ 850.181622] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware [ 850.185487] usb 1-2: firmware: agent loaded dvb-usb-dib0700-1.20.fw into memory [ 853.291628] dib0700: firmware started successfully. [ 853.794138] dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state. [ 853.794255] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 853.795277] DVB: registering new adapter (Hauppauge Nova-T Stick) [ 854.350077] DVB: registering adapter 1 frontend 0 (DiBcom 7000PC)... [ 854.359052] MT2060: successfully identified (IF1 = 1220) [ 854.999066] dvb-usb: Hauppauge Nova-T Stick successfully initialized and connected. Dmesg for MyTV.t (this device fails): [ 505.753256] usb 1-1: Product: myTV.t [ 505.753257] usb 1-1: Manufacturer: Eskape Labs [ 505.753258] usb 1-1: SerialNumber: 4030928317 [ 505.861413] dib0700: loaded with support for 21 different device-types [ 510.853328] dvb-usb: found a 'Hauppauge Nova-T MyTV.t' in cold state, will try to load a firmware [ 510.924679] usb 1-1: firmware: agent loaded dvb-usb-dib0700-1.20.fw into memory [ 514.327591] dib0700: firmware started successfully. [ 514.830712] dvb-usb: found a 'Hauppauge Nova-T MyTV.t' in warm state. [ 514.830796] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 514.832785] DVB: registering new adapter (Hauppauge Nova-T MyTV.t) [ 515.335819] DVB: registering adapter 0 frontend 0 (DiBcom 7000PC)... [ 515.789061] DiB0070: successfully identified [ 515.789065] dvb-usb: Hauppauge Nova-T MyTV.t successfully initialized and connected. [ 515.790175] usbcore: registered new interface driver dvb_usb_dib0700 Dmesg for PCTV290e (this device works): [ 314.918928] em28xx: New device PCTV Systems PCTV 290e @ 480 Mbps (2013:024f, interface 0, class 0) [ 314.920018] em28xx #0: chip ID is em28174 [ 315.251613] em28xx #0: Identified as PCTV nanoStick T2 290e (card=78) [ 315.331134] Registered IR keymap rc-pinnacle-pctv-hd [ 315.331262] input: em28xx IR (em28xx #0) as /devices/pci:00/:00:11.0/:02:03.0/usb1/1-1/rc/rc0/input6 [ 315.331726] rc0: em28xx IR (em28xx #0) as /devices/pci:00/:00:11.0/:02:03.0/usb1/1-1/rc/rc0 [ 315.338297] em28xx #0: v4l2 driver version 0.1.3 [ 315.408548] em28xx #0: V4L2 video device registered as video0 [ 315.408572] usbcore: registered new interface driver em28xx [ 315.408573] em28xx driver loaded [ 315.510762] tda18271 0-0060: creating new instance [ 315.540382] TDA18271HD/C2 detected @ 0-0060 [ 316.283833] tda18271 0-0060: attaching existing instance [ 316.283836] DVB: registering new adapter (em28xx #0) [ 316.283838] DVB: registering adapter 0 frontend 0 (Sony CXD2820R (DVB-T/T2))... [ 316.284044] DVB: registering adapter 0 frontend 1 (Sony CXD2820R (DVB-C))... [ 316.284947] em28xx #0: Successfully loaded em28xx-dvb [ 316.284950] Em28xx: Initialized (Em28xx dvb Extension) extension Output of scan for Nova-T and MyTV.t: scanning /usr/share/dvb/dvb-t/uk-Hannington using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 70600 0 3 9 1 0 0 0 initial transponder 650167000 0 2 9 3 0 0 0 initial transponder 626167000 0 2 9 3 0 0 0 initial transponder 674167000 0 3 9 1 0 0 0 initial transponder 658167000 0 3 9 1 0 0 0 initial transponder 634167000 0 3 9 1 0 0 0 tune to: 70600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 70600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 650167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 650167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 626167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 626167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to:
Hauppauge Nova-T Stick 3 Issues
Hi all, I recently purchased a Hauppauge Nova-T USB DVB-T receiver and have been having trouble getting it to work. I read through the Wiki page (http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-Stick) for this device and followed the instructions but still no luck. Most of the time the frontend will fail to attach (as show below), on the rare occasions when the frontend does attach it will hang when I try to scan for channels. In both cases the driver complains of I2C read/write failures. I am using the latest from code from the V4L-DVB backports repository with a 2.6.35 Kernel (Mythubuntu 10.10) Any advice on what to try? r...@pvr:~$ uname -a Linux pvr 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:34:50 UTC 2010 i686 GNU/Linux r...@pvr:~$ lsusb Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub ... Bus 001 Device 004: ID 2040:7070 Hauppauge Nova-T Stick 3 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub r...@pvr:~$ dmesg [ 18.492014] usb 1-4: new high speed USB device using ehci_hcd and address 4 [ 18.653158] WARNING: You're using an experimental version of the DVB stack. As the driver [ 18.653160] is backported to an older kernel, it doesn't offer enough quality for [ 18.653161] its usage in production. [ 18.653161] Use it with care. [ 18.667402] dib0700: loaded with support for 14 different device-types [ 18.667425] check for cold 10b8 1e14 [ 18.667426] check for cold 10b8 1e78 [ 18.667427] check for cold 2040 7050 [ 18.667428] check for cold 2040 7060 [ 18.667430] check for cold 7ca a807 [ 18.667431] check for cold 7ca b808 [ 18.667432] check for cold 185b 1e78 [ 18.667433] check for cold 185b 1e80 [ 18.667434] check for cold 1584 6003 [ 18.667436] check for cold 413 6f00 [ 18.667437] check for cold 413 6f01 [ 18.667438] check for cold 7ca b568 [ 18.667439] check for cold 1044 7001 [ 18.667440] check for cold 2040 9941 [ 18.667441] check for cold 2040 9950 [ 18.667443] check for cold 2304 22c [ 18.667444] check for cold ccd 5a [ 18.667445] check for cold 2040 9580 [ 18.667446] check for cold 10b8 1ef0 [ 18.667447] check for cold 1164 1e8c [ 18.667448] check for cold b05 171f [ 18.667450] check for cold 1164 1edc [ 18.667451] check for cold ccd 62 [ 18.667452] check for cold 10b8 1ebc [ 18.667453] check for cold 2304 228 [ 18.667454] check for cold 5d8 810f [ 18.667456] check for cold b05 173f [ 18.667457] check for cold 2040 7070 [ 18.667565] FW GET_VERSION length: -32 [ 18.667567] cold: 1 [ 18.667568] dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware [ 18.674300] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw' [ 18.875965] dib0700: firmware started successfully. [ 24.376079] dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state. [ 24.376086] power control: 1 [ 24.376129] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 24.376546] DVB: registering new adapter (Hauppauge Nova-T Stick) [ 74.424074] ep 0 read error (status = -110) [ 74.424079] I2C read failed on address 0x40 [ 84.424148] ep 0 read error (status = -110) [ 84.424151] I2C read failed on address 0x09 [ 84.424157] dib0700: stk7070p_frontend_attach: dib7000p_i2c_enumeration failed. Cannot continue [ 84.424159] [ 84.424162] dvb-usb: no frontend was attached by 'Hauppauge Nova-T Stick' [ 84.424166] power control: 0 [ 84.424168] dvb-usb: Hauppauge Nova-T Stick successfully initialized and connected. [ 89.424093] Firmware version: 0, -1941421839, 0x100, 1348026105 [ 94.424065] dib0700: ir protocol setup failed [ 94.424104] usbcore: registered new interface driver dvb_usb_dib0700 r...@pvr:~$ cat /etc/modprobe.d/options.conf options dvb_usb_dib0700 force_lna_activation=1 debug=1 options dvb_usb disable_rc_polling=1 debug=1 options dvb_core debug=1 r...@pvr:~$ lsmod Module Size Used by dvb_usb_dib070056317 0 dib7000p 16176 1 dvb_usb_dib0700 dib00901 1 dvb_usb_dib0700 dib7000m 13132 1 dvb_usb_dib0700 dib0070 7766 1 dvb_usb_dib0700 dvb_usb17643 1 dvb_usb_dib0700 dib800025510 1 dvb_usb_dib0700 dvb_core 86744 3 dib7000p,dvb_usb,dib8000 dib3000mc 11200 1 dvb_usb_dib0700 dibx000_common 3112 4 dib7000p,dib7000m,dib8000,dib3000mc usbhid 36882 0 hid67742 1 usbhid ... Thanks Ray Kinsella -- 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
technisat cablestar hd2, cinergy C pci hd, 2.6.35, no remote (VP2040)
This is with reference to: http://www.spinics.net/lists/linux-media/msg15042.html It looks to me that the IR interface related stuff is not in the 2.6.35 kernel either. Since I need it for a set-top box that I building, I was looking for the canonical source for that code so that I can package it separately. Till now I have only found the bits in Igor's s2-liplianin tree. However it looks to me that the code did not originate there because the RC keymap file (linux/drivers/media/IR/keymaps/rc-vp2040.c) was created by a commit marked merge http://linuxtv.org/hg/v4l-dvb; (hg export 15052). I am confused because the v4l-dvb tree does not have the VP2040 IR bits, and my limited knowledge of Mercurial is hindering me from figuring out the origins of the code. Could you kindly point me to the correct direction? Thanks, Debarshi -- The camera is to the brush what Java is to assembly. -- Sougata Santra -- 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: technisat cablestar hd2, cinergy C pci hd, 2.6.35, no remote (VP2040)
AFAIR, the code originated from these changesets: http://jusst.de/hg/mantis-v4l-dvb.old/rev/9cb8ffc573a2 http://jusst.de/hg/mantis-v4l-dvb.old/rev/c2391fa88112 later on, it was moved to another repository http://jusst.de/hg/mantis-v4l-dvb/rev/ad8b00c9edc2 But the code in Igor's s2-liplianin tree has evolved further than the one in the mantis-v4l-dvb tree. eg., the keymaps are now split into separate files in drivers/media/IR/keymaps. Is there any Git tree with the latest state of the code or is the s2-liplianin tree the one I am looking for? Thanks, Debarshi -- The camera is to the brush what Java is to assembly. -- Sougata Santra -- 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
pinnacle 801e help please!
I am new to Linux (somewhat) and I am running Linux mint 9. So far so good, I have replaced dreamweaver with NVU, office with open office. Outlook with evolution and so on. Everything is now perfect no looking back to windows except I just spent about 1.5 hours going through configuring mythtv only to find it doesn't think my pinnacle usb hd stick is a dvb device. So i did more research and stumbled upon all of your hard work and tried downloading the tar for my device but it wouldn't download. 2 questions 1) will this device work now 2) how do I implement all of you fixes in mint Linux 9 gnome running mythtv? thanks for any help Ray -- 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 port on TechniSat CableStar HD 2
I read [1] that you were working on adding support for the IR port on the TechniSat CableStar HD 2 card. However, when I tried to compile the drivers from http://linuxtv.org/hg/v4l-dvb as instructed on http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers#If_the_Modules_did_not_load_correctly_or_the_device_is_still_not_configured_correctly_for_use it did not work. The device is not listed in /proc/bus/input/devices I am using Debian testing which has the 2.6.32 kernel and here are some of the modules I have loaded: b...@bob:~$ lsmod | grep mantis mantis 14872 0 mantis_core23989 6 mantis ir_common 3621 1 mantis_core ir_core10193 7 ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_rc5_decoder,mantis_core,ir_nec_decoder,ir_common tda665x 2679 1 mantis lnbp21 1740 1 mantis mb86a1616566 1 mantis stb6100 5525 1 mantis tda100214774 1 mantis tda100235823 1 mantis zl10353 5861 1 mantis stb089928713 1 mantis stv0299 7812 1 mantis dvb_core 74866 3 b2c2_flexcop,mantis_core,stv0299 i2c_core 15712 20 b2c2_flexcop,cx24123,cx24113,s5h1420,mantis,mantis_core,tda665x,lnbp21,mb86a16,stb6100,tda10021,tda10023,zl10353,stb0899,stv0299,nouveau,drm_kms_helper,drm,i2c_algo_bit,i2c_nforce2 I also tried to build the drivers from http://jusst.de/hg/mantis-v4l-dvb/ but the build failed. Could you please let me know what is the current status? Thanks, Debarshi [1] http://www.mail-archive.com/linux-media@vger.kernel.org/msg14620.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
Re: [RFC] What are the goals for the architecture of an in-kernel IR system?
On Sun, Nov 29, 2009 at 9:28 AM, Maxim Levitsky maximlevit...@gmail.com wrote: This has zero advantages besides good developer feeling that My system has one less daemon... Surely it's clear that having an unnecessary daemon is introducing another point of failure? Reducing complexity is not just its own reward in a 'Developer Feel Good' way. If decoding can *only* be sanely handled in user-space, that's one thing. If it can be handled in kernel, then that would be better. -- 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: [RFC] What are the goals for the architecture of an in-kernel IR system?
On Sun, Nov 29, 2009 at 10:13 AM, Alan Cox a...@lxorguk.ukuu.org.uk wrote: If decoding can *only* be sanely handled in user-space, that's one thing. If it can be handled in kernel, then that would be better. Why ? I can compute fast fourier transforms in the kernel but that doesn't make it better than doing it in user space. Of course not. I can write web servers in the kernel and the same applies. I'm not so young as to not recall Tux. That was again a bad idea, for the same reason. It introduced unnecessary complexity. Enabling userspace to be able to service web requests faster improved all user-space code. Yay. The question is which solution is more complex, the current one that requires userspace to be an active participant in the decoding, so that we can handle bare diodes hooked up to a sound-card, or having the kernel do decode for the sane devices and providing some fall-back for broken hardware. The former has the advantage of being flexible at the cost of increased fragility and surface area for security, and latency in responding to events, the latter has the problem of requiring two different decoding paths to be maintained, at least if you want to support odd-ball hardware. Jon is asking for an architecture discussion, y'know, with use cases. Maxim seems to be saying it's obvious that what we have today works fine. Except it doesn't appear that we have a consensus that everything is fine, nor an obvious winner for how to reduce the complexity here and keep the kernel in a happy, maintainable state for the long haul. Who knows, perhaps I misunderstood the dozens of messages up-thread -- wouldn't be the first time, in which case I'll shut up and let you get back to work. -- 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: [RFC] What are the goals for the architecture of an in-kernel IR system?
On Sun, Nov 29, 2009 at 3:35 PM, Andy Walls awa...@radix.net wrote: If decoding can *only* be sanely handled in user-space, that's one thing. If it can be handled in kernel, then that would be better. Why does the address space in which decoding is performed make the decoding process better or worse? The in kernel infrastructre and restrictions add constraints to a decoding implementation. Userspace is much more flexible. In which case I look forward to seeing your patches to move drivers/hid/ to userspace. Please cc: me so I can enjoy the ensuing festival. -- 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
