From: Hans Verkuil <hverkuil@xs4all.nl>
To: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
Cc: Scott Jiang <scott.jiang.linux@gmail.com>,
adi-buildroot-devel@lists.sourceforge.net,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
LMML <linux-media@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 00/15] media: blackfin: bfin_capture enhancements
Date: Sat, 07 Mar 2015 17:35:54 +0100 [thread overview]
Message-ID: <54FB28EA.4040206@xs4all.nl> (raw)
In-Reply-To: <CA+V-a8vTBJuiHRPjEN7VHHmAZhAu=W=Zi5a_N9DiLiRZH-Ab0A@mail.gmail.com>
On 03/07/2015 05:22 PM, Lad, Prabhakar wrote:
> On Thu, Mar 5, 2015 at 10:26 AM, Hans Verkuil <hverkuil@xs4all.nl> wrote:
>> On 03/05/15 10:44, Scott Jiang wrote:
>>> Hi Hans,
> [snip]
>>>>>
>>>>> cd utils/v4l2-compliance
>>>>> cat *.cpp >x.cpp
>>>>> g++ -o v4l2-compliance x.cpp -I . -I ../../include/ -DNO_LIBV4L2
>>>>>
>>>>> I've never used uclibc, so I don't know what the limitations are.
>>>>>
>>>> Not sure what exactly fails, I haven’t tried compiling it, that was a
>>>> response from Scott for v2 series.
>>>>
>>>
>>> I found if I disabled libjpeg ./configure --without-jpeg, it can pass
>>> compilation.
>>
>> Great!
>>
>>> Would you like me to send the result now or after Lad's v4 patch?
>>
>> Send it now as v4 won't have any meaningful code changes.
>>
> But anyway I cant help here much if there are any compliance issues,
> as i don't have the hardware.
Often compliance issues are trivially fixed, even without hardware. But step
one is just to run the tool and see what it reports.
Regards,
Hans
prev parent reply other threads:[~2015-03-07 16:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-21 18:39 [PATCH v3 00/15] media: blackfin: bfin_capture enhancements Lad Prabhakar
2015-02-21 18:39 ` [PATCH v3 01/15] media: blackfin: bfin_capture: drop buf_init() callback Lad Prabhakar
2015-02-21 18:39 ` [PATCH v3 02/15] media: blackfin: bfin_capture: release buffers in case start_streaming() call back fails Lad Prabhakar
2015-02-21 18:39 ` [PATCH v3 03/15] media: blackfin: bfin_capture: set min_buffers_needed Lad Prabhakar
2015-02-21 18:39 ` [PATCH v3 04/15] media: blackfin: bfin_capture: improve buf_prepare() callback Lad Prabhakar
2015-03-03 15:21 ` Hans Verkuil
2015-02-21 18:39 ` [PATCH v3 05/15] media: blackfin: bfin_capture: improve queue_setup() callback Lad Prabhakar
2015-03-03 14:13 ` Mauro Carvalho Chehab
2015-02-21 18:39 ` [PATCH v3 06/15] media: blackfin: bfin_capture: use vb2_fop_mmap/poll Lad Prabhakar
2015-03-03 10:14 ` Hans Verkuil
2015-02-21 18:39 ` [PATCH v3 07/15] media: blackfin: bfin_capture: use v4l2_fh_open and vb2_fop_release Lad Prabhakar
2015-02-21 18:39 ` [PATCH v3 08/15] media: blackfin: bfin_capture: use vb2_ioctl_* helpers Lad Prabhakar
2015-02-21 18:39 ` [PATCH v3 09/15] media: blackfin: bfin_capture: make sure all buffers are returned on stop_streaming() callback Lad Prabhakar
2015-02-21 18:39 ` [PATCH v3 10/15] media: blackfin: bfin_capture: return -ENODATA for *std calls Lad Prabhakar
2015-02-21 18:39 ` [PATCH v3 11/15] media: blackfin: bfin_capture: return -ENODATA for *dv_timings calls Lad Prabhakar
2015-02-21 18:39 ` [PATCH v3 12/15] media: blackfin: bfin_capture: add support for vidioc_create_bufs Lad Prabhakar
2015-02-21 18:39 ` [PATCH v3 13/15] media: blackfin: bfin_capture: add support for VB2_DMABUF Lad Prabhakar
2015-02-21 18:40 ` [PATCH v3 14/15] media: blackfin: bfin_capture: add support for VIDIOC_EXPBUF Lad Prabhakar
2015-02-21 18:40 ` [PATCH v3 15/15] media: blackfin: bfin_capture: set v4l2 buffer sequence Lad Prabhakar
2015-03-02 7:57 ` [PATCH v3 00/15] media: blackfin: bfin_capture enhancements Scott Jiang
2015-03-03 8:49 ` Hans Verkuil
2015-03-03 9:30 ` Lad, Prabhakar
2015-03-03 9:39 ` Hans Verkuil
2015-03-03 9:43 ` Lad, Prabhakar
2015-03-05 9:44 ` Scott Jiang
2015-03-05 10:26 ` Hans Verkuil
2015-03-07 16:22 ` Lad, Prabhakar
2015-03-07 16:35 ` Hans Verkuil [this message]
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=54FB28EA.4040206@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=adi-buildroot-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=prabhakar.csengg@gmail.com \
--cc=scott.jiang.linux@gmail.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).