All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Jourdan <maxi.jourdan@wanadoo.fr>
To: Jerome Brunet <jbrunet@baylibre.com>,
	Neil <narmstrong@baylibre.com>, Hans Verkuil <hverkuil@xs4all.nl>
Cc: Maxime Jourdan <maxi.jourdan@wanadoo.fr>,
	linux-media@vger.kernel.org,
	linux-amlogic <linux-amlogic@lists.infradead.org>
Subject: Re: [RFC 0/4] media: meson: add video decoder driver
Date: Thu, 2 Aug 2018 14:56:22 +0200	[thread overview]
Message-ID: <CAHStOZ4pt4ECYcLkv8mXZkB5JvUm0NVp9sD6mfQofDLgpUHMiA@mail.gmail.com> (raw)
In-Reply-To: <80eb63eee4ad1927a617ce526e7aba2342ac66f8.camel@baylibre.com>

Hi Jerome, Neil, Hans,

Thanks a lot for all the insights.

2018-08-02 8:59 GMT+02:00 Hans Verkuil <hverkuil@xs4all.nl>:
>>       fail: ../../../v4l-utils-1.12.3/utils/v4l2-compliance/v4l2-test-buffers.cpp(571): q.has_expbuf(node)
>>       test VIDIOC_EXPBUF: FAIL
>
> Not sure, might well be a knock-on result of the 'one open' problem.
>
> BTW, always get the latest code from the v4l-utils git repo, don't use a released
> version for v4l2-compliance: it's always evolving and you don't want to use an
> old version. Also for the next version of this patch series add the output of
> v4l2-compliance to this cover letter, I want to see it.

Will do.

> Finally, are you aware of the work Tomasz Figa on specifying the codec behavior?
>
> https://lkml.org/lkml/2018/7/24/539
>
> The final version will be close to what was posted there.

I wasn't, thanks for pointing it out.

WARNING: multiple messages have this Message-ID (diff)
From: maxi.jourdan@wanadoo.fr (Maxime Jourdan)
To: linus-amlogic@lists.infradead.org
Subject: [RFC 0/4] media: meson: add video decoder driver
Date: Thu, 2 Aug 2018 14:56:22 +0200	[thread overview]
Message-ID: <CAHStOZ4pt4ECYcLkv8mXZkB5JvUm0NVp9sD6mfQofDLgpUHMiA@mail.gmail.com> (raw)
In-Reply-To: <80eb63eee4ad1927a617ce526e7aba2342ac66f8.camel@baylibre.com>

Hi Jerome, Neil, Hans,

Thanks a lot for all the insights.

2018-08-02 8:59 GMT+02:00 Hans Verkuil <hverkuil@xs4all.nl>:
>>       fail: ../../../v4l-utils-1.12.3/utils/v4l2-compliance/v4l2-test-buffers.cpp(571): q.has_expbuf(node)
>>       test VIDIOC_EXPBUF: FAIL
>
> Not sure, might well be a knock-on result of the 'one open' problem.
>
> BTW, always get the latest code from the v4l-utils git repo, don't use a released
> version for v4l2-compliance: it's always evolving and you don't want to use an
> old version. Also for the next version of this patch series add the output of
> v4l2-compliance to this cover letter, I want to see it.

Will do.

> Finally, are you aware of the work Tomasz Figa on specifying the codec behavior?
>
> https://lkml.org/lkml/2018/7/24/539
>
> The final version will be close to what was posted there.

I wasn't, thanks for pointing it out.

  reply	other threads:[~2018-08-02 14:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-01 19:33 [RFC 0/4] media: meson: add video decoder driver Maxime Jourdan
2018-08-01 19:33 ` Maxime Jourdan
2018-08-01 19:33 ` [RFC 1/4] media: meson: add v4l2 m2m " Maxime Jourdan
2018-08-01 19:33   ` Maxime Jourdan
2018-08-02 10:30   ` Jerome Brunet
2018-08-02 10:30     ` Jerome Brunet
2018-08-02 16:54     ` Maxime Jourdan
2018-08-02 16:54       ` Maxime Jourdan
2018-08-01 19:33 ` [RFC 2/4] ARM64: dts: meson-gx: add vdec entry Maxime Jourdan
2018-08-01 19:33   ` Maxime Jourdan
2018-08-01 19:33 ` [RFC 3/4] ARM64: dts: meson: add vdec entries Maxime Jourdan
2018-08-01 19:33   ` Maxime Jourdan
2018-08-01 19:33 ` [RFC 4/4] dt-bindings: media: add Amlogic Meson Video Decoder Bindings Maxime Jourdan
2018-08-01 19:33   ` Maxime Jourdan
2018-08-01 20:13   ` Martin Blumenstingl
2018-08-01 20:13     ` Martin Blumenstingl
2018-08-02 10:33   ` Jerome Brunet
2018-08-02 10:33     ` Jerome Brunet
2018-08-02 12:48     ` Maxime Jourdan
2018-08-02 12:48       ` Maxime Jourdan
2018-08-02  6:59 ` [RFC 0/4] media: meson: add video decoder driver Hans Verkuil
2018-08-02  6:59   ` Hans Verkuil
2018-08-02  8:54 ` Neil Armstrong
2018-08-02  8:54   ` Neil Armstrong
2018-08-02  9:14 ` Jerome Brunet
2018-08-02  9:14   ` Jerome Brunet
2018-08-02 12:56   ` Maxime Jourdan [this message]
2018-08-02 12:56     ` Maxime Jourdan

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=CAHStOZ4pt4ECYcLkv8mXZkB5JvUm0NVp9sD6mfQofDLgpUHMiA@mail.gmail.com \
    --to=maxi.jourdan@wanadoo.fr \
    --cc=hverkuil@xs4all.nl \
    --cc=jbrunet@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-media@vger.kernel.org \
    --cc=narmstrong@baylibre.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.