Trying to compile for kernel version 2.6.28

Trying to compile for kernel version 2.6.28

[Jan Hoogenraad]

At this moment, I cannot figure out how to compile v4l with kernel 
version 2.6.28.
I see, however, that the daily build reports:
linux-2.6.28-i686: OK

I have the same problem as in the old message:
http://www.spinics.net/lists/linux-media/msg10047.html
I have included the text of that message below.

How do I revert the latest changepatch to videobuf-dma-config ?


And could somebody preferably put  a kernel-version-dependent #if around 
that changepatch ?


-------------------

>/ /
>/ Then I made it here:/
>/ /
>/   CC [M]  /home/mythbox/Firmware/v4l-dvb/v4l/videobuf-core.o/
>/   CC [M]  /home/mythbox/Firmware/v4l-dvb/v4l/videobuf-dma-sg.o/
>/   CC [M]  /home/mythbox/Firmware/v4l-dvb/v4l/videobuf-dma-contig.o/
>/ /home/mythbox/Firmware/v4l-dvb/v4l/videobuf-dma-contig.c: In function/
>/ 'videobuf_dma_contig_user_get':/
>/ /home/mythbox/Firmware/v4l-dvb/v4l/videobuf-dma-contig.c:164: error:/
>/ implicit declaration of function 'follow_pfn'/
>/ make[3]: *** [/home/mythbox/Firmware/v4l-dvb/v4l/videobuf-dma-contig.o] Error 1/
>/ make[2]: *** [_module_/home/mythbox/Firmware/v4l-dvb/v4l] Error 2/
>/ make[2]: Leaving directory `/usr/src/linux-headers-2.6.28-15-generic'/
>/ make[1]: *** [default] Error 2/
>/ make[1]: Leaving directory `/home/mythbox/Firmware/v4l-dvb/v4l'/
>/ make: *** [all] Error 2/
>/ /
>/ Its kinda annoying that a year ago this was super easy.../
>/ /
>/ I dont really want to bump up to 2.6.31 seeing it just came out a few days ago./

Ok, this is the usual backport issues we have every time we need to backport patches upstream. This should be solved soon, but currently my priority is to merge the pending patches at the tree. Up to then, you may do a:
	make menuconfig

and select only the drivers you need, or just revert the latest changepatch to videobuf-dma-config.




Cheers,
Mauro

Re: Trying to compile for kernel version 2.6.28

[Mauro Carvalho Chehab]

Hi Jan,

Em Tue, 03 Nov 2009 16:45:15 +0100
Jan Hoogenraad <jan-conceptronic@hoogenraad.net> escreveu:

> At this moment, I cannot figure out how to compile v4l with kernel 
> version 2.6.28.
> I see, however, that the daily build reports:
> linux-2.6.28-i686: OK

Yes, and that's correct. It does compile from scratch with 2.6.28.

If you look at v4l/versions.txt, this is already marked to compile only with
kernels 2.6.31 or newer. It should be noticed, however, that the building system
won't touch at your .config if you just do an hg update (or hg pull -u).

You'll need to ask it explicitly to process versions.txt again, by calling one of
the alternatives bellow that re-generates a v4l/.config.

If you are using a customized config, you'll need to call either one of those:
	make menuconfig
	make config
	make xconfig
	  or
	make gconfig

(in this specific case, just entering there and saving the config is enough - there's
no need to touch on any items)

Or, at the simple case were you're just building everything, you'll need to do:
	make allmodconfig

A side effect of touching at v4l/.config is that all (selected) drivers will
recompile again.

Cheers,
Mauro

Re: Trying to compile for kernel version 2.6.28

[Jan Hoogenraad]

Thanks a lot.
Only syncing my sources every 2 months, I forgot about the
	make allmodconfig

I keep
  http://linuxtv.org/hg/~jhoogenraad/rtl2831-r2.
in sync until Antti's sources have been tested, and IR support is put 
in, so that these sticks can be supported from the normal kernel.

Mauro Carvalho Chehab wrote:
> Hi Jan,
> 
> Em Tue, 03 Nov 2009 16:45:15 +0100
> Jan Hoogenraad <jan-conceptronic@hoogenraad.net> escreveu:
> 
>> At this moment, I cannot figure out how to compile v4l with kernel 
>> version 2.6.28.
>> I see, however, that the daily build reports:
>> linux-2.6.28-i686: OK
> 
> Yes, and that's correct. It does compile from scratch with 2.6.28.
> 
> If you look at v4l/versions.txt, this is already marked to compile only with
> kernels 2.6.31 or newer. It should be noticed, however, that the building system
> won't touch at your .config if you just do an hg update (or hg pull -u).
> 
> You'll need to ask it explicitly to process versions.txt again, by calling one of
> the alternatives bellow that re-generates a v4l/.config.
> 
> If you are using a customized config, you'll need to call either one of those:
> 	make menuconfig
> 	make config
> 	make xconfig
> 	  or
> 	make gconfig
> 
> (in this specific case, just entering there and saving the config is enough - there's
> no need to touch on any items)
> 
> Or, at the simple case were you're just building everything, you'll need to do:
> 	make allmodconfig
> 
> A side effect of touching at v4l/.config is that all (selected) drivers will
> recompile again.
> 
> Cheers,
> Mauro
> 


-- 
Jan Hoogenraad
Hoogenraad Interface Services
Postbus 2717
3500 GS Utrecht