[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <541C8A26.6050207@ventoso.org>
Date: Fri, 19 Sep 2014 21:55:18 +0200
From: Luca Olivetti <luca@...toso.org>
To: Frank Schäfer <fschaefer.oss@...glemail.com>,
Fengguang Wu <fengguang.wu@...el.com>
CC: Mauro Carvalho Chehab <m.chehab@...sung.com>,
linux-media@...r.kernel.org, Jet Chen <jet.chen@...el.com>,
Su Tao <tao.su@...el.com>, Yuanhan Liu <yuanhan.liu@...el.com>,
LKP <lkp@...org>, linux-kernel@...r.kernel.org, crope@....fi
Subject: Re: [media/dvb_usb_af9005] BUG: unable to handle kernel paging request
(WAS: [media/em28xx] BUG: unable to handle kernel)
El 19/09/14 21:22, Frank Schäfer ha escrit:
>>
>> So symbol_request() returns pointers.!= NULL
>>
>> A closer look at the definition of symbol_request() shows, that it does
>> nothing if CONFIG_MODULES is disabled (it just returns its argument).
>>
>>
>> One possibility to fix this bug would be to embrace these three lines with
>>
>> #ifdef CONFIG_DVB_USB_AF9005_REMOTE
>> ...
>> #endif
> Luca, what do you think ?
>
> This seems to be an ancient bug, which is known at least since 5 1/2 years:
> https://lkml.org/lkml/2009/2/4/350
Well, it's been a while so I don't remember the details, but I think the
same now as then ;-)
The idea behind CONFIG_DVB_USB_AF9005_REMOTE was to provide an
alternative implementation (based on lirc, at the time it wasn't in the
kernel), since this adapter doesn't decode the IR pulses by itself.
In theory you could leave it undefined but still provide an
implementation in a different module. Just adding
#ifdef CONFIG_DVB_USB_AF9005_REMOTE
would nuke the (futile?) effort.
Now, since the problem seems to be with CONFIG_MODULES disabled, maybe
you could combine both conditions
#if defined(CONFIG_MODULE) || defined(CONFIG_DVB_USB_AF9005_REMOTE)
Bye
--
Luca
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists