public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Brandon Philips <brandon@ifup.org>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Douglas Landgraf <dougsland@gmail.com>
Subject: Re: [ANNOUNCE] git tree repositories & libv4l
Date: Wed, 24 Feb 2010 10:42:13 -0300	[thread overview]
Message-ID: <4B852CB5.5040909@infradead.org> (raw)
In-Reply-To: <4B8521CF.7090500@redhat.com>

Hans de Goede wrote:
> Hi,
> 
> On 02/24/2010 01:58 AM, Mauro Carvalho Chehab wrote:
>> Hans de Goede wrote:
>>> Hi,
>>>
>>> On 02/23/2010 04:37 PM, Mauro Carvalho Chehab wrote:
>>>> Hans de Goede wrote:
>>>>
>>>>> Ok, so this will give me a local tree, how do I get this onto
>>>>> linuxtv.org ?
>>>>
>>>> I added it. In thesis, it is open for commit to you, me, hverkuil and
>>>> dougsland.
>>>>
>>>
>>> I see good, thanks! Can someone (Douglas ?) with better hg / git powers
>>> then me please
>>> somehow import all the libv4l changes from:
>>> http://linuxtv.org/hg/~hgoede/libv4l
>>
>> Ok, I added there. The procedure were simple: I ran Brandon script again,
>> but after pulling from your tree. Then, I used git format-patch to
>> generate
>> a quilt series, and used git quiltimport on the correct -git tree.
>>
> 
> Thanks!
> 
> 
>>> Once that is done I'll retire my own tree, and move all my userspace
>>> work to
>>> the git tree.
>>>
>>> For starters I plan to create / modify Makefiles so that everything will
>>> build
>>> out of the box, and has proper make install targets which can be used by
>>> distro's
>>>
>>> So:
>>> -proper honoring of CFLAGS
>>> -work with standard (and possibly somewhat older kernel headers)
>>> -honor DESTDIR, PREFIX and LIBDIR when doing make install
>>
>> The better here is to have the latest kernel headers copied on the tree.
>> This way, it is possible to compile libv4l2 with an older kernel
>> version and
>> later upgrade the kernel, if needed, or to use a fast machine to compile
>> it, and then use it on another machine.
>>
> 
> If possible I would like to avoid this, afaik no other userspace utility
> packages
> are doing this.
> 
> Where necessary libv4l currently has code snippets like:
> 
> #ifndef V4L2_PIX_FMT_SPCA501
> #define V4L2_PIX_FMT_SPCA501 v4l2_fourcc('S','5','0','1') /* YUYV per
> line */
> #endif
> 
> So libv4l (in its current state) will already compile fine with older
> kernel
> headers. I expect that the other utilities will not need a lot of
> recent kernel ABI. So for now I would like to try and extend the above
> approach
> to the other utilities.

I think build will fail. I remember I had some such troubles when compiling
it against RHEL5, before we did the merge with the in-tree videodev2.h.

It should be reminded that, when people upgrade their kernels by hand,
they generally don't run "make headers_install". So, the kernel headers
on /usr/include/linux are the ones found on the original distro kernel,
and not the ones that are needed by the user.

> The reason for this is that I want to avoid carrying a copy of a dir
> from some
> other tree, with all getting stale and needing sync all the time issues
> that
> come with that,

The sync problem will keep existing, since some of the tools from
this tree are used as examples on media-specs.

> not to mention chicken and egg problems in the case of
> new formats which simultaneously  need to be added to both libv4l and
> the kernel.
> 
> For example often I add support for V4L2_PIX_FMT_NEW_FOO to libv4l,
> before it
> hits any official v4l-dvb kernel tree, with the:
> #ifndef V4L2_PIX_FMT_SPCA501
> #define V4L2_PIX_FMT_SPCA501 v4l2_fourcc('S','5','0','1') /* YUYV per
> line */
> #endif
> 
> Approach this works fine, if I were to carry an include tree copy, that
> would
> now need to become a patched include tree copy, and with the next sync I
> then
> need to ensure that any needed patches are either already in the sync
> source,
> or applied again.

True, but the additional work for those occasional changes are minimum, and
may save some time when handling complains about why the tree don't build
on his machine.

-- 

Cheers,
Mauro

  parent reply	other threads:[~2010-02-24 13:42 UTC|newest]

