Hi Antti.
My suspend / resume patch implemented Kaffeine continues viewing channel after
resume.
Some of the ideas could be still useful:
http://www.spinics.net/lists/linux-dvb/msg19651.html
Rest of this email has a more thorough description.
Regards,
Marko Ristola
On 06/28/2012 03:33 AM,
-- Oorspronkelijk bericht --
From: Olivier GRENIE olivier.gre...@parrot.com
To: cedric.dew...@telfort.nl cedric.dew...@telfort.nl,
linux-media@vger.kernel.org linux-media@vger.kernel.org
Date: Fri, 29 Jun 2012 15:25:00 +0100
Subject: RE: dib0700 can't enable debug messages
Hello,
did you
This is an IVC-100-LEG from ebay
http://www.ebay.co.uk/itm/370609954186?ssPageName=STRK:MEWNX:IT_trksid=p3984.m1497.l2649
It works with insmod option card=110 which is for the vanilla IVC-100
[8.257854] Linux video capture interface: v2.00
[8.264465] bttv: driver version 0.9.18 loaded
On 05/15/2012 10:44 PM, Sylwester Nawrocki wrote:
Remove documentation chunk of not existent V4L2_CID_AUTO_FOCUS_AREA
control. It fixes following build error:
Error: no ID for constraint linkend: v4l2-auto-focus-area.
Ping.
This patch is still not in linux-next (and marked as Changes
On Mon, Jun 25, 2012 at 09:14:41PM +0200, Sylwester Nawrocki wrote:
Signed-off-by: Sylwester Nawrocki sylvester.nawro...@gmail.com
---
Added more precise description of what is being removed.
---
Documentation/feature-removal-schedule.txt | 18 ++
1 files changed, 18
Hi,
Changed since the last time:
- Added V4L2 subdev backward compatibility definitions for *_ACTUAL
targets (patch 2) and flags (patch 5). These are needed since the changes
won't make it to 3.5.
- Added Sylwester's patch for feature removal documentation (patch 7).
Kind regards,
--
Unify flags on the selection interfaces on V4L2 and V4L2 subdev. Flags are
very similar to targets in this case: there are more similarities than
differences between the two interfaces.
Signed-off-by: Sakari Ailus sakari.ai...@iki.fi
---
drivers/media/video/omap3isp/ispccdc.c|2 +-
Signed-off-by: Sakari Ailus sakari.ai...@iki.fi
Signed-off-by: Sylwester Nawrocki s.nawro...@samsung.com
---
drivers/media/video/omap3isp/ispccdc.c |6 +-
drivers/media/video/omap3isp/isppreview.c |6 +-
drivers/media/video/omap3isp/ispresizer.c |6 +-
The string _ACTUAL does not say anything more about the target names. Drop
it. V4L2 selection API was changed by V4L: Remove _ACTIVE from the
selection target name definitions by Sylwester Nawrocki. This patch does
the same for the V4L2 subdev API.
Signed-off-by: Sakari Ailus sakari.ai...@iki.fi
From: Sylwester Nawrocki sylvester.nawro...@gmail.com
After unification of the V4L2 and V4L2 subdev selection targets and flags
the old flags are no longer required. Thus they can be removed. However, as
the API is present in a kernel release, this must go through the feature
removal process.
Both V4L2 and V4L2 subdev interface have very similar selection APIs with
differences foremost related to in-memory and media bus formats. However,
the selection targets are the same for both. Most targets are and in the
future will likely continue to be more the same than with any differences.
The API reference documents that the KEEP_CONFIG flag tells the
configuration should not be propagated by the driver whereas the interface
documentation (dev-subdev.xml) prohibited any changes to the rest of the
pipeline. Resolve the conflict by changing the API reference to disallow
changes.
From: Sylwester Nawrocki sylvester.nawro...@gmail.com
This patch drops the _ACTIVE part from the selection target names
as a prerequisite to unify the selection target names across the subdev
and regular video node API.
The meaning of V4L2_SEL_TGT_*_ACTIVE and V4L2_SUBDEV_SEL_TGT_*_ACTUAL
As for the selection targets, the selection flags are now the same on V4L2
and V4L2 subdev interfaces. Also document them so.
Signed-off-by: Sakari Ailus sakari.ai...@iki.fi
---
Documentation/DocBook/media/v4l/dev-subdev.xml |6 +-
Documentation/DocBook/media/v4l/selection-api.xml |
Change the firmware logic to use request_firmware_nowait(), and
to preserve the loaded firmwares in memory, to reduce the risk
of troubles with buggy userspace apps.
With this change, while the firmware is being loaded, the driver
will return -EAGAIN to any calls. If, for some reason, firmware
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:Sat Jun 30 19:02:20 CEST 2012
git hash:704a28e88ab6c9cfe393ae626b612cab8b46028e
gcc version: i686-linux-gcc
Currently mem-to-mem devices are identified through V4L2_CAP_VIDEO_CAPTURE
and V4L2_CAP_VIDEO_OUTPUT capabilities. This is not reliable and may
lead to false identification of mem-to-mem devices as video capture
or output devices, if an application doesn't check both flags.
As a follow up to an
This patch adds new V4L2_CAP_VIDEO_M2M and V4L2_CAP_VIDEO_M2M_MPLANE capability
flags that are intended to be used for memory-to-memory (M2M) devices, instead
of ORed V4L2_CAP_VIDEO_CAPTURE and V4L2_CAP_VIDEO_OUTPUT.
V4L2_CAP_VIDEO_M2M flag is added at the drivers, CAPTURE and OUTPUT capability
Identifying a memory-to-memory video device through an ORed output and capture
capability flags is not reliable. Schedule this for removal.
Signed-off-by: Sylwester Nawrocki sylvester.nawro...@gmail.com
---
Documentation/feature-removal-schedule.txt | 14 ++
1 files changed, 14
Hi Sakari,
On 06/30/2012 07:03 PM, Sakari Ailus wrote:
The string _ACTUAL does not say anything more about the target names. Drop
it. V4L2 selection API was changed by V4L: Remove _ACTIVE from the
selection target name definitions by Sylwester Nawrocki. This patch does
the same for the V4L2
Hi Sakari,
On 06/30/2012 07:03 PM, Sakari Ailus wrote:
The API reference documents that the KEEP_CONFIG flag tells the
configuration should not be propagated by the driver whereas the interface
documentation (dev-subdev.xml) prohibited any changes to the rest of the
pipeline. Resolve the
Hi Sakari,
On 06/30/2012 07:03 PM, Sakari Ailus wrote:
Unify flags on the selection interfaces on V4L2 and V4L2 subdev. Flags are
very similar to targets in this case: there are more similarities than
differences between the two interfaces.
Signed-off-by: Sakari Ailussakari.ai...@iki.fi
Hi Sakari,
On 06/30/2012 07:03 PM, Sakari Ailus wrote:
Would be good to add at least a small description here, that this
patch converts users of V4L2_SUBDEV_SEL_TGT_* to use V4L2_SEL_TGT_*,
or something similar.
Signed-off-by: Sakari Ailussakari.ai...@iki.fi
Signed-off-by: Sylwester
On 06/30/2012 07:03 PM, Sakari Ailus wrote:
Both V4L2 and V4L2 subdev interface have very similar selection APIs with
differences foremost related to in-memory and media bus formats. However,
the selection targets are the same for both. Most targets are and in the
future will likely continue to
On 06/30/2012 07:03 PM, Sakari Ailus wrote:
As for the selection targets, the selection flags are now the same on V4L2
and V4L2 subdev interfaces. Also document them so.
Signed-off-by: Sakari Ailussakari.ai...@iki.fi
---
Documentation/DocBook/media/v4l/dev-subdev.xml |6 +-
Hi,
this is an updated version of my patch.
Thanks to Mauro Carvalho Chehab and Ralph Metzler for the suggestions.
Regards,
Martin
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Currently there are two different implementations (in the firmware) for
the QAM demodulator command: one takes 4 and the other takes 2 parameters.
The driver shows an error in dmesg When using the 4-parameter command with
firmware that implements the 2-parameter command.
Unfortunately this happens
This patch simply fixes some logging calls:
- Use KERN_INFO when printing the chip status.
- Add a missing space when logging the drxk_gate_ctrl call.
- Use the same logging text as always if the scu_command in GetQAMLockStatus
fails.
Signed-off-by: Martin Blumenstingl
Em 30-06-2012 19:32, Martin Blumenstingl escreveu:
Currently there are two different implementations (in the firmware) for
the QAM demodulator command: one takes 4 and the other takes 2 parameters.
The driver shows an error in dmesg When using the 4-parameter command with
firmware that
29 matches
Mail list logo
