[PATCH] [MEDIA] add device IDs to ngene driver
Author: Helmut Auer <v...@helmutauer.de>
Date: Fri Jan 27 09:09:35 2017 +0100
Adding 2 device ID's to ngene driver.
Signed-off-by: Helmut Auer <v...@helmutauer.de>
--- drivers/media/pci/ngene/ngene-cards.c2016-12-11
20:17:54.0 +0100
+++ drivers/media/pci/ngene/ngene-cards.c2017-01-20
08:46:48.263666132 +0100
@@ -753,6 +753,8 @@
//
static const struct pci_device_id ngene_id_tbl[] = {
+ NGENE_ID(0x18c3, 0xab04, ngene_info_cineS2),
+ NGENE_ID(0x18c3, 0xab05, ngene_info_cineS2v5),
NGENE_ID(0x18c3, 0xabc3, ngene_info_cineS2),
NGENE_ID(0x18c3, 0xabc4, ngene_info_cineS2),
NGENE_ID(0x18c3, 0xdb01, ngene_info_satixS2),
Re: [PATCH] [MEDIA] add device ID to ati remote
P.S. Here is the patch again with a correction.
> On Tue, Feb 07, 2017 at 09:42:47AM +0100, v...@helmutauer.de wrote:
>>
>> Author: Helmut Auer <v...@xxx.de>
>> Date: Fri Jan 27 19:09:35 2017 +0100
>>
>> Adding 1 device ID to ati_remote driver.
>
> If possible, a more descriptive message would be preferred, e.g. what
> device do you have, what branding, what product did it come with.
>
>>
>> Signed-off-by: Helmut Auer <v...@xxx.de>
>
> Unless I'm mistaken, contributions can't be anonymous or use a fake email
> address.
>
>>
>> diff --git a/drivers/media/rc/ati_remote.c
>> b/drivers/media/rc/ati_remote.c
>> index 0884b7d..83022b1 100644
>> --- a/drivers/media/rc/ati_remote.c
>> +++ b/drivers/media/rc/ati_remote.c
>> @@ -108,6 +108,7 @@
>> #define NVIDIA_REMOTE_PRODUCT_ID 0x0005
>> #define MEDION_REMOTE_PRODUCT_ID 0x0006
>> #define FIREFLY_REMOTE_PRODUCT_ID 0x0008
>> +#define REYCOM_REMOTE_PRODUCT_ID 0x000c
>>
>> #define DRIVER_VERSION "2.2.1"
>> #define DRIVER_AUTHOR "Torrey Hoffman <thoff...@arnor.net>"
>> @@ -227,6 +228,10 @@ static struct usb_device_id ati_remote_table[] = {
>> USB_DEVICE(ATI_REMOTE_VENDOR_ID,
>> FIREFLY_REMOTE_PRODUCT_ID),
>> .driver_info = (unsigned long)_firefly
>> },
>> + {
>> + USB_DEVICE(ATI_REMOTE_VENDOR_ID,
>> REYCOM_REMOTE_PRODUCT_ID),
>> + .driver_info = (unsigned long)_firefly
>> + },
>> {} /* Terminating entry */
>> };
>
> Your email client replaced all tabs with spaces so the patch no longer
> applies.
>
> Thanks,
> Sean
>
015_atireycom.patch
Description: Binary data
Re: [PATCH] [MEDIA] add device ID to ati remote
Hello
Thanks for the info, but sorry I'm not willinmg to do anything more to get the
patch into the kernel.
I have an own distribution and I am applying those patches and thats easier
than committing it to the kernel ;)
Maybe anyone who needs this finds this patch.
Kind regards
Helmut
Am 13.02.2017 um 14:42 schrieb Sean Young:
On Tue, Feb 07, 2017 at 09:42:47AM +0100, v...@helmutauer.de wrote:
Author: Helmut Auer <v...@xxx.de>
Date: Fri Jan 27 19:09:35 2017 +0100
Adding 1 device ID to ati_remote driver.
If possible, a more descriptive message would be preferred, e.g. what
device do you have, what branding, what product did it come with.
Signed-off-by: Helmut Auer <v...@xxx.de>
Unless I'm mistaken, contributions can't be anonymous or use a fake email
address.
diff --git a/drivers/media/rc/ati_remote.c b/drivers/media/rc/ati_remote.c
index 0884b7d..83022b1 100644
--- a/drivers/media/rc/ati_remote.c
+++ b/drivers/media/rc/ati_remote.c
@@ -108,6 +108,7 @@
#define NVIDIA_REMOTE_PRODUCT_ID 0x0005
#define MEDION_REMOTE_PRODUCT_ID 0x0006
#define FIREFLY_REMOTE_PRODUCT_ID 0x0008
+#define REYCOM_REMOTE_PRODUCT_ID 0x000c
#define DRIVER_VERSION "2.2.1"
#define DRIVER_AUTHOR "Torrey Hoffman <thoff...@arnor.net>"
@@ -227,6 +228,10 @@ static struct usb_device_id ati_remote_table[] = {
USB_DEVICE(ATI_REMOTE_VENDOR_ID, FIREFLY_REMOTE_PRODUCT_ID),
.driver_info = (unsigned long)_firefly
},
+ {
+ USB_DEVICE(ATI_REMOTE_VENDOR_ID, REYCOM_REMOTE_PRODUCT_ID),
+ .driver_info = (unsigned long)_firefly
+ },
{} /* Terminating entry */
};
Your email client replaced all tabs with spaces so the patch no longer
applies.
Thanks,
Sean
FM RDS receiver
Hello List, Can you recommend any FM receiver card or usb stick currently available in Germany with RDS support ? -- Helmut Auer, hel...@helmutauer.de -- 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: Bug: media_build always compiles with '-DDEBUG'
Hi Replacing ifdef CONFIG_VIDEO_OMAP3_DEBUG by ifeq ($(CONFIG_VIDEO_OMAP3_DEBUG),y) would do the trick. I guess that would not ive the intended result. Setting CONFIG_VIDEO_OMAP3_DEBUG to yes should not lead to debug messages in all media modules, Bye Helmut -- 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: Bug: media_build always compiles with '-DDEBUG'
Am 18.06.2011 23:38, schrieb Oliver Endriss: On Saturday 18 June 2011 23:11:21 Helmut Auer wrote: Hi Replacing ifdef CONFIG_VIDEO_OMAP3_DEBUG by ifeq ($(CONFIG_VIDEO_OMAP3_DEBUG),y) would do the trick. I guess that would not ive the intended result. Setting CONFIG_VIDEO_OMAP3_DEBUG to yes should not lead to debug messages in all media modules, True, but it will happen only if you manually enable CONFIG_VIDEO_OMAP3_DEBUG in Kconfig. You cannot avoid this without major changes of the media_build system - imho not worth the effort. Then imho it would be better to drop the CONFIG_VIDEO_OMAP3_DEBUG variable completely, you can set CONFIG_DEBUG which would give the same results. Bye Helmut -- 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 an media build tree
Hello List How long does it usually take til patches are integrated into the media build tree ( after posting these here ) ? I'm just wondering because I miss some patches posted here. -- Helmut Auer, hel...@helmutauer.de -- 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: kernel oops with TT S2-3200
] [c1002810] ? sysenter_do_call+0x12/0x26 Jun 07 12:49:05 [kernel] ---[ end trace 100a66f59725996d ]--- -- Helmut Auer, hel...@helmutauer.de -- 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: Kernel oops with current hg (ir-sysfs.c ?)
] [c0101131] ? do_one_initcall+0x31/0x190 May 24 13:30:22 ubuntuvdr1 kernel: [5.692937] [f8ce7000] ? budget_ci_init+0x0/0xf [budget_ci] May 24 13:30:22 ubuntuvdr1 kernel: [5.692945] [c0182340] ? sys_init_module+0xb0/0x210 May 24 13:30:22 ubuntuvdr1 kernel: [5.692951] [c01033ec] ? syscall_call+0x7/0xb May 24 13:30:22 ubuntuvdr1 kernel: [5.692956] Code: 00 89 c6 8d 80 a0 07 00 00 e8 bf a7 18 c8 ba 00 01 00 00 89 c3 b8 0c d4 25 f8 e8 6e ec 0e c8 89 c7 85 ff 78 6f 8b 83 44 01 $ May 24 13:30:22 ubuntuvdr1 kernel: [5.693003] EIP: [f825bd7e] ir_register_class+0x3e/0x190 [ir_core] SS:ESP 0068:f61d5d4c May 24 13:30:22 ubuntuvdr1 kernel: [5.693015] CR2: May 24 13:30:22 ubuntuvdr1 kernel: [5.693020] ---[ end trace 2c915ef882a2f862 ]--- --I can confirm this. Loading budget_ci from current v4l-dvb hg with kernel 2.6.34 causes kernel oops: Jun 07 12:49:05 [kernel] budget_ci dvb :01:00.0: PCI INT A - GSI 19 (level, low) - IRQ 19 Jun 07 12:49:05 [kernel] IRQ 19/: IRQF_DISABLED is not guaranteed on shared IRQs Jun 07 12:49:05 [kernel] saa7146: found saa7146 @ mem f949ac00 (revision 1, irq 19) (0x13c2,0x1010). Jun 07 12:49:05 [kernel] saa7146 (0): dma buffer size 192512 Jun 07 12:49:05 [kernel] DVB: registering new adapter (TT-Budget-C-CI PCI) Jun 07 12:49:05 [kernel] IR NEC protocol handler initialized Jun 07 12:49:05 [kernel] IR RC5(x) protocol handler initialized Jun 07 12:49:05 [kernel] IR RC6 protocol handler initialized Jun 07 12:49:05 [kernel] IR JVC protocol handler initialized Jun 07 12:49:05 [kernel] IR Sony protocol handler initialized Jun 07 12:49:05 [kernel] Registered IR keymap rc-tt-1500 Jun 07 12:49:05 [kernel] BUG: unable to handle kernel NULL pointer dereference at (null) Jun 07 12:49:05 [kernel] IP: [f9435cc0] ir_register_class+0x3f/0x123 [ir_core] Jun 07 12:49:05 [kernel] *pdpt = 36cb9001 *pde = Jun 07 12:49:05 [kernel] Modules linked in: rc_tt_1500 ir_sony_decoder ir_jvc_decoder ir_rc6_decoder ir_rc5_decoder ir_nec_decoder budget_ci(+) budget_core dvb_core saa7146 ttpci_eeprom ir_core i2c_core snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_pcm snd_timer snd_page_alloc Jun 07 12:49:05 [kernel] Pid: 1877, comm: modprobe Not tainted 2.6.34-gentoo #1 IPM31/To Be Filled By O.E.M. Jun 07 12:49:05 [kernel] EIP: 0060:[f9435cc0] EFLAGS: 00010246 CPU: 0 Jun 07 12:49:05 [kernel] EIP is at ir_register_class+0x3f/0x123 [ir_core] Jun 07 12:49:05 [kernel] EAX: f9436a44 EBX: fff4 ECX: EDX: Jun 07 12:49:05 [kernel] ESI: f6da6200 EDI: f6fd1000 EBP: f6bf5dbc ESP: f6bf5dac Jun 07 12:49:05 [kernel] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 Jun 07 12:49:05 [kernel] fff4 f6da6200 f6bf5de8 f9435572 f9636048 f6fd1000 Jun 07 12:49:05 [kernel] 0 f6da62c4 f6fd1784 f6da62e0 0282 f651f5d0 f6fd1000 f651f588 f6bf5e24 Jun 07 12:49:05 [kernel] 0 f9491e04 f9492ee7 f6bf5e04 f6bf5e98 f651f000 f9449110 f9636048 Jun 07 12:49:05 [kernel] [f9435572] ? __ir_input_register+0x220/0x3aa [ir_core] Jun 07 12:49:05 [kernel] [f9491e04] ? 0xf9491e04 Jun 07 12:49:05 [kernel] [f9448312] ? saa7146_pgtable_free+0x57f/0x795 [saa7146] Jun 07 12:49:05 [kernel] [c10c110a] ? sysfs_addrm_finish+0x15/0xa3 Jun 07 12:49:05 [kernel] [c10c0b33] ? sysfs_add_one+0x12/0x7a Jun 07 12:49:05 [kernel] [c12b232b] ? pci_match_device+0xa4/0xac Jun 07 12:49:05 [kernel] [c12b21f4] ? local_pci_probe+0xe/0x10 Jun 07 12:49:05 [kernel] [c12b2bf5] ? pci_device_probe+0x43/0x66 Jun 07 12:49:05 [kernel] [c132471e] ? driver_probe_device+0x79/0x105 Jun 07 12:49:05 [kernel] [c13247ed] ? __driver_attach+0x43/0x5f Jun 07 12:49:05 [kernel] [c132413d] ? bus_for_each_dev+0x3d/0x67 Jun 07 12:49:05 [kernel] [c13245f7] ? driver_attach+0x14/0x16 Jun 07 12:49:05 [kernel] [c13247aa] ? __driver_attach+0x0/0x5f Jun 07 12:49:05 [kernel] [c1323bb7] ? bus_add_driver+0xa2/0x1d4 Jun 07 12:49:05 [kernel] [c1324a33] ? driver_register+0x8b/0xeb Jun 07 12:49:05 [kernel] [c12b2dc8] ? __pci_register_driver+0x38/0x91 Jun 07 12:49:05 [kernel] [f9497000] ? init_module+0x0/0xf [budget_ci] Jun 07 12:49:05 [kernel] [f9447bb9] ? saa7146_register_extension+0x68/0x242 [saa7146] Jun 07 12:49:05 [kernel] [f949700d] ? init_module+0xd/0xf [budget_ci] Jun 07 12:49:05 [kernel] [c1001139] ? do_one_initcall+0x4c/0x131 Jun 07 12:49:05 [kernel] [c104b5ae] ? sys_init_module+0xa7/0x1db Jun 07 12:49:05 [kernel] [c1002810] ? sysenter_do_call+0x12/0x26 Jun 07 12:49:05 [kernel] ---[ end trace 100a66f59725996d ]--- It looks to me that v4l-dvb is not really maintained anymore :( Helmut Auer, hel...@helmutauer.de -- 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 - Is it still usable for a distribution ?
Hi ... Another problem (after fixing the compile issues) is the IR Part of v4l-dvb which includes an Imon module. This module doesn't provide any lirc devices, so how can this oe be used as an IR device ? You don't need lirc to use imon, since it now provides a standard input/event interface. So, the driver currently can be used with lirc event interface, or alone. See http://wilsonet.com/jarod/imon_stuff/imon-devinput-lirc/ for the config I use w/my own imon hardware. Tanks for the hint ! Til now I am using lirc_imon which fit all my needs. Lirc-dev patches are currently being discussed. There are just a few adjustments on it, in order to get it finally merged. The kernel-userspace interface will likely need a few changes, so you'll likely need to update lirc after the merge. Better to follow the IR threads at linux-media ML, in order to be in-tune with the changes. I've considered adding lirc_dev support back to the imon driver when we get it merged, but it really doesn't make a whole lot of sense, given that the imon devices do all IR decoding in hardware. As long as the keymap is complete, there's no benefit to wiring up lirc_dev vs. just using lircd's devinput access method for imon devices. You're right, also inputlircd can do the job. Is your imon driver fully compatible with the lirc_imon in the display part ? It would be very helpful to add a parameter for disabling the IR Part, I have many users which are using only the display part. -- Helmut Auer, hel...@helmutauer.de -- 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 - Is it still usable for a distribution ?
Hello Now with kernel 2.6.34 this doesn't work anymore, because v4l-dvb doesn't compile. Douglas returned from this 2 week trip abroad and he is backporting the upstream stuff. Yesterday, he reported to me that the tree is now compiling with 2.6.34. Ok - I also got it compiling, but budget-ci is causing kernel oops (see other ML thread) The final question for me: Does it make any sense anymore to stay with v4l-dvb or do I have to change to the kernel drivers ? The major disadvantage of the kernel drivers is the fact that I cannot switch to newer dvb drivers, I am stuck to the ones included in the kernel. Well, this is something that you need to answer by yourself ;) Thats not what I wanted to hear ;) I don't recommend using a random snapshot of the tree on a distro package, as regressions may happen during the development period. Also, the backports are done at best efforts. There are no warranties, no QA and generally no tests with real hardware when a backport is done. So, while we hope that the backport will work, you may have a bug introduced on the backport stuff that may affect your card, not present upstream. IMHO, the better is to just upgrade to the next stable kernel. Ok - that what I also thought formerly v4l-dvb was the bleeding edge and the kernel draivers were about 2 Versions behind. Now the kernel drivers are often the newer ones, so I have to switch. Another alternative is to manually apply on your distro the patches that you need there. All patches with c/c to sta...@kernel.org are bug fixes that needs to be backported to older (stable) kernels. So, a good hint is to check for those stable patches. Unfortunately, not all developers remind to add a c/c to stable. I try to do my best to re-tag those emails when sending the patches upstream, but I generally opt to trust on the developers, since a fix may apply only at the latest upstream kernel. Thats surely an option, but an average user of my distri can't compile a kernel ;) Emerging v4l-dvb is much easier ;) -- Helmut Auer, hel...@helmutauer.de -- 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 - Is it still usable for a distribution ?
Hello Is your imon driver fully compatible with the lirc_imon in the display part ? Yes, works perfectly fine with the exact same lcdproc setup here -- both vfd and lcd tested. fine - I will give it a try ! It would be very helpful to add a parameter for disabling the IR Part, I have many users which are using only the display part. Hm. I was going to suggest that if people aren't using the receiver, there should be no need to disable IR, but I guess someone might want to use an mce remote w/an mce receiver, and that would have interesting results if they had one of the imon IR receivers programmed for mce mode. Thats what I meant :) I'll keep it in mind for the next time I'm poking at the imon code in depth. Maybe you can use the already available ir_protocol parameter. -- Helmut Auer, hel...@helmutauer.de -- 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 does not compile with kernel 2.6.34
Am 25.05.2010 23:59, schrieb Helmut Auer: Hello I just wanted to compile v4l-dvb for my Gen2VDR Ditribution with kernel 2.6.34, but it fails because many modules are missing: #include linux/slab.h and are getting errors like: /tmp/portage/media-tv/v4l-dvb-hg-0.1-r3/work/v4l-dvb/v4l/tuner-xc2028.c: In function 'free_firmware': /tmp/portage/media-tv/v4l-dvb-hg-0.1-r3/work/v4l-dvb/v4l/tuner-xc2028.c:252: error: implicit declaration of function 'kfree' /tmp/portage/media-tv/v4l-dvb-hg-0.1-r3/work/v4l-dvb/v4l/tuner-xc2028.c: In function 'load_all_firmwares': /tmp/portage/media-tv/v4l-dvb-hg-0.1-r3/work/v4l-dvb/v4l/tuner-xc2028.c:314: error: implicit declaration of function Am I missing something or is v4l-dvb broken ? An easy patch for this problem is: --- v4l/compat.h.org2010-05-26 22:22:31.0 +0200 +++ v4l/compat.h2010-05-26 22:22:43.0 +0200 @@ -28,6 +28,10 @@ #include linux/i2c-dev.h #endif +#if LINUX_VERSION_CODE = KERNEL_VERSION(2, 6, 33) +#include linux/slab.h +#endif + #if LINUX_VERSION_CODE KERNEL_VERSION(2, 6, 26) #ifdef CONFIG_PROC_FS #include linux/module.h -- Helmut Auer, hel...@helmutauer.de -- 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 does not compile with kernel 2.6.34 [solved]
Am 25.05.2010 23:59, schrieb Helmut Auer:
Hello
I just wanted to compile v4l-dvb for my Gen2VDR Ditribution with kernel
2.6.34, but it fails
because many modules are missing:
#include linux/slab.h
and are getting errors like:
/tmp/portage/media-tv/v4l-dvb-hg-0.1-r3/work/v4l-dvb/v4l/tuner-xc2028.c: In
function
'free_firmware':
/tmp/portage/media-tv/v4l-dvb-hg-0.1-r3/work/v4l-dvb/v4l/tuner-xc2028.c:252:
error: implicit
declaration of function 'kfree'
/tmp/portage/media-tv/v4l-dvb-hg-0.1-r3/work/v4l-dvb/v4l/tuner-xc2028.c: In
function
'load_all_firmwares':
/tmp/portage/media-tv/v4l-dvb-hg-0.1-r3/work/v4l-dvb/v4l/tuner-xc2028.c:314:
error: implicit
declaration of function
Am I missing something or is v4l-dvb broken ?
Here is the complete patch I am using:
--- v4l/compat.h.org2010-05-26 22:22:31.0 +0200
+++ v4l/compat.h2010-05-26 22:22:43.0 +0200
@@ -28,6 +28,10 @@
#include linux/i2c-dev.h
#endif
+#if LINUX_VERSION_CODE = KERNEL_VERSION(2, 6, 33)
+#include linux/slab.h
+#endif
+
#if LINUX_VERSION_CODE KERNEL_VERSION(2, 6, 26)
#ifdef CONFIG_PROC_FS
#include linux/module.h
--- linux/drivers/media/IR/ir-raw-event.c.org 2010-05-26 22:35:12.0
+0200
+++ linux/drivers/media/IR/ir-raw-event.c 2010-05-26 22:35:43.0
+0200
@@ -15,6 +15,7 @@
#include linux/workqueue.h
#include linux/spinlock.h
#include linux/sched.h
+#include linux/slab.h
#include ir-core-priv.h
/* Define the max number of pulse/space transitions to buffer */
--- linux/drivers/media/dvb/dvb-core/dvb_frontend.h.org 2010-05-26
23:06:50.0 +0200
+++ linux/drivers/media/dvb/dvb-core/dvb_frontend.h 2010-05-26
23:06:21.0 +0200
@@ -39,6 +39,7 @@
#include linux/dvb/frontend.h
+#include compat.h
#include dvbdev.h
struct dvb_frontend_tune_settings {
diff -upr /home/v4l/tmp/oldtree/drivers/media/radio/radio-tea5764.c
./drivers/media/radio/radio-tea5764.c
--- linux/drivers/media/radio/radio-tea5764.c.org 2010-05-25
23:56:57.0 -0300
+++ linux/drivers/media/radio/radio-tea5764.c 2010-05-21 11:21:19.0
-0300
@@ -32,6 +32,7 @@
* add RDS support
*/
#include linux/kernel.h
+#include linux/slab.h
#include linux/module.h
#include linux/init.h/* Initdata
*/
#include linux/videodev2.h /* kernel radio structs */
--
Helmut Auer, hel...@helmutauer.de
--
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-dvb does not compile with kernel 2.6.34
Hello I just wanted to compile v4l-dvb for my Gen2VDR Ditribution with kernel 2.6.34, but it fails because many modules are missing: #include linux/slab.h and are getting errors like: /tmp/portage/media-tv/v4l-dvb-hg-0.1-r3/work/v4l-dvb/v4l/tuner-xc2028.c: In function 'free_firmware': /tmp/portage/media-tv/v4l-dvb-hg-0.1-r3/work/v4l-dvb/v4l/tuner-xc2028.c:252: error: implicit declaration of function 'kfree' /tmp/portage/media-tv/v4l-dvb-hg-0.1-r3/work/v4l-dvb/v4l/tuner-xc2028.c: In function 'load_all_firmwares': /tmp/portage/media-tv/v4l-dvb-hg-0.1-r3/work/v4l-dvb/v4l/tuner-xc2028.c:314: error: implicit declaration of function Am I missing something or is v4l-dvb broken ? -- Helmut Auer, hel...@helmutauer.de -- 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
Mantis not in modules.pcimap
Hello, The mantis module is build and working fine with the Skystar2 HD, but it I cannot autodetect it, because modules.pcimap is not filled with the vendor id of the card using this module. What's to do to get these ID's ? In my case its a: 01:08.0 0480: 1822:4e35 (rev 01) Subsystem: 1ae4:0003 Flags: bus master, medium devsel, latency 32, IRQ 16 Memory at fddff000 (32-bit, prefetchable) [size=4K] -- Helmut Auer, hel...@helmutauer.de -- 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]Add support for SMT7020 to cx88
Am 11.02.2010 22:06, schrieb Helmut Auer: From: Helmut Auer hel...@helmutauer.de This patch (originally written by Dirk Herrendoerfer) adds support for the built-in dvb device of a Samsung SMT7020s (x86 based STB) to the cx88 family. (see http://www.linuxtv.org/pipermail/linux-dvb/2007-January/015208.html) Signed-off-by: Helmut Auer hel...@helmutauer.de What's to do to get attention for this ? -- Helmut Auer, hel...@helmutauer.de -- 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]Add support for SMT7020 to cx88
Am 11.02.2010 22:06, schrieb Helmut Auer: From: Helmut Auer hel...@helmutauer.de This patch (originally written by Dirk Herrendoerfer) adds support for the built-in dvb device of a Samsung SMT7020s (x86 based STB) to the cx88 family. (see http://www.linuxtv.org/pipermail/linux-dvb/2007-January/015208.html) Signed-off-by: Helmut Auer hel...@helmutauer.de What do I have to do to get some attention ? -- Helmut Auer, hel...@helmutauer.de -- 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 support for SMT7020 to cx88
From: Helmut Auer hel...@helmutauer.de
This patch (originally written by Dirk Herrendoerfer) adds support for the
built-in dvb device
of a Samsung SMT7020s (x86 based STB) to the cx88 family.
(see http://www.linuxtv.org/pipermail/linux-dvb/2007-January/015208.html)
Signed-off-by: Helmut Auer hel...@helmutauer.de
--
Helmut Auer, hel...@helmutauer.de
diff -r 095b1aec2354 linux/drivers/media/video/cx88/cx88-cards.c
--- a/linux/drivers/media/video/cx88/cx88-cards.c Thu Feb 11 15:43:41
2010 -0200
+++ b/linux/drivers/media/video/cx88/cx88-cards.c Thu Feb 11 22:01:13
2010 +0100
@@ -1499,6 +1499,18 @@
.audioroute = 8,
},
},
+ [CX88_BOARD_SAMSUNG_SMT_7020] = {
+ .name = Samsung SMT 7020 DVB-S,
+ .tuner_type = TUNER_ABSENT,
+ .radio_type = UNSET,
+ .tuner_addr = ADDR_UNSET,
+ .radio_addr = ADDR_UNSET,
+ .input = { {
+ .type = CX88_VMUX_DVB,
+ .vmux = 0,
+ } },
+ .mpeg = CX88_MPEG_DVB,
+ },
[CX88_BOARD_ADSTECH_PTV_390] = {
.name = ADS Tech Instant Video PCI,
.tuner_type = TUNER_ABSENT,
@@ -2388,6 +2400,14 @@
.subvendor = 0x0070,
.subdevice = 0x1404,
.card = CX88_BOARD_HAUPPAUGE_HVR3000,
+ }, {
+ .subvendor = 0x18ac,
+ .subdevice = 0xdc00,
+ .card = CX88_BOARD_SAMSUNG_SMT_7020,
+ }, {
+ .subvendor = 0x18ac,
+ .subdevice = 0xdccd,
+ .card = CX88_BOARD_SAMSUNG_SMT_7020,
},{
.subvendor = 0x1461,
.subdevice = 0xc111, /* AverMedia M150-D */
@@ -2666,6 +2686,9 @@
case 98559: /* WinTV-HVR1100LP (Video no IR, Retail - Low Profile) */
/* known */
break;
+ case CX88_BOARD_SAMSUNG_SMT_7020:
+ cx_set(MO_GP0_IO, 0x008989FF);
+ break;
default:
warn_printk(core, warning: unknown hauppauge model #%d\n,
tv.model);
diff -r 095b1aec2354 linux/drivers/media/video/cx88/cx88-dvb.c
--- a/linux/drivers/media/video/cx88/cx88-dvb.c Thu Feb 11 15:43:41 2010 -0200
+++ b/linux/drivers/media/video/cx88/cx88-dvb.c Thu Feb 11 22:01:13 2010 +0100
@@ -681,6 +681,194 @@
return 0;
}
+
+
+static u8 samsung_smt_7020_inittab[] = {
+0x01, 0x15,
+0x02, 0x00,
+0x03, 0x00,
+0x04, 0x7D,
+0x05, 0x0F,
+0x06, 0x02,
+0x07, 0x00,
+0x08, 0x60,
+
+0x0A, 0xC2,
+0x0B, 0x00,
+0x0C, 0x01,
+0x0D, 0x81,
+0x0E, 0x44,
+0x0F, 0x09,
+0x10, 0x3C,
+0x11, 0x84,
+0x12, 0xDA,
+0x13, 0x99,
+0x14, 0x8D,
+0x15, 0xCE,
+0x16, 0xE8,
+0x17, 0x43,
+0x18, 0x1C,
+0x19, 0x1B,
+0x1A, 0x1D,
+
+0x1C, 0x12,
+0x1D, 0x00,
+0x1E, 0x00,
+0x1F, 0x00,
+0x20, 0x00,
+0x21, 0x00,
+0x22, 0x00,
+0x23, 0x00,
+
+0x28, 0x02,
+0x29, 0x28,
+0x2A, 0x14,
+0x2B, 0x0F,
+0x2C, 0x09,
+0x2D, 0x05,
+
+0x31, 0x1F,
+0x32, 0x19,
+0x33, 0xFC,
+0x34, 0x13,
+0xff, 0xff,
+};
+
+
+static int samsung_smt_7020_tuner_set_params(struct dvb_frontend *fe,
+ struct dvb_frontend_parameters *params)
+{
+ struct cx8802_dev *dev = fe-dvb-priv;
+ u8 buf[4];
+ u32 div;
+ struct i2c_msg msg = {
+ .addr = 0x61,
+ .flags = 0,
+ .buf = buf,
+ .len = sizeof(buf) };
+
+ div = params-frequency / 125;
+
+ buf[0] = (div 8) 0x7f;
+ buf[1] = div 0xff;
+ buf[2] = 0x84; /* 0xC4 */
+ buf[3] = 0x00;
+
+ if (params-frequency 150)
+ buf[3] |= 0x10;
+
+ if (fe-ops.i2c_gate_ctrl)
+ fe-ops.i2c_gate_ctrl(fe, 1);
+
+ if (i2c_transfer(dev-core-i2c_adap, msg, 1) != 1)
+ return -EIO;
+
+ return 0;
+}
+
+static int samsung_smt_7020_set_tone(struct dvb_frontend *fe,
+ fe_sec_tone_mode_t tone)
+{
+ struct cx8802_dev *dev = fe-dvb-priv;
+ struct cx88_core *core = dev-core;
+
+ cx_set(MO_GP0_IO, 0x0800);
+
+ switch (tone) {
+ case SEC_TONE_ON:
+ cx_set(MO_GP0_IO, 0x08);
+ break;
+ case SEC_TONE_OFF:
+ cx_clear(MO_GP0_IO, 0x08);
+ break;
+ default:
+ return -EINVAL
Re: [PULL] nGene driver - http://endr...@linuxtv.org/hg/~endriss/ngene
Am 03.02.2010 21:02, schrieb Mauro Carvalho Chehab:
...
ERROR: that open brace { should be on the previous line
#1693: FILE: drivers/media/dvb/ngene/ngene-core.c:1615:
+ u8 tsin4_config[6] =
+ {3072 / 64, 3072 / 64, 0, 3072 / 64, 3072 / 64, 0};
ERROR: that open brace { should be on the previous line
#1695: FILE: drivers/media/dvb/ngene/ngene-core.c:1617:
+ u8 default_config[6] =
+ {4096 / 64, 4096 / 64, 0, 2048 / 64, 2048 / 64, 0};
...
WARNING: do not add new typedefs
#2313: FILE: drivers/media/dvb/ngene/ngene.h:203:
+typedef struct EVENT_BUFFER *PEVENT_BUFFER;
WARNING: do not add new typedefs
#2601: FILE: drivers/media/dvb/ngene/ngene.h:491:
+typedef struct HW_SCATTER_GATHER_ELEMENT *PHW_SCATTER_GATHER_ELEMENT;
WARNING: do not add new typedefs
#2602: FILE: drivers/media/dvb/ngene/ngene.h:492:
+typedef struct FWRB *PFWRB;
WARNING: do not add new typedefs
#2667: FILE: drivers/media/dvb/ngene/ngene.h:557:
+typedef struct {
total: 2 errors, 8 warnings, 2935 lines checked
Sorry but the kernel guys seems to have a lot of time to waste, if they have
time to care about
these warnings ;)
--
Helmut Auer, hel...@helmutauer.de
--
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
Status of v4l repositories / merging new one
Hello List AFAIK there are different v4l repositories supporting differnet hardware, e.g v4l-dvb(missing skystar HD), liplianin (missing knc1) etc. To add another one, we have a repository supporting the pci-e dual dvb-s low pointer profile mediapointer card :) But for my distribution I'd like to have one repository, supporting all cards Whats to do to get all these repositories merged ? Are there any plans about doing that ? -- Helmut Auer, hel...@helmutauer.de -- 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
