On 12/17/2013 05:40 PM, Antti Palosaari wrote:
> On 17.12.2013 09:34, Hans Verkuil wrote:
>> On 12/16/2013 11:08 PM, Antti Palosaari wrote:
>>> + } else if (is_sdr) {
>
>>> +
>>> + if (is_rx) {
>>> + SET_VALID_IOCTL(ops, VIDIOC_ENUMINPUT,
>>> vidioc_enum_input);
>>>
On 16.12.2013 22:49, "Sven Müller" wrote:
>
>
>> Gesendet: Montag, 16. Dezember 2013 um 21:20 Uhr
>> Von: "Matthias Schwarzott"
>> An: "Sven Müller" , linux-media@vger.kernel.org
>> Betreff: Re: Aw: Re: Card with si2165
>>
>> On 16.12.2013 09:26, "Sven Müller" wrote:
>>>
>>> I have a Hauppauge W
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 Dec 18 04:00:30 CET 2013
git branch: test
git hash: 675722b0e3917c6c917f1aa5f6d005cd3a0479f5
gcc versio
Hello all,
I am facing media-ctl commands problems past some days. My caspa
camera driver is "omap3isp" and using "mt9v032" sensor.
My medi-ctl commands are as follows:
$ media-ctl -r -l '"mt9v032 3-005c":0->"OMAP3 ISP CCDC":0[1], "OMAP3
ISP CCDC":2->"OMAP3 ISP preview":0[1], "OMAP3 ISP preview"
On Tue, Dec 17, 2013 at 4:09 PM, Antti Palosaari wrote:
> That shared DVB / V4L2 tuner is one problem that I have also currently (SDR
> is on V4L2 API and DTV is provided via DVB API). I have decided to try model
> where I separate RF tuner totally independent used DVB / V4L2 APIs, just to
> plain
On 17.12.2013 15:17, Hans Verkuil wrote:
The correct LLC DLL phase depends on the board layout, so this
should be part of the platform_data.
Verified-by: Martin Bugge
Nit, but the documentation says correct tag is Tested-by :)
regards
Antti
--
http://palosaari.fi/
--
To unsubscribe from thi
Off-topic, Cc:s dropped, related to DVB / V4L2 tuner communication problems.
On 17.12.2013 07:39, Devin Heitmueller wrote:
Hi Connor,
On Tue, Dec 17, 2013 at 12:28 AM, Connor Behan wrote:
Thanks for the detailed answer. I have tried your patch and updated the
wiki page. Would a 950 or 950Q be
--
Kedves E Mail felhasználói:
Túllépte a határt 23.432 tárolás postafiók beállítva a
WEB SERVICE / Administrator, és akkor problémái küldött
és a bejövő üzenetek Amíg ezt újból érvényesíti. Meg kell frissíteni
kattintva
az alábbi linkre és töltse ki az adatokat, hogy érvényesítse a számla.
Kér
The advantage of DVBv5 stats is that it allows adding proper
scales to all measures. use it for this frontend.
This patch adds a basic set of stats, basically cloning what's already
provided by DVBv3 API. Latter patches will improve it.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/dvb
On dib8000, the block error count is a monotonic 32 bits register.
With DVBv5 stats, we use a 64 bits counter, that it is reset
when a new channel is tuned.
Change the UCB counting start from 0 and to be returned with
64 bits, just like the API requests.
Signed-off-by: Mauro Carvalho Chehab
---
PER/UCB statistics are collected once on each 1 second.
However, it doesn't provide the total number of packets
needed to calculate PER.
Yet, as we know the bit rate, it is possible to estimate
such number. So, do it.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/dvb-frontends/dib8000.
On dib8000, the BER statistics are updated on every 1.25e6 bits.
Adjust the code to only update the statistics after having it
done.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/media/dvb-frontends/dib8000.c | 240 ++
1 file changed, 182 insertions(+), 58 dele
DVBv5 stats is more complete than the DVBv3 ones, and provide
scales to the statistics.
Add support for it with dib8000.
After this patchset, the stats will look like:
Lock (0x1f) Quality= Poor Signal= -26.93dBm C/N= 22.45dB UCB= 229 postBER=
16.6x10^-6 PER= 1.12x10^-3
For the first version
Use multiple linear segments to better interpolate the dBm
for the signal strength.
The table that converts from linear strength to dB was
empirically determinated with the help of a signal generator
(DTA-2111).
The entries from -35dBm to -22.5dBm were taken using just
the signal generator and th
Better to have Signal strength in dB.
This takes a very rough estimation for the signal strength,
that was calibrated using a Dektec DTA-2111 Gold RF generator
and a Pixelview dib8076 stick.
It estimates the signal strength using a linear equation where:
- the max is -22.5 dBm, with return
Hi Dan,
Thank you for the patch.
On Monday 16 December 2013 23:19:50 Dan Carpenter wrote:
> Smatch complains here because name is a 32 character buffer and we
> adding the "OMAP4 ISS " prefix as well for a total of 42 characters.
> The sd->name buffer can only hold 32 characters. I've changed it
Hi Dan,
Thank you for the patch.
On Monday 16 December 2013 18:06:12 Dan Carpenter wrote:
> The spin_lock_irqsave() macro is not nestable. The second call will
> overwrite the first record of "flags" so the IRQs will not be enabled
> correctly at the end of the function.
>
> I haven't looked at
On 17.12.2013 09:36, Hans Verkuil wrote:
On 12/16/2013 11:08 PM, Antti Palosaari wrote:
Now with some changes done requested by Hans.
I did not agree very well that VIDIOC_G_FREQUENCY tuner type check
exception, but here it is...
Also two patches, as example, conversion of msi3101 and rtl2832_s
On 17.12.2013 09:34, Hans Verkuil wrote:
On 12/16/2013 11:08 PM, Antti Palosaari wrote:
+ } else if (is_sdr) {
+
+ if (is_rx) {
+ SET_VALID_IOCTL(ops, VIDIOC_ENUMINPUT,
vidioc_enum_input);
+ SET_VALID_IOCTL(ops, VIDIOC_G_INPUT,
When the sub-device is registered, increment the use count of the sub-device
owner only if it's different from the owner of the driver for the media
device. This avoids increasing the use count by the module itself and thus
making it possible to unload it when it's not in use.
Signed-off-by: Sakar
The correct LLC DLL phase depends on the board layout, so this
should be part of the platform_data.
Verified-by: Martin Bugge
Signed-off-by: Hans Verkuil
---
drivers/media/i2c/adv7842.c | 6 +-
include/media/adv7842.h | 6 ++
2 files changed, 7 insertions(+), 5 deletions(-)
diff --
This timing must be supported by all HDMI equipment, so that's a
reasonable default.
Signed-off-by: Hans Verkuil
---
drivers/media/i2c/adv7842.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/media/i2c/adv7842.c b/drivers/media/i2c/adv7842.c
index 2eb4058..4bd6915 100644
--- a/dr
Return 0 if the new timings are equal to the current timings as
it caused extra cp-loss/lock interrupts.
Signed-off-by: Martin Bugge
Signed-off-by: Hans Verkuil
---
drivers/media/i2c/adv7842.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/media/i2c/adv7842.c b/drivers/media/i
Signed-off-by: Mats Randgaard
Signed-off-by: Hans Verkuil
---
drivers/media/i2c/adv7604.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/media/i2c/adv7604.c b/drivers/media/i2c/adv7604.c
index cfeaaaf..a1fa9a0 100644
--- a/drivers/media/i2c/adv7604.c
+++ b/drivers/media/i2c/adv
Signed-off-by: Martin Bugge
Signed-off-by: Hans Verkuil
---
drivers/media/i2c/adv7604.c | 5 +++--
include/media/adv7604.h | 4
2 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/media/i2c/adv7604.c b/drivers/media/i2c/adv7604.c
index a1fa9a0..3f40616 100644
--- a/dr
This timing must be supported by all HDMI equipment, so that's a
reasonable default.
Signed-off-by: Hans Verkuil
---
drivers/media/i2c/adv7604.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/media/i2c/adv7604.c b/drivers/media/i2c/adv7604.c
index 3f40616..f06316
Ignore EDID's where the header is wrong.
Signed-off-by: Martin Bugge
Signed-off-by: Hans Verkuil
---
drivers/media/i2c/adv7511.c | 35 ---
1 file changed, 24 insertions(+), 11 deletions(-)
diff --git a/drivers/media/i2c/adv7511.c b/drivers/media/i2c/adv7511.c
in
Hello Enrico,
On 12/06/2013 11:54 AM, Enrico wrote:
> On Fri, Dec 6, 2013 at 11:31 AM, Florian Vaussard
> wrote:
>> Hello,
>>
>> On 12/06/2013 11:13 AM, Enrico wrote:
>>> Hi,
>>>
>>> i know there is some work going on for omap3isp device tree support,
>>> but right now is it possible to enable it
Hi,
On Tuesday 17 December 2013 05:19 PM, Hans Verkuil wrote:
On 12/17/13 12:19, Archit Taneja wrote:
Hi Hans,
On Tuesday 17 December 2013 01:30 PM, Hans Verkuil wrote:
On 12/12/2013 09:35 AM, Archit Taneja wrote:
The VPE and VIP IPs in DRA7x contain common scaler and color
conversion hardwa
On 12/17/13 12:19, Archit Taneja wrote:
> Hi Hans,
>
> On Tuesday 17 December 2013 01:30 PM, Hans Verkuil wrote:
>> On 12/12/2013 09:35 AM, Archit Taneja wrote:
>>> The VPE and VIP IPs in DRA7x contain common scaler and color
>>> conversion hardware blocks. We create libraries for these
>>> compon
Hi Hans,
On Tuesday 17 December 2013 01:30 PM, Hans Verkuil wrote:
On 12/12/2013 09:35 AM, Archit Taneja wrote:
The VPE and VIP IPs in DRA7x contain common scaler and color conversion hardware
blocks. We create libraries for these components such that the vpe driver and
the vip driver(in future
Hello Laurent,
I was working on having a functional IOMMU/ISP for 3.14, and had an
issue with an image completely distorted. Comparing with another kernel,
I saw that PRV_HORZ_INFO and PRV_VERT_INFO differed. On the newer
kernel, sph, eph, svl, and slv were all off-by 2, causing my final image
to
On 12/17/2013 08:52 AM, Hans Verkuil wrote:
> On 12/03/2013 12:51 PM, Archit Taneja wrote:
>> This series fixes 2 issues in the VPE driver. The first fix allows us to use
>> UYVY color format for source and destination buffers. The second fix makes
>> sure
>> we don't set pixel format widths which
On 12/12/2013 09:35 AM, Archit Taneja wrote:
> The VPE and VIP IPs in DRA7x contain common scaler and color conversion
> hardware
> blocks. We create libraries for these components such that the vpe driver and
> the vip driver(in future) can use these library funcs to configure the blocks.
>
> Th
34 matches
Mail list logo