Thread overview: 91+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-19  5:34 [ANNOUNCE] git tree repositories Mauro Carvalho Chehab
2010-01-19  7:53 ` Hans Verkuil
2010-01-19  8:10   ` Patrick Boettcher
2010-01-19 11:20     ` Johannes Stezenbach
2010-01-19 11:49       ` Patrick Boettcher
2010-01-19 12:44       ` Mauro Carvalho Chehab
2010-01-20  8:04         ` Markus Heidelberg
2010-01-20 15:11           ` Mauro Carvalho Chehab
2010-01-19 11:55     ` Mauro Carvalho Chehab
2010-01-19 23:38     ` Andy Walls
2010-01-20  1:10       ` hermann pitton
2010-01-20  3:29         ` Andy Walls
2010-01-20  3:29       ` Mauro Carvalho Chehab
2010-01-20  4:08         ` Andy Walls
2010-01-20 15:05           ` Mauro Carvalho Chehab
2010-01-20 11:43         ` BOUWSMA Barry
2010-01-20 10:19       ` BOUWSMA Barry
2010-01-19 11:08   ` Mauro Carvalho Chehab
2010-01-20  8:36     ` [ANNOUNCE] git tree repositories & libv4l Hans de Goede
2010-01-20  8:55       ` Hans Verkuil
2010-01-20 15:41         ` Mauro Carvalho Chehab
2010-01-20 18:50           ` Hans de Goede
2010-01-20 21:07             ` Brandon Philips
2010-01-21  2:07               ` Mauro Carvalho Chehab
2010-01-21  2:46                 ` Brandon Philips
2010-01-21  7:34                   ` Hans Verkuil
2010-01-21 20:15                     ` Mauro Carvalho Chehab
2010-01-23 17:24                     ` Hans de Goede
2010-02-22 22:54                       ` Brandon Philips
2010-02-22 23:26                         ` Hans Verkuil
2010-02-22 23:38                           ` Brandon Philips
2010-02-23  0:41                             ` Mauro Carvalho Chehab
2010-02-23  1:12                               ` Mauro Carvalho Chehab
2010-02-23  8:04                                 ` Brandon Philips
2010-02-23 13:37                                   ` Mauro Carvalho Chehab
2010-02-23  9:45                               ` Manu Abraham
2010-02-23 11:20                                 ` Mauro Carvalho Chehab
2010-02-24  2:32                                 ` hermann pitton
2010-02-23 11:20                           ` Manu Abraham
2010-02-23  8:49                         ` Hans de Goede
2010-02-23  9:01                           ` Hans Verkuil
2010-02-23  9:23                             ` Hans de Goede
2010-02-23  9:38                               ` Manu Abraham
2010-02-23 12:21                                 ` Mauro Carvalho Chehab
2010-02-23 13:07                                   ` Manu Abraham
2010-02-23 13:36                                     ` Mauro Carvalho Chehab
2010-02-23 14:09                                       ` Manu Abraham
2010-02-23 12:10                               ` Mauro Carvalho Chehab
2010-02-23 11:49                           ` Mauro Carvalho Chehab
2010-02-23 15:37                           ` Mauro Carvalho Chehab
2010-02-23 15:51                             ` Hans de Goede
2010-02-24  0:58                               ` Mauro Carvalho Chehab
2010-02-24 12:55                                 ` Hans de Goede
2010-02-24 13:40                                   ` Hans Verkuil
2010-02-24 13:42                                   ` Mauro Carvalho Chehab [this message]
2010-02-24 14:32                                   ` Brandon Philips
2010-02-25 10:52                                     ` Hans de Goede
2010-02-24  6:05                               ` Brandon Philips
2010-02-24 12:44                                 ` Hans de Goede
2010-02-24 13:26                                   ` Mauro Carvalho Chehab
2010-02-24 14:29                                     ` Patrick Boettcher
2010-02-25  4:55                               ` Douglas Schilling Landgraf
2010-01-21  7:23                 ` Hans Verkuil
2010-01-21 20:04                   ` Mauro Carvalho Chehab
2010-01-23 17:28                   ` Hans de Goede
2010-01-24  0:42                     ` Mauro Carvalho Chehab
2010-01-25 16:03                       ` Hans de Goede
2010-01-20  9:43       ` Laurent Pinchart
2010-01-20  9:54       ` Paulo Assis
2010-01-20 10:43         ` libwecam & uvcdynctrl (was Re: [ANNOUNCE] git tree repositories & libv4l) Hans de Goede
2010-01-19 15:54   ` [ANNOUNCE] git tree repositories Douglas Schilling Landgraf
2010-01-19  8:04 ` Laurent Pinchart
2010-01-19 11:12   ` Mauro Carvalho Chehab
2010-01-19 11:50     ` Laurent Pinchart
2010-01-19 12:36       ` Mauro Carvalho Chehab
2010-01-19 10:04 ` Devin Heitmueller
2010-01-19 11:52   ` Patrick Boettcher
2010-01-19 12:39     ` Mauro Carvalho Chehab
2010-01-19 12:16   ` Mauro Carvalho Chehab
2010-01-19 21:21     ` Bob Cunningham
2010-01-19 22:37       ` hermann pitton
2010-01-20 13:54   ` Laurent Pinchart
2010-01-20 15:00     ` Mauro Carvalho Chehab
2010-01-19 12:56 ` Laurent Pinchart
2010-01-19 13:07   ` Mauro Carvalho Chehab
2010-01-19 13:12     ` Laurent Pinchart
2010-01-19 21:59 ` Johannes Stezenbach
2010-01-21  2:19   ` Mauro Carvalho Chehab
2010-01-21  2:53     ` Trent Piepho
2010-01-21  3:09       ` Mauro Carvalho Chehab
2010-01-20 19:09 ` Guennadi Liakhovetski

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=4B852CB5.5040909@infradead.org \
    --to=mchehab@infradead.org \
    --cc=brandon@ifup.org \
    --cc=dougsland@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.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