public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@linuxtv.org>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Theodore Kilgore <kilgota@banach.math.auburn.edu>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	Devin Heitmueller <dheitmueller@kernellabs.com>,
	linux-media@vger.kernel.org
Subject: Re: Debug code in HG repositories
Date: Mon, 10 Jan 2011 14:05:19 +0100	[thread overview]
Message-ID: <20110110130519.GA4996@linuxtv.org> (raw)
In-Reply-To: <4D2AF1A0.3090809@redhat.com>

On Mon, Jan 10, 2011 at 09:46:40AM -0200, Mauro Carvalho Chehab wrote:
> Em 07-01-2011 21:42, Theodore Kilgore escreveu:
>  
> >> Have you tried Mauro's media_build tree? I had to use it today to test a
> >> driver from git on a 2.6.35 kernel. Works quite nicely. Perhaps we 
> > should
> >> promote this more. 
> > 
> > Probably a good idea. I have been too busy to know about it, myself. And I 
> > even do try to keep up with what is going on.
> > 
> >> I could add backwards compatibility builds to my 
> > daily
> >> build script that uses this in order to check for which kernel versions
> >> this compiles if there is sufficient interest.
...
> I think Hans can enable it. The backport effort on media-build is a way
> easier than with -hg. For example, in order to support kernel 2.6.31 (the oldest
> one on that tree), we need only 10 patches. The patches themself are simple:
> 
> $ wc -l *.patch
>    61 v2.6.31_nodename.patch
>   540 v2.6.32_kfifo.patch
>    42 v2.6.33_input_handlers_are_int.patch
>    70 v2.6.33_pvrusb2_sysfs.patch
>    40 v2.6.34_dvb_net.patch
>    22 v2.6.34_fix_define_warnings.patch
>    16 v2.6.35_firedtv_handle_fcp.patch
>   104 v2.6.35_i2c_new_probed_device.patch
>   145 v2.6.35_work_handler.patch
>   104 v2.6.36_input_getkeycode.patch
>  1144 total
> 
> And almost all patches are trivial.

FWIW, linux-wireless developers maintain a generic compat tree used
for backporting wireless drivers:
http://git.kernel.org/?p=linux/kernel/git/mcgrof/compat.git;a=summary

I suppose it might be useful to share this between linux-wireless
and linux-media?


(It is used together with three other trees to autobuild
the compat-wireless releases.
http://wireless.kernel.org/en/users/Download

It works like that:
- compat.git: generic backporting layer
- compat-wireless-2.6.git: build system
- compat-user.git: autobuild scripts called via cron
- wireless-testing.git: linux-wireless development tree

(wireless-testing.git is based on latest stable kernel but with
the wireless code from linux-next)

compat-wireless releases are not meant for development, but
they can be used as a build system together with a wireless-testing.git
tree and a few symlinks.)


Johannes

  reply	other threads:[~2011-01-10 13:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07 19:53 Debug code in HG repositories Oliver Endriss
2011-01-07 20:13 ` Devin Heitmueller
2011-01-07 21:06   ` Hans Verkuil
2011-01-07 23:42     ` Theodore Kilgore
2011-01-10 11:46       ` Mauro Carvalho Chehab
2011-01-10 13:05         ` Johannes Stezenbach [this message]
2011-01-10 22:00         ` Theodore Kilgore
2011-01-07 23:56     ` Oliver Endriss
2011-01-10 12:04       ` Mauro Carvalho Chehab
2011-01-10 12:27         ` Mauro Carvalho Chehab
2011-01-11  1:20           ` Oliver Endriss
2011-01-11  1:10         ` Oliver Endriss
2011-04-03 13:40           ` Mauro Carvalho Chehab
2011-01-08  1:02     ` Vincent McIntyre
2011-01-10 12:33       ` Mauro Carvalho Chehab
2011-01-11 10:37         ` Vincent McIntyre
2011-01-11 16:21           ` Mauro Carvalho Chehab
2011-01-11 10:47         ` Vincent McIntyre
2011-01-11 16:26           ` Mauro Carvalho Chehab
2011-01-08  4:08     ` VDR User
2011-01-10 11:27     ` Mauro Carvalho Chehab
2011-01-08  6:06   ` Jarod Wilson

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=20110110130519.GA4996@linuxtv.org \
    --to=js@linuxtv.org \
    --cc=dheitmueller@kernellabs.com \
    --cc=hverkuil@xs4all.nl \
    --cc=kilgota@banach.math.auburn.edu \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    /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