Re: Automatic device driver back-porting with media_build

2015-12-28 Thread Mauro Carvalho Chehab
Hi Mason, Em Mon, 28 Dec 2015 13:21:03 +0100 Mason escreveu: > On 28/12/2015 11:44, Mason wrote: > > > Hello Mauro, > > > > Haven't heard back from you in a while. Maybe someone else can point > > out what I'm doing wrong? > > > > On 17/12/2015 13:55, Mauro Carvalho Chehab wrote: > > > >> Ma

Re: Automatic device driver back-porting with media_build

2015-12-28 Thread Mason
On 28/12/2015 11:44, Mason wrote: > Hello Mauro, > > Haven't heard back from you in a while. Maybe someone else can point > out what I'm doing wrong? > > On 17/12/2015 13:55, Mauro Carvalho Chehab wrote: > >> Mason wrote: >> >>> I have a TechnoTrend TT-TVStick CT2-4400v2 USB tuner, as described

Re: Automatic device driver back-porting with media_build

2015-12-28 Thread Mason
Hello Mauro, Haven't heard back from you in a while. Maybe someone else can point out what I'm doing wrong? On 17/12/2015 13:55, Mauro Carvalho Chehab wrote: > Mason wrote: > >> I have a TechnoTrend TT-TVStick CT2-4400v2 USB tuner, as described here: >> http://linuxtv.org/wiki/index.php/TechnoT

Re: Automatic device driver back-porting with media_build

2015-12-18 Thread Mason
On 18/12/2015 18:10, Mason wrote: > Am I doing something wrong? Yes, I didn't have I2C enabled. By running 'make menuconfig' in a recent kernel, I could see which Kconfig options are required to build the dvbsky driver. Mauro, I hope you'll find time to address my remaining bug reports. Issue

Re: Automatic device driver back-porting with media_build

2015-12-18 Thread Mason
On 17/12/2015 15:55, Mauro Carvalho Chehab wrote: > Did the driver compile fine? Once all the modules finish building, I have many *.ko files in v4l. I copy them to my target's /lib/modules/3.4.39.13/kernel and run depmod -a It seems modprobe rc-dvbsky doesn't bring in all the stuff needed to a

Re: Automatic device driver back-porting with media_build

