At present, dma_buf_export() takes a series of parameters, which
makes it difficult to add any new parameters for exporters, if required.
Make it simpler by moving all these parameters into a struct, and pass
the struct * as parameter to dma_buf_export().
While at it, unite dma_buf_export_named()
It is possible to have HW seek support in TDA8290 cards as in recent TEA575x?
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
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: Wed Jan 28 04:00:15 CET 2015
git branch: test
git hash: 8d44aeefcd79e9be3b6db4f37efc7544995b619e
gcc versio
Hi, Guennadi
On 11/28/2014 4:13 AM, Guennadi Liakhovetski wrote:
Hi Josh,
On Thu, 27 Nov 2014, Josh Wu wrote:
Hi, Guennadi
On 11/26/2014 6:23 AM, Guennadi Liakhovetski wrote:
Hi Josh,
On Tue, 25 Nov 2014, Josh Wu wrote:
Add SVGA, UXGA and XGA size definitions to v4l2-image-sizes.h.
The d
Attn: Jonathon McCrohan,
I expect you have already received an automated notification from ubuntu
launchpad. I have just reported a new bug against this file to bring the
multiplex frequencies up to date.
I apologise for wimping out of your advice to patch against the original
source! I have
Sorry, forgot to include related link to kernel bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=91181
Ciao!
Luca
On 26/01/2015 11:38, Luca Bonissi wrote:
> Hi!
>
> I found a problem on vc032x gspca usb webcam subdriver: "bytesperline"
> property is wrong for YUYV and YVYU formats.
> Wit
Em Tue, 27 Jan 2015 19:27:54 +0200
Antti Palosaari escreveu:
> It is not pulled, try again.
>
>
> The following changes since commit 71947828caef0c83d4245f7d1eaddc799b4ff1d1:
>
>[media] mn88473: One function call less in mn88473_init() after error
> (2014-12-04 16:00:47 -0200)
>
> are av
It is not pulled, try again.
The following changes since commit 71947828caef0c83d4245f7d1eaddc799b4ff1d1:
[media] mn88473: One function call less in mn88473_init() after error
(2014-12-04 16:00:47 -0200)
are available in the git repository at:
git://linuxtv.org/anttip/media_tree.git sil
I discovered this bug today and it explains why vivid behaved so strangely
when generating full range Y'CbCr patterns. It was introduced in 3.19, so it
would be really nice if this can be fixed before 3.19 is released.
Regards,
Hans
The following changes since commit 8d44aeefcd79e9be3b6d
When converting to or from Y'CbCr and R'G'B' the Y offset depends
on the quantization range: it's 0 for full and 16 for limited range.
But in the code it was hardcoded to 16. This messed up the brightness
of the generated pattern.
Signed-off-by: Hans Verkuil
---
drivers/media/platform/vivid/vivi
On 01/27/2015 03:14 PM, Hans Verkuil wrote:
On 01/27/15 14:32, Jacek Anaszewski wrote:
While testing the LED / flash API integration patches
I noticed that the v4l2-controls marked as volatile with
V4L2_CTRL_FLAG_VOLATILE flag behave differently than I would
expect.
Let's consider following use
Hi Jean-Michel,
Long time no news of this. There are any progress?
I am interested in this. Can any of you send me the pdf of pipeline? I
want to take a look.
Regards,
Carlos S.
2014-10-24 15:42 GMT+02:00 Jean-Michel Hautbois
:
> Hi Philipp,
>
> 2014-09-15 16:13 GMT+02:00 Jean-Michel Hautbois
On 01/27/15 14:32, Jacek Anaszewski wrote:
> While testing the LED / flash API integration patches
> I noticed that the v4l2-controls marked as volatile with
> V4L2_CTRL_FLAG_VOLATILE flag behave differently than I would
> expect.
>
> Let's consider following use case:
>
> There is a volatile V4L
> John replied off list:
>
> "http://linux-media.vger.kernel.narkive.com/kAviSkda/chipset-change-for-cx88-board-pinnacle-pctv-hd-800i
>
> Wonder if any code was ever integrated?"
>
> It looks like basics of a patch was developed to support the card but
> it was incompatible with the existing cards
While testing the LED / flash API integration patches
I noticed that the v4l2-controls marked as volatile with
V4L2_CTRL_FLAG_VOLATILE flag behave differently than I would
expect.
Let's consider following use case:
There is a volatile V4L2_CID_FLASH_INTENSITY v4l2 control with
following constrai
On Tue, Jan 27, 2015 at 12:25 AM, John Klug wrote:
> I moved it to a dual boot system, and it works in windows, and the
> same error in Linux.
>
> The chips are marked:
> Conexant CX23880
> Samsung S5H1411
> Cirrus CS5340CZZ
> Atmel ATMLH138
>
> three out of four are a
Em Tue, 23 Dec 2014 22:48:58 +0200
Antti Palosaari escreveu:
> Convert driver to kernel I2C model. Old DVB proprietary model is
> still left there also.
>
> Signed-off-by: Antti Palosaari
> ---
> drivers/media/dvb-frontends/Kconfig| 2 +-
> drivers/media/dvb-frontends/rtl2830.c
Em Wed, 10 Dec 2014 12:06:34 +0200
Antti Palosaari escreveu:
> These are mostly small improvements, having very small functionality
> changes.
Hmm... I was unable to pull it. Maybe this got already applied?
Regards,
Mauro
>
> regards
> Antti
>
> The following changes since commit 71947828ca
Hi,
On 23/01/15 14:05, Baluta, Teodora wrote:
...
>>> So why not v4l? These are effectively image sensors..
>>
>> Well, here's why I don't think v4l would be the best option:
>>
>> - an image scanner could be implemented in the v4l subsystem, but
>> it seems far more compl
Hello again,
I was able to solve the problem... now the userspace program use the
correct value for VIDIOC_QUERYCTRL.
Regards
Francesco
Il 27/01/2015 11:43, Francesco Marletta ha scritto:
Hello to anyone,
I'm working on a problem with V4L2 on Linux Kernel 2.6.37.
The problem arise when I tr
Hello to anyone,
I'm working on a problem with V4L2 on Linux Kernel 2.6.37.
The problem arise when I try to query a video device to list the
controls it provides.
When is call
ioctl(fd, VIDIOC_QUERYCTRL, &queryctrl)
the function doesn't return 0 and errno is set to EINVAL
This happen for
Hey folks,
I seem to keep getting the this error after a day or two with my DVBSky T9580.
The card appears to keep working regardless of the error but
unfortunately whenever this occurs the Sky (UK)+ HD box downstairs
goes completely bonkers (poor signal, blocking etc) until I tune to a
service o
Hi Mauro,
The recent smiapp OF support patches contained a small issue related to
reading 64-bit numbers from the device tree, such that the compilation fails
if CONFIG_OF is undefined.
This patch provides a temporary fix to the matter. The proper one is to use
of_property_read_u64_array(), but t
of_read_number() is defined in of.h but does not return an error code, so
that non-of implementation could simply return an error.
Temporarily work around this until of_read_number() can be replaced by
of_property_read_u64_array().
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/smiapp/smiapp
Add some helpers to share the constraints of devices while attaching
to the dmabuf buffer.
At each attach, the constraints are calculated based on the following:
- max_segment_size, max_segment_count, segment_boundary_mask from
device_dma_parameters.
In case the attaching device's constraints
From: Rob Clark
For devices which have constraints about maximum number of segments in
an sglist. For example, a device which could only deal with contiguous
buffers would set max_segment_count to 1.
The initial motivation is for devices sharing buffers via dma-buf,
to allow the buffer exporter
26 matches
Mail list logo
