On 04/01/2014 08:55 PM, Sriakhil Gogineni wrote:
> Hi Hans,
>
> Thanks for the detailed response. As, much as I would love to have a
> robust, fully functioning implementation for v1, I think it might be
> a a bit of 'over-optimization' to write the complete spec into the
> driver from the beginni
Hi Laurent,
On Tue, 2014-04-01 at 15:49 +0200, Laurent Pinchart wrote:
> Hi Olivier,
>
> On Sunday 30 March 2014 00:23:01 Olivier Langlois wrote:
> > Hi Laurent,
> >
> > > > Yes. ffmpeg uses wall clock time to create timestamps for audio packets
> > > > from ALSA device.
> > >
> > > OK. I suppo
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 Apr 2 04:00:27 CEST 2014
git branch: test
git hash: a83b93a7480441a47856dc9104bea970e84cda87
gcc versi
Hi Sakari,
Thank you for the patch.
Given that the timestamp type and source are not supposed to change during
streaming, do we really need to print them for every frame ?
On Saturday 01 March 2014 18:18:08 Sakari Ailus wrote:
> Signed-off-by: Sakari Ailus
> ---
> yavta.c | 52 +
Hi Sakari,
Thank you for the patches, and sorry for the late reply.
I've pushed outstanding multiplane patches to the master branch of the yavta
repository, and applied the first two patches of this series on top of that.
After addressing the commends I've made on the individual patches, could
Hi Sakari,
Thank you for the patch.
On Saturday 01 March 2014 18:18:07 Sakari Ailus wrote:
> Signed-off-by: Sakari Ailus
> ---
> yavta.c | 18 +-
> 1 file changed, 17 insertions(+), 1 deletion(-)
>
> diff --git a/yavta.c b/yavta.c
> index a9b192a..71c1477 100644
> --- a/yavta
Hi Sakari,
Thank you for the patch.
On Saturday 01 March 2014 18:18:06 Sakari Ailus wrote:
> Signed-off-by: Sakari Ailus
> ---
> yavta.c | 63
> 1 file changed, 43 insertions(+), 20 deletions(-)
>
> diff --git a/yavta.c b/yavta.c
>
Hi Sakari,
Thank you for the patch.
On Saturday 01 March 2014 18:18:04 Sakari Ailus wrote:
> The option is --output, or -o.
Wouldn't it make sense to have an option to force the device type to a user-
specified value instead of just an option for the output type ? "-o" is also
usually used to s
Hi Hans,
Thanks for the detailed response. As, much as I would love to have a robust,
fully functioning implementation for v1, I think it might be a a bit of
'over-optimization' to write the complete spec into the driver from the
beginning.
The question I ask myself is, "how can we get it mai
Hi Anton,
On Saturday 29 March 2014 09:28:02 Anton Leontiev wrote:
> 28.03.2014 20:12, Laurent Pinchart пишет:
> + * Set error flag for incomplete buffer.
> + */
> +static void uvc_buffer_check_bytesused(const struct uvc_streaming
> *const stream,
> >
> > No need for the secon
Hi Jean-François,
Sorry for the late reply.
On Thursday 27 March 2014 12:34:49 Jean-Francois Moine wrote:
> On Wed, 26 Mar 2014 18:33:09 +0100 Laurent Pinchart wrote:
> > That could work in your case, but I don't really like that.
> >
> > We need to describe the hardware topology, that might be
Am 28.03.2014 21:21, schrieb aaron.mo...@alsatis.net:
> Hi,
>
> I have endless problems since upgarding to ubuntu12.04 with my usb
> microscope and it's a big problem cos i need it for work.
Which device are you talking about ? Which sensor does it use ?
What does "endless problems" mean ?
Which k
On 04/01/2014 06:48 PM, Christopher Li wrote:
> On Mon, Mar 31, 2014 at 10:22 AM, Linus Torvalds
> wrote:
>> On Mon, Mar 31, 2014 at 1:06 AM, Hans Verkuil wrote:
>>
>> Chris, can you please add this to the test cases since Hans did the
>> work to create a nice small test-case?
>
> Sure, I want t
On Mon, Mar 31, 2014 at 10:22 AM, Linus Torvalds
wrote:
> On Mon, Mar 31, 2014 at 1:06 AM, Hans Verkuil wrote:
>
> Chris, can you please add this to the test cases since Hans did the
> work to create a nice small test-case?
Sure, I want to add them to the test case.
Hans, May I get a signed-off
Le mardi 01 avril 2014 à 16:34 +0200, Sylwester Nawrocki a écrit :
> It should be "BGRA, 32 bpp", I can fix it when applying, if
> you won't send next version of this patch until then.
Good catch, I'll let you fix when applying.
thanks,
Nicolas
signature.asc
Description: This is a digitall
Oops. I send this to Mauro's old email address. Sorry about that.
regards,
dan carpenter
On Tue, Apr 01, 2014 at 05:38:07PM +0300, Dan Carpenter wrote:
> I'd like to send this patch except that it "breaks"
> cx24116_send_diseqc_msg(). The cx24116 driver accepts ->msg_len values
> up to 24 but
Hi Hans,
On Tue, Apr 1, 2014 at 8:12 PM, Hans Verkuil wrote:
> On 04/01/14 16:26, Hans Verkuil wrote:
>>
>>
>> On 04/01/14 16:06, Prabhakar Lad wrote:
>>> Hi Hans,
>>>
>>> On Tue, Apr 1, 2014 at 7:20 PM, Hans Verkuil wrote:
Hi Prabhakar,
On 04/01/14 15:45, Lad, Prabhakar wrote:
>>
On 04/01/14 16:26, Hans Verkuil wrote:
>
>
> On 04/01/14 16:06, Prabhakar Lad wrote:
>> Hi Hans,
>>
>> On Tue, Apr 1, 2014 at 7:20 PM, Hans Verkuil wrote:
>>> Hi Prabhakar,
>>>
>>> On 04/01/14 15:45, Lad, Prabhakar wrote:
From: "Lad, Prabhakar"
There was a conflict between the mm
I'd like to send this patch except that it "breaks"
cx24116_send_diseqc_msg(). The cx24116 driver accepts ->msg_len values
up to 24 but it looks like it's just copying 16 bytes past the end of
the ->msg[] array so it's already broken.
cmd->msg_len is an unsigned char. The comment next to the str
On 25/03/14 21:55, Nicolas Dufresne wrote:
> Testing showed that HW produces BGR32 rather then RGB32 as exposed
> in the driver. The documentation seems to state the pixels are stored
> in little endian order.
>
> Signed-off-by: Nicolas Dufresne
> ---
> drivers/media/platform/exynos4-is/fimc-cor
On 04/01/14 16:06, Prabhakar Lad wrote:
> Hi Hans,
>
> On Tue, Apr 1, 2014 at 7:20 PM, Hans Verkuil wrote:
>> Hi Prabhakar,
>>
>> On 04/01/14 15:45, Lad, Prabhakar wrote:
>>> From: "Lad, Prabhakar"
>>>
>>> There was a conflict between the mmap function pointer prototype of
>>> struct v4l_fd an
On Tue, Apr 01, 2014 at 09:04:12AM +0200, Hans Verkuil wrote:
> When running sparse over drivers/media/v4l2-core/v4l2-ioctl.c I get these
> errors:
>
> drivers/media/v4l2-core/v4l2-ioctl.c:2043:9: error: bad integer constant
> expression
> drivers/media/v4l2-core/v4l2-ioctl.c:2044:9: error: bad i
Hi Nicolas,
On 01/04/14 16:13, Nicolas Dufresne wrote:
> Any comment/input ?
My apologies for the delay. The patches look good to me, I'm going
to apply them to my tree for 3.16, as the media tree is already closed
for 3.15. Thanks a lot for these fixes!
> Le mardi 25 mars 2014 à 16:45 -0400, Ni
Any comment/input ?
Le mardi 25 mars 2014 à 16:45 -0400, Nicolas Dufresne a écrit :
> This patch series fixes several bugs found in the s5p-fimc driver. These
> bugs relate to bad parameters in the formats definition and short size
> of image buffers.
>
> Nicolas Dufresne (5):
> s5p-fimc: Reuse
Hi Hans,
On Tue, Apr 1, 2014 at 7:20 PM, Hans Verkuil wrote:
> Hi Prabhakar,
>
> On 04/01/14 15:45, Lad, Prabhakar wrote:
>> From: "Lad, Prabhakar"
>>
>> There was a conflict between the mmap function pointer prototype of
>> struct v4l_fd and the actual function used. Make sure it is in sync
>>
Hi Olivier,
On Sunday 30 March 2014 00:23:01 Olivier Langlois wrote:
> Hi Laurent,
>
> > > Yes. ffmpeg uses wall clock time to create timestamps for audio packets
> > > from ALSA device.
> >
> > OK. I suppose I shouldn't drop support for the realtime clock like I
> > wanted to then :-)
> >
> >
Hi Prabhakar,
On 04/01/14 15:45, Lad, Prabhakar wrote:
> From: "Lad, Prabhakar"
>
> There was a conflict between the mmap function pointer prototype of
> struct v4l_fd and the actual function used. Make sure it is in sync
> with the prototype of v4l2_mmap.
The prototype of v4l2_mmap uses int64_
Signed-off-by: Mikhail Domrachev
---
drivers/media/pci/saa7134/saa7134-empress.c | 1 +
drivers/media/pci/saa7134/saa7134-reg.h | 5
drivers/media/pci/saa7134/saa7134-video.c | 41 +++--
drivers/media/pci/saa7134/saa7134.h | 1 +
4 files changed, 46 i
From: "Lad, Prabhakar"
There was a conflict between the mmap function pointer prototype of
struct v4l_fd and the actual function used. Make sure it is in sync
with the prototype of v4l2_mmap.
This patch fixes following build error,
v4l2-compliance.cpp: In function 'void v4l_fd_test_init(v4l_fd*
On 01/04/14 07:39, Josh Wu wrote:
Hi, Ben
On 3/31/2014 6:10 PM, Ben Dooks wrote:
On 31/03/14 10:28, Josh Wu wrote:
Hi, Ben
Thanks for the patch, I just test atmel-isi with the your patch,
I find the "mclk" registered in soc-camera driver cannot be find
by the soc-camera sensors. See comment i
Hi,
It seems the patch has been applied twice in linux-next/master:
$ git log --oneline -25 linux-next/master
drivers/media/v4l2-core/videobuf2-core.c
9cf3c31 [media] vb2: call buf_finish after the state check
3f1a9a3 [media] vb2: fix streamoff handling if streamon wasn't called
e4d2581 [media] v
Hi Sri,
On 03/31/14 23:12, Sriakhil Gogineni wrote:
> Hi,
>
> I'm trying to write a HDMI-CEC driver for the Radxa Rock
> (Specification - Radxa). I am coming from a software background and
> have found libcec and am looking at other implementation.
>
> I'm wondering how to connect the hardware a
When running sparse over drivers/media/v4l2-core/v4l2-ioctl.c I get these
errors:
drivers/media/v4l2-core/v4l2-ioctl.c:2043:9: error: bad integer constant
expression
drivers/media/v4l2-core/v4l2-ioctl.c:2044:9: error: bad integer constant
expression
drivers/media/v4l2-core/v4l2-ioctl.c:2045:9: e
33 matches
Mail list logo
