Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/dvb/frontends/drxk_hard.c
b/drivers/media/dvb/frontends/drxk_hard.c
index aaef8e3..7ea73df 100644
--- a/drivers/media/dvb/frontends/drxk_hard.c
+++ b/drivers/media/dvb/frontends/drxk_hard.c
@@ -6431,6 +6431,18 @@ struct dvb_frontend
Now, it outputs:
[10927.639641] drxk: SCU_RESULT_INVPAR while sending cmd 0x0203 with params:
[10927.646283] drxk: 02 00 00 00 10 00 07 00 03 02..
Better than ERROR -3. This happens with Terratec H5 firmware.
It adds 2 new error conditions, and something useful to tra
The set mode routines assume that state were changed to the
new mode, otherwise, they'll fail.
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/dvb/frontends/drxk_hard.c
b/drivers/media/dvb/frontends/drxk_hard.c
index 74e986f..1d29ed2 100644
--- a/drivers/media/dvb/frontends/drxk
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/dvb/frontends/drxk_hard.c
b/drivers/media/dvb/frontends/drxk_hard.c
index 7ea73df..bb8627f 100644
--- a/drivers/media/dvb/frontends/drxk_hard.c
+++ b/drivers/media/dvb/frontends/drxk_hard.c
@@ -1806,57 +1806,59 @@ static int SetOper
The driver is too limited: it assumes that UIO is used only for
controlling the antenna, and that only UIO-1 is in usage. However,
from Terratec H7 driver [1], 3 UIO's can be used. In fact, it seems
that H7 needs to use all 3. So, make the code generic enough to handle
the most complex scenario. Fo
Terratec H5 doesn't require to switch mode, but generates
an error due to this logic. Also, GPIO's are board-dependent.
So, add it at the board config struct.
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/dvb/frontends/drxk.h
b/drivers/media/dvb/frontends/drxk.h
index 9c99f31
DRX-K configuration is interesting when writing/testing
new devices. Add an info line showing the discovered info.
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/dvb/frontends/drxk_hard.c
b/drivers/media/dvb/frontends/drxk_hard.c
index 91f3296..0d288a7 100644
--- a/drivers/medi
On em28xx, tda18271C2 is accessible when the i2c port
is not touched. Touching on it breaks the driver.
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/dvb/frontends/drxk.h
b/drivers/media/dvb/frontends/drxk.h
index dd54512..9c99f31 100644
--- a/drivers/media/dvb/frontends/drxk.
All I2C logs we got for em28xx does that. With Terratec H5, at
400MHz speed, it seems that this is required, to avoid having
troubles at the I2C bus.
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/video/em28xx/em28xx-i2c.c
b/drivers/media/video/em28xx/em28xx-i2c.c
index 548d2df
If something bad happens during firmware load, an error
should be printed at dmesg.
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/dvb/frontends/drxk_hard.c
b/drivers/media/dvb/frontends/drxk_hard.c
index 89db378..1452e82 100644
--- a/drivers/media/dvb/frontends/drxk_hard.c
+++
Don't read paste the buffer, if the firmware is corrupted.
Instead, print an error message.
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/dvb/frontends/drxk_hard.c
b/drivers/media/dvb/frontends/drxk_hard.c
index c4b35a5..89db378 100644
--- a/drivers/media/dvb/frontends/drxk_ha
The microcode firmware provided on Terratec H5 seems to be
different. Add a parameter to allow specifying a different
firmware per-device.
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/dvb/frontends/drxk.h
b/drivers/media/dvb/frontends/drxk.h
index d5b6f9f..dd54512 100644
---
Instead of using #ifdef I2C_LONG_ADR for some devices, convert
it into a parameter. Terratec H5 logs from the original driver
seems to need this mode.
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/dvb/frontends/drxk.h
b/drivers/media/dvb/frontends/drxk.h
index a7b295f..d5b6f9f
Currently, the only parameter to be configured is the I2C
address. However, Terratec H5 logs shows that it needs a different
setting for some things, and it has its own firmware.
So, move the addr into a config structure, in order to allow adding
the required configuration bits.
Signed-off-by: Ma
This is a complex driver. Adding support for other devices with drxk
requires to be able to debug it and see where it is failing. So, add
optional printk messages to allow debugging it.
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/dvb/frontends/drxk_hard.c
b/drivers/media/dvb
This patch series applies after the DRX-K/ngene/ddbridge patches that
Oliver Endriss submitted.
It does a cleanup on several small issues at drx-k, including driver
removal. It also adds support for Terratec H5 (only DVB-C were tested).
In order to use Terratec H5, a different firmware is needed.
It is hard to identify the origin for those errors without a
prefix to indicate which driver produced them:
[ 1390.220984] i2c_write error
[ 1390.224133] I2C Write error
[ 1391.284202] i2c_read error
[ 1392.288685] i2c_read error
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/d
It is hard to identify the origin for those errors without a
prefix to indicate which driver produced them:
[ 1390.220984] i2c_write error
[ 1390.224133] I2C Write error
[ 1391.284202] i2c_read error
[ 1392.288685] i2c_read error
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/d
Not working yet. There are some fixes at the DRX-K that are needed
for it to work.
Signed-off-by: Mauro Carvalho Chehab
diff --git a/drivers/media/video/em28xx/Kconfig
b/drivers/media/video/em28xx/Kconfig
index 49878fd..281ee42 100644
--- a/drivers/media/video/em28xx/Kconfig
+++ b/drivers/media
The QAM standard is set using this scu_command:
SCU_RAM_COMMAND_STANDARD_QAM |
SCU_RAM_COMMAND_CMD_DEMOD_SET_PARAM
The driver implements a version that has 4 parameters, however,
Terratec H5 needs to break this into two separate commands, otherwise,
DVB-C doesn't work.
With this f
2011/7/10 Rémi Denis-Courmont :
> Le dimanche 10 juillet 2011 13:43:03 Stefan Seyfried, vous avez écrit :
>> Hi all,
>>
>> I patched test_dvr to use DMX_OUT_TSDEMUX_TAP and named it test_tapdmx.
>> Might be useful for others, too :-)
>> This is my first experience with mercurial, so bear with me if
The following patch provides wider carrier search.
As with existing code search starts at MSB aligned. The boundary
is widened to start at -9. In order to save time, if no carrier is
detected at the start it advances to the next alignment until carrier
is found.
The stv0288 will detect a DVB-S2
On Wed, 2011-07-06 at 21:35 +0100, Malcolm Priestley wrote:
> On Wed, 2011-07-06 at 13:34 +0200, Sébastien RAILLARD (COEXSI) wrote:
> >
> > > -Original Message-
> > > From: Oliver Endriss [mailto:o.endr...@gmx.de]
> > > Sent: lundi 4 juillet 2011 00:43
> > > To: Linux Media Mailing List
>
From: Randy Dunlap
Add HEX_STRING(value) to stringify.h so that drivers can
convert kconfig hex values (without leading "0x") to useful
hex constants.
Several drivers/media/radio/ drivers need this. I haven't
checked if any other drivers need to do this.
Alternatively, kconfig could produce he
From: Randy Dunlap
Modify radio-aztech to use HEX_STRING(CONFIG_RADIO_AZTECH_PORT)
so that the correct IO port value is used.
Fixes the IO port value that is used since this is hex:
CONFIG_RADIO_AZTECH_PORT=350
but it was being interpreted as decimal instead of hex.
Signed-off-by: Randy Dunlap
From: Randy Dunlap
Modify radio-rtrack2 to use HEX_STRING(CONFIG_RADIO_RTRACK2_PORT)
so that the correct IO port value is used.
Fixes this error message when CONFIG_RADIO_RTRACK2_PORT=30c:
drivers/media/radio/radio-rtrack2.c:31:17: error: invalid suffix "c" on integer
constant
Signed-off-by: R
From: Randy Dunlap
Modify radio-terratec to use HEX_STRING(CONFIG_RADIO_TERRATEC_PORT)
so that the correct IO port value is used.
Fixes the IO port value that is used since this is hex:
CONFIG_RADIO_TERRATEC_PORT=590
but it was being interpreted as decimal instead of hex.
Signed-off-by: Randy D
From: Randy Dunlap
Modify radio-zoltrix to use HEX_STRING(CONFIG_RADIO_ZOLTRIX_PORT)
so that the correct IO port value is used.
Fixes this error message when CONFIG_RADIO_ZOLTRIX_PORT=20c:
drivers/media/radio/radio-zoltrix.c:51:17: error: invalid suffix "c" on integer
constant
Signed-off-by: R
From: Randy Dunlap
Modify radio-trust to use HEX_STRING(CONFIG_RADIO_TRUST_PORT)
so that the correct IO port value is used.
Fixes the IO port value that is used since this is hex:
CONFIG_RADIO_TRUST_PORT=350
but it was being interpreted as decimal instead of hex.
Signed-off-by: Randy Dunlap
--
From: Randy Dunlap
Modify radio-gemtek to use HEX_STRING(CONFIG_RADIO_GEMTEK_PORT)
so that the correct IO port value is used.
Fixes this error message when CONFIG_RADIO_GEMTEK_PORT=34c:
drivers/media/radio/radio-gemtek.c:49:18: error: invalid suffix "c" on integer
constant
Signed-off-by: Randy
From: Randy Dunlap
Modify radio-typhoon to use HEX_STRING(CONFIG_RADIO_TYPHOON_PORT)
so that the correct IO port value is used.
Fixes the IO port value that is used since this is hex:
CONFIG_RADIO_TYPHOON_PORT=316
but it was being interpreted as decimal instead of hex.
Signed-off-by: Randy Dunl
From: Randy Dunlap
Modify radio-aimslab to use HEX_STRING(CONFIG_RADIO_RTRACK_PORT)
so that the correct IO port value is used.
Fixes this error message when CONFIG_RADIO_RTRACK_PORT=20f:
drivers/media/radio/radio-aimslab.c:49:17: error: invalid suffix "f" on integer
constant
Signed-off-by: Ran
Am Sun, 10 Jul 2011 16:45:46 +0300
schrieb "Rémi Denis-Courmont" :
> Le dimanche 10 juillet 2011 13:43:03 Stefan Seyfried, vous avez écrit :
> > Hi all,
> >
> > I patched test_dvr to use DMX_OUT_TSDEMUX_TAP and named it test_tapdmx.
> > Might be useful for others, too :-)
> > This is my first exp
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:Sun Jul 10 19:00:39 CEST 2011
git hash:6068c012c3741537c9f965be5b4249f989aa5efc
gcc version: i686-linux-gcc (GCC) 4.5
The ADV7175A/ADV7176A can operate in either 8-bit or 16-bit YCrCb mode.
* 8-Bit YCrCb Mode
This default mode accepts multiplexed YCrCb inputs through
the P7-P0 pixel inputs. The inputs follow the sequence Cb0, Y0
Cr0, Y1 Cb1, Y2, etc. The Y, Cb and Cr data are input on a
rising clock edge.
* 16-B
Signed-off-by: Christian Gmeiner
---
diff --git a/Documentation/DocBook/media/v4l/subdev-formats.xml
b/Documentation/DocBook/media/v4l/subdev-formats.xml
index 49c532e..18e30b0 100644
--- a/Documentation/DocBook/media/v4l/subdev-formats.xml
+++ b/Documentation/DocBook/media/v4l/subdev-formats.xml
@
Signed-off-by: Christian Gmeiner
---
diff --git a/include/linux/v4l2-mediabus.h b/include/linux/v4l2-mediabus.h
index 5ea7f75..11b916d 100644
--- a/include/linux/v4l2-mediabus.h
+++ b/include/linux/v4l2-mediabus.h
@@ -92,6 +92,10 @@ enum v4l2_mbus_pixelcode {
/* JPEG compressed formats - n
Hello,
The attached patch addresses a problem raised by Florent Audebert
where the video decoder was not setup properly if you were capturing
on the HVR-1300's s-video port while using the MPEG encoder.
The issue is described in greater detail in the patch itself.
Devin
--
Devin J. Heitmueller
Hi.
When pulseaudio enables the audio capturing, the
driver unmutes the sound. But, if no app have properly
tuned the tuner yet, you get the white noise.
I think the capturing must not touch the mute state,
because, without tuning the tuner first, you can't capture
anything anyway.
Without this p
Le dimanche 10 juillet 2011 13:43:03 Stefan Seyfried, vous avez écrit :
> Hi all,
>
> I patched test_dvr to use DMX_OUT_TSDEMUX_TAP and named it test_tapdmx.
> Might be useful for others, too :-)
> This is my first experience with mercurial, so bear with me if it's
> totally wrong.
Did it work fo
On Sun, Jul 10, 2011 at 10:14 AM, Duncan Brown wrote:
> Hi all
>
> I'm having issues using the latest drivers using the media_build
> script. (Fedora 14 - 2.6.35.13-92.x86_64)
>
> The build appears to go ok apart from midway where I get:
>
> Building modules, stage 2.
> MODPOST 461 modules
> WAR
Hi all,
I patched test_dvr to use DMX_OUT_TSDEMUX_TAP and named it test_tapdmx.
Might be useful for others, too :-)
This is my first experience with mercurial, so bear with me if it's
totally wrong.
Best regards,
Stefan
(attached in case the mailer screws it up)
# HG changeset patch
#
Hi all
I'm having issues using the latest drivers using the media_build
script. (Fedora 14 - 2.6.35.13-92.x86_64)
The build appears to go ok apart from midway where I get:
Building modules, stage 2.
MODPOST 461 modules
WARNING: "put_compat_timespec" [/usr/src/media_build/v4l/
v4l2-compat-ioctl
>-- Oorspronkelijk bericht --
>Date: Fri, 24 Jun 2011 11:01:37 +0200
>From: cedric.dew...@telfort.nl
>To: linux-...@linuxtv.org
>Subject: [linux-dvb] dib0700 hangs when usb receiver is unplugged while
> watching TV
>Reply-To: linux-media@vger.kernel.org
>
>
>Hi All,
>
>I have the PCTV nanost
44 matches
Mail list logo
