(Resending as the first try apparently hasn't made it onto the mailing-list)
On 06.06.2015 16:17, Antti Palosaari wrote:
On 06/06/2015 05:07 PM, Hurda wrote:
Thanks, this worked.
The kernel of Ubuntu 15.04 already was compiled with dynamic debug,
which saved
me a lot of time.
The driver is
Hi Hans,
On Monday 15 June 2015 12:25:37 Hans Verkuil wrote:
On 06/15/2015 12:08 AM, Laurent Pinchart wrote:
On Thursday 09 April 2015 12:21:23 Hans Verkuil wrote:
From: Hans Verkuil hans.verk...@cisco.com
The g_mbus_fmt video op is a duplicate of the pad op. Replace all uses
by the
Hi,
Sort of a basic v4l2/soc-camera question.
First time posting on this mailing list; Let me know if this not the
right forum to post.
I am working on an old platform software based on kernel 3.6;
in my case, I have host driver and an i2c sub device driver (based on 5640)
Both are .ko (loadable
The Camera Adaptation Layer (CAL) is a block which consists of a dual
port CSI2/MIPI camera capture engine.
Port #0 can handle CSI2 camera connected to up to 4 data lanes.
Port #1 can handle CSI2 camera connected to up to 2 data lanes.
The driver implements the required API/ioctls to be V4L2
Device Tree bindings for the Camera Adaptation Layer (CAL) driver
Signed-off-by: Benoit Parrot bpar...@ti.com
---
Documentation/devicetree/bindings/media/ti-cal.txt | 70 ++
1 file changed, 70 insertions(+)
create mode 100644
The Camera Adaptation Layer (CAL) is a block which consists of a dual
port CSI2/MIPI camera capture engine.
This camera engine is currently found on DRA72xx family of devices.
Port #0 can handle CSI2 camera connected to up to 4 data lanes.
Port #1 can handle CSI2 camera connected to up to 2 data
Hello guys,
please find out down this email patch to support EVOLVEO XtraTV stick.
This tuner is for android phones with microusb connecter, however with
reduction it works perfectly with linux kernel:
The device identify itself at USB bus as Bus 002 Device 004: ID
1f4d:a115 G-Tek Electronics
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 Jun 17 04:00:18 CEST 2015
git branch: test
git hash: e42c8c6eb456f8978de417ea349eef676ef4385c
gcc
Hello,
Mrs. Liliane picked you. For details email her
directly: lilbetencou...@hotmail.com
--
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 http://vger.kernel.org/majordomo-info.html
On 05/04/2015 07:32 PM, Kamil Debski wrote:
Hi,
The sixth version of this patchset addresses recent comments on the mailing
list. Please see the changelog below for details.
Just in case people are wondering what happened to this: about a month ago I
took over from Kamil and I am working
Hi Ricardo,
This patch series looks good to me. I'll wait a bit to see if anyone else has
comments. If not, then I'll merge for 4.3.
Regards,
Hans
On 06/12/2015 06:46 PM, Ricardo Ribalda Delgado wrote:
Integer controls provide a way to get their default/initial value, but
any other
* Gabor Z. Papp gzpapp.li...@gmail.com:
| I would like to use my Pinnacle Dazzle DVC usb encoder with kernels
| 3.10-4.0, but I'm getting the same error all the time.
| Latest working kernel is the 3.4 line.
| What happend with the driver?
Should I provide more details than the dmesg output?
Let me fill in the subject line so people know what it is about :-)
Hans
On 06/16/15 08:22, Hans Verkuil wrote:
On 05/04/2015 07:32 PM, Kamil Debski wrote:
Hi,
The sixth version of this patchset addresses recent comments on the mailing
list. Please see the changelog below for
Hello Hans
On Tue, Jun 16, 2015 at 8:09 AM, Hans Verkuil hverk...@xs4all.nl wrote:
Hi Ricardo,
This patch series looks good to me. I'll wait a bit to see if anyone else has
comments. If not, then I'll merge for 4.3.
If this is merged in 4.3 I need to fix the documentation.
Please use the
Em Tue, 16 Jun 2015 08:54:58 +0200
Gabor Z. Papp gzpapp.li...@gmail.com escreveu:
* Gabor Z. Papp gzpapp.li...@gmail.com:
| I would like to use my Pinnacle Dazzle DVC usb encoder with kernels
| 3.10-4.0, but I'm getting the same error all the time.
| Latest working kernel is the 3.4 line.
Add documentation for new ioctl.
Signed-off-by: Ricardo Ribalda Delgado ricardo.riba...@gmail.com
---
v4:
-Add Author information
-Set kernel version to 4,3
Documentation/DocBook/media/v4l/v4l2.xml | 20
.../DocBook/media/v4l/vidioc-g-ext-ctrls.xml | 13
Since when we start discussions about the usage Media Controller for
complex hardware, one thing become clear: the way it is, MC fails to
map anything different than capture/output/m2m video-only streaming.
The point is that MC has entities named as devnodes, but the only
devnode used (before the
This is a preliminary patch in order to add support for ALSA.
It replaces all current i2c access with regmap.
Signed-off-by: Pablo Anton pablo.an...@veo-labs.com
Signed-off-by: Jean-Michel Hautbois jean-michel.hautb...@veo-labs.com
---
v2: Rebase after renaming
drivers/media/i2c/adv7604.c | 337
Mauro Carvalho Chehab wrote:
Em Tue, 16 Jun 2015 08:54:58 +0200 Gabor Z. Papp
gzpapp.li...@gmail.com escreveu:
* Gabor Z. Papp gzpapp.li...@gmail.com:
| I would like to use my Pinnacle Dazzle DVC usb encoder with
kernels | 3.10-4.0, but I'm getting the same error all the time.
| Latest
GTF standards document specifies to use round() for v_lines_rnd
calculations. This change will affect only if image height is odd.
Cc: Hans Verkuil hans.verk...@cisco.com
Signed-off-by: Prashant Laddha prlad...@cisco.com
---
utils/v4l2-ctl/v4l2-ctl-modes.cpp | 2 +-
1 file changed, 1
For interlaced format, the standards equation use interlace = 0.5.
Modified the implementation to handle this fraction correctly.
Cc: Hans Verkuil hans.verk...@cisco.com
Signed-off-by: Prashant Laddha prlad...@cisco.com
---
utils/v4l2-ctl/v4l2-ctl-modes.cpp | 16 ++--
1 file changed,
Hi,
Recently, while testing reduced blanking implementation, I came across few
differences
between the results produced by cvt, gtf modeline implementation and results
given by
standards spreadsheet. The resultant timing differences were minor and seen
only for
few input combinations. However,
In case of CVT reduced blanking, pixel clock calculation does not
use h period estimates, it rather directly uses refresh rate and
total vertical lines. This difference can lead to a minor mismatch
between the pixel clocks calculated by v4l2-utils and the standards
spreadsheet.
Cc: Hans Verkuil
To support the timings calculations for reduced blanking version 2
(RB v2), extended the command line options to include flag indicating
whether to use RB V2 or not. Updated the command usage for the same.
Cc: Hans Verkuil hans.verk...@cisco.com
Signed-off-by: Prashant Laddha prlad...@cisco.com
Added support for reduced blanking version 2 (RB V2) in cvt
modeline calculations. Recently, RB V2 support was added to
v4l2-dv-timings. This patch follows up on that work.
Extended calc_cvt_modeline() api to pass an additional flag to
indicate the version of reduced blanking. This flag takes
Hi,
Please find patches adding support for reduced blanking v2 (RB v2) in cvt
modeline
calculations in v4l2-utils. Recently, RB v2 support was added to
v4l2-dv-timings and
RB v2 support in v4l2-utils is a follow up on that work. Please review.
Regards,
Prashant
Prashant Laddha (2):
On Fri 2015-06-12 09:47:28, Uwe Kleine-König wrote:
Without setting the direction of a gpio to output a call to
gpiod_set_value doesn't have a defined outcome.
Furthermore this is one caller less that stops us making the flags
argument to gpiod_get*() mandatory.
Signed-off-by: Uwe
27 matches
Mail list logo
