On 04/14/2011 12:00 AM, Russell King - ARM Linux wrote:
On Wed, Apr 13, 2011 at 10:56:39PM +0200, Janusz Krzysztofik wrote:
Dnia środa 13 kwiecień 2011 o 20:32:31 Russell King - ARM Linux
napisał(a):
On Wed, Apr 13, 2011 at 12:52:31PM +0200, Janusz Krzysztofik wrote:
Taking into account that
Laurent Pinchart wrote:
...
That's the ideal situation: sensors should not produce any data (or rather
any
transition on the VS/HS signals) when they're supposed to be stopped.
Unfortunately that's not always easy, as some dumb sensors (or sensor-like
hardware) can't be stopped. The ISP
Hello,
On Monday, April 18, 2011 4:13 PM Arnd Bergmann wrote:
On Monday 18 April 2011, Marek Szyprowski wrote:
From: Andrzej Pietrasiewicz andrze...@samsung.com
This patch performs a complete rewrite of sysmmu driver for Samsung
platform:
- simplified the resource management: no more
Hello,
On Monday, April 18, 2011 4:16 PM Arnd Bergmann wrote:
On Monday 18 April 2011, Marek Szyprowski wrote:
From: Andrzej Pietrasiewicz andrze...@samsung.com
This patch adds new videobuf2 memory allocator dedicated to devices that
supports IOMMU DMA mappings. A device with IOMMU
Hi,
I finally received my LI-5M03 for the Beagleboard which includes mt9p031 sensor.
I know Guennadi has somewhere an outdated version of a driver for it.
I would like to help you out on updating the driver so that it can be
submitted to mainline.
Guennadi please, if you could point me out to
On Tue, 19 Apr 2011, javier Martin wrote:
Hi,
I finally received my LI-5M03 for the Beagleboard which includes mt9p031
sensor.
I know Guennadi has somewhere an outdated version of a driver for it.
I would like to help you out on updating the driver so that it can be
submitted to
On Tue, Apr 19, 2011 at 11:02:34AM +0200, Marek Szyprowski wrote:
On Monday, April 18, 2011 4:16 PM Arnd Bergmann wrote:
My feeling is that this is not the right abstraction. Why can't you
just implement the regular dma-mapping.h interfaces for your IOMMU
so that the videobuf code can use
On 19 April 2011 11:19, Guennadi Liakhovetski g.liakhovet...@gmx.de wrote:
On Tue, 19 Apr 2011, javier Martin wrote:
Hi,
I finally received my LI-5M03 for the Beagleboard which includes mt9p031
sensor.
I know Guennadi has somewhere an outdated version of a driver for it.
I would like to
On Tue, 19 Apr 2011, javier Martin wrote:
On 19 April 2011 11:19, Guennadi Liakhovetski g.liakhovet...@gmx.de wrote:
On Tue, 19 Apr 2011, javier Martin wrote:
Hi,
I finally received my LI-5M03 for the Beagleboard which includes mt9p031
sensor.
I know Guennadi has somewhere an
Sure, feel free to grab this
http://download.open-technology.de/BeagleBoard_xM-MT9P031/
follow instructions in the text file and update the sources. I'll be
happy, if you manage to mainline it yourself, since I'm currently under a
pretty severe time-pressure.
Thanks, I'll do my best.
On Tuesday 19 April 2011 11:42:47 javier Martin wrote:
Sure, feel free to grab this
http://download.open-technology.de/BeagleBoard_xM-MT9P031/
follow instructions in the text file and update the sources. I'll be
happy, if you manage to mainline it yourself, since I'm currently under
All right,
just one more question, does this patch for mt9p031 apply in any
repository out there out of the box so that I can test my hardware
first?
Thank you.
--
Javier Martin
Vista Silicon S.L.
CDTUC - FASE C - Oficina S-345
Avda de los Castros s/n
39005- Santander. Cantabria. Spain
+34 942
On Tuesday 19 April 2011, Russell King - ARM Linux wrote:
On Tue, Apr 19, 2011 at 11:02:34AM +0200, Marek Szyprowski wrote:
On Monday, April 18, 2011 4:16 PM Arnd Bergmann wrote:
My feeling is that this is not the right abstraction. Why can't you
just implement the regular dma-mapping.h
Hello Guennadi,
*1*
I haven't reviewed your sources in detail, just two comments, regarding
something, that caught my eye:
+static struct platform_device rj65na20_camera = {
+ .name = soc-camera-pdrv-2M,
This name has to match with what's advertised in
Hi,
On Tuesday 12 April 2011 19:53:22 Zdeněk Materna wrote:
Hello,
I'm sorry for another mail. It works with quirks 128 and uncompressed
YUV format. Is there any way how to use compressed MJPEG? Should I try
compile never uvcvideo driver?
Could you post the output of lsusb -v for your
On Mon, 2011-04-18 at 18:48 -0400, Eric B Munson wrote:
On Mon, 18 Apr 2011, Andy Walls wrote:
Eric B Munson emun...@mgebm.net wrote:
On Mon, 11 Apr 2011, Eric B Munson wrote:
On Sun, 10 Apr 2011, Andy Walls wrote:
On Wed, 2011-04-06 at 13:28 -0400, Eric B Munson wrote:
Hi Sakari,
On Saturday 16 April 2011 10:51:27 Sakari Ailus wrote:
Hans Verkuil wrote:
Hans Verkuil wrote:
Whenever a control changes value an event is sent to anyone that
subscribed
to it.
Signed-off-by: Hans Verkuil hans.verk...@cisco.com
---
Hello Hans,
The camera module needs to be initialized by writing values to the
registers.
Do I need to write init function at the following?
static const struct v4l2_subdev_core_ops rj65na20_core_ops = {
.reset = rj65na20_reset,
[snip]
}
AFAICS neither soc_camera.c,
Em 19-04-2011 03:08, Jiri Slaby escreveu:
On 04/14/2011 12:00 AM, Russell King - ARM Linux wrote:
On Wed, Apr 13, 2011 at 10:56:39PM +0200, Janusz Krzysztofik wrote:
Dnia środa 13 kwiecień 2011 o 20:32:31 Russell King - ARM Linux
napisał(a):
On Wed, Apr 13, 2011 at 12:52:31PM +0200, Janusz
(adding Joerg to Cc)
On Tuesday 19 April 2011, Marek Szyprowski wrote:
These look wrong for a number of reasons:
* try_module_get(THIS_MODULE) makes no sense at all, the idea of the
try_module_get is to pin down another module that was calling down,
which I suppose is not needed
On Tue, Apr 19, 2011 at 08:49:50AM -0400, Arnd Bergmann wrote:
(adding Joerg to Cc)
On Tuesday 19 April 2011, Marek Szyprowski wrote:
* This extends the generic IOMMU API in platform specific ways, don't
do that.
This is certainly not a good idea. Please Cc me on IOMMU-API changes
Hello,
On Tuesday, April 19, 2011 2:50 PM Arnd Bergmann wrote:
On Tuesday 19 April 2011, Marek Szyprowski wrote:
These look wrong for a number of reasons:
* try_module_get(THIS_MODULE) makes no sense at all, the idea of the
try_module_get is to pin down another module that was
On Tuesday 19 April 2011, Roedel, Joerg wrote:
On Tue, Apr 19, 2011 at 08:49:50AM -0400, Arnd Bergmann wrote:
Ok, it looks I don't fully get how this iommu.h should be used. It looks
that there can be only one instance of iommu ops registered in the system,
so only one iommu driver can
On Apr 18, 2011, at 11:06 PM, Vincent McIntyre wrote:
Hi list,
I just (2011-04-19) upgraded to the current media_build with build.sh
commit bcfdefe9f4538abf12fca1cdb631c80e3d598026
Author: Mauro Carvalho Chehab mchehab@nehalem.(none)
Date: Sun Apr 17 08:21:25 2011 -0300
and hit a
On Tuesday 19 April 2011, Marek Szyprowski wrote:
1. change the runtime_pm subsystem to allow it to ignore some devices
in an easy way.
2. change the device layout if the sysmmu. If the iommu device is
a child of the device that it is responsible for, I guess you don't
have this
On Tue, Apr 19, 2011 at 10:28:39AM -0400, Arnd Bergmann wrote:
On Tuesday 19 April 2011, Roedel, Joerg wrote:
On Tue, Apr 19, 2011 at 08:49:50AM -0400, Arnd Bergmann wrote:
Ok, it looks I don't fully get how this iommu.h should be used. It looks
that there can be only one instance of
On function videobuf_pages_to_sg the statement sg_set_page(sglist[0],
pages[0], PAGE_SIZE -
offset, offset) will failed if if size is less than PAGE_SIZE.
Signed-off-by: Newson Edouard newson...@gmail.com
---
drivers/media/video/videobuf-dma-sg.c |5 +++--
1 files changed, 3 insertions(+),
On Tue, Apr 19, 2011 at 10:03:27AM -0400, Marek Szyprowski wrote:
Ok. I understand. IOMMU API is quite nice abstraction of the IOMMU chip.
dma-mapping API is something much more complex that creates the actual
mapping for various sets of the devices. IMHO the right direction will
be to create
On Tuesday 19 April 2011, Roedel, Joerg wrote:
Getting back to our video codec - it has 2 IOMMU controllers. The codec
hardware is able to address only 256MiB of space. Do you have an idea how
this can be handled with dma-mapping API? The only idea that comes to my
mind is to provide a
On Tue, 19 Apr 2011, Andy Walls wrote:
On Mon, 2011-04-18 at 18:48 -0400, Eric B Munson wrote:
On Mon, 18 Apr 2011, Andy Walls wrote:
Eric B Munson emun...@mgebm.net wrote:
On Mon, 11 Apr 2011, Eric B Munson wrote:
On Sun, 10 Apr 2011, Andy Walls wrote:
On Wed,
The following changes since commit
d58307d6a1e2441ebaf2d924df4346309ff84c7d:
[media] anysee: add more info about known board configs (2011-04-19 10:35:37
-0300)
are available in the git repository at:
git://linuxtv.org/jfrancois/gspca.git for_v2.6.40
Antonio Ospite (2):
Add Y10B, a
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:Tue Apr 19 19:00:44 CEST 2011
git hash:d58307d6a1e2441ebaf2d924df4346309ff84c7d
gcc version: i686-linux-gcc (GCC)
Per Sensoray Model 314 ( http://www.sensoray.com/products/314.htm )
customer's request, we have tested 314 with LiPPERT's Cool XpressRunner-GS45
( http://www.lippertembedded.com/en/lipperts-cool-xpressrunner-gs45.html )
SBC (Single Board Computer).
Per customer's request and for their
Per Sensoray Model 311 ( http://www.sensoray.com/products/311.htm )
customer's request, we have tested 311 with LiPPERT's Cool XpressRunner-GS45
( http://www.lippertembedded.com/en/lipperts-cool-xpressrunner-gs45.html )
SBC (Single Board Computer).
Per customer's request and for their
On Tue, 19 Apr 2011 20:20:29 +0200
Jean-Francois Moine moin...@free.fr wrote:
The following changes since commit
d58307d6a1e2441ebaf2d924df4346309ff84c7d:
[media] anysee: add more info about known board configs (2011-04-19
10:35:37 -0300)
are available in the git repository at:
Em 19-04-2011 16:54, Antonio Ospite escreveu:
On Tue, 19 Apr 2011 20:20:29 +0200
Jean-Francois Moine moin...@free.fr wrote:
The following changes since commit
d58307d6a1e2441ebaf2d924df4346309ff84c7d:
[media] anysee: add more info about known board configs (2011-04-19
10:35:37 -0300)
Em 04-04-2011 17:18, stefan.rin...@arcor.de escreveu:
From: Stefan Ringel stefan.rin...@arcor.de
add mts parameter
Stefan,
The MTS config depends on the specific board design (generally present on
mono NTSC cards). So, it should be inside the cards struct, and not
provided as an userspace
Em 04-04-2011 17:18, stefan.rin...@arcor.de escreveu:
From: Stefan Ringel stefan.rin...@arcor.de
add dtv78 parameter
The dtv78 entry is a hack meant for card usage in Australia, that
speeds up channel detection there. Again, it should be specified
only when needed, and at per-board basis.
IR additions and misc minor media_tree fixes for 2.6.40. There's an input.h
patch included in here, which was merged in 2.6.39-rc4, that the patch
just after it depends upon, wasn't quite sure how to handle that, since it
wasn't already in the staging/for_v2.6.40 branch that this is on top of...
Em 04-04-2011 17:18, stefan.rin...@arcor.de escreveu:
From: Stefan Ringel stefan.rin...@arcor.de
add audio mode parameter
Why we need a parameter for it? It should be determined based on
the standard.
Signed-off-by: Stefan Ringel stefan.rin...@arcor.de
---
On Tue, 2011-04-19 at 13:12 -0400, Eric B Munson wrote:
On Tue, 19 Apr 2011, Andy Walls wrote:
Have you used v4l2-ctl or ivtv-tune to tune to the proper tv channel
(the driver defaults to US channel 4)?
emunson@grover:~$ v4l2-ctl -F
Frequency: 0 (0.00 MHz)
41 matches
Mail list logo
