Jeongtae Park wrote:
>
> This patch adds clock support for MFC v5.1.
>
> Reviewed-by: Peter Oh
> Signed-off-by: Jeongtae Park
> Cc: Marek Szyprowski
> Cc: Kamil Debski
> ---
> arch/arm/mach-s5pv310/clock.c | 68
> +++
> arch/arm/mach-s5pv310/include/ma
Kamil Debski wrote:
>
> This patch adds platform support for Multi Format Codec 5.1.
> MFC 5.1 is capable of handling a range of video codecs and this driver
> provides V4L2 interface for video decoding.
>
> Signed-off-by: Kamil Debski
> Signed-off-by: Kyungmin Park
> ---
> arch/arm/mach-s5pv3
Hi Martin,
On Fri, Mar 11, 2011 at 12:36:09PM +0100, Martin Bugge (marbugge) wrote:
> Not every tx status is applicable for all modes, see table 1.
>
> |-|
> |Av link Mode | CEC | 1 | 2 | 3 |
> |
I'll add the following kernel debug info for what it's worth:
-
Mar 12 11:22:51 mythtv kernel: [ 14.025097] saa7130/34: v4l2 driver
version 0.2.16 loaded
Mar 12 11:22:51 mythtv kernel: [ 14.026609] saa7134 :00:09.0:
PCI INT A -> GSI 17 (level, low) -> IRQ 17
Mar 12 11:22:51 mythtv kern
Marek Szyprowski wrote:
>
> From: Sylwester Nawrocki
>
> Add support for fourth FIMC platform device definition and define
> resources for FIMC modules on S5PV310 machines.
>
> Signed-off-by: Sylwester Nawrocki
> Signed-off-by: Kyungmin Park
> Signed-off-by: Marek Szyprowski
> ---
> arch/ar
I just bought a pair of what are a version of the My Cinema 7131 Hybrid cards.
The kernel reports it as saa7134: Asus Tiger revision 1.0, subsys 1043:4857
I did inititially try Mythbuntu 10.04 but the firmware upload seemed
to fail fairly consistently. Restarting with v10.10 the firmware
loads b
On Fri, Mar 11, 2011 at 6:30 PM, wrote:
>
>> Doesn't seem weird to me at all. This is a pretty uncommon card, so
>> it is entirely possible that many revisions could go by without
>> someone noticing a regression. I know for example that the HVR-1500Q
>> (the US version of that board) was broke
> Doesn't seem weird to me at all. This is a pretty uncommon card, so
> it is entirely possible that many revisions could go by without
> someone noticing a regression. I know for example that the HVR-1500Q
> (the US version of that board) was broken for months and nobody
> noticed.
Well. How w
On Fri, Mar 11, 2011 at 6:04 PM, wrote:
>
> Hey,
>
> i tried to revert that patch manually (e.g. switching into the directory,
> vim cx23885-i2c.c, removing the stuff which was added), then "make clean"
> "make distclean" followed by "./build.sh" then make rmmod, then plugged in
> the card, dmesg
Hey,
i tried to revert that patch manually (e.g. switching into the directory,
vim cx23885-i2c.c, removing the stuff which was added), then "make clean"
"make distclean" followed by "./build.sh" then make rmmod, then plugged in
the card, dmesg shows it loaded the card correctly, all fine, then i
On Fri, 11 Mar 2011, Mauro Carvalho Chehab wrote:
> /home/mchehab/new_build/v4l/pvrusb2-v4l2.c: In function 'pvr2_v4l2_do_ioctl':
> /home/mchehab/new_build/v4l/pvrusb2-v4l2.c:798:23: warning: variable 'cap'
> set but not used [-Wunused-but-set-variable]
I will look into these. I'm a little puzz
Andreas Oberritter wrote:
On 03/10/2011 04:29 PM, Issa Gorissen wrote:
As the cxd20099 driver is in staging due to abuse of the sec0 device, this
patch renames it to cam0. The sec0 device is not in use and can be removed
That doesn't solve anything. Besides, your patch doesn't even do
Andreas Oberritter writes:
> >> On 03/10/2011 04:29 PM, Issa Gorissen wrote:
> > Now, according to Mauro comments, he has put this code into staging
> > because of
> > the usage of sec0 name for a cam device.
> >
> > Please comment on Oliver's explanations from this thread
> >
> > http:/
With this fix the spec compiles without any errors.
Regards,
Hans
The following changes since commit 41f3becb7bef489f9e8c35284dd88a1ff59b190c:
[media] V4L DocBook: update V4L2 version (2011-03-11 18:09:02 -0300)
are available in the git repository at:
ssh://linuxtv.org/git/hverkuil
>> On 03/10/2011 04:29 PM, Issa Gorissen wrote:
>>> As the cxd20099 driver is in staging due to abuse of the sec0 device,
> this
>>> patch renames it to cam0. The sec0 device is not in use and can be
> removed
>>
>> That doesn't solve anything. Besides, your patch doesn't even do what
>> you descri
* David Cohen [110309 01:16]:
> Hi,
>
> Previous patch 2/3 was dropped in this new version. Patch 1 was updated
> according to a comment it got.
>
> ---
> IOVMM driver checks input 'da == 0' when mapping address to determine whether
> user wants fixed 'da' or not. At the same time, it doesn't di
cpia2_core.c:529:14: warning: variable 'dir' set but not used
[-Wunused-but-set-variable]
cpia2_core.c:526:5: warning: variable 'block_index' set but not used
[-Wunused-but-set-variable]
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/video/cpia2/cpia2_core.c
b/drivers/media/v
au0828-dvb.c:99:6: warning: variable 'ptr' set but not used
[-Wunused-but-set-variable]
au0828-video.c:1180:25: warning: variable 'maxheight' set but not used
[-Wunused-but-set-variable]
au0828-video.c:1180:15: warning: variable 'maxwidth' set but not used
[-Wunused-but-set-variable]
bttv-input.
Hi Sylwester, Pawel,
The daily build reports this warning when building for i686:
media_build/v4l/videobuf2-dma-contig.c: In function 'vb2_dma_contig_cookie':
media_build/v4l/videobuf2-dma-contig.c:81:9: warning: cast to pointer from
integer of different size
This refers to the void * cast in t
This message is generated daily by a cron job that builds v4l-dvb for
the kernels and architectures in the list below.
Results of the daily build of v4l-dvb:
date:Fri Mar 11 19:00:45 CET 2011
git hash:97c6bc5e15e60c0c15ff028c03af2cf42ad9a07e
gcc version: i686-linux-gcc (GCC) 4.5.
The following changes since commit 97c6bc5e15e60c0c15ff028c03af2cf42ad9a07e:
[media] altera-ci.h: add missing inline (2011-03-11 14:17:05 -0300)
are available in the git repository at:
ssh://linuxtv.org/git/hverkuil/media_tree.git fixes
Hans Verkuil (2):
V4L doc fixes
V4L DocBook
Em 11-03-2011 16:20, Hans Verkuil escreveu:
> On Friday, March 11, 2011 19:28:59 Mauro Carvalho Chehab wrote:
>> Hi Hans/Matti
>>
>> I did a compilation of the media_build tree against Fedora Rawhide, to check
>> what warnings are happening
>> with gcc 4.6, as it is easier to me to just run a VM w
On Friday, March 11, 2011 19:28:59 Mauro Carvalho Chehab wrote:
> Hi Hans/Matti
>
> I did a compilation of the media_build tree against Fedora Rawhide, to check
> what warnings are happening
> with gcc 4.6, as it is easier to me to just run a VM with Rawhide than to
> keep an updated set of gcc
Hi,
On 03/11/2011 07:04 PM, Chen, Xianwen wrote:
Hi there,
I'm having a hard time locating the proper driver for "0c45:6413
Microdia" webcam. I consulted "Documentation/video4linux/gspca.txt",
but didn't find such a device.
The 6413 is a UVC compatible camera / controller from Microdia, as
su
From: Andreas Oberritter
To: Issa Gorissen Cc: linux-media@vger.kernel.org,
r...@metzlerbros.de
Subject: Re: [PATCH] Ngene cam device name
> On 03/10/2011 04:29 PM, Issa Gorissen wrote:
> > As the cxd20099 driver is in staging due to abuse of the sec0 device,
this
> > patch renames it to cam0. Th
Hi Hans/Matti
I did a compilation of the media_build tree against Fedora Rawhide, to check
what warnings are happening
with gcc 4.6, as it is easier to me to just run a VM with Rawhide than to keep
an updated set of gcc
compiled by me on some place.
The compilation, however, ended earlier due t
Hi there,
I'm having a hard time locating the proper driver for "0c45:6413
Microdia" webcam. I consulted "Documentation/video4linux/gspca.txt",
but didn't find such a device.
Here is the lsusb output:
Bus 001 Device 003: ID 0c45:6413 Microdia
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrat
Hi all!
Today the Media Controller (and the OMAP3 driver that uses it!) was merged.
This is a major achievement after approximately three years of work. I think
I contacted Manju Hadli from Texas Instruments early 2008 and the first RFC
was posted July 18th 2008:
http://lists-archives.org/video4l
On Tue, 8 Mar 2011, Sergio Aguirre wrote:
> Hi Guennadi,
>
> On 03/08/2011 01:17 AM, Guennadi Liakhovetski wrote:
> > Hi Sergio
> >
> > On Mon, 7 Mar 2011, Sergio Aguirre wrote:
> >
> > > This helps redirect mmap calls to custom memory managers which
> > > already have preallocated space to use
On 03/11/2011 10:48 AM, Guennadi Liakhovetski wrote:
On Fri, 11 Mar 2011, Sergio Aguirre wrote:
Hi Guennadi,
On 03/11/2011 10:36 AM, Guennadi Liakhovetski wrote:
On Tue, 8 Mar 2011, Sergio Aguirre wrote:
Hi Guennadi,
On 03/08/2011 01:19 AM, Guennadi Liakhovetski wrote:
On Mon, 7 Mar 2011,
On Fri, 11 Mar 2011, Sergio Aguirre wrote:
> Hi Guennadi,
>
> On 03/11/2011 10:36 AM, Guennadi Liakhovetski wrote:
> > On Tue, 8 Mar 2011, Sergio Aguirre wrote:
> >
> > > Hi Guennadi,
> > >
> > > On 03/08/2011 01:19 AM, Guennadi Liakhovetski wrote:
> > > > On Mon, 7 Mar 2011, Sergio Aguirre wro
On 03/08/2011 07:45 AM, Guennadi Liakhovetski wrote:
On Tue, 8 Mar 2011, Sergio Aguirre wrote:
Hi Guennadi,
On 03/08/2011 01:17 AM, Guennadi Liakhovetski wrote:
Hi Sergio
On Mon, 7 Mar 2011, Sergio Aguirre wrote:
This helps redirect mmap calls to custom memory managers which
already have
Hi Guennadi,
On 03/11/2011 10:36 AM, Guennadi Liakhovetski wrote:
On Tue, 8 Mar 2011, Sergio Aguirre wrote:
Hi Guennadi,
On 03/08/2011 01:19 AM, Guennadi Liakhovetski wrote:
On Mon, 7 Mar 2011, Sergio Aguirre wrote:
This fixes the problem in which a host driver
sets a personalized sizeimag
On Tue, 8 Mar 2011, Sergio Aguirre wrote:
> Hi Guennadi,
>
> On 03/08/2011 01:19 AM, Guennadi Liakhovetski wrote:
> > On Mon, 7 Mar 2011, Sergio Aguirre wrote:
> >
> > > This fixes the problem in which a host driver
> > > sets a personalized sizeimage or bytesperline field,
> > > and gets ignore
On Friday 11 March 2011, Marek Szyprowski wrote:
> > > > does not support IOMMUs, but that could be changed by wrapping it
> > > > using the include/asm-generic/dma-mapping-common.h infrastructure.
> > >
> > > ARM dma-mapping framework also requires some additional research for
> > > better DMA
>
On 03/10/2011 04:29 PM, Issa Gorissen wrote:
> As the cxd20099 driver is in staging due to abuse of the sec0 device, this
> patch renames it to cam0. The sec0 device is not in use and can be removed
That doesn't solve anything. Besides, your patch doesn't even do what
you describe.
Wouldn't it be
Hi Mauro,
On Friday 11 March 2011 16:40:42 Mauro Carvalho Chehab wrote:
> Em 07-03-2011 08:57, Mauro Carvalho Chehab escreveu:
> > Em 05-03-2011 17:48, Laurent Pinchart escreveu:
> >
> > Added both patches and folded them as requested, and added the remaining
> > patches after my review. The new
Em 07-03-2011 08:57, Mauro Carvalho Chehab escreveu:
> Em 05-03-2011 17:48, Laurent Pinchart escreveu:
> Added both patches and folded them as requested, and added the remaining
> patches after my review. The new tree is at:
>
> http://git.linuxtv.org/mchehab/experimental.git?a=shortlog;h=refs/he
Hello,
On Friday, March 11, 2011 4:15 PM Arnd Bergmann wrote:
> On Friday 11 March 2011, Marek Szyprowski wrote:
> > On Friday, March 11, 2011 3:08 PM Arnd Bergmann wrote:
> >
> > > On Friday 11 March 2011, Marek Szyprowski wrote:
> > > > > The iommu API is not really meant to be KVM specific, it
On Friday 11 March 2011, Marek Szyprowski wrote:
> On Friday, March 11, 2011 3:08 PM Arnd Bergmann wrote:
>
> > On Friday 11 March 2011, Marek Szyprowski wrote:
> > > > The iommu API is not really meant to be KVM specific, it's just that the
> > > > in-tree users are basically limited to KVM at th
Hello,
On Friday, March 11, 2011 3:08 PM Arnd Bergmann wrote:
> On Friday 11 March 2011, Marek Szyprowski wrote:
> > > The iommu API is not really meant to be KVM specific, it's just that the
> > > in-tree users are basically limited to KVM at the moment. Another user
> > > that
> > > is coming
On Friday 11 March 2011, Marek Szyprowski wrote:
> > The iommu API is not really meant to be KVM specific, it's just that the
> > in-tree users are basically limited to KVM at the moment. Another user that
> > is coming up soon is the vmio device driver that can be used to
> > transparently
> > pa
Hello,
On Friday, March 11, 2011 12:51 PM Arnd Bergmann wrote:
> On Friday 11 March 2011, Marek Szyprowski wrote:
> >
> > We followed the style of iommu API for other mainline ARM platforms (both
> > OMAP and MSM
> > also have custom API for their iommu modules). I've briefly checked
> > includ
On Friday 11 March 2011, Marek Szyprowski wrote:
>
> We followed the style of iommu API for other mainline ARM platforms (both
> OMAP and MSM
> also have custom API for their iommu modules). I've briefly checked
> include/linux/iommu.h
> API and I've noticed that it has been designed mainly for
Hi
This is an updated version of the proposal for adding an api for
HDMI-CEC to V4L2.
Main difference is the support of AV.link EN 50157-2-[123]. (thanks to
Daniel Glöckner)
Author: Martin Bugge
Date: Fri, 11th of March 2010
=
This is a proposal for adding a Co
On Fri, 11 Mar 2011 10:38:08 +0100
Michael Jones wrote:
> On 03/11/2011 10:21 AM, Antonio Ospite wrote:
> > Hi Michael,
> >
> > are you going to release also Y12 conversion routines for libv4lconvert?
> >
> > Regards,
> >Antonio
> >
>
> Hi Antonio,
>
> As I am neither a user nor develope
Hi Mauro,
please pull from
git://git.infradead.org/users/kmpark/linux-2.6-samsung for-mauro
for a couple of videobuf2 and s5p fimc driver fixes and updates.
Included is also the missing Docbook documentation for NV12MT format.
The following changes since commit 88a763df226facb74fdb25456
On 03/11/2011 10:21 AM, Antonio Ospite wrote:
> Hi Michael,
>
> are you going to release also Y12 conversion routines for libv4lconvert?
>
> Regards,
>Antonio
>
Hi Antonio,
As I am neither a user nor developer of libv4lconvert, I am not planning
on adding Y12 conversion routines there. Ho
On Fri, 11 Mar 2011 09:05:46 +0100
Michael Jones wrote:
> Signed-off-by: Michael Jones
> ---
> Documentation/DocBook/v4l/pixfmt-y12.xml | 79
> ++
> include/linux/videodev2.h|1 +
> 2 files changed, 80 insertions(+), 0 deletions(-)
> create mo
Hello,
On Thursday, March 10, 2011 3:52 PM Arnd Bergmann wrote:
> On Friday 04 March 2011, Marek Szyprowski wrote:
> > From: Andrzej Pietrasiewicz
> >
> > This patch performs a complete rewrite of sysmmu driver for Samsung
> > platform:
> > - the new version introduces an api to construct devic
Hi Michael,
Thanks for the patch.
On Friday 11 March 2011 09:05:46 Michael Jones wrote:
> Signed-off-by: Michael Jones
> ---
> Documentation/DocBook/v4l/pixfmt-y12.xml | 79 +++
> include/linux/videodev2.h|1 +
> 2 files changed, 80 insertions(+), 0
To use the lane shifter, set different pixel formats at each end of
the link at the CCDC input.
Signed-off-by: Michael Jones
---
drivers/media/video/omap3-isp/isp.c |7 ++-
drivers/media/video/omap3-isp/isp.h |5 +-
drivers/media/video/omap3-isp/ispccdc.c | 27 ++--
driv
Signed-off-by: Michael Jones
Acked-by: Laurent Pinchart
---
drivers/media/video/omap3-isp/ispccdc.c |6 ++
drivers/media/video/omap3-isp/ispvideo.c | 12
2 files changed, 18 insertions(+), 0 deletions(-)
diff --git a/drivers/media/video/omap3-isp/ispccdc.c
b/drivers/med
Signed-off-by: Michael Jones
---
Documentation/DocBook/v4l/subdev-formats.xml | 59 ++
include/linux/v4l2-mediabus.h|7 ++-
2 files changed, 64 insertions(+), 2 deletions(-)
diff --git a/Documentation/DocBook/v4l/subdev-formats.xml
b/Documentation/D
Signed-off-by: Michael Jones
---
Documentation/DocBook/v4l/pixfmt-y12.xml | 79 ++
include/linux/videodev2.h|1 +
2 files changed, 80 insertions(+), 0 deletions(-)
create mode 100644 Documentation/DocBook/v4l/pixfmt-y12.xml
diff --git a/Document
Add support for the ISP's lane shifter. To use the shifter, set different
pixel formats at each end of the link at the CCDC input.
This has only been tested shifting Y12 and SBGGR12 from a parallel sensor to Y8
and SBGGR8 (respectively) at the CCDC input. Support has also been added for
other fo
56 matches
Mail list logo
