hermann pitton a écrit :
Hi Tom,
Am Mittwoch, den 23.12.2009, 13:17 +0100 schrieb tomloh...@gmail.com:
Some news,
Hi hermann,
we are this results :
with
&tda827x_cfg_0, &tda827x_cfg_1 or &tda827x_cfg_2
we have a perfect image without sound on the analogic part (test with
mp
On Wed, 2009-12-23 at 14:17 +0100, Pawel Osciak wrote:
> A mem-to-mem device is a device that uses memory buffers passed by
> userspace applications for both source and destination data. This is
> different from existing drivers, which use memory buffers for only one
> of those at once.
>
> In ter
I wrote several patches those days in order to allow dvb-apps to properly
parse ISDB-T channel.conf.
On ISDB-T, there are several new parameters, so the parsing is more complex
than all the other currently supported video standards.
I've added the changes at:
http://linuxtv.org/hg/~mchehab/dvb-a
On sre, 2009-12-23 at 23:24 +0400, Manu Abraham wrote:
> > Aljaz, do you have the module mantis.ko?
> There was a build issue when i posted the link originally, but it had
> been fixed..
>
> m...@manu-04:/stor/work/merge/v4l-dvb/v4l> ls *.ko |grep mantis
> mantis_core.ko
> mantis.ko
>
Yup, I hav
Hi Tom,
Am Mittwoch, den 23.12.2009, 13:17 +0100 schrieb tomloh...@gmail.com:
> Some news,
> > Hi hermann,
> >
> > we are this results :
> >
> > with
> >
> > &tda827x_cfg_0, &tda827x_cfg_1 or &tda827x_cfg_2
> >
>
> > we have a perfect image without sound on the analogic part (test with
> > mplay
Hi,
one of the sensors managed by the gspca_gl860 has some weird
resolutions : 800 x 598 and 1600 x 1198. To set these resolutions to
800 x 600 and 1600 x 1200 causes a flickering effect because of both
missing lines of data from the sensor. Thus a stupid question, does
the resolutions are these c
Hello,
On Wed, Dec 23, 2009 at 1:08 PM, Pawel Osciak wrote:
> The rotator device present on Samsung S3C and S5P series SoCs allows image
> rotation and flipping. It requires contiguous memory buffers to operate,
> as it does not have scatter-gather support. It is also an example of
> a memory-to-
Manu Abraham schrieb:
> On Thu, Dec 24, 2009 at 12:01 AM, Ruediger Dohmhardt
> wrote:
>
>> Manu Abraham schrieb:
>>
>>> Hello Ruediger,
>>>
>>> On Wed, Dec 23, 2009 at 11:04 PM, Ruediger Dohmhardt
>>> wrote:
>>>
>>>
Aljaž Prusnik schrieb:
> If using the
On Thu, Dec 24, 2009 at 12:01 AM, Ruediger Dohmhardt
wrote:
> Manu Abraham schrieb:
>> Hello Ruediger,
>>
>> On Wed, Dec 23, 2009 at 11:04 PM, Ruediger Dohmhardt
>> wrote:
>>
>>> Aljaž Prusnik schrieb:
>>>
If using the http://jusst.de/hg/v4l-dvb tree, everything compiles ok,
module load
Manu Abraham schrieb:
> Hello Ruediger,
>
> On Wed, Dec 23, 2009 at 11:04 PM, Ruediger Dohmhardt
> wrote:
>
>> Aljaž Prusnik schrieb:
>>
>>> If using the http://jusst.de/hg/v4l-dvb tree, everything compiles ok,
>>> module loads, but there is no remote anywhere (there is an IR folder
>>> wi
Hello Ruediger,
On Wed, Dec 23, 2009 at 11:04 PM, Ruediger Dohmhardt
wrote:
> Aljaž Prusnik schrieb:
>>
>> If using the http://jusst.de/hg/v4l-dvb tree, everything compiles ok,
>> module loads, but there is no remote anywhere (there is an IR folder
>> with the ir-common.ko file, under common ther
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:Wed Dec 23 19:00:13 CET 2009
path:http://www.linuxtv.org/hg/v4l-dvb
changeset: 13842:4506e2d54126
gcc version: gcc (
Aljaž Prusnik schrieb:
>
> If using the http://jusst.de/hg/v4l-dvb tree, everything compiles ok,
> module loads, but there is no remote anywhere (there is an IR folder
> with the ir-common.ko file, under common there is not).
>
>
Aljaz, do you have the module mantis.ko?
Ruediger
--
To unsubscr
> -Original Message-
> From: Karicheri, Muralidharan
> Sent: Monday, December 21, 2009 7:00 PM
> To: Hiremath, Vaibhav; linux-media@vger.kernel.org
> Cc: hverk...@xs4all.nl
> Subject: RE: [PATCH] Davinci VPFE Capture: Add Suspend/Resume
> Support
>
> Vaibhav,
>
> Did you address my comme
On sre, 2009-12-23 at 17:53 +0200, Igor M. Liplianin wrote:
> Since module ir-common.ko moved to IR directory just remove old one.
>
> rm /lib/modules/$(uname -r)/kernel/drivers/media/common/ir-common.ko
>
> Also it would be good to do
>
> make remove
>
> Then again build and instal
Hi,
I would like to add support for cached user mapping to
videobuf-dma-contig.c.
For enabling this, "vma->vm_page_prot =
pgprot_noncached(vma->vm_page_prot);" line should be removed.
But now we should ensure user mapping cache coherency.
For that, for a camera we should :
- invalidate cache bef
On 23 декабря 2009 16:30:16 Aljaž Prusnik wrote:
> In the same vein, I'm interested in this one, namely:
>
> I have tried the http://jusst.de/hg/v4l-dvb, since recently the
> liplianin mantis driver is not working (unknown symbols...).
>
> However, the problems I have as opposed to the previously w
Hans,
The change is because of the void * type that we use. Since ccdc parameter
structures are different for different IPs, a constant type for this arg
is not possible. The ccdc driver needs the pointer to structure. But the
v4l2 core tries to copies 4 bytes of data from the void * pointed loca
On Wednesday 23 December 2009 14:17:32 Pawel Osciak wrote:
> Hello,
>
> this is the second version of the proposed implementation for mem-to-mem
> memory
> device framework. Your comments are very welcome.
Hi Pawel,
Thank you for working on this! It's much appreciated. Now I've noticed that
pat
In the same vein, I'm interested in this one, namely:
I have tried the http://jusst.de/hg/v4l-dvb, since recently the
liplianin mantis driver is not working (unknown symbols...).
However, the problems I have as opposed to the previously working driver
are:
- the module does not install in a way
Hi Murali,
Sorry for the long delay in reviewing this patch series. I've been very busy,
first at work, and now for Christmas preparations (and occasionally I'd like
to relax as well :-) ).
I'm OK with the other patches in this series, but I do have a few comments
on this one: I noticed that you
This is an example application for testing mem-to-mem framework using
mem2mem-testdev device.
It is intended to be executed multiple times in parallel to test multi-instance
operation and scheduling. Each process can be configured differently using
command-line arguments.
The application opens vi
A mem-to-mem device is a device that uses memory buffers passed by
userspace applications for both source and destination data. This is
different from existing drivers, which use memory buffers for only one
of those at once.
In terms of V4L2 such a device would be both of OUTPUT and CAPTURE type.
This is a virtual device driver for testing the mem-to-mem V4L2 framework.
It simulates a device that uses memory buffers for both source and
destination, processes the data and issues an "IRQ" (simulated by a timer).
The device is capable of multi-instance, multi-buffer-per-transaction
operation (
Hello,
this is the second version of the proposed implementation for mem-to-mem memory
device framework. Your comments are very welcome.
In v2.1:
I am very sorry for the resend, but somehow an orphaned endif found its way to
Kconfig during the rebase.
Changes since v1:
- v4l2_m2m_buf_queue() now
The C99 specification states in section 6.11.5:
The placement of a storage-class specifier other than at the beginning
of the declaration specifiers in a declaration is an obsolescent
feature.
Signed-off-by: Tobias Klauser
Cc: Erik Andren
Cc: Jean-Francois Moine
---
drivers/media/video/gspca/
The C99 specification states in section 6.11.5:
The placement of a storage-class specifier other than at the beginning
of the declaration specifiers in a declaration is an obsolescent
feature.
Signed-off-by: Tobias Klauser
---
drivers/media/video/rj54n1cb0c.c | 12 ++--
1 files change
The C99 specification states in section 6.11.5:
The placement of a storage-class specifier other than at the beginning
of the declaration specifiers in a declaration is an obsolescent
feature.
Signed-off-by: Tobias Klauser
---
drivers/media/dvb/dvb-usb/friio-fe.c |2 +-
1 files changed, 1 i
Some news,
Hi hermann,
we are this results :
with
&tda827x_cfg_0, &tda827x_cfg_1 or &tda827x_cfg_2
we have a perfect image without sound on the analogic part (test with
mplayer),
a partial result with dvb-t : we need to initialize first with
analogic (with cold boot, the card doesn't wor
Hi,
I'm trying to compile v4l on Fedora 11, latest available RPM kernel, but
there are many problem.
I've tried to go in the past with revision (hg update ), and
the last revision I can compile without problem is 13823.
Is this a know bug/error due to have not last kernel?
Thanks for the help
Hi Andy,
Andy Walls wrote:
+int v4l2_event_pending(struct v4l2_fh *fh)
+{
+ struct v4l2_events *events =&fh->events;
+ unsigned long flags;
+ int ret;
+
+ spin_lock_irqsave(&events->lock, flags);
+ ret = !list_empty(&events->available);
+ spin_unlock_irqrestor
The rotator device present on Samsung S3C and S5P series SoCs allows image
rotation and flipping. It requires contiguous memory buffers to operate,
as it does not have scatter-gather support. It is also an example of
a memory-to-memory device, and so uses the mem-2-mem device V4L2 framework.
Signe
This is an example application for testing the S3C/S5P rotator device.
It uses framebuffer memory for its source and destination buffers, as the
device requires them to be in contiguous memory.
Source image is read from a file passed as an argument and saved to another
file, which name is also pass
Hello,
this is a driver for Samsung S3C/S5P series image rotator device driver.
This driver utilizes the proposed memory-to-memory V4L2 framework, just posted
by me in the previous patch series.
An example application for testing the device is also included.
This series contains:
[PATCH 1/2] [
Add S3C/S5P rotator platform device.
Signed-off-by: Pawel Osciak
Signed-off-by: Sylwester Nawrocki
Reviewed-by: Marek Szyprowski
Reviewed-by: Kyungmin Park
---
arch/arm/mach-s3c6400/include/mach/map.h |2 +
arch/arm/plat-s3c/Kconfig |5 ++
arch/arm/plat-s3c/Ma
This is an example application for testing mem-to-mem framework using
mem2mem-testdev device.
It is intended to be executed multiple times in parallel to test multi-instance
operation and scheduling. Each process can be configured differently using
command-line arguments.
The application opens vi
This is a virtual device driver for testing the mem-to-mem V4L2 framework.
It simulates a device that uses memory buffers for both source and
destination, processes the data and issues an "IRQ" (simulated by a timer).
The device is capable of multi-instance, multi-buffer-per-transaction
operation (
A mem-to-mem device is a device that uses memory buffers passed by
userspace applications for both source and destination data. This is
different from existing drivers, which use memory buffers for only one
of those at once.
In terms of V4L2 such a device would be both of OUTPUT and CAPTURE type.
Hello,
this is the second version of the proposed implementation for mem-to-mem memory
device framework. Your comments are very welcome.
Changes since v1:
- v4l2_m2m_buf_queue() now requires m2m_ctx as its argument
- video_queue private data stores driver private data
- a new submenu in kconfig f
39 matches
Mail list logo
