Re: [PATCH v2 18/31] gp8psk: don't do DMA on stack

I applied this patch to the 4.8.4 kernel driver (that I'm currently running) and it caused nothing but "frontend 0/0 timed out while tuning". Is there another patch that should be used in conjunction with this? If not, this patch breaks the gp8psk driver. Thanks. On Tue, Oct 11, 2016 at 3:09 AM,

Re: Question about 2 gp8psk patches I noticed, and possible bug.

Hi Mauro, Here are the results after testing the latest patch: [33922.643770] usbcore: deregistering interface driver dvb_usb_gp8psk [33922.643789] gp8psk: unregistering fe0 [33922.643865] gp8psk: detaching fe0 [33922.643868] [ cut here ] [33922.643875] WARNING: CPU: 1

Re: Question about 2 gp8psk patches I noticed, and possible bug.

$ gdb /usr/src/linux/vmlinux GNU gdb (Debian 7.11.1-2) 7.11.1 ... Reading symbols from /usr/src/linux/vmlinux...done. (gdb) l *module_put+0x67 0xc10a4b87 is in module_put (kernel/module.c:1108). 1103int ret; 1104 1105if (module) { 1106preempt_disable();

Re: Question about 2 gp8psk patches I noticed, and possible bug.

>> (gdb) l *module_put+0x67 >> 0xc10a4b87 is in module_put (kernel/module.c:1108). >> 1103int ret; >> 1104 >> 1105if (module) { >> 1106preempt_disable(); >> 1107ret = atomic_dec_if_positive(>refcnt); >> 1108

Re: Question about 2 gp8psk patches I noticed, and possible bug.

> Hmm... dvb_attach() assumes that the symbol is exported. Please try > this patch. If it fixes the bug, I'll likely do something else, to > avoid the need of EXPORT_SYMBOL. > > > [PATCH] [media] gp8psk: Fix DVB frontend attach > > it should be calling module_get() at attach, as otherwise >

Re: Question about 2 gp8psk patches I noticed, and possible bug.

> commit 0c979a12309af49894bb1dc60e747c3cd53fa888 > Author: Mauro Carvalho Chehab > Date: Wed Nov 9 15:33:17 2016 -0200 > > [media] gp8psk: Fix DVB frontend attach > > it should be calling module_get() at attach, as otherwise > module_put() will crash. > >

Re: Question about 2 gp8psk patches I noticed, and possible bug.

> Sorry, forgot to add one file to the patch. > > The right fix is this one. This patch seems to fix the unload crash but unfortunately now all I get is "frontend 0/0 timed out while tuning". > [PATCH v2] [media] gp8psk: Fix DVB frontend attach > > The DVB binding schema at the DVB core

Re: Question about 2 gp8psk patches I noticed, and possible bug.

>> Sorry, forgot to add one file to the patch. >> >> The right fix is this one. > > This patch seems to fix the unload crash but unfortunately now all I > get is "frontend 0/0 timed out while tuning". Forgot to mention that I didn't see the gp8psk-fe entry in menuconfig customize frontends even

Re: Question about 2 gp8psk patches I noticed, and possible bug.

>>> Sorry, forgot to add one file to the patch. >>> >>> The right fix is this one. >> >> This patch seems to fix the unload crash but unfortunately now all I >> get is "frontend 0/0 timed out while tuning". > > Forgot to mention that I didn't see the gp8psk-fe entry in menuconfig > customize

Re: Question about 2 gp8psk patches I noticed, and possible bug.

Ok, I think I had too much patching going on (I switched from 4.8.4 kernel drivers to media_build) so I started from scratch with a fresh update to kernel 4.8.7. First I applied the dma stuff in this order: (from https://patchwork.linuxtv.org/patch/37395/raw/)

Re: [PATCH 2/2] [media] lirc: remove lirc_serial driver

> serial_ir driver in rc-core Which kernel did this happen in? I don't see a sign of it in 4.8.5 and I want to make sure that homebrew serial devices still work with lirc after this. Are you sure the serial_ir driver you refer to isn't about a usb-based serial ir? Thanks for clarity. -- To

Re: [PATCH] [media] gp8psk: fix spelling mistake: "firmare" -> "firmware"

> - err("firmare chunk size bigger than 64 bytes."); > + err("firmware chunk size bigger than 64 bytes."); Yup. > -"HW don't support CMAC encrypiton, use software CMAC > encrypiton\n"); > +"HW don't

Re: [PATCH v4 0/3] IR decoding using BPF

Sean, I'd like to echo Matthias's appreciation for your work with this BPF project. I'm very much looking forward to the possibility of using my remotes directly with decoders generated from the existing lircd.conf's. Excited seeing your work progress! Cheers, Derek On Tue, May 22, 2018 at 6:50

Re: [PATCH v2] Input: Add missing event codes for common IR remote buttons

> On Sat, 2018-11-03 at 07:55 -0700, Derek Kelly wrote: > > The following patch adds event codes for common buttons found on > > various > > provider and universal remote controls. They represent functions not > > covered by existing event codes. Once added, rc_keymaps can be > > updated > >

<    1   2