Compling drivers from v4l-dvb hg tree
Hi all,
What's the recommended way for compiling drivers from v4l-dvb hg tree?
Cheers,
Erik
Signature · 18 lines
======================= erik de castro lopo senior design engineer bCODE level 2, 2a glen street milsons point sydney nsw 2061 australia tel +61 (0)2 9954 4411 fax +61 (0)2 9954 4422 www.bcode.com -- video4linux-list mailing list Unsubscribe mailto:[email protected]?subject=unsubscribe https://www.redhat.com/mailman/listinfo/video4linux-list
Quoted 6 lines · Erik de Castro Lopo
Hi all,
What's the recommended way for compiling drivers from v4l-dvb hg tree?
Cheers,
Erik
Devin
Signature · 8 lines
Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller -- video4linux-list mailing list Unsubscribe mailto:[email protected]?subject=unsubscribe https://www.redhat.com/mailman/listinfo/video4linux-list
Quoted 7 lines · On Fri, 24 Apr 2009 09:25:00 -0400 Devin Heitmueller…
Quoted 3 lines · Erik de Castro Lopo
Hi all,
What's the recommended way for compiling drivers from v4l-dvb hg tree?
Ok, but how do I patch the v4l-dvb sources into a linux kernel tree?
Erik
Signature · 18 lines
======================= erik de castro lopo senior design engineer bCODE level 2, 2a glen street milsons point sydney nsw 2061 australia tel +61 (0)2 9954 4411 fax +61 (0)2 9954 4422 www.bcode.com -- video4linux-list mailing list Unsubscribe mailto:[email protected]?subject=unsubscribe https://www.redhat.com/mailman/listinfo/video4linux-list
Quoted 4 lines · Erik de Castro Lopo
Quoted 1 line · On Fri, 24 Apr 2009 09:25:00 -0400 Devin Heitmueller…
On Fri, Apr 24, 2009 at 3:03 AM, Erik de Castro Lopo <[email protected]> wrote:
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
Hi all,
What's the recommended way for compiling drivers from v4l-dvb hg tree?
Ok, but how do I patch the v4l-dvb sources into a linux kernel tree?
You don't.
The v4l-dvb sources are maintained out-of-tree, and override whatever is in the linux kernel tree. Periodically, the v4l-dvb maintainer syncs with the kernel tree and the changes are pushed upstream into the mainline kernel. This approach allows for the v4l-dvb project to be used with kernel releases other than the current bleeding edge kernel.
Devin
Signature · 8 lines
Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller -- video4linux-list mailing list Unsubscribe mailto:[email protected]?subject=unsubscribe https://www.redhat.com/mailman/listinfo/video4linux-list
Quoted 10 lines · On Fri, 24 Apr 2009 18:09:17 -0400 Devin Heitmueller…
Quoted 1 line
Ok, but how do I patch the v4l-dvb sources into a linux kernel tree?
You don't.
The v4l-dvb sources are maintained out-of-tree, and override whatever is in the linux kernel tree. Periodically, the v4l-dvb maintainer syncs with the kernel tree and the changes are pushed upstream into the mainline kernel. This approach allows for the v4l-dvb project to be used with kernel releases other than the current bleeding edge kernel.
Ok, but the instructions on http://linuxtv.org/repo compiles the driver for the current running kernel. How do I compile it for another kernel, ie an x86 embedded device that I normally do not compile on?
Erik
Signature · 18 lines
======================= erik de castro lopo senior design engineer bCODE level 2, 2a glen street milsons point sydney nsw 2061 australia tel +61 (0)2 9954 4411 fax +61 (0)2 9954 4422 www.bcode.com -- video4linux-list mailing list Unsubscribe mailto:[email protected]?subject=unsubscribe https://www.redhat.com/mailman/listinfo/video4linux-list
Quoted 4 lines · Erik de Castro Lopo
Ok, but the instructions on http://linuxtv.org/repo compiles the driver for the current running kernel. How do I compile it for another kernel, ie an x86 embedded device that I normally do not compile on?
Yeah, that's a bit harder. I did it a couple of months ago for ARM. I had to change the path to ensure the path to the cross-compiler's version of strip was ahead of the base operating system's version.
Check the linux-media archives for the subject "4vl + usb + arm" for the discussion in March.
Devin
Signature · 8 lines
Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller -- video4linux-list mailing list Unsubscribe mailto:[email protected]?subject=unsubscribe https://www.redhat.com/mailman/listinfo/video4linux-list
Quoted 3 lines · On Fri, 24 Apr 2009 18:22:40 -0400 Devin Heitmueller…
Yeah, that's a bit harder. I did it a couple of months ago for ARM. I had to change the path to ensure the path to the cross-compiler's version of strip was ahead of the base operating system's version.
Well both my compile machine and my target are running x86 Ubuntu. The only really relevant difference is that they have different kernels, 2.6.26 on the compile machine and 2.6.29 on the target.
I've looked at the top level Makefile but there doesn't seem to be a way os specifying compiling against another kernel.
Erik
Signature · 18 lines
======================= erik de castro lopo senior design engineer bCODE level 2, 2a glen street milsons point sydney nsw 2061 australia tel +61 (0)2 9954 4411 fax +61 (0)2 9954 4422 www.bcode.com -- video4linux-list mailing list Unsubscribe mailto:[email protected]?subject=unsubscribe https://www.redhat.com/mailman/listinfo/video4linux-list
Quoted 7 lines · Erik de Castro Lopo
Quoted 3 lines · On Fri, 24 Apr 2009 18:22:40 -0400 Devin Heitmueller…
Yeah, that's a bit harder. I did it a couple of months ago for ARM. I had to change the path to ensure the path to the cross-compiler's version of strip was ahead of the base operating system's version.
Quoted 6 lines
Well both my compile machine and my target are running x86 Ubuntu. The only really relevant difference is that they have different kernels, 2.6.26 on the compile machine and 2.6.29 on the target.
I've looked at the top level
Makefilebut there doesn't seem to be a way os specifying compiling against another kernel.
It's the same basic issue. To use a different kernel tree for the headers, add "SRCDIR=" as an argument to make.
Devin
Signature · 8 lines
Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller -- video4linux-list mailing list Unsubscribe mailto:[email protected]?subject=unsubscribe https://www.redhat.com/mailman/listinfo/video4linux-list
Quoted 2 lines · On Fri, 24 Apr 2009 18:33:57 -0400 Devin Heitmueller…
It's the same basic issue. To use a different kernel tree for the headers, add "SRCDIR=" as an argument to make.
Cool, thanks for your help Devin.
Cheers,
Erik
Signature · 18 lines
======================= erik de castro lopo senior design engineer bCODE level 2, 2a glen street milsons point sydney nsw 2061 australia tel +61 (0)2 9954 4411 fax +61 (0)2 9954 4422 www.bcode.com -- video4linux-list mailing list Unsubscribe mailto:[email protected]?subject=unsubscribe https://www.redhat.com/mailman/listinfo/video4linux-list
Quoted 6 lines · Erik de Castro Lopo
Quoted 3 lines · On Fri, 24 Apr 2009 18:09:17 -0400 Devin Heitmueller…
Quoted 1 line
Ok, but how do I patch the v4l-dvb sources into a linux kernel tree?
You don't.
You can, make kernel-links
Quoted 11 lines
Quoted 6 lines
The v4l-dvb sources are maintained out-of-tree, and override whatever is in the linux kernel tree. Periodically, the v4l-dvb maintainer syncs with the kernel tree and the changes are pushed upstream into the mainline kernel. This approach allows for the v4l-dvb project to be used with kernel releases other than the current bleeding edge kernel.
Ok, but the instructions on http://linuxtv.org/repo compiles the driver for the current running kernel. How do I compile it for another kernel, ie an x86 embedded device that I normally do not compile on?
See "make help", it explains this. Use "make release DIR=/other/kernel/src/dir" to compile for any kernel you want. I haven't tried cross-compiling v4l-dvb so I'm not sure how that will work. I'd just try the standard ARCH and CROSS_COMPILE settings like a kernel build uses and see what happens.