Hello,
Le Wed, 21 Dec 2011 13:14:55 -0500,
Full Name danew...@excite.com a écrit :
I just got an EasyCAP usb device with component and S-video inputs, and it
doesn't match what I was expecting from reading lists about drivers.
Be careful, there are several devices that the commercial name
Hi,
are there any comments on this?
May I suppose you agree and it will be applied?
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 25 32 60
www.vista-silicon.com
--
To unsubscribe from this list:
Hello,
On Wednesday, December 14, 2011 3:00 PM Ming Lei wrote:
DMA contig memory resource is very limited and precious, also
accessing to it from CPU is very slow on some platform.
For some cases(such as the comming face detection driver), DMA Streaming
buffer is enough, so introduce
Hi James,
On Thursday 22 December 2011 07:23:56 James wrote:
Tried the new yavta but encountered a different situation.
yavta -p -f Y12 -s 640x512 -n 2 --capture=10 --skip 5 -F `media-ctl -e
OMAP3 ISP CCDC output` --file=./DCIM/Y12
yavta will hang for infinite time and only Ctrl+C will
From: Márton Németh nm...@freemail.hu
When a V4L2 ioctl is executed the memory provided by the caller in user space
is copied to the kernel space in video_usercopy() function. To find out
how many bytes has to be copied the check_array_args() helper function is used.
This patch adds a check for
Hi Guennadi,
On Wednesday 21 December 2011 23:46:24 Guennadi Liakhovetski wrote:
On Wed, 21 Dec 2011, Laurent Pinchart wrote:
On Wednesday 21 December 2011 14:56:36 Hadli, Manjunath wrote:
On Wed, Dec 21, 2011 at 05:32:08, Laurent Pinchart wrote:
On Friday 16 December 2011 14:42:48
Hello,
On Thursday, December 22, 2011 7:29 AM Dan Carpenter wrote:
I changed the function definitions for dt3155_queue_setup() to match the
newer API. The dt3155_start_streaming() function didn't do anything so
I just removed it.
This silences the following gcc warnings:
Convert the existing data struct to use the QAM modulation macros,
instead of assuming that they're numbered from 0 to 5.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
drivers/media/dvb/frontends/tda10023.c | 66 +---
1 files changed, 43 insertions(+),
Instead of using the same delivery system for both Annex A and
Annex C, split them into two separate ones. This helps to support
devices that only support Annex A.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
Documentation/DocBook/media/dvb/dvbproperty.xml | 11 +--
The difference between Annex A and C is the roll-off factor.
Properly implement it inside the driver, using the information
provided by Andreas.
Thanks-to: Andreas Oberriter o...@linuxtv.org
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
drivers/media/dvb/frontends/tda10023.c | 46
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
drivers/media/dvb/frontends/drxk_hard.c | 28
1 files changed, 28 insertions(+), 0 deletions(-)
diff --git a/drivers/media/dvb/frontends/drxk_hard.c
b/drivers/media/dvb/frontends/drxk_hard.c
index
Instead of using DVBv3 parameters, rely on DVBv5 parameters to
set the tuner.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
drivers/media/common/tuners/tuner-xc2028.c | 83
1 files changed, 36 insertions(+), 47 deletions(-)
diff --git
Instead of using DVBv3 parameters, rely on DVBv5 parameters to
set the tuner.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
drivers/media/common/tuners/tda827x.c | 49 +++--
1 files changed, 28 insertions(+), 21 deletions(-)
diff --git
Instead of using DVBv3 parameters, rely on DVBv5 parameters to
set the tuner.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
drivers/media/common/tuners/mxl5007t.c | 53 ++--
1 files changed, 23 insertions(+), 30 deletions(-)
diff --git
With the previous code, when the bandwidth changes, but using
the same delivery system, the code used to discard such changes.
This was happening because the bandwidth calculus were after the
check for delivery system changes. The previous patch changed
it to happen together with the delivery
Instead of using DVBv3 parameters, rely on DVBv5 parameters to
set the tuner.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
drivers/media/dvb/bt8xx/dvb-bt8xx.c | 31 ---
1 files changed, 16 insertions(+), 15 deletions(-)
diff --git
Instead of using DVBv3 parameters, rely on DVBv5 parameters to
set the tuner.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
drivers/media/common/tuners/mc44s803.c |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/media/common/tuners/mc44s803.c
Instead of using DVBv3 parameters, rely on DVBv5 parameters to
set the tuner.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
drivers/media/common/tuners/mt2266.c | 20 +---
1 files changed, 9 insertions(+), 11 deletions(-)
diff --git
Instead of using DVBv3 parameters, rely on DVBv5 parameters to
set the tuner.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
drivers/media/common/tuners/max2165.c | 60
1 files changed, 37 insertions(+), 23 deletions(-)
diff --git
Convert the existing data struct to use the QAM modulation macros,
instead of assuming that they're numbered from 0 to 5.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
drivers/media/dvb/frontends/tda10021.c | 59
1 files changed, 37 insertions(+),
Instead of using DVBv3 parameters, rely on DVBv5 parameters to
set the tuner.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
drivers/media/common/tuners/tda18218.c | 15 ++-
1 files changed, 6 insertions(+), 9 deletions(-)
diff --git
Instead of using DVBv3 parameters, rely on DVBv5 parameters to
set the tuner.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
drivers/media/common/tuners/tda18271-fe.c | 74 +---
1 files changed, 34 insertions(+), 40 deletions(-)
diff --git
Instead of using a roll-off factor, change DRX-K friends to select
the bandwidth filter and the Nyquist half roll-off via delivery system.
This provides a cleaner support for Annex A/C switch.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
drivers/media/common/tuners/xc5000.c
From: Manu Abraham abraham.m...@gmail.com
Use a unique delivery system identifier for DVBC_ANNEX_C, just like any
other.
DVBC_ANNEX_A and DVBC_ANNEX_C have slightly different parameters
and are used in 2 geographically different locations.
Signed-off-by: Manu Abraham abraham.m...@gmail.com
Despite its name, tuner-simple has a complex logic to set freqs ;)
Basically, it can be called by two different ways: via set_params()
or via calc_regs() callbacks. Both are bound to the DVBv3 API.
Also, set_params internally calls calc_regs().
In order to get rid of DVBv3 params at
Instead of using DVBv3 parameters, rely on DVBv5 parameters to
set the tuner.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
drivers/media/dvb/frontends/dvb-pll.c | 61 +---
1 files changed, 32 insertions(+), 29 deletions(-)
diff --git
While tda10021 supports both DVB-C Annex A and C, it is currently
hard-coded to Annex A. Add support for Annex C and re-work the
code in order to report the delivery systems, thans to Andreas,
that passed us the register settings for the Roll-off factor.
Thanks-to: Andreas Oberriter
This standard is not properly documented, but its settings are at
the tda18271dd driver, and are somewhat obvious, as they follow
the same logic as DVB-T 7MHz.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
drivers/media/common/tuners/tda18271-maps.c |4
Passing DVBv3 parameters to set_frontend is not fun, as the
core doesn't have any way to know if the driver is using the
v3 or v5 parameters. So, rename the callback and add a new
one to allow distinguish between a mixed v3/v5 paramenter call
from a pure v5 call.
After having all frontends to use
Instead of just estimating the bandwidth for DVB-C annex A/C,
also fill it at the core for ATSC and DVB-C annex B. This
simplifies the logic inside the tuners, as all non-satellite
tuners can just use c-bandwidth_hz for all supported
delivery systems.
Signed-off-by: Mauro Carvalho Chehab
This driver implements a fake get_bandwidth() callback. In
reallity, the tuner driver won't adjust its low-pass
filter based on a bandwidth, and were just providing a fake
method for demods to read whatever was set.
This code is useless, as none of the drivers that use
this tuner seems to require
Instead of using DVBv3 parameters, rely on DVBv5 parameters to
set the tuner.
Signed-off-by: Mauro Carvalho Chehab mche...@redhat.com
---
drivers/media/common/tuners/xc4000.c | 97 +++---
1 files changed, 42 insertions(+), 55 deletions(-)
diff --git
This driver implements a fake get_bandwidth() callback. In
reallity, the tuner driver won't adjust its low-pass
filter based on a bandwidth, and were just providing a fake
method for demods to read whatever was set.
This code is useless, as none of the drivers that use
this tuner seems to require
This patch series were originated from Manu's changes to add support
for DELSYS. It contains two parts.
The first part (5 patches) adds a better way to support DVB-C Annex C, as
proposed by Manu: to use a separate delivery system for Annex C.
At the second part, all tuner drivers were changed to
This driver implements a fake get_bandwidth() callback. In
reallity, the tuner driver won't adjust its low-pass
filter based on a bandwidth, and were just providing a fake
method for demods to read whatever was set.
This code is useless, as none of the drivers that use
this tuner seems to require
Hi Laurent,
On 12/21/2011 01:20 AM, Laurent Pinchart wrote:
On Wednesday 14 December 2011 13:23:07 Sylwester Nawrocki wrote:
The purpose of the new field is to allow the video pipeline elements
to negotiate memory buffer size for compressed data frames, where
the buffer size cannot be derived
Hi Manju,
On Wed, Dec 21, 2011 at 19:13:34, Hadli, Manjunath wrote:
remove machine specific inclusion from the driver which
comes in the way of platform code consolidation.
I think it would be more readable to use the term header file
here and in the headline. Just machine specific inclusion
Hi,
we have a processing chain composed of three v4l2 devices:
- ---
--
| v4l2 source || v4l2 fixer | | v4l2 encoder |
| (capture) |--| (mem2mem)| | (mem2mem) |
To properly detect frame loss the driver must keep
track of a frame_count.
Furthermore, field_count use was erroneous because
in progressive format this must be incremented twice.
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers/media/video/mx2_camera.c |5 -
Argh,
sorry, there is a file here that souldn't be included.
I'll resend it again.
On 22 December 2011 16:05, Javier Martin
javier.mar...@vista-silicon.com wrote:
To properly detect frame loss the driver must keep
track of a frame_count.
Furthermore, field_count use was erroneous because
in
To properly detect frame loss the driver must keep
track of a frame_count.
Furthermore, field_count use was erroneous because
in progressive format this must be incremented twice.
Signed-off-by: Javier Martin javier.mar...@vista-silicon.com
---
drivers/media/video/mx2_camera.c |5 -
1
On 12/21/2011 11:53 AM, Antti Palosaari wrote:
I am adding DTMB/CTTB support for the Linux Kernel DVB API. Do anyone
have clear idea which correct name?
Background of that discussion can be found from the following patch:
http://patchwork.linuxtv.org/patch/8827/
There is already defined
On 12/21/2011 11:07 PM, Miroslav Slugeň wrote:
XC4000 based cards are not using AGC control in normal way, so it is
not possible to get signal level from AGC registres of zl10353
demodulator, instead of this i send previous patch to implement signal
level directly in xc4000 tuner and now sending
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:Thu Dec 22 19:00:21 CET 2011
git hash:875e2e3edf48a206c64195666cf408dd3d119137
gcc version: i686-linux-gcc
On 22-12-2011 14:45, Antti Palosaari wrote:
On 12/21/2011 11:53 AM, Antti Palosaari wrote:
I am adding DTMB/CTTB support for the Linux Kernel DVB API. Do anyone
have clear idea which correct name?
Background of that discussion can be found from the following patch:
- enable fast usb quirk
- use usleep_range instead on msleep for short sleep
- merge i2c out and usb delay
- do like the windows driver that upload the tuner firmware with 80 bytes
packets
Signed-off-by: Matthieu CASTET castet.matth...@free.fr
CC: Thierry Reding thierry.red...@avionic-design.de
On 22-12-2011 17:56, Mauro Carvalho Chehab wrote:
On 22-12-2011 14:45, Antti Palosaari wrote:
On 12/21/2011 11:53 AM, Antti Palosaari wrote:
I am adding DTMB/CTTB support for the Linux Kernel DVB API. Do anyone
have clear idea which correct name?
Background of that discussion can be found
1. I renamed it to the DTMB. I looked very many research papers and CTTB
was very, very rare. DTMB seems to exists almost all documents even very
recent.
2. added new values needed for the existing parameters.
3. new parameter u32 interleaving
DTMB supports 240 and 720 interleavers. I added
Rename DMB-TH to DTMB.
Add few new values for existing parameters.
Add two new parameters, interleaving and carrier.
DTMB supports interleavers: 240 and 720.
DTMB supports carriers: 1 and 3780.
Signed-off-by: Antti Palosaari cr...@iki.fi
---
drivers/media/dvb/dvb-core/dvb_frontend.c | 19
Thanks Miroslav,
your patches fixed the problems with my leadtek 1800H card. Radio now
works again and tunes to the correct frequency.
On 17/12/2011 11:55 AM, Miroslav Slugeň wrote:
Fix radio for cx88 driver.
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the
This has now been fixed after applying patches by Miroslav Slugen.
On 18/04/2011 10:15 PM, Andrew Goff wrote:
On 23/03/2011 7:56 PM, Mauro Carvalho Chehab wrote:
Em 22-03-2011 08:54, Andrew Goff escreveu:
On Tue, Mar 22, 2011 at 8:09 AM, Mauro Carvalho Chehab
mche...@redhat.com wrote:
Em
On Thu, 22 Dec 2011, Javier Martin wrote:
To properly detect frame loss the driver must keep
track of a frame_count.
Furthermore, field_count use was erroneous because
in progressive format this must be incremented twice.
Hm, sorry, why this? I just looked at vivi.c - the version before
Hi Javier
On Thu, 22 Dec 2011, javier Martin wrote:
Hi,
are there any comments on this?
May I suppose you agree and it will be applied?
Yes, I've applied it to my 3.3 outgoing branch and will push it out soon.
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software
For xc4000 based tuners we can read signal directly from tuner even
for demodulator. This is updated patch of id 8933. This patch depends
on id 8926 (Add signal information to xc4000 tuner).
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to
For xc4000 based tuners we can read signal directly from tuner even
for demodulator. This is updated patch of id 8933. This patch depends
on id 8926 (Add signal information to xc4000 tuner).
From 4e51d66e51e54983b38ea556c370a7bf3dd5e273 Mon Sep 17 00:00:00 2001
From: Miroslav thunde...@email.cz
Hi,
Eduard Bloch wrote[1]:
current revision of the Cinergy S2 USB box from Terratec seems to use
another USB-IDs. The manufacturer provides patches at
http://linux.terratec.de/tv_en.html and it seems like the only
difference is really just the new ID and a couple of init flag changes.
This patch is wrong, please use 8971 instead.
--
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 Wed, Dec 21, 2011 at 3:56 AM, Rob Clark r...@ti.com wrote:
On Tue, Dec 20, 2011 at 2:20 PM, Dave Airlie airl...@gmail.com wrote:
snip
I think this is a really good v1 version of dma_buf. It contains all the
required bits (with well-specified semantics in the doc patch) to
implement some
Hello,
On Thursday, December 22, 2011 3:34 PM Javier Martin wrote:
we have a processing chain composed of three v4l2 devices:
- ---
--
| v4l2 source || v4l2 fixer | | v4l2
encoder |
|
Hi Guennadi,
thank you for your comments.
On 23 December 2011 00:17, Guennadi Liakhovetski g.liakhovet...@gmx.de wrote:
On Thu, 22 Dec 2011, Javier Martin wrote:
To properly detect frame loss the driver must keep
track of a frame_count.
Furthermore, field_count use was erroneous because
in
60 matches
Mail list logo
