All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Antonio Ospite <ao2@ao2.it>
Cc: Hans de Goede <hdegoede@redhat.com>,
	linux-media@vger.kernel.org, kyungmin.park@samsung.com,
	s.nawrocki@samsung.com,
	Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [PATCH/RFC 1/1] Add a libv4l plugin for Exynos4 camera
Date: Thu, 09 Oct 2014 09:51:38 +0200	[thread overview]
Message-ID: <54363E8A.2020201@samsung.com> (raw)
In-Reply-To: <20141008174957.8451ebb426619d88d7a30cfd@ao2.it>

On 10/08/2014 05:49 PM, Antonio Ospite wrote:
> On Wed, 08 Oct 2014 15:22:43 +0200
> Jacek Anaszewski <j.anaszewski@samsung.com> wrote:
>
>> Hi Hans,
>>
>> On 10/08/2014 02:42 PM, Hans de Goede wrote:
>>> Hi,
>>>
>>> On 10/08/2014 10:46 AM, Jacek Anaszewski wrote:
>>>> The plugin provides support for the media device on Exynos4 SoC.
>>>> Added is also a media device configuration file parser.
>>>> The media configuration file is used for conveying information
>>>> about media device links that need to be established as well
>>>> as V4L2 user control ioctls redirection to a particular
>>>> sub-device.
>>>>
>>>> The plugin performs single plane <-> multi plane API conversion,
>>>> video pipeline linking and takes care of automatic data format
>>>> negotiation for the whole pipeline, after intercepting
>>>> VIDIOC_S_FMT or VIDIOC_TRY_FMT ioctls.
>>>>
>>>> Signed-off-by: Jacek Anaszewski <j.anaszewski@samsung.com>
>>>> Acked-by: Kyungmin Park <kyungmin.park@samsung.com>
>>>> Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
>>>> Cc: Hans Verkuil <hans.verkuil@cisco.com>
>>>> ---
>>>>    configure.ac                                       |    1 +
>>>>    lib/Makefile.am                                    |    5 +-
>>>>    lib/libv4l-exynos4-camera/Makefile.am              |    7 +
>>>>    .../libv4l-devconfig-parser.h                      |  145 ++
>>>>    lib/libv4l-exynos4-camera/libv4l-exynos4-camera.c  | 2486 ++++++++++++++++++++
>>>>    5 files changed, 2642 insertions(+), 2 deletions(-)
>>>>    create mode 100644 lib/libv4l-exynos4-camera/Makefile.am
>>>>    create mode 100644 lib/libv4l-exynos4-camera/libv4l-devconfig-parser.h
>>>>    create mode 100644 lib/libv4l-exynos4-camera/libv4l-exynos4-camera.c
>>>
>>> Ugh, that is a big plugin. Can you please split out the parser stuff
>>> into a separate file ?
>>
>> Yes, I tried to split it, but spent so much time fighting with
>> autotools, that I decided to submit it in this form and ask
>> more experienced v4l-utils build system maintainers for the advice.
>> I mentioned this in the cover letter.
>>
>
> What autotools issue in particular?
> The following change followed by "automake && ./configure" should be
> enough to add a new file libv4l-devconfig-parser.c:

The same modifications produced libv4l-exynos4-camera.so without parser 
symbols, when I applied them previously, but when I tried them again
everything is ok. Probably I wasn't doing proper cleanup.
Thanks for the hints.

Best Regards,
Jacek Anaszewski

  reply	other threads:[~2014-10-09  7:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-08  8:46 [PATCH/RFC 0/1] Libv4l: Add a plugin for the Exynos4 camera Jacek Anaszewski
2014-10-08  8:46 ` [PATCH/RFC 1/1] Add a libv4l plugin for " Jacek Anaszewski
2014-10-08 12:42   ` Hans de Goede
2014-10-08 13:22     ` Jacek Anaszewski
2014-10-08 15:49       ` Antonio Ospite
2014-10-09  7:51         ` Jacek Anaszewski [this message]
2014-10-09  8:20       ` Hans de Goede
2014-10-10  8:07         ` Jacek Anaszewski
2014-10-10  8:54   ` Hans Verkuil
2014-10-10 15:10     ` Jacek Anaszewski
2014-10-09 17:46 ` [PATCH/RFC 0/1] Libv4l: Add a plugin for the " Gregor Jasny
2014-10-10  8:14   ` Jacek Anaszewski

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=54363E8A.2020201@samsung.com \
    --to=j.anaszewski@samsung.com \
    --cc=ao2@ao2.it \
    --cc=hans.verkuil@cisco.com \
    --cc=hdegoede@redhat.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@osg.samsung.com \
    --cc=s.nawrocki@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.