Hauppauge Aero-M Driver Problem
Hello, all: Since my previous e-mail, I was able to get a Linux driver for the tuner from Hauppauge. It came in the form of a v4l tree with the driver included. I adjusted the v4l/.config file to only build the necessary driver. Once it built and I invoked depmod -a, I hooked in my tuner, it detected the tuner, but then dmesg gave me: [31537.360109] dvb_usb_mxl111sf: probe of 2-1.4:1.0 failed with error -22 Does anyone have any idea what this could be? I can't find anything helpful about error -22 when I go looking. I can provide the link to the driver or output from any command requested, I just need to know what to provide and how best to share it. There was also a driver for the Mobile DTV half of the tuner included, but I could not get that part to build successfully, so I abandoned it for the time being in favor of getting the regular ATSC part to work. Thanks for any thoughts or assistance. It is greatly appreciated. =) - Trip www.rabbitears.info -- 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
TerraTec T6 Dual Tuner Stick initial support available
Hi all, just wanted to inform you that I got the TerraTec Dual DVB-T Stick working using a slightly patched driver from Afatech. Please see the wiki entry http://www.linuxtv.org/wiki/index.php/TerraTec_T6_Dual_DVB-T_Stick Currently both tuners work, but the remote doesn't. This driver is only supposed to be a temporary solution until I have integrated the bits into Antti's af9035 driver, see http://openee.googlecode.com/svn-history/r137/trunk/recipes/v4l-dvb/files/v4l- dvb-af9035.patch http://openee.googlecode.com/svn-history/r137/trunk/recipes/v4l-dvb/files/v4l- dvb-af9033.patch Regards, Hans-Frieder Hans-Frieder Vogt e-mail: hfvogt at gmx .dot. net -- 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 7/9] ARM: DMA: steal memory for DMA coherent mappings
On Fri, Aug 12, 2011 at 02:53:05PM +0200, Arnd Bergmann wrote: On Friday 12 August 2011, Marek Szyprowski wrote: From: Russell King rmk+ker...@arm.linux.org.uk Steal memory from the kernel to provide coherent DMA memory to drivers. This avoids the problem with multiple mappings with differing attributes on later CPUs. Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk [m.szyprowski: rebased onto 3.1-rc1] Signed-off-by: Marek Szyprowski m.szyprow...@samsung.com Hi Marek, Is this the same patch that Russell had to revert because it didn't work on some of the older machines, in particular those using dmabounce? I thought that our discussion ended with the plan to use this only for ARMv6+ (which has a problem with double mapping) but not on ARMv5 and below (which don't have this problem but might need dmabounce). I thought we'd decided to have a pool of available CMA memory on ARMv6K to satisfy atomic allocations, which can grow and shrink in size, rather than setting aside a fixed amount of contiguous system memory. ARMv6 and ARMv7+ could use CMA directly, and = ARMv5 can use the existing allocation method. Has something changed? -- 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: TerraTec T6 Dual Tuner Stick initial support available
On 08/14/2011 10:30 AM, Hans-Frieder Vogt wrote: just wanted to inform you that I got the TerraTec Dual DVB-T Stick working using a slightly patched driver from Afatech. Please see the wiki entry http://www.linuxtv.org/wiki/index.php/TerraTec_T6_Dual_DVB-T_Stick Currently both tuners work, but the remote doesn't. This driver is only supposed to be a temporary solution until I have integrated the bits into Antti's af9035 driver, see http://openee.googlecode.com/svn-history/r137/trunk/recipes/v4l-dvb/files/v4l- dvb-af9035.patch http://openee.googlecode.com/svn-history/r137/trunk/recipes/v4l-dvb/files/v4l- dvb-af9033.patch Situation of my AF9035 AF9033 driver is and have been years totally frozen, I given it up since I never got permission from ITE to push it Kernel and firmware distribution. Thus I left it. I have had in mind to write out all vendor code (not much code I think) to get rid of copyrights and do what I want - but never had enough time. Due to that I am not going to work my AF9035 + AF9033 unless something changes dramatically at least now when there is other drivers. regards Antti -- http://palosaari.fi/ -- 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: Hauppauge Aero-M Driver Problem
On Sun, Aug 14, 2011 at 2:33 AM, Trip Ericson webmas...@rabbitears.info wrote: Hello, all: Since my previous e-mail, I was able to get a Linux driver for the tuner from Hauppauge. It came in the form of a v4l tree with the driver included. I adjusted the v4l/.config file to only build the necessary driver. Once it built and I invoked depmod -a, I hooked in my tuner, it detected the tuner, but then dmesg gave me: [31537.360109] dvb_usb_mxl111sf: probe of 2-1.4:1.0 failed with error -22 Does anyone have any idea what this could be? I can't find anything helpful about error -22 when I go looking. I can provide the link to the driver or output from any command requested, I just need to know what to provide and how best to share it. There was also a driver for the Mobile DTV half of the tuner included, but I could not get that part to build successfully, so I abandoned it for the time being in favor of getting the regular ATSC part to work. Thanks for any thoughts or assistance. It is greatly appreciated. =) - Trip Hello Trip, If Hauppauge provided you a driver, you need to direct all support questions to them. We aren't going to know the first thing about what is wrong with such a driver since we've never seen it. If they've made available a driver in source form under the GPL, that's a great first step. However it doesn't mean that the open source community all of a sudden becomes responsible for the burden associated with supporting such a driver (in particular when no datasheets have been made available). Cheers, Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- 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
How to git and build HVR-2200 drivers from Kernel labs ?
Hi I've got a 8940 edition of a Hauppauge HVR-2200. The driver is called saa7164. The versions included in my OS (mythbuntu 10.10 x86 32bit, kernel 2.6.35-30) and from linuxtv.org are too old to recognise the 8940 edition. Posts #124 to #128 in the Hauppauge HVR-2200 Tuner Install Guide topic (http://www.pcmediacenter.com.au/forum/topic/37541-hauppauge-hvr-2200-tuner- install-guide/page__view__findpost__p__321195) document my efforts with those versions. So I wish to use the latest stable drivers from the driver maintainers, ie http://kernellabs.com/gitweb/?p=stoth/saa7164-stable.git;a=summary Problem is, I don't know git and I don't know how I'm suppose to git, build and install it. Taking a guess I've tried: git clone git://kernellabs.com/stoth/saa7164-stable.git cd saa7164-stable make menuconfig make However I suspect these are not the optimum steps, as it seems to have downloaded and built much more than just the saa7164 drivers. The git pulled down nearly 1GB (which seems a lot) and the resultant menuconfig produced a very big .config. Am I doing the right steps or should I be doing something else to git, build and install the latest drivers ? Thanks, Declan -- 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: PCTV 290e nanostick and remote control support
On 08/14/2011 04:48 AM, Devin Heitmueller wrote:
On Sat, Aug 13, 2011 at 9:43 PM, Chris Rankin ranki...@yahoo.com wrote:
The rc-pinnacle-pctv-hd keymap is missing the definition of the OK key:
--- linux-3.0/drivers/media/rc/keymaps/rc-pinnacle-pctv-hd.c.orig
2011-08-14 02:42:01.0 +0100
+++ linux-3.0/drivers/media/rc/keymaps/rc-pinnacle-pctv-hd.c2011-08-14
02:12:45.0 +0100
@@ -20,6 +20,7 @@
{ 0x0701, KEY_MENU }, /* Pinnacle logo */
{ 0x0739, KEY_POWER },
{ 0x0703, KEY_VOLUMEUP },
+ { 0x0705, KEY_OK },
{ 0x0709, KEY_VOLUMEDOWN },
{ 0x0706, KEY_CHANNELUP },
{ 0x070c, KEY_CHANNELDOWN },
Cheers,
Chris
Wow, how the hell did I miss that? I did numerous remotes for em28xx
based devices that use that RC profile, and never noticed that issue.
Will have to check the merge logs. Maybe the key got lost when they
refactored the IR support.
It seems to be very old bug, year 2007, not coming from merge errors! It
could be even possible there have not been such button originally. Very
weird situation none have found it earlier. For example I just pressed
few buttons to see number are coming to console = OK it works (didn't
looked all buttons sends events).
That's commit which adds those keytables:
commit 54d75ebaa02809f24a16624e32706af3bf97588e
regards
Antti
--
http://palosaari.fi/
--
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: How to git and build HVR-2200 drivers from Kernel labs ?
On Sun, Aug 14, 2011 at 5:21 AM, Declan Mullen declan.mul...@bigpond.com wrote: Hi I've got a 8940 edition of a Hauppauge HVR-2200. The driver is called saa7164. The versions included in my OS (mythbuntu 10.10 x86 32bit, kernel 2.6.35-30) and from linuxtv.org are too old to recognise the 8940 edition. Posts #124 to #128 in the Hauppauge HVR-2200 Tuner Install Guide topic (http://www.pcmediacenter.com.au/forum/topic/37541-hauppauge-hvr-2200-tuner- install-guide/page__view__findpost__p__321195) document my efforts with those versions. So I wish to use the latest stable drivers from the driver maintainers, ie http://kernellabs.com/gitweb/?p=stoth/saa7164-stable.git;a=summary Problem is, I don't know git and I don't know how I'm suppose to git, build and install it. Taking a guess I've tried: git clone git://kernellabs.com/stoth/saa7164-stable.git cd saa7164-stable make menuconfig make However I suspect these are not the optimum steps, as it seems to have downloaded and built much more than just the saa7164 drivers. The git pulled down nearly 1GB (which seems a lot) and the resultant menuconfig produced a very big .config. Am I doing the right steps or should I be doing something else to git, build and install the latest drivers ? Thanks, Declan Hello Declan, Blame Mauro and the other LinuxTV developers for moving to Git. When we had HG you could do just the v4l-dvb stack and apply it to your existing kernel. Now you have to suck down the *entire* kernel, and there's no easy way to separate out just the v4l-dvb stuff (like the saa7164 driver). The net effect is it's that much harder for end-users to try out new drivers, and even harder still for developers to maintain drivers out-of-tree. All that said, Ubuntu 10.10 deviates very little in terms of the saa7164 driver. What you have is probably already identical to what's in the kernellabs.com tree. And yes, PAL support is broken even in the kernellabs tree, so if that was your motivation then updating to the current KL stable tree won't help you. Cheers, Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- 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
[PATCH] Add missing OK key to PCTV IR keymap
Hi,
The following patch adds the IR code for the missing OK key to the Pinnacle
PCTV HD map. This map is now used by the PCTV 290e DVB-T2 device, whose remote
control has 26 buttons.
Cheers,
Chris
Signed-off-by: Chris Rankin ranki...@yahoo.com
--- linux-3.0/drivers/media/rc/keymaps/rc-pinnacle-pctv-hd.c.orig 2011-08-14 02:42:01.0 +0100
+++ linux-3.0/drivers/media/rc/keymaps/rc-pinnacle-pctv-hd.c 2011-08-14 02:12:45.0 +0100
@@ -20,6 +20,7 @@
{ 0x0701, KEY_MENU }, /* Pinnacle logo */
{ 0x0739, KEY_POWER },
{ 0x0703, KEY_VOLUMEUP },
+ { 0x0705, KEY_OK },
{ 0x0709, KEY_VOLUMEDOWN },
{ 0x0706, KEY_CHANNELUP },
{ 0x070c, KEY_CHANNELDOWN },
Re: TerraTec T6 Dual Tuner Stick initial support available
On Sun, 2011-08-14 at 14:26 +0300, Antti Palosaari wrote: On 08/14/2011 10:30 AM, Hans-Frieder Vogt wrote: just wanted to inform you that I got the TerraTec Dual DVB-T Stick working using a slightly patched driver from Afatech. Please see the wiki entry http://www.linuxtv.org/wiki/index.php/TerraTec_T6_Dual_DVB-T_Stick Currently both tuners work, but the remote doesn't. This driver is only supposed to be a temporary solution until I have integrated the bits into Antti's af9035 driver, see http://openee.googlecode.com/svn-history/r137/trunk/recipes/v4l-dvb/files/v4l- dvb-af9035.patch http://openee.googlecode.com/svn-history/r137/trunk/recipes/v4l-dvb/files/v4l- dvb-af9033.patch Situation of my AF9035 AF9033 driver is and have been years totally frozen, I given it up since I never got permission from ITE to push it Kernel and firmware distribution. Thus I left it. I have had in mind to write out all vendor code (not much code I think) to get rid of copyrights and do what I want - but never had enough time. Due to that I am not going to work my AF9035 + AF9033 unless something changes dramatically at least now when there is other drivers. The situation has not got any better by ITE submitting a clearly Windows patched driver earlier this month, which does not work in dual mode, at least with IT9137 it doesn't. I wrote a driver for the IT9137, but have lost interest to develop it any further. Regards Malcolm -- 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
Differend Technisat CableStar HD2 card
Hi all, I have a card Technisat CableStar HD2 lspci -s 04:00.0 -v 04:00.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] (rev 01) Subsystem: Device ffbf:02e4 Flags: bus master, medium devsel, latency 32, IRQ 21 Memory at 8810 (32-bit, prefetchable) [size=4K] Kernel driver in use: Mantis Kernel modules: mantis It looks like a supported card but the Subsystem id's are wrong. On the wiki site the id's are 1ae4:0002. Using kernel 2.6.39-gentoo-r3, form the gentoo distribution. But when i replace the id's in the source code from the driver mantis_common.h #define TECHNISAT 0x1ae4 into #define TECHNISAT 0xffbf and file mantis_vp2040.h #define CABLESTAR_HD2 0x0002 into #define CABLESTAR_HD2 0x02e4 Then the driver loads just fine, and 1 get 4 devices in /dev/dvb/adapter0/ demux0 dvr0 frontend0 net0 And wen installing tvheadend the card seams to work just fine. I recorded several shows without any problem. Is there a way to test if the driver is working good, and why am i missing the ca0 device? Thanks, Rene -- 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: [mythtv-users] Anyone tested the DVB-T2 dual tuner TBS6280?
Thanks for sharing your experience. On Sat, Aug 13, 2011 at 11:08 AM, Lawrence Rust l...@softsystem.co.uk wrote: The stock v4l sources supplied are old (from around 2.6.35) and don't contain many current fixes. This isn't a problem per-se unless you intend to use the card with another v4l card. In this case your brand new, bug fixed drivers are replaced by TBS's version which may or, as in my case, may not work. I have 2 other older cards that I intend to use it with, but currently I'm using Ubuntu 10.04 LTS which have a 2.6.32 kernel, so this would not be a problem, but later when I upgrade to 12.04 LTS and a newer kernel this will be problematic. Since I can't trust that TBS will deliver newer drivers. I repeatedly mailed TBS support at supp...@tbsdtv.com to ask how I could only install the 6981 driver but never got an answer. In desperation I setup a git tree of 2.6.35 and merged it with the TBS drivers in order to separate their changes. Finally after many hours I have a set of patches that I can apply to 2.6.39 that produce a working driver. Is it possible to mix modules based on different versions of v4l? To me that looks like it will work as long as the core infrastructure is the same, but as soon as some common data structure that is used by the obj files is changed it will break and you might not notice directly. Just as you say with the IR changes, but also more subtle changes by adding/removing elements in structures. Be warned that if you run a 2.6.38 or later kernel then the IR RC won't work because of significant changes to the RC architecture that TBS don't like (see http://www.tbsdtv.com/forum/viewtopic.php?f=22t=929 and http://www.tbsdtv.com/forum/viewtopic.php?f=22t=110start=90#p2693 ) In the links you refer to the driver author (at least he seems to be the author) states that he has not upgraded to the latest IR code due to compatibility issues between the CX23885 and IR. /Harald -- 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
[regression] uvcvideo: BUG at drivers/media/media-entity.c:346 for compaq presario cq56 (laptop) built-in webcam
Hi, Daniel Dickinson wrote[1]: New in 3.0.0: webcam oopses and then spams syslog. Didn't happen in .39 so is a regression. uvcvideo: Found UVC 1.00 device HP Webcam-101 (0bda:58e0) From syslog: [ 428.117889] Linux video capture interface: v2.00 [ 428.161164] uvcvideo: Found UVC 1.00 device HP Webcam-101 (0bda:58e0) [ 428.167520] [ cut here ] [ 428.167562] kernel BUG at [...]/drivers/media/media-entity.c:346! [ 428.167605] invalid opcode: [#1] SMP [ 428.167705] CPU 1 [ 428.167739] Modules linked in: uvcvideo(+) snd_seq_midi joydev videodev media v4l2_compat_ioctl32 snd_rawmidi snd_seq_midi_event snd_seq arc4 snd_timer snd_seq_device ath9k radeon(+) mac80211 ath9k_common ath9k_hw ttm ath drm_kms_helper drm snd hp_wmi cfg80211 sparse_keymap sp5100_tco edac_core soundcore rfkill i2c_algo_bit evdev snd_page_alloc edac_mce_amd psmouse k10temp shpchp i2c_piix4 serio_raw ac battery video i2c_core power_supply pci_hotplug pcspkr wmi button processor ext4 mbcache jbd2 crc16 sha256_generic cryptd aes_x86_64 aes_generic cbc dm_crypt dm_mod raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 multipath linear md_mod usbhid hid sg sr_mod sd_mod cdrom crc_t10dif ohci_hcd thermal thermal_sys ahci libahci r8169 ehci_hcd mii libata scsi_mod usbcore [last unloaded: scsi_wait_scan] [ 428.170836] [ 428.170872] Pid: 659, comm: modprobe Not tainted 3.0.0-1-amd64 #1 Hewlett-Packard Presario CQ56 Notebook PC/1604 [ 428.171010] RIP: 0010:[a04d0d18] [a04d0d18] media_entity_create_link+0x2c/0xd4 [media] [ 428.171088] RSP: 0018:8801093c5c28 EFLAGS: 00010246 [ 428.171125] RAX: 88010861f800 RBX: 88010861f870 RCX: [ 428.171163] RDX: 880108603870 RSI: RDI: 88010861f870 [ 428.171201] RBP: 880108603870 R08: 0003 R09: 81756440 [ 428.171238] R10: 00012800 R11: 00015670 R12: [ 428.171276] R13: 880108603870 R14: R15: [ 428.171315] FS: 7f6831cb3700() GS:88010fc8() knlGS: [ 428.171355] CS: 0010 DS: ES: CR0: 8005003b [ 428.171360] CR2: 01858008 CR3: 000109eaa000 CR4: 06e0 [ 428.171360] DR0: DR1: DR2: [ 428.171360] DR3: DR6: 0ff0 DR7: 0400 [ 428.171360] Process modprobe (pid: 659, threadinfo 8801093c4000, task 880107a70300) [ 428.171360] Stack: [ 428.171360] 0002 0002 880108603800 [ 428.171360] 88010a0eac40 880108603870 88010a0eac58 [ 428.171360] a04fefb1 8801099c1408 88010a0eac48 [ 428.171360] Call Trace: [ 428.171360] [a04fefb1] ? uvc_mc_register_entities+0x160/0x1eb [uvcvideo] [ 428.171360] [a04f9793] ? uvc_probe+0x1ee7/0x1f18 [uvcvideo] [ 428.171360] [a006c79d] ? usb_probe_interface+0xfc/0x16f [usbcore] [ 428.171360] [81249a37] ? driver_probe_device+0xb2/0x142 [ 428.171360] [81249b16] ? __driver_attach+0x4f/0x6f [ 428.171360] [81249ac7] ? driver_probe_device+0x142/0x142 [ 428.171360] [81248d22] ? bus_for_each_dev+0x47/0x72 [ 428.171360] [812493a9] ? bus_add_driver+0xa2/0x1f2 [ 428.171360] [81249fb0] ? driver_register+0x8d/0xf5 [ 428.171360] [a006ba66] ? usb_register_driver+0x80/0x128 [usbcore] [ 428.171360] [a0508000] ? 0xa0507fff [ 428.171360] [a050801b] ? uvc_init+0x1b/0x1000 [uvcvideo] [ 428.171360] [81002172] ? do_one_initcall+0x78/0x132 [ 428.171360] [81076703] ? sys_init_module+0xbc/0x245 [ 428.171360] [8133ba92] ? system_call_fastpath+0x16/0x1b [ 428.171360] Code: 57 41 89 cf 41 56 41 89 f6 41 55 41 54 55 48 89 d5 53 48 89 fb 48 83 ec 18 48 85 d2 74 05 48 85 ff 75 02 0f 0b 66 3b 77 3c 72 02 0f 0b 66 3b 4a 3c 72 02 0f 0b 44 89 44 24 08 41 bd f4 ff ff ff [ 428.171360] RIP [a04d0d18] media_entity_create_link+0x2c/0xd4 [media] [ 428.171360] RSP 8801093c5c28 [ 428.175002] ---[ end trace 3db524e10ad1aec0 ]--- and then: udevd[420]: timeout: killing 'usb_id --export /devices/pci:00/:00:12.2/usb1/1-3/1-3:1.0/video4linux/video0' [712] Known problem? Any hints for tracking it down? Thanks, Jonathan [1] http://bugs.debian.org/637740 -- 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
[cron job] v4l-dvb daily build: WARNINGS
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:Sun Aug 14 19:00:32 CEST 2011 git hash:9bed77ee2fb46b74782d0d9d14b92e9d07f3df6e gcc version: i686-linux-gcc (GCC) 4.6.1 host hardware:x86_64 host os: 2.6.32.5 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: WARNINGS linux-git-powerpc64: WARNINGS linux-git-x86_64: 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-i686: WARNINGS linux-2.6.37-i686: WARNINGS linux-2.6.38.2-i686: WARNINGS linux-2.6.39.1-i686: WARNINGS linux-3.0-i686: WARNINGS linux-3.1-rc1-i686: 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-x86_64: WARNINGS linux-2.6.37-x86_64: WARNINGS linux-2.6.38.2-x86_64: WARNINGS linux-2.6.39.1-x86_64: WARNINGS linux-3.0-x86_64: WARNINGS linux-3.1-rc1-x86_64: WARNINGS spec-git: WARNINGS sparse: ERRORS Detailed results are available here: http://www.xs4all.nl/~hverkuil/logs/Sunday.log Full logs are available here: http://www.xs4all.nl/~hverkuil/logs/Sunday.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
PCTV 290e - assorted problems
Hi, I've been experimenting with my new PCTV 290e DVB-T2 device this weekend, and have a couple of observations. For example, the device sometimes has trouble initialising itself: usb 4-2: new high speed USB device number 4 using ehci_hcd em28xx: New device PCTV Systems PCTV 290e @ 480 Mbps (2013:024f, interface 0, class 0) em28xx #0: chip ID is em28174 em28xx #0: Identified as PCTV nanoStick T2 290e (card=78) Registered IR keymap rc-pinnacle-pctv-hd input: em28xx IR (em28xx #0) as /devices/pci:00/:00:1d.7/usb4/4-2/rc/rc1/input10 rc1: em28xx IR (em28xx #0) as /devices/pci:00/:00:1d.7/usb4/4-2/rc/rc1 em28xx #0: v4l2 driver version 0.1.2 em28xx #0: V4L2 video device registered as video1 INFO: task khubd:1100 blocked for more than 120 seconds. echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. khubd D 0 1100 2 0x 8801a694e930 0046 8801a691ffd8 8162b020 00010280 8801a691ffd8 4000 00010280 8801a691ffd8 8801a694e930 00010280 8801a691e000 Call Trace: [8128580e] ? apic_timer_interrupt+0xe/0x20 [8113] ? memscan+0x3/0x18 [8128354e] ? __mutex_lock_slowpath+0x15c/0x295 [81283690] ? mutex_lock+0x9/0x18 [a06af671] ? dvb_init+0x99/0xcc8 [em28xx_dvb] [a067d459] ? em28xx_init_extension+0x35/0x53 [em28xx] [a067b938] ? em28xx_usb_probe+0x827/0x8df [em28xx] [a013f5bc] ? usb_probe_interface+0xfc/0x16f [usbcore] [811c2eec] ? driver_probe_device+0xa8/0x138 [811c2feb] ? __driver_attach+0x6f/0x6f [811c1f19] ? bus_for_each_drv+0x47/0x7b [811c2d8d] ? device_attach+0x6f/0x8f [811c2714] ? bus_probe_device+0x22/0x40 [811c0f80] ? device_add+0x3bf/0x531 [811bfffa] ? dev_set_name+0x3f/0x44 [8102956d] ? sub_preempt_count+0x83/0x94 [a013e1b1] ? usb_set_configuration+0x536/0x58f [usbcore] [8110cd99] ? sysfs_do_create_link+0x14c/0x1a1 [a01450c5] ? generic_probe+0x48/0x77 [usbcore] [811c2eec] ? driver_probe_device+0xa8/0x138 [811c2feb] ? __driver_attach+0x6f/0x6f [811c1f19] ? bus_for_each_drv+0x47/0x7b [811c2d8d] ? device_attach+0x6f/0x8f [811c2714] ? bus_probe_device+0x22/0x40 [811c0f80] ? device_add+0x3bf/0x531 [810b3818] ? kfree+0x13/0xa2 [a013811b] ? usb_new_device+0x9d/0x111 [usbcore] [a01391cd] ? hub_thread+0xa03/0xe89 [usbcore] [81046361] ? wake_up_bit+0x23/0x23 [a01387ca] ? usb_remote_wakeup+0x2f/0x2f [usbcore] [a01387ca] ? usb_remote_wakeup+0x2f/0x2f [usbcore] [81045f73] ? kthread+0x7a/0x82 [81285c54] ? kernel_thread_helper+0x4/0x10 [81045ef9] ? kthread_worker_fn+0x149/0x149 [81285c50] ? gs_change+0xb/0xb INFO: task usb_id:13895 blocked for more than 120 seconds. echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. usb_id D 0004 0 13895 13887 0x0080 880195e5ef60 0082 880196064e60 88018e8156a0 00010280 88018b2c5fd8 4000 00010280 88018b2c5fd8 880195e5ef60 00010280 88018b2c4000 Call Trace: [81088f59] ? __alloc_pages_nodemask+0x130/0x72a [810294d8] ? get_parent_ip+0x9/0x1b [8128354e] ? __mutex_lock_slowpath+0x15c/0x295 [81283690] ? mutex_lock+0x9/0x18 [a01416a8] ? show_manufacturer+0x1a/0x45 [usbcore] [811c001d] ? dev_attr_show+0x1e/0x46 [810895e1] ? __get_free_pages+0x12/0x52 [8110b3b6] ? sysfs_read_file+0xa8/0x12e [8102956d] ? sub_preempt_count+0x83/0x94 [810bb922] ? vfs_read+0xac/0x126 [810bb9e1] ? sys_read+0x45/0x6e [81284e7b] ? system_call_fastpath+0x16/0x1b A more successful hotplug looks like this: usb 4-3.1: new high speed USB device number 3 using ehci_hcd IR NEC protocol handler initialized IR RC5(x) protocol handler initialized lirc_dev: IR Remote Control driver registered, major 250 IR LIRC bridge handler initialized em28xx: New device PCTV Systems PCTV 290e @ 480 Mbps (2013:024f, interface 0, class 0) em28xx #0: chip ID is em28174 em28xx #0: Identified as PCTV nanoStick T2 290e (card=78) Registered IR keymap rc-pinnacle-pctv-hd input: em28xx IR (em28xx #0) as /devices/pci:00/:00:1d.7/usb4/4-3/4-3.1/rc/rc0/input7 rc0: em28xx IR (em28xx #0) as /devices/pci:00/:00:1d.7/usb4/4-3/4-3.1/rc/rc0 em28xx #0: v4l2 driver version 0.1.2 em28xx #0: V4L2 video device registered as video1 usbcore: registered new interface driver em28xx em28xx driver loaded tda18271 7-0060: creating new instance TDA18271HD/C2 detected @ 7-0060 tda18271 7-0060: attaching existing instance DVB: registering new adapter (em28xx #0) DVB: registering adapter 0 frontend 0 (Sony CXD2820R (DVB-T/T2))... DVB: registering adapter 0
Re: How to git and build HVR-2200 drivers from Kernel labs ?
On Sunday 14 August 2011 22:14:48 you wrote: On Sun, Aug 14, 2011 at 5:21 AM, Declan Mullen declan.mul...@bigpond.com wrote: Hi I've got a 8940 edition of a Hauppauge HVR-2200. The driver is called saa7164. The versions included in my OS (mythbuntu 10.10 x86 32bit, kernel 2.6.35-30) and from linuxtv.org are too old to recognise the 8940 edition. Posts #124 to #128 in the Hauppauge HVR-2200 Tuner Install Guide topic (http://www.pcmediacenter.com.au/forum/topic/37541-hauppauge-hvr-2200-tun er- install-guide/page__view__findpost__p__321195) document my efforts with those versions. So I wish to use the latest stable drivers from the driver maintainers, ie http://kernellabs.com/gitweb/?p=stoth/saa7164-stable.git;a=summary Problem is, I don't know git and I don't know how I'm suppose to git, build and install it. Taking a guess I've tried: git clone git://kernellabs.com/stoth/saa7164-stable.git cd saa7164-stable make menuconfig make However I suspect these are not the optimum steps, as it seems to have downloaded and built much more than just the saa7164 drivers. The git pulled down nearly 1GB (which seems a lot) and the resultant menuconfig produced a very big .config. Am I doing the right steps or should I be doing something else to git, build and install the latest drivers ? Thanks, Declan Hello Declan, Blame Mauro and the other LinuxTV developers for moving to Git. When we had HG you could do just the v4l-dvb stack and apply it to your existing kernel. Now you have to suck down the *entire* kernel, and there's no easy way to separate out just the v4l-dvb stuff (like the saa7164 driver). The net effect is it's that much harder for end-users to try out new drivers, and even harder still for developers to maintain drivers out-of-tree. All that said, Ubuntu 10.10 deviates very little in terms of the saa7164 driver. What you have is probably already identical to what's in the kernellabs.com tree. And yes, PAL support is broken even in the kernellabs tree, so if that was your motivation then updating to the current KL stable tree won't help you. Cheers, Devin Many thanks for the clarification about git. The only reason why I'm attempting to use a newer saa7164 driver is because the driver in my ubuntu 10.10 (2.6.35-30, x86 32bit) doesn't recognise the 8940 edition of my HVR-2200 (and doesn't support the card=9 option that I believe is specifically for the 8940 edition). Example dmesg output: $ dmesg | grep saa7 [ 18.367431] saa7164 driver loaded [ 18.367467] saa7164 :02:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 18.367472] saa7164[0]: Your board isn't known (yet) to the driver. [ 18.367473] saa7164[0]: Try to pick one of the existing card configs via [ 18.367474] saa7164[0]: card=n insmod option. Updating to the latest [ 18.367475] saa7164[0]: version might help as well. [ 18.367684] saa7164[0]: Here are valid choices for the card=n insmod option: [ 18.367739] saa7164[0]:card=0 - Unknown [ 18.367789] saa7164[0]:card=1 - Generic Rev2 [ 18.367840] saa7164[0]:card=2 - Generic Rev3 [ 18.367891] saa7164[0]:card=3 - Hauppauge WinTV-HVR2250 [ 18.367943] saa7164[0]:card=4 - Hauppauge WinTV-HVR2200 [ 18.367995] saa7164[0]:card=5 - Hauppauge WinTV-HVR2200 [ 18.368059] saa7164[0]:card=6 - Hauppauge WinTV-HVR2200 [ 18.368112] saa7164[0]:card=7 - Hauppauge WinTV-HVR2250 [ 18.368164] saa7164[0]:card=8 - Hauppauge WinTV-HVR2250 [ 18.369142] CORE saa7164[0]: subsystem: 0070:8940, board: Unknown [card=0,autodetected] [ 18.369147] saa7164[0]/0: found at :02:00.0, rev: 129, irq: 16, latency: 0, mmio: 0xfd40 [ 18.369152] saa7164 :02:00.0: setting latency timer to 64 [ 18.369162] saa7164_initdev() Unsupported board detected, registering without firmware To get this 8940 card working with my ubuntu 10.10 system, what would you recommend I try ? Should I be trying to extract the new driver from what the above git and makes, ie just copy into place the new saa7164.ko file ? Or should my existing driver work if i use the card=4 option ? Thanks, Declan -- 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: How to git and build HVR-2200 drivers from Kernel labs ?
Only Steven can look at the schematic and know for sure what prompted them to update to a new PCI ID. However, you can definitely try doing card=4 and see if it works. Card=9 won't work since that card number is not valid given the card list in your driver. Devin On Sun, Aug 14, 2011 at 7:23 PM, Declan Mullen declan.mul...@bigpond.com wrote: On Sunday 14 August 2011 22:14:48 you wrote: On Sun, Aug 14, 2011 at 5:21 AM, Declan Mullen declan.mul...@bigpond.com wrote: Hi I've got a 8940 edition of a Hauppauge HVR-2200. The driver is called saa7164. The versions included in my OS (mythbuntu 10.10 x86 32bit, kernel 2.6.35-30) and from linuxtv.org are too old to recognise the 8940 edition. Posts #124 to #128 in the Hauppauge HVR-2200 Tuner Install Guide topic (http://www.pcmediacenter.com.au/forum/topic/37541-hauppauge-hvr-2200-tun er- install-guide/page__view__findpost__p__321195) document my efforts with those versions. So I wish to use the latest stable drivers from the driver maintainers, ie http://kernellabs.com/gitweb/?p=stoth/saa7164-stable.git;a=summary Problem is, I don't know git and I don't know how I'm suppose to git, build and install it. Taking a guess I've tried: git clone git://kernellabs.com/stoth/saa7164-stable.git cd saa7164-stable make menuconfig make However I suspect these are not the optimum steps, as it seems to have downloaded and built much more than just the saa7164 drivers. The git pulled down nearly 1GB (which seems a lot) and the resultant menuconfig produced a very big .config. Am I doing the right steps or should I be doing something else to git, build and install the latest drivers ? Thanks, Declan Hello Declan, Blame Mauro and the other LinuxTV developers for moving to Git. When we had HG you could do just the v4l-dvb stack and apply it to your existing kernel. Now you have to suck down the *entire* kernel, and there's no easy way to separate out just the v4l-dvb stuff (like the saa7164 driver). The net effect is it's that much harder for end-users to try out new drivers, and even harder still for developers to maintain drivers out-of-tree. All that said, Ubuntu 10.10 deviates very little in terms of the saa7164 driver. What you have is probably already identical to what's in the kernellabs.com tree. And yes, PAL support is broken even in the kernellabs tree, so if that was your motivation then updating to the current KL stable tree won't help you. Cheers, Devin Many thanks for the clarification about git. The only reason why I'm attempting to use a newer saa7164 driver is because the driver in my ubuntu 10.10 (2.6.35-30, x86 32bit) doesn't recognise the 8940 edition of my HVR-2200 (and doesn't support the card=9 option that I believe is specifically for the 8940 edition). Example dmesg output: $ dmesg | grep saa7 [ 18.367431] saa7164 driver loaded [ 18.367467] saa7164 :02:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 18.367472] saa7164[0]: Your board isn't known (yet) to the driver. [ 18.367473] saa7164[0]: Try to pick one of the existing card configs via [ 18.367474] saa7164[0]: card=n insmod option. Updating to the latest [ 18.367475] saa7164[0]: version might help as well. [ 18.367684] saa7164[0]: Here are valid choices for the card=n insmod option: [ 18.367739] saa7164[0]: card=0 - Unknown [ 18.367789] saa7164[0]: card=1 - Generic Rev2 [ 18.367840] saa7164[0]: card=2 - Generic Rev3 [ 18.367891] saa7164[0]: card=3 - Hauppauge WinTV-HVR2250 [ 18.367943] saa7164[0]: card=4 - Hauppauge WinTV-HVR2200 [ 18.367995] saa7164[0]: card=5 - Hauppauge WinTV-HVR2200 [ 18.368059] saa7164[0]: card=6 - Hauppauge WinTV-HVR2200 [ 18.368112] saa7164[0]: card=7 - Hauppauge WinTV-HVR2250 [ 18.368164] saa7164[0]: card=8 - Hauppauge WinTV-HVR2250 [ 18.369142] CORE saa7164[0]: subsystem: 0070:8940, board: Unknown [card=0,autodetected] [ 18.369147] saa7164[0]/0: found at :02:00.0, rev: 129, irq: 16, latency: 0, mmio: 0xfd40 [ 18.369152] saa7164 :02:00.0: setting latency timer to 64 [ 18.369162] saa7164_initdev() Unsupported board detected, registering without firmware To get this 8940 card working with my ubuntu 10.10 system, what would you recommend I try ? Should I be trying to extract the new driver from what the above git and makes, ie just copy into place the new saa7164.ko file ? Or should my existing driver work if i use the card=4 option ? Thanks, Declan -- 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 -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to
PCTV 290e - assorted problems (cont)
Another thing I've noticed - a successful hotplug outputs the following messages into the dmesg log: DVB: registering new adapter (em28xx #0) DVB: registering adapter 0 frontend 0 (Sony CXD2820R (DVB-T/T2))... DVB: registering adapter 0 frontend 1 (Sony CXD2820R (DVB-C))... em28xx #0: Successfully loaded em28xx-dvb Em28xx: Initialized (Em28xx dvb Extension) extension However, I'm suspecting that the DVB adapter doesn't actually become usable until these messages have also appeared: tda18271: performing RF tracking filter calibration tda18271: RF tracking filter calibration complete The most obvious example of this is when using xine's DVB plugin: xine fails on the first attempt after a fresh hotplug, saying Sorry, No DVB input device found.. And it's also possible that trying to use xine with the device before the tracking filter calibration completes is what is making em28xx_usb_probe() hang... Oh well, it's early days... Cheers, Chris -- 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: Smart card reader support for Anysee DVB devices
Hello, I looked your codes and examined also some more. About your driver, I don't like you put so much functionality to the Kernel driver. Just put this functionality to the userspace driver all and offer only lowest possible interface (read + write) from Kernel. If you look other IFDs it is like that. On the other hand I see it could be possible to add some glue and functionality to the Kernel driver if you find already existing userspace protocol (IFD driver) which can be used. Add some emulation to Kernel and use existing user space. Select some well supported serial smartcard reader and make Anysee driver speak like that. Biggest problem I see whole thing is poor application support. OpenCT is rather legacy but there is no good alternative. All this kind of serial drivers seems to be OpenCT currently. regards Antti On 07/17/2011 05:18 PM, István Váradi wrote: Hi, I have developed smart card reader support for the Anysee devices by extending Antti Palosaari's driver. I attached the patches for it. It registers a character device named /dev/anysee_scN for each Anysee device. The character device supports two ioctl's (see anysee_sc), one for detecting the presence of a card, the other one for resetting the card and querying the ATR. The write() operation writes to the card by packaging the bytes into USB commands. The read() operation issues an appropriate command over USB and returns the reply. I have also written a simple OpenCT driver (attached) which shows the usage. I would like to have the kernel driver included in the official sources. For this reason I corresponded with Antti, and he suggested the perhaps the kernel driver should have a lower-level interface. I had the following proposal: We would continue having the two ioctls, ANYSEE_SC_ACTIVATE and ANYSEE_SC_PRESENT, however, ANYSEE_SC_ACTIVATE would do only the register reading and writing. Besides these two we need access to the anysee_ctrl_msg() function somehow. I think the cleanest way would be via another ioctl() call in which we would pass the return buffer as well, with the length so that we know how many bytes to copy. Another possibility would be that a call to write() calls anysee_ctrl_msg() and stores the return data in a 64 byte buffer that we allocate for each device. The read() following a write() would read this buffer, then discard it. Further read() attempts would fail with EAGAIN, or we could maintain an offset into the 64 byte buffer, and read as long as there is data, and fail only then. A write() would cause losing any unread data. What do you think? Thanks, Istvan -- http://palosaari.fi/ -- 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: PCTV 290e - assorted problems
--- On Mon, 15/8/11, Antti Palosaari cr...@iki.fi wrote: T 55400 8MHz + auto auto auto etc. is enough. Hmm, not here it isn't: $ scandvb -u -vvv uk-CrystalPalace scanning uk-CrystalPalace using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 55400 0 9 9 6 2 4 4 tune to: 55400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_AUTO tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x0f tuning status == 0x0f tuning status == 0x0f tuning status == 0x0f tuning status == 0x0f tuning status == 0x0f tuning status == 0x0f WARNING: tuning failed!!! tune to: 55400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_AUTO (tuning failed) tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x0f tuning status == 0x0f tuning status == 0x0f tuning status == 0x0f tuning status == 0x0f tuning status == 0x0f tuning status == 0x0f WARNING: tuning failed!!! ERROR: initial tuning failed dumping lists (0 services) Done. Although it was working (briefly) on Saturday morning. Have you tried it on Windows? No, because I don't own a Windows machine. Cheers, Chris -- 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: PCTV 290e - assorted problems
On 08/15/2011 02:56 AM, Chris Rankin wrote: tuning status == 0x0f tuning status == 0x0f WARNING: tuning failed!!! ERROR: initial tuning failed dumping lists (0 services) Done. Although it was working (briefly) on Saturday morning. Have you tried it on Windows? No, because I don't own a Windows machine. Most likely demod does not got full lock since weak/noisy signal. It is possible to increase lock waiting time from changing driver but it is not wise before signal is known to be good enough. Antti -- http://palosaari.fi/ -- 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: PCTV 290e - assorted problems
INFO: task khubd:1100 blocked for more than 120 seconds. echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. khubd D 0 1100 2 0x 8801a694e930 0046 8801a691ffd8 8162b020 00010280 8801a691ffd8 4000 00010280 8801a691ffd8 8801a694e930 00010280 8801a691e000 Call Trace: [8128580e] ? apic_timer_interrupt+0xe/0x20 [8113] ? memscan+0x3/0x18 [8128354e] ? __mutex_lock_slowpath+0x15c/0x295 [81283690] ? mutex_lock+0x9/0x18 [a06af671] ? dvb_init+0x99/0xcc8 [em28xx_dvb] [a067d459] ? em28xx_init_extension+0x35/0x53 [em28xx] [a067b938] ? em28xx_usb_probe+0x827/0x8df [em28xx] I think it crashes before it even goes to PCTV 290e specific part. I suspect it is bug somewhere in em28xx driver. The scenario that triggers this crash is: a) Plug the 290e in, and allow it to initialise correctly b) Use xine to watch any DVB-T channel successfully c) Try switching to previously-tuned DVB-T2 channel; this makes xine hang. d) Kill xine e) Physically replug adapter em28xx re-initialisation will now fail: ... tda18271: performing RF tracking filter calibration tda18271: RF tracking filter calibration complete usb 4-1: USB disconnect, device number 3 em28xx #0: disconnecting em28xx #0 video em28xx #0: V4L2 device video1 deregistered tda18271 7-0060: destroying instance usb 4-1: new high speed USB device number 4 using ehci_hcd em28xx: New device PCTV Systems PCTV 290e @ 480 Mbps (2013:024f, interface 0, class 0) em28xx #0: chip ID is em28174 em28xx #0: Identified as PCTV nanoStick T2 290e (card=78) Registered IR keymap rc-pinnacle-pctv-hd input: em28xx IR (em28xx #0) as /devices/pci:00/:00:1d.7/usb4/4-1/rc/rc1/input8 rc1: em28xx IR (em28xx #0) as /devices/pci:00/:00:1d.7/usb4/4-1/rc/rc1 em28xx #0: v4l2 driver version 0.1.2 em28xx #0: V4L2 video device registered as video1 INFO: task khubd:1217 blocked for more than 120 seconds. echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. khubd D 0 1217 2 0x 8801a7081ef0 0046 8801a69a9fd8 8162b020 00010280 8801a69a9fd8 4000 00010280 8801a69a9fd8 8801a7081ef0 00010280 8801a69a8000 Call Trace: [8128580e] ? apic_timer_interrupt+0xe/0x20 [8113] ? memscan+0x3/0x18 [8128354e] ? __mutex_lock_slowpath+0x15c/0x295 [81283690] ? mutex_lock+0x9/0x18 [a0694671] ? dvb_init+0x99/0xcc8 [em28xx_dvb] [a0662459] ? em28xx_init_extension+0x35/0x53 [em28xx] [a0660938] ? em28xx_usb_probe+0x827/0x8df [em28xx] Cheers, Chris -- 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
dvb-apps: update DVB-T intial tuning files for Finland (fi-*)
Moi Christoph, Updates all Finnish channels as today. Antti -- http://palosaari.fi/ diff -r 36a084aace47 util/scan/dvb-t/fi-Alajarvi --- a/util/scan/dvb-t/fi-Alajarvi Sat Jul 16 17:42:28 2011 +0200 +++ b/util/scan/dvb-t/fi-Alajarvi Mon Aug 15 03:30:49 2011 +0300 @@ -2,4 +2,5 @@ # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 64200 8MHz 2/3 NONE QAM64 8k 1/8 NONE T 73000 8MHz 2/3 NONE QAM64 8k 1/8 NONE +T 77800 8MHz 2/3 NONE QAM64 8k 1/8 NONE T 57800 8MHz 2/3 NONE QAM64 8k 1/8 NONE diff -r 36a084aace47 util/scan/dvb-t/fi-Hanko --- a/util/scan/dvb-t/fi-Hanko Sat Jul 16 17:42:28 2011 +0200 +++ b/util/scan/dvb-t/fi-Hanko Mon Aug 15 03:30:49 2011 +0300 @@ -1,5 +1,6 @@ # automatically generated from http://www.digitv.fi/sivu.asp?path=1;8224;9519 # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy -T 61800 8MHz 2/3 NONE QAM64 8k 1/8 NONE -T 74600 8MHz 2/3 NONE QAM64 8k 1/8 NONE -T 70600 8MHz 2/3 NONE QAM64 8k 1/8 NONE +T 59400 8MHz 2/3 NONE QAM64 8k 1/8 NONE +T 57000 8MHz 2/3 NONE QAM64 8k 1/8 NONE +T 69000 8MHz 2/3 NONE QAM64 8k 1/8 NONE +T 51400 8MHz 2/3 NONE QAM64 8k 1/8 NONE diff -r 36a084aace47 util/scan/dvb-t/fi-Hartola --- a/util/scan/dvb-t/fi-HartolaSat Jul 16 17:42:28 2011 +0200 +++ b/util/scan/dvb-t/fi-HartolaMon Aug 15 03:30:49 2011 +0300 @@ -2,3 +2,4 @@ # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 51400 8MHz 2/3 NONE QAM64 8k 1/8 NONE T 60200 8MHz 2/3 NONE QAM64 8k 1/8 NONE +T 64200 8MHz 2/3 NONE QAM64 8k 1/8 NONE diff -r 36a084aace47 util/scan/dvb-t/fi-Heinavesi --- a/util/scan/dvb-t/fi-Heinavesi Sat Jul 16 17:42:28 2011 +0200 +++ b/util/scan/dvb-t/fi-Heinavesi Mon Aug 15 03:30:49 2011 +0300 @@ -2,3 +2,4 @@ # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 65800 8MHz 2/3 NONE QAM64 8k 1/8 NONE T 70600 8MHz 2/3 NONE QAM64 8k 1/8 NONE +T 51400 8MHz 2/3 NONE QAM64 8k 1/8 NONE diff -r 36a084aace47 util/scan/dvb-t/fi-Heinola --- a/util/scan/dvb-t/fi-HeinolaSat Jul 16 17:42:28 2011 +0200 +++ b/util/scan/dvb-t/fi-HeinolaMon Aug 15 03:30:49 2011 +0300 @@ -2,5 +2,5 @@ # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 55400 8MHz 2/3 NONE QAM64 8k 1/8 NONE T 78600 8MHz 2/3 NONE QAM64 8k 1/8 NONE -T 82600 8MHz 2/3 NONE QAM64 8k 1/8 NONE +T 53000 8MHz 2/3 NONE QAM64 8k 1/8 NONE T 70600 8MHz 2/3 NONE QAM64 8k 1/8 NONE diff -r 36a084aace47 util/scan/dvb-t/fi-Houtskari --- a/util/scan/dvb-t/fi-Houtskari Sat Jul 16 17:42:28 2011 +0200 +++ b/util/scan/dvb-t/fi-Houtskari Mon Aug 15 03:30:49 2011 +0300 @@ -2,4 +2,5 @@ # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 62600 8MHz 2/3 NONE QAM64 8k 1/8 NONE T 68200 8MHz 2/3 NONE QAM64 8k 1/8 NONE +T 57800 8MHz 2/3 NONE QAM64 8k 1/8 NONE T 52200 8MHz 2/3 NONE QAM64 8k 1/8 NONE diff -r 36a084aace47 util/scan/dvb-t/fi-Hyrynsalmi --- a/util/scan/dvb-t/fi-Hyrynsalmi Sat Jul 16 17:42:28 2011 +0200 +++ b/util/scan/dvb-t/fi-Hyrynsalmi Mon Aug 15 03:30:49 2011 +0300 @@ -2,3 +2,4 @@ # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 62600 8MHz 2/3 NONE QAM64 8k 1/8 NONE T 65800 8MHz 2/3 NONE QAM64 8k 1/8 NONE +T 57800 8MHz 2/3 NONE QAM64 8k 1/8 NONE diff -r 36a084aace47 util/scan/dvb-t/fi-Hyrynsalmi_Kyparavaara --- a/util/scan/dvb-t/fi-Hyrynsalmi_Kyparavaara Sat Jul 16 17:42:28 2011 +0200 +++ b/util/scan/dvb-t/fi-Hyrynsalmi_Kyparavaara Mon Aug 15 03:30:49 2011 +0300 @@ -2,3 +2,4 @@ # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 62600 8MHz 2/3 NONE QAM64 8k 1/8 NONE T 65800 8MHz 2/3 NONE QAM64 8k 1/8 NONE +T 49800 8MHz 2/3 NONE QAM64 8k 1/8 NONE diff -r 36a084aace47 util/scan/dvb-t/fi-Hyvinkaa_Musta-Mannisto --- a/util/scan/dvb-t/fi-Hyvinkaa_Musta-MannistoSat Jul 16 17:42:28 2011 +0200 +++ b/util/scan/dvb-t/fi-Hyvinkaa_Musta-MannistoMon Aug 15 03:30:49 2011 +0300 @@ -2,4 +2,5 @@ # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 53800 8MHz 2/3 NONE QAM64 8k 1/8 NONE T 69800 8MHz 2/3 NONE QAM64 8k 1/8 NONE +T 35000 8MHz 2/3 NONE QAM64 8k 1/8 NONE T 75400 8MHz 2/3 NONE QAM64 8k 1/8 NONE diff -r 36a084aace47 util/scan/dvb-t/fi-Ikaalinen --- a/util/scan/dvb-t/fi-Ikaalinen Sat Jul 16 17:42:28 2011 +0200 +++ b/util/scan/dvb-t/fi-Ikaalinen Mon Aug 15 03:30:49 2011 +0300 @@ -2,4 +2,5 @@ # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 53800 8MHz 2/3 NONE QAM64 8k 1/8 NONE T 65800 8MHz 2/3 NONE QAM64 8k 1/8 NONE +T 76200 8MHz 2/3 NONE QAM64 8k 1/8 NONE T 61800 8MHz 2/3 NONE QAM64 8k 1/8 NONE diff -r 36a084aace47 util/scan/dvb-t/fi-Ikaalinen_Riitiala --- a/util/scan/dvb-t/fi-Ikaalinen_Riitiala Sat Jul 16 17:42:28 2011 +0200 +++
[PATCH 05/11] drivers/media: do not use EXTRA_CFLAGS
Usage of these flags has been deprecated for nearly 4 years by:
commit f77bf01425b11947eeb3b5b54685212c302741b8
Author: Sam Ravnborg sam@neptun.(none)
Date: Mon Oct 15 22:25:06 2007 +0200
kbuild: introduce ccflags-y, asflags-y and ldflags-y
Moreover, these flags (at least EXTRA_CFLAGS) have been documented for command
line use. By default, gmake(1) do not override command line setting, so this is
likely to result in build failure or unexpected behavior.
Replace their usage by Kbuild's `{as,cc,ld}flags-y'.
Cc: Sam Ravnborg s...@ravnborg.org
Cc: Mauro Carvalho Chehab mche...@infradead.org
Cc: linux-media@vger.kernel.org
---
drivers/media/common/tuners/Makefile |4 ++--
drivers/media/dvb/b2c2/Makefile|4 ++--
drivers/media/dvb/bt8xx/Makefile |8
drivers/media/dvb/ddbridge/Makefile|8
drivers/media/dvb/dm1105/Makefile |2 +-
drivers/media/dvb/dvb-usb/Makefile |4 ++--
drivers/media/dvb/frontends/Makefile |4 ++--
drivers/media/dvb/mantis/Makefile |2 +-
drivers/media/dvb/ngene/Makefile |8
drivers/media/dvb/pluto2/Makefile |2 +-
drivers/media/dvb/pt1/Makefile |2 +-
drivers/media/dvb/siano/Makefile |4 ++--
drivers/media/dvb/ttpci/Makefile |4 ++--
drivers/media/dvb/ttusb-budget/Makefile|2 +-
drivers/media/dvb/ttusb-dec/Makefile |2 +-
drivers/media/radio/Makefile |2 +-
drivers/media/video/Makefile |6 +++---
drivers/media/video/au0828/Makefile|8
drivers/media/video/bt8xx/Makefile |6 +++---
drivers/media/video/cx18/Makefile |6 +++---
drivers/media/video/cx231xx/Makefile | 10 +-
drivers/media/video/cx23885/Makefile | 10 +-
drivers/media/video/cx25840/Makefile |2 +-
drivers/media/video/cx88/Makefile |8
drivers/media/video/em28xx/Makefile|8
drivers/media/video/gspca/gl860/Makefile |2 +-
drivers/media/video/gspca/m5602/Makefile |2 +-
drivers/media/video/gspca/stv06xx/Makefile |2 +-
drivers/media/video/hdpvr/Makefile |4 ++--
drivers/media/video/ivtv/Makefile |8
drivers/media/video/omap3isp/Makefile |4 +---
drivers/media/video/pvrusb2/Makefile |8
drivers/media/video/saa7134/Makefile |8
drivers/media/video/saa7164/Makefile | 10 +-
drivers/media/video/tlg2300/Makefile |8
drivers/media/video/usbvision/Makefile |4 ++--
36 files changed, 92 insertions(+), 94 deletions(-)
diff --git a/drivers/media/common/tuners/Makefile
b/drivers/media/common/tuners/Makefile
index 20d24fc..196c12a 100644
--- a/drivers/media/common/tuners/Makefile
+++ b/drivers/media/common/tuners/Makefile
@@ -28,5 +28,5 @@ obj-$(CONFIG_MEDIA_TUNER_MAX2165) += max2165.o
obj-$(CONFIG_MEDIA_TUNER_TDA18218) += tda18218.o
obj-$(CONFIG_MEDIA_TUNER_TDA18212) += tda18212.o
-EXTRA_CFLAGS += -Idrivers/media/dvb/dvb-core
-EXTRA_CFLAGS += -Idrivers/media/dvb/frontends
+ccflags-y += -Idrivers/media/dvb/dvb-core
+ccflags-y += -Idrivers/media/dvb/frontends
diff --git a/drivers/media/dvb/b2c2/Makefile b/drivers/media/dvb/b2c2/Makefile
index b97cf72..3d04a8d 100644
--- a/drivers/media/dvb/b2c2/Makefile
+++ b/drivers/media/dvb/b2c2/Makefile
@@ -12,5 +12,5 @@ obj-$(CONFIG_DVB_B2C2_FLEXCOP_PCI) += b2c2-flexcop-pci.o
b2c2-flexcop-usb-objs = flexcop-usb.o
obj-$(CONFIG_DVB_B2C2_FLEXCOP_USB) += b2c2-flexcop-usb.o
-EXTRA_CFLAGS += -Idrivers/media/dvb/dvb-core/ -Idrivers/media/dvb/frontends/
-EXTRA_CFLAGS += -Idrivers/media/common/tuners/
+ccflags-y += -Idrivers/media/dvb/dvb-core/ -Idrivers/media/dvb/frontends/
+ccflags-y += -Idrivers/media/common/tuners/
diff --git a/drivers/media/dvb/bt8xx/Makefile b/drivers/media/dvb/bt8xx/Makefile
index d98f1d4..0713b3a 100644
--- a/drivers/media/dvb/bt8xx/Makefile
+++ b/drivers/media/dvb/bt8xx/Makefile
@@ -1,6 +1,6 @@
obj-$(CONFIG_DVB_BT8XX) += bt878.o dvb-bt8xx.o dst.o dst_ca.o
-EXTRA_CFLAGS += -Idrivers/media/dvb/dvb-core
-EXTRA_CFLAGS += -Idrivers/media/dvb/frontends
-EXTRA_CFLAGS += -Idrivers/media/video/bt8xx
-EXTRA_CFLAGS += -Idrivers/media/common/tuners
+ccflags-y += -Idrivers/media/dvb/dvb-core
+ccflags-y += -Idrivers/media/dvb/frontends
+ccflags-y += -Idrivers/media/video/bt8xx
+ccflags-y += -Idrivers/media/common/tuners
diff --git a/drivers/media/dvb/ddbridge/Makefile
b/drivers/media/dvb/ddbridge/Makefile
index de4fe19..cf7214e 100644
--- a/drivers/media/dvb/ddbridge/Makefile
+++ b/drivers/media/dvb/ddbridge/Makefile
@@ -6,9 +6,9 @@ ddbridge-objs := ddbridge-core.o
obj-$(CONFIG_DVB_DDBRIDGE) += ddbridge.o
-EXTRA_CFLAGS += -Idrivers/media/dvb/dvb-core/
-EXTRA_CFLAGS += -Idrivers/media/dvb/frontends/
-EXTRA_CFLAGS += -Idrivers/media/common/tuners/
Re: [PATCH 05/11] drivers/media: do not use EXTRA_CFLAGS
Hi,
On Mon, Aug 15, 2011 at 1:07 AM, Arnaud Lacombe lacom...@gmail.com wrote:
Usage of these flags has been deprecated for nearly 4 years by:
commit f77bf01425b11947eeb3b5b54685212c302741b8
Author: Sam Ravnborg sam@neptun.(none)
Date: Mon Oct 15 22:25:06 2007 +0200
kbuild: introduce ccflags-y, asflags-y and ldflags-y
Moreover, these flags (at least EXTRA_CFLAGS) have been documented for command
line use. By default, gmake(1) do not override command line setting, so this
is
likely to result in build failure or unexpected behavior.
Replace their usage by Kbuild's `{as,cc,ld}flags-y'.
Cc: Sam Ravnborg s...@ravnborg.org
Cc: Mauro Carvalho Chehab mche...@infradead.org
Cc: linux-media@vger.kernel.org
Signed-off-by: Arnaud Lacombe lacom...@gmail.com
- Arnaud
---
drivers/media/common/tuners/Makefile | 4 ++--
drivers/media/dvb/b2c2/Makefile | 4 ++--
drivers/media/dvb/bt8xx/Makefile | 8
drivers/media/dvb/ddbridge/Makefile | 8
drivers/media/dvb/dm1105/Makefile | 2 +-
drivers/media/dvb/dvb-usb/Makefile | 4 ++--
drivers/media/dvb/frontends/Makefile | 4 ++--
drivers/media/dvb/mantis/Makefile | 2 +-
drivers/media/dvb/ngene/Makefile | 8
drivers/media/dvb/pluto2/Makefile | 2 +-
drivers/media/dvb/pt1/Makefile | 2 +-
drivers/media/dvb/siano/Makefile | 4 ++--
drivers/media/dvb/ttpci/Makefile | 4 ++--
drivers/media/dvb/ttusb-budget/Makefile | 2 +-
drivers/media/dvb/ttusb-dec/Makefile | 2 +-
drivers/media/radio/Makefile | 2 +-
drivers/media/video/Makefile | 6 +++---
drivers/media/video/au0828/Makefile | 8
drivers/media/video/bt8xx/Makefile | 6 +++---
drivers/media/video/cx18/Makefile | 6 +++---
drivers/media/video/cx231xx/Makefile | 10 +-
drivers/media/video/cx23885/Makefile | 10 +-
drivers/media/video/cx25840/Makefile | 2 +-
drivers/media/video/cx88/Makefile | 8
drivers/media/video/em28xx/Makefile | 8
drivers/media/video/gspca/gl860/Makefile | 2 +-
drivers/media/video/gspca/m5602/Makefile | 2 +-
drivers/media/video/gspca/stv06xx/Makefile | 2 +-
drivers/media/video/hdpvr/Makefile | 4 ++--
drivers/media/video/ivtv/Makefile | 8
drivers/media/video/omap3isp/Makefile | 4 +---
drivers/media/video/pvrusb2/Makefile | 8
drivers/media/video/saa7134/Makefile | 8
drivers/media/video/saa7164/Makefile | 10 +-
drivers/media/video/tlg2300/Makefile | 8
drivers/media/video/usbvision/Makefile | 4 ++--
36 files changed, 92 insertions(+), 94 deletions(-)
diff --git a/drivers/media/common/tuners/Makefile
b/drivers/media/common/tuners/Makefile
index 20d24fc..196c12a 100644
--- a/drivers/media/common/tuners/Makefile
+++ b/drivers/media/common/tuners/Makefile
@@ -28,5 +28,5 @@ obj-$(CONFIG_MEDIA_TUNER_MAX2165) += max2165.o
obj-$(CONFIG_MEDIA_TUNER_TDA18218) += tda18218.o
obj-$(CONFIG_MEDIA_TUNER_TDA18212) += tda18212.o
-EXTRA_CFLAGS += -Idrivers/media/dvb/dvb-core
-EXTRA_CFLAGS += -Idrivers/media/dvb/frontends
+ccflags-y += -Idrivers/media/dvb/dvb-core
+ccflags-y += -Idrivers/media/dvb/frontends
diff --git a/drivers/media/dvb/b2c2/Makefile b/drivers/media/dvb/b2c2/Makefile
index b97cf72..3d04a8d 100644
--- a/drivers/media/dvb/b2c2/Makefile
+++ b/drivers/media/dvb/b2c2/Makefile
@@ -12,5 +12,5 @@ obj-$(CONFIG_DVB_B2C2_FLEXCOP_PCI) += b2c2-flexcop-pci.o
b2c2-flexcop-usb-objs = flexcop-usb.o
obj-$(CONFIG_DVB_B2C2_FLEXCOP_USB) += b2c2-flexcop-usb.o
-EXTRA_CFLAGS += -Idrivers/media/dvb/dvb-core/ -Idrivers/media/dvb/frontends/
-EXTRA_CFLAGS += -Idrivers/media/common/tuners/
+ccflags-y += -Idrivers/media/dvb/dvb-core/ -Idrivers/media/dvb/frontends/
+ccflags-y += -Idrivers/media/common/tuners/
diff --git a/drivers/media/dvb/bt8xx/Makefile
b/drivers/media/dvb/bt8xx/Makefile
index d98f1d4..0713b3a 100644
--- a/drivers/media/dvb/bt8xx/Makefile
+++ b/drivers/media/dvb/bt8xx/Makefile
@@ -1,6 +1,6 @@
obj-$(CONFIG_DVB_BT8XX) += bt878.o dvb-bt8xx.o dst.o dst_ca.o
-EXTRA_CFLAGS += -Idrivers/media/dvb/dvb-core
-EXTRA_CFLAGS += -Idrivers/media/dvb/frontends
-EXTRA_CFLAGS += -Idrivers/media/video/bt8xx
-EXTRA_CFLAGS += -Idrivers/media/common/tuners
+ccflags-y += -Idrivers/media/dvb/dvb-core
+ccflags-y += -Idrivers/media/dvb/frontends
+ccflags-y += -Idrivers/media/video/bt8xx
+ccflags-y += -Idrivers/media/common/tuners
diff --git a/drivers/media/dvb/ddbridge/Makefile
b/drivers/media/dvb/ddbridge/Makefile
index de4fe19..cf7214e 100644
--- a/drivers/media/dvb/ddbridge/Makefile
+++ b/drivers/media/dvb/ddbridge/Makefile
@@ -6,9
