From: Jan Hoogenraad <jan-conceptronic@hoogenraad.net>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: linux-media@vger.kernel.org
Subject: Re: Trying to compile for kernel version 2.6.28
Date: Wed, 04 Nov 2009 14:30:35 +0100 [thread overview]
Message-ID: <4AF181FB.7010003@hoogenraad.net> (raw)
In-Reply-To: <20091104052129.2e2dad47@pedra.chehab.org>
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
prev parent reply other threads:[~2009-11-04 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 15:45 Trying to compile for kernel version 2.6.28 Jan Hoogenraad
2009-11-04 7:21 ` Mauro Carvalho Chehab
2009-11-04 13:30 ` Jan Hoogenraad [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AF181FB.7010003@hoogenraad.net \
--to=jan-conceptronic@hoogenraad.net \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox