While working on the m2m-deinterlace driver I needed to test it,
and the easiest way to do that was with a Pandaboard. While
doing that I found a bug in the omap-dma driver:
https://patchwork.linuxtv.org/patch/57778/
That bug affected omap_vout as well, so the next step was to
test that driver. A
Convert omap_vout to the vb2 framework. After this change
'v4l2-compliance -s' passes all tests.
As usual, this vb2 conversion is a 'big bang' patch and hard to read.
Tested on a Pandaboard and a Beagle XM board.
Signed-off-by: Hans Verkuil
---
drivers/media/platform/omap/Kconfig |
This patch fixes the following v4l2-compliance failures:
- FIELD_ANY could be returned, which is not allowed.
- JPEG colorspace was set instead of SRGB.
- No control events.
- Empty bus_info in QUERYCAP.
- Overlay format handling wasn't zeroing bitmap/clips and
didn't return the chromakey correc
The dma_mask and coherent_dma_mask values were never set.
This prevented the media omap_vout driver from loading successfully.
Tested on a Pandaboard and Beagle XM board.
Signed-off-by: Hans Verkuil
---
arch/arm/mach-omap2/devices.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/ar
The OMAP 4 TRM specifies that when using double-index addressing
the address increases by the ES plus the EI value minus 1 within
a frame. When a full frame is transferred, the address increases
by the ES plus the frame index (FI) value minus 1.
The omap-dma code didn't account for the 'minus 1' i
This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date: Tue Jul 30 05:00:11 CEST 2019
media-tree git hash:a8f910ec66583bfb61558c3f333195b3960d832d
media_build gi
Good morning k
http://coea.org.kh/production.php?kkis=QPSGAC20301
Raymond
Hi Simon,
Thanks for your work.
On 2019-07-29 09:47:57 +0200, Simon Horman wrote:
> Renesas media binding documentation files uses a naming schema of
> 'renesas,.txt'. Rename IMR file to match this pattern.
>
> Cc: Niklas Söderlund
> Signed-off-by: Simon Horman
Reviewed-by: Niklas Söderlund
Hi,
On 2019-07-29 09:43:55 +0200, Simon Horman wrote:
> On Fri, Jul 12, 2019 at 04:17:03PM +0900, Niklas Söderlund wrote:
> > Hi,
> >
> > A gentle ping on this patch. I assume if it could get a ack from Rob it
> > could be taken in thru the media-tree?
>
> Given the lack of interest I think it
Possible inconsistent memory deallocation and/or race conditions were
detected specifically with respect to remaining open handles to the video
device handled by the tw686x driver. This patch addresses this by
implementing a revised independent instance of the video_device_release
function t
Le vendredi 26 juillet 2019 à 12:02 +0200, Hans Verkuil a écrit :
> On 7/26/19 11:56 AM, Chen-Yu Tsai wrote:
> > On Fri, Jul 26, 2019 at 5:50 PM Maxime Jourdan
> > wrote:
> > > On Wed, Jul 24, 2019 at 1:27 PM Hans Verkuil
> > > wrote:
> > > > (There were too many recipients for my provider, so
Hi Hans,
I recall us agreeing that a custom function to free the last resources
attached to the video device would be preferable. So may I clarify, in
your words, what bug I may be fixing? I please need a description to
report to patchwork and to my mentor..
Also I’m getting confused reactio
On Mon, 29 Jul 2019 15:25:21 +0200
Paul Kocialkowski wrote:
> Hi,
>
> On Sat 27 Jul 19, 11:46, Boris Brezillon wrote:
> > On Sat, 27 Jul 2019 11:27:43 +0200
> > Paul Kocialkowski wrote:
> >
> > > Hi,
> > >
> > > On Fri 26 Jul 19, 10:53, Hans Verkuil wrote:
> > > > On 7/26/19 9:30 AM, Bori
Hi,
On Sat 27 Jul 19, 15:49, Boris Brezillon wrote:
> On Sat, 27 Jul 2019 09:52:24 -0300
> Ezequiel Garcia wrote:
>
>
> > > >
> > > > That's not my understanding of the Annex B section (quoting the spec
> > > > for reference):
> > > >
> > > > "
> > > > The byte stream format consists of a seq
Hi,
On Sat 27 Jul 19, 11:46, Boris Brezillon wrote:
> On Sat, 27 Jul 2019 11:27:43 +0200
> Paul Kocialkowski wrote:
>
> > Hi,
> >
> > On Fri 26 Jul 19, 10:53, Hans Verkuil wrote:
> > > On 7/26/19 9:30 AM, Boris Brezillon wrote:
> > > > On Fri, 26 Jul 2019 08:28:28 +0200
> > > > Boris Brezillo
On Mon, Jul 29, 2019 at 10:12 PM Paul Kocialkowski
wrote:
>
> Hi,
>
> On Sun 28 Jul 19, 23:05, Tomasz Figa wrote:
> > On Sat, Jul 27, 2019 at 6:37 PM Paul Kocialkowski
> > wrote:
> > >
> > > Hi,
> > >
> > > On Wed 24 Jul 19, 13:05, Hans Verkuil wrote:
> > > > Add an enum_fmt format flag to specif
Hi,
On Sun 28 Jul 19, 23:05, Tomasz Figa wrote:
> On Sat, Jul 27, 2019 at 6:37 PM Paul Kocialkowski
> wrote:
> >
> > Hi,
> >
> > On Wed 24 Jul 19, 13:05, Hans Verkuil wrote:
> > > Add an enum_fmt format flag to specifically tag coded formats where
> > > full bitstream parsing is supported by the
Hi Tomasz,
On Mon, 2019-07-29 at 17:57 +0800, Tomasz Figa wrote:
> On Mon, Jul 29, 2019 at 3:01 PM Jerry-ch Chen
> wrote:
> >
> > Hi Enrico,
> >
> > On Tue, 2019-07-09 at 18:56 +0800, Enrico Weigelt, metux IT consult
> > wrote:
> > > On 09.07.19 10:41, Jerry-ch Chen wrote:
> > >
> > > Hi,
> > >
>
On 7/29/19, Hans Verkuil wrote:
> On 7/29/19 10:54 AM, Vincent McIntyre wrote:
>> Hi,
>>
>> I am getting build failures in v4l2-fwnode.c. I'm sending this because
>> the daily build logs
>> are not showing any errors for this kernel (version below).
>>
>> I've tried flushing the git checkout and r
Hi Sakari,
On 19-06-25 15:27, Sakari Ailus wrote:
> Hi Marco,
>
> Thanks for the set.
>
> Looks quite good to me in general; a few minor comments below.
Sorry for the delayed response.
> On Wed, Jun 19, 2019 at 05:28:38PM +0200, Marco Felsch wrote:
> > Adding support for the TC358746 bridge. T
On Mon, Jul 29, 2019 at 3:01 PM Jerry-ch Chen
wrote:
>
> Hi Enrico,
>
> On Tue, 2019-07-09 at 18:56 +0800, Enrico Weigelt, metux IT consult
> wrote:
> > On 09.07.19 10:41, Jerry-ch Chen wrote:
> >
> > Hi,
> >
> >
> > > diff --git a/drivers/media/platform/mtk-isp/fd/mtk_fd.h
> > > b/drivers/media/
On 7/29/19 10:54 AM, Vincent McIntyre wrote:
> Hi,
>
> I am getting build failures in v4l2-fwnode.c. I'm sending this because
> the daily build logs
> are not showing any errors for this kernel (version below).
>
> I've tried flushing the git checkout and rerunning but I still get the
> failures
Hi Mauro,
Just one fix for vivid: this bug causes a regression in the test-media
cec tests.
Regards,
Hans
The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
are available in the Git repository at:
git://linuxtv.o
Hi,
I am getting build failures in v4l2-fwnode.c. I'm sending this because
the daily build logs
are not showing any errors for this kernel (version below).
I've tried flushing the git checkout and rerunning but I still get the failures.
I can send a fuller log off-list if you like.
/home/me/git/
On Mon, Jul 29, 2019 at 9:48 AM Simon Horman wrote:
> Renesas media binding documentation files uses a naming schema of
use
> 'renesas,.txt'. Rename IMR file to match this pattern.
the IMR file?
>
> Cc: Niklas Söderlund
> Signed-off-by: Simon Horman
Reviewed-by: Geert Uytterhoeven
Gr{oetj
Renesas media binding documentation files uses a naming schema of
'renesas,.txt'. Rename IMR file to match this pattern.
Cc: Niklas Söderlund
Signed-off-by: Simon Horman
---
Documentation/devicetree/bindings/media/{rcar_imr.txt => renesas,imr.txt} | 0
1 file changed, 0 insertions(+), 0 deletio
On Fri, Jul 12, 2019 at 04:17:03PM +0900, Niklas Söderlund wrote:
> Hi,
>
> A gentle ping on this patch. I assume if it could get a ack from Rob it
> could be taken in thru the media-tree?
Given the lack of interest I think it could also be taken through
Geert's tree.
>
> On 2019-06-12 23:12:4
27 matches
Mail list logo