2015-12-18 Thread Mason
On 18/12/2015 14:40, Mason wrote: > I will try building a kernel with CONFIG_OF=n Build works much better with CONFIG_OF=n I suppose OF support with ancient kernels is untested. (My setup didn't need it anyway.) The remaining issue is: WARNING: "nsecs_to_jiffies" [/tmp/sandbox/media_build/v4l/g

Re: Automatic device driver back-porting with media_build

2015-12-18 Thread Mason
On 18/12/2015 13:59, Mason wrote: [snip previous work-arounds] Compilation completes. make -C /tmp/sandbox/custom-linux-3.4 SUBDIRS=/tmp/sandbox/media_build/v4l modules make[2]: Entering directory `/tmp/sandbox/custom-linux-3.4' Building modules, stage 2. MODPOST 209 modules WARNING: "of_gr

Re: Automatic device driver back-porting with media_build

2015-12-18 Thread Mason
On 18/12/2015 13:10, Mason wrote: > On 18/12/2015 12:22, Mauro Carvalho Chehab wrote: > >> Patch applied. > > Great! Thanks. > > Using the latest media_build master + my writel_relaxed work-around, > compilation proceeds much further, then dies on device tree stuff: > (same error with vanilla a

Re: Automatic device driver back-porting with media_build

2015-12-18 Thread Mason
On 18/12/2015 12:22, Mauro Carvalho Chehab wrote: > Patch applied. Great! Thanks. Using the latest media_build master + my writel_relaxed work-around, compilation proceeds much further, then dies on device tree stuff: (same error with vanilla and custom kernel) Will look into it. Any idea? :-(

Re: Automatic device driver back-porting with media_build

2015-12-18 Thread Mauro Carvalho Chehab
Em Fri, 18 Dec 2015 09:03:45 -0200 Mauro Carvalho Chehab escreveu: > Em Fri, 18 Dec 2015 11:44:35 +0100 > Mason escreveu: > > > On 17/12/2015 18:03, Mason wrote: > > > > > The media_build process prints: > > > > > > "Preparing to compile for kernel version 3.4.3913" > > > > > > In fact, the

Re: Automatic device driver back-porting with media_build

2015-12-18 Thread Mauro Carvalho Chehab
Em Fri, 18 Dec 2015 11:44:35 +0100 Mason escreveu: > On 17/12/2015 18:03, Mason wrote: > > > The media_build process prints: > > > > "Preparing to compile for kernel version 3.4.3913" > > > > In fact, the custom kernel's Makefile contains: > > > > VERSION = 3 > > PATCHLEVEL = 4 > > SUBLEVEL =

Re: Automatic device driver back-porting with media_build

2015-12-18 Thread Mason
On 18/12/2015 11:37, Mauro Carvalho Chehab wrote: > Em Thu, 17 Dec 2015 17:48:57 +0100 > Mason escreveu: > >> On 17/12/2015 17:09, Mauro Carvalho Chehab wrote: >>> Em Thu, 17 Dec 2015 16:32:54 +0100 >>> Mason escreveu: >>> I wanted to fix the NEED_WRITEL_RELAXED warning, but I don't know Pe

Re: Automatic device driver back-porting with media_build

2015-12-18 Thread Mason
On 17/12/2015 18:03, Mason wrote: > The media_build process prints: > > "Preparing to compile for kernel version 3.4.3913" > > In fact, the custom kernel's Makefile contains: > > VERSION = 3 > PATCHLEVEL = 4 > SUBLEVEL = 39 > EXTRAVERSION = 13 > NAME = Saber-toothed Squirrel > > Is it possible

Re: Automatic device driver back-porting with media_build

2015-12-18 Thread Mauro Carvalho Chehab
Em Thu, 17 Dec 2015 17:48:57 +0100 Mason escreveu: > On 17/12/2015 17:09, Mauro Carvalho Chehab wrote: > > Em Thu, 17 Dec 2015 16:32:54 +0100 > > Mason escreveu: > > > >> I wanted to fix the NEED_WRITEL_RELAXED warning, but I don't know Perl. > >> > >> v4l/scripts/make_config_compat.pl > >> > >

Re: Automatic device driver back-porting with media_build

2015-12-17 Thread Mason
On 17/12/2015 18:03, Mason wrote: > On 17/12/2015 17:09, Mauro Carvalho Chehab wrote: > >> As I said before, heavily patched Kernel. It seems that the network stack >> was updated to some newer version. The media_build backport considers >> only the upstream Kernels. In the specific case of 3.4,

Re: Automatic device driver back-porting with media_build

2015-12-17 Thread Mason
On 17/12/2015 17:09, Mauro Carvalho Chehab wrote: > As I said before, heavily patched Kernel. It seems that the network stack > was updated to some newer version. The media_build backport considers > only the upstream Kernels. In the specific case of 3.4, it is known > to build fine with Kernel li

Re: Automatic device driver back-porting with media_build

2015-12-17 Thread Mason
On 17/12/2015 17:09, Mauro Carvalho Chehab wrote: > Em Thu, 17 Dec 2015 16:32:54 +0100 > Mason escreveu: > >> I wanted to fix the NEED_WRITEL_RELAXED warning, but I don't know Perl. >> >> v4l/scripts/make_config_compat.pl >> >> check_files_for_func("writel_relaxed", "NEED_WRITEL_RELAXED", >> "in

Re: Automatic device driver back-porting with media_build

2015-12-17 Thread Mauro Carvalho Chehab
Em Thu, 17 Dec 2015 16:32:54 +0100 Mason escreveu: > On 17/12/2015 15:55, Mauro Carvalho Chehab wrote: > > > Em Thu, 17 Dec 2015 15:30:43 +0100 > > Mason escreveu: > > > >> On 17/12/2015 15:08, Mauro Carvalho Chehab wrote: > >> > >>> Then I guess you're not using vanilla 3.4 Kernel, but some h

Re: Automatic device driver back-porting with media_build

2015-12-17 Thread Mason
On 17/12/2015 15:55, Mauro Carvalho Chehab wrote: > Em Thu, 17 Dec 2015 15:30:43 +0100 > Mason escreveu: > >> On 17/12/2015 15:08, Mauro Carvalho Chehab wrote: >> >>> Then I guess you're not using vanilla 3.4 Kernel, but some heavily >>> modified version. You're on your own here. >> >> #ifdef NE

Re: Automatic device driver back-porting with media_build

2015-12-17 Thread Mauro Carvalho Chehab
Em Thu, 17 Dec 2015 15:30:43 +0100 Mason escreveu: > On 17/12/2015 15:08, Mauro Carvalho Chehab wrote: > > > Then I guess you're not using vanilla 3.4 Kernel, but some heavily > > modified version. You're on your own here. > > #ifdef NEED_KVFREE > #include > static inline void kvfree(const voi

Re: Automatic device driver back-porting with media_build

2015-12-17 Thread Mason
On 17/12/2015 15:08, Mauro Carvalho Chehab wrote: > Then I guess you're not using vanilla 3.4 Kernel, but some heavily > modified version. You're on your own here. #ifdef NEED_KVFREE #include static inline void kvfree(const void *addr) { if (is_vmalloc_addr(addr)) vfree(a

Re: Automatic device driver back-porting with media_build

2015-12-17 Thread Mauro Carvalho Chehab
Em Thu, 17 Dec 2015 14:52:21 +0100 Mason escreveu: > Hello Mauro, > > On 17/12/2015 13:55, Mauro Carvalho Chehab wrote: > > > Mason wrote: > > > >> I have a TechnoTrend TT-TVStick CT2-4400v2 USB tuner, as described here: > >> http://linuxtv.org/wiki/index.php/TechnoTrend_TT-TVStick_CT2-4400 >

Re: Automatic device driver back-porting with media_build

2015-12-17 Thread Mason
Hello Mauro, On 17/12/2015 13:55, Mauro Carvalho Chehab wrote: > Mason wrote: > >> I have a TechnoTrend TT-TVStick CT2-4400v2 USB tuner, as described here: >> http://linuxtv.org/wiki/index.php/TechnoTrend_TT-TVStick_CT2-4400 >> >> According to the article, the device is supported since kernel 3.

Re: Automatic device driver back-porting with media_build

2015-12-17 Thread Mauro Carvalho Chehab
Em Thu, 17 Dec 2015 13:13:36 +0100 Mason escreveu: > Hello everyone, > > I have a TechnoTrend TT-TVStick CT2-4400v2 USB tuner, as described here: > http://linuxtv.org/wiki/index.php/TechnoTrend_TT-TVStick_CT2-4400 > > According to the article, the device is supported since kernel 3.19 > and ind

Automatic device driver back-porting with media_build

2015-12-17 Thread Mason
Hello everyone, I have a TechnoTrend TT-TVStick CT2-4400v2 USB tuner, as described here: http://linuxtv.org/wiki/index.php/TechnoTrend_TT-TVStick_CT2-4400 According to the article, the device is supported since kernel 3.19 and indeed, if I use a 4.1 kernel, I can pick CONFIG_DVB_USB_DVBSKY and ev