From: Hans de Goede <hdegoede@redhat.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>, linux-media@vger.kernel.org
Cc: j.anaszewski@samsung.com
Subject: Re: [v4l-utils RFC 0/2] libmediatext library
Date: Thu, 23 Oct 2014 10:19:45 +0200 [thread overview]
Message-ID: <5448BA21.2040001@redhat.com> (raw)
In-Reply-To: <54477D20.4030207@linux.intel.com>
Hi,
On 10/22/2014 11:47 AM, Sakari Ailus wrote:
> Hi Hans,
>
> Hans de Goede wrote:
>> Hi Sakari,
>>
>> On 10/21/2014 12:40 PM, Sakari Ailus wrote:
>>> Hi,
>>>
>>> This is a tiny library for parsing text-based media link, V4L2 sub-device
>>> format (and selection) configurations as well as controls with limited
>>> types.
>>
>> Hmm, we also have:
>>
>> [PATCH/RFC v2 1/4] Add a media device configuration file parser.
>>
>> How do these 2 relate ?
>
> Jacek is working on a Samsung Exynos libv4l2 plugin, a part of which is not specific to that plugin itself, and thus should be elsewhere (libmediactl, for instance). I didn't know about that effort, and having written something close to that in the past but without finishing it, I posted mine here as well.
>
> The common subset of functionality is limited to parsing text based link configurations. Most of that is really implemented in libmediactl.
Hmm, I guess we need to sort this out then before merging Jacek's plugin.
Jacek, have you looked into using (and if necessary extending) libmediactl
inside your plugin ?
Regards,
Hans
next prev parent reply other threads:[~2014-10-23 8:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 10:40 [v4l-utils RFC 0/2] libmediatext library Sakari Ailus
2014-10-21 10:40 ` [v4l-utils RFC 1/2] mediactl: Separate entity and pad parsing Sakari Ailus
2014-10-21 10:40 ` [v4l-utils RFC 2/2] mediatext: Add library Sakari Ailus
2014-10-21 13:21 ` [v4l-utils RFC 0/2] libmediatext library Hans de Goede
2014-10-22 9:47 ` Sakari Ailus
2014-10-23 8:19 ` Hans de Goede [this message]
2014-10-23 8:54 ` Jacek Anaszewski
2014-10-23 9:31 ` Hans de Goede
2014-10-23 9:40 ` Sakari Ailus
2014-10-23 10:01 ` Laurent Pinchart
2014-10-23 13:13 ` Hans de Goede
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=5448BA21.2040001@redhat.com \
--to=hdegoede@redhat.com \
--cc=j.anaszewski@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.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;
as well as URLs for NNTP newsgroup(s).