Hi Benoît,
thank you for your answer.
On 7 March 2013 13:13, Benoît Thébaudeau wrote:
> Dear Javier Martin,
>
> On Thursday, March 7, 2013 10:43:42 AM, Javier Martin wrote:
>> Hi,
>> I am testing mt9m131 sensor (which is supported in mt9m111.c) in
>> mainline kernel 3.8 with my Visstrim M10, whic
On Thu, Mar 7, 2013 at 8:21 PM, Sylwester Nawrocki
wrote:
> On 02/21/2013 12:54 PM, Shaik Ameer Basha wrote:
>> Changing the variable type to 'int' from 'unsigned int'. Driver
>> logic expects the variable type to be 'int'.
>>
>> Signed-off-by: Shaik Ameer Basha
>> ---
>> drivers/media/platform/
Hi
Names of V4L2 device nodes keep on varying depending on target, on some
targets, the device node assigned to my device is /dev/video21 and on some
it is /dev/video15. In order to determine my device, i am opening it,
reading the capabilities, enumerating its formats and then chose the one
match
Hi Mr. Dae,
On 7 March 2013 13:34, Inki Dae wrote:
>
>
>> -Original Message-
>> From: linux-media-ow...@vger.kernel.org [mailto:linux-media-
>> ow...@vger.kernel.org] On Behalf Of Vikas Sajjan
>> Sent: Thursday, March 07, 2013 4:40 PM
>> To: dri-de...@lists.freedesktop.org
>> Cc: linux-me
On Thu, 7 Mar 2013, javier Martin wrote:
> Hi,
>
> On 26 February 2013 19:32, Benoît Thébaudeau
> wrote:
> > Commit f9bd5843658e18a7097fc7258c60fb840109eaa8 changed
> > V4L2_CID_EXPOSURE_AUTO
> > from boolean to enum, and commit af8425c54beb3c32cbb503a379132b3975535289
> > changed the creation
Em Thu, 07 Mar 2013 16:18:41 -0500
Andy Walls escreveu:
> Oliver Schinagl wrote:
>
> >On 03/06/13 18:36, Jean Delvare wrote:
> >> Hi all,
> >>
> >> I have a TerraTec Cinergy T PCIe Dual card, with DRX-3916K and
> >> DRX-3913K frontends. I am thus using the drxk dvb-frontend driver.
> >> While t
Hi Christian
On Wed, 6 Mar 2013, Christian Rhodin wrote:
> Hi,
>
> I'm looking for some guidance on the correct way to handle a new pixel
> format. What I'm dealing with is a CMOS image sensor that supports
> dynamic switching between linear and iHDR modes. iHDR stands for
> "interlaced High D
Oliver Schinagl wrote:
>On 03/06/13 18:36, Jean Delvare wrote:
>> Hi all,
>>
>> I have a TerraTec Cinergy T PCIe Dual card, with DRX-3916K and
>> DRX-3913K frontends. I am thus using the drxk dvb-frontend driver.
>> While trying to find the best antenna, position and amplification, I
>> found tha
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: Thu Mar 7 19:00:24 CET 2013
git branch: test
git hash: 457ba4ce4f435d0b4dd82a0acc6c796e541a2ea7
gcc versio
On Sun, 3 Mar 2013 00:45:16 +0100
Hans Verkuil wrote:
> 3) What is the meaning of this snippet of code in v4l2-enc.c?
>
> if (pix->priv)
> solo_enc->type = SOLO_ENC_TYPE_EXT;
>
>I've commented it out since it is completely undocumented and no
> driver should assume that
This patch:
http://git.linuxtv.org/media_tree.git/commit/b86d15440b683f8634c0cb26fc0861a5bc4913ac
is missing a chunk when compared to an older version:
https://patchwork.kernel.org/patch/2063281/
probably because of an unresolved merging conflict.
This causes the following error:
WARNING: "cx231xx
On 02/21/2013 12:54 PM, Shaik Ameer Basha wrote:
> Changing the variable type to 'int' from 'unsigned int'. Driver
> logic expects the variable type to be 'int'.
>
> Signed-off-by: Shaik Ameer Basha
> ---
> drivers/media/platform/s5p-fimc/fimc-lite-reg.c |4 ++--
> 1 file changed, 2 insertio
Add copying of buffer timestamps and set the timestamp_type to
V4L2_BUF_FLAG_TIMESTAMP_COPY to avoid warnings about UNDEFINED
timestamp type like:
WARNING: at drivers/media/v4l2-core/videobuf2-core.c:2042
vb2_queue_init+0xe0/0x18c()
Modules linked in:
[] (unwind_backtrace+0x0/0x13c) from []
(war
Added support for the GOTVIEW SatelliteHD card which is based on
Montage M88DS3000 and works very well with this driver.
Signed-off-by: Andrey Pavlenko
---
drivers/media/usb/dvb-usb/dw2102.c | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/drivers/media/usb/dvb-us
This fixes following warnings when all links are being disconnected:
[ 20.08] WARNING: at drivers/media/platform/s5p-fimc/fimc-mdevice.c:1269
__fimc_md_set_camclk+0x208/0x20c()
[ 20.09] Modules linked in:
[ 20.095000] [] (unwind_backtrace+0x0/0x13c) from []
(warn_slowpath_common+0x
From: Andrzej Hajda
Due to improper condition check streaming start for some pixel
formats was prevent and the s_stream just reatuned -EINVAL.
This fixes regression introduced in commit 5565a2ad47cdd8e697
[media] m5mols: Protect driver data with a mutex.
Cc: sta...@vger.kernel.org # 3.7
Signed-o
Hi,
On 26 February 2013 19:32, Benoît Thébaudeau
wrote:
> Commit f9bd5843658e18a7097fc7258c60fb840109eaa8 changed V4L2_CID_EXPOSURE_AUTO
> from boolean to enum, and commit af8425c54beb3c32cbb503a379132b3975535289
> changed the creation of this control into a menu for the mt9m111. However,
> mt9m1
Dear Javier Martin,
On Thursday, March 7, 2013 10:43:42 AM, Javier Martin wrote:
> Hi,
> I am testing mt9m131 sensor (which is supported in mt9m111.c) in
> mainline kernel 3.8 with my Visstrim M10, which is an i.MX27 board.
>
> Since both mx2_camera.c and mt9m111.c are soc_camera drivers making i
Hi Sekhar,
On Thu, Mar 7, 2013 at 4:54 PM, Sekhar Nori wrote:
> On 3/7/2013 12:47 PM, Prabhakar Lad wrote:
>
>> On Wed, Mar 6, 2013 at 7:51 PM, Sekhar Nori wrote:
>>> So instead of presenting a non-useful vpif selection to users,
>>> vpif.c dependency is better handled in makefile, no?
>>>
>> Ag
On 3/7/2013 12:47 PM, Prabhakar Lad wrote:
> On Wed, Mar 6, 2013 at 7:51 PM, Sekhar Nori wrote:
>> So instead of presenting a non-useful vpif selection to users,
>> vpif.c dependency is better handled in makefile, no?
>>
> Agreed that’s a better fix.
How about VIDEO_VPFE_CAPTURE? Does enabling j
Hi Sachin,
On Thu, Mar 7, 2013 at 1:36 PM, Sachin Kamat wrote:
> Hi Prabhakar,
>
>>> BTW, who is supposed to pick this patch?
>>>
>> I'll queue it for 3.10 and a issue a pull request to Mauro soon.
>> Or if you have a branch and want to issue a pull no problem(anyways
>> I have Acked it). what do
On 03/07/2013 05:23 AM, Arun Kumar K wrote:
>> Do you mean this problem was not observed in 3.8 kernel and something
>> has changed in the v4l2 core so it fails in 3.9-rc now ? Or is it
>> related to some change in the driver itself ?
>
> I saw this problem in 3.9rc1 and also in 3.8 stable.
> But
On 03/07/2013 03:20 AM, Shaik Ameer Basha wrote:
> v4l2_ctrl_new() uses check_range() for control range checking (which
> is added newly).
> This function expects 'step' value for V4L2_CTRL_TYPE_BOOLEAN type control.
> If 'step' value doesn't match to '1', it returns -ERANGE error.
>
> Its a chang
Hi all,
One thing that has annoyed me for a long time is that it is too much
work for drivers to implement these debug ioctls. What you really want in
a driver is just to implement functions to get and set registers and have
it all working automatically.
Also it is quite annoying that the v4l2-ch
Hi,
sorry for the long delay. I missed this one.
On 5 March 2013 18:56, Guennadi Liakhovetski wrote:
> (Javier's opinion requested)
>
> I'm no expert in i.MX27 hardware, would be great to have an ack from
> someone, intensively working in this area. Javier, what do you think? Is
> this really cor
Hi,
I am testing mt9m131 sensor (which is supported in mt9m111.c) in
mainline kernel 3.8 with my Visstrim M10, which is an i.MX27 board.
Since both mx2_camera.c and mt9m111.c are soc_camera drivers making it
work was quite straightforward. However, I've found several issues
regarding mt9m111.c:
1
Hi Prabhakar,
>> BTW, who is supposed to pick this patch?
>>
> I'll queue it for 3.10 and a issue a pull request to Mauro soon.
> Or if you have a branch and want to issue a pull no problem(anyways
> I have Acked it). what do you suggest ?
Please queue it in your tree and go ahead with the pull r
> -Original Message-
> From: linux-media-ow...@vger.kernel.org [mailto:linux-media-
> ow...@vger.kernel.org] On Behalf Of Vikas Sajjan
> Sent: Thursday, March 07, 2013 4:40 PM
> To: dri-de...@lists.freedesktop.org
> Cc: linux-media@vger.kernel.org; kgene@samsung.com;
> inki@samsun
28 matches
Mail list logo
