public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: "Aguirre, Sergio" <saaguirre@ti.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Doing a stable v4l-utils release
Date: Tue, 27 Apr 2010 21:55:05 -0300	[thread overview]
Message-ID: <4BD78769.8070002@redhat.com> (raw)
In-Reply-To: <A24693684029E5489D1D202277BE894454F78141@dlee02.ent.ti.com>

Hi Sergio,

Aguirre, Sergio wrote:
> Hi,
> 
>> -----Original Message-----
>> From: linux-media-owner@vger.kernel.org [mailto:linux-media-
>> owner@vger.kernel.org] On Behalf Of Hans de Goede
>> Sent: Tuesday, April 27, 2010 3:08 AM
>> To: Hans Verkuil
>> Cc: Linux Media Mailing List
>> Subject: Re: Doing a stable v4l-utils release
>>
>> Hi,
>>
>> On 04/26/2010 09:55 AM, Hans Verkuil wrote:
>>> On Monday 26 April 2010 09:35:23 Hans de Goede wrote:
>>>> Hi all,
>>>>
>>>> Currently v4l-utils is at version 0.7.91, which as the version
>>>> suggests is meant as a beta release.
>>>>
>>>> As this release seems to be working well I would like to do
>>>> a v4l-utils-0.8.0 release soon. This is a headsup, to give
>>>> people a chance to notify me of any bugs they would like to
>>>> see fixed first / any patches they would like to add first.
>>> This is a good opportunity to mention that I would like to run
>> checkpatch
>>> over the libs and clean them up.
>>>
>>> I also know that there is a bug in the control handling code w.r.t.
>>> V4L2_CTRL_FLAG_NEXT_CTRL. I have a patch, but I'd like to do the clean
>> up
>>> first.
>>>
>>> If no one else has major patch series that they need to apply, then I
>> can
>>> start working on this. The clean up is just purely whitespace changes to
>>> improve readability, no functionality will be touched.
>>>
>> I've no big changes planned on the short term, so from my pov go ahead.
> 
> I have one question regarding this utils:
> 
> Is it meant to be platform agnostic v4l2 utilities?
> 
> I tried once to compile it for a ARM based CPU (OMAP3 to be specific) from my x86 using a Codesourcery cross compilation toolchain, but it required some changes, which I haven't done still...
> 
> Anyways, before proposing patches for this, I just wanted to know how much priority you're giving to multi-platform support.

The major usage of v4l-utils is on x86 and x86_64 archs. I don't see why not adding
there a logic that will also work with ARM and other architectures, providing, of
course, that they won't break compilation on x86/x86_64 ;) Eventually, maybe the qt
tools (currently, qv4l2) may need a specific versions for those architectures, as they
may need different graphics layouts, in order to better work on cellular phones and 
other devices that have smaller screens.


Cheers,
Mauro

  reply	other threads:[~2010-04-28  6:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26  7:35 Doing a stable v4l-utils release Hans de Goede
2010-04-26  7:55 ` Hans Verkuil
2010-04-27  8:08   ` Hans de Goede
2010-04-27 21:47     ` Aguirre, Sergio
2010-04-28  0:55       ` Mauro Carvalho Chehab [this message]
2010-04-28  6:22     ` Hans Verkuil
2010-04-30  6:43       ` Hans Verkuil
2010-05-01 13:12         ` Hans Verkuil

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=4BD78769.8070002@redhat.com \
    --to=mchehab@redhat.com \
    --cc=hdegoede@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=saaguirre@ti.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