Hi Maxime,
many thanks for your work!
On Wed, Aug 1, 2018 at 9:34 PM Maxime Jourdan wrote:
>
> Add documentation for the meson vdec dts node.
>
> Signed-off-by: Maxime Jourdan
> ---
> .../bindings/media/amlogic,meson-vdec.txt | 60 +++
> 1 file changed, 60 insertions(+)
>
Hi Neil,
On Sat, Mar 24, 2018 at 2:41 PM, Neil Armstrong wrote:
> Hi Martin,
>
>> Le 24 mars 2018 à 12:00, Martin Blumenstingl
>> a écrit :
>>
>> Hello Hans, Hi Neil,
>>
>> (apologies in advance if any of this is wrong, I don't have any CEC
>
Hello Hans, Hi Neil,
(apologies in advance if any of this is wrong, I don't have any CEC
capable TV so I can't test it)
On Fri, Mar 23, 2018 at 1:59 PM, Hans Verkuil wrote:
> From: Hans Verkuil
>
> Some boards (amlogic) have two CEC controllers: the DesignWare controller
> and their own CEC con
On Wed, Feb 1, 2017 at 11:14 PM, Martin Blumenstingl
wrote:
> The driver already parses the "linux,rc-map-name" property. Add this
> information to the documentation so .dts maintainers don't have to look
> it up in the source-code.
>
> Signed-off-by: Martin Blumens
The driver already parses the "linux,rc-map-name" property. Add this
information to the documentation so .dts maintainers don't have to look
it up in the source-code.
Signed-off-by: Martin Blumenstingl
Acked-by: Rob Herring
---
Changes since v1:
- removed character which shows u
The driver already parses the "linux,rc-map-name" property. Add this
information to the documentation so .dts maintainers don't have to look
it up in the source-code.
Signed-off-by: Martin Blumenstingl
---
Documentation/devicetree/bindings/media/meson-ir.txt | 3 +++
1
Signed-off-by: Martin Blumenstingl
---
The geekbox keymap was added while the documentation patch was not
applied yet (and I wasn't aware of this pending patch). This ensures
that the documentation is in sync with the actual keymaps.
Documentation/devicetree/bindings/media/rc.txt | 1 +
1
The GeekBox ships with a 12 button remote control which seems to use the
NEC protocol. The button keycodes were captured with the "ir-keytable"
tool (ir-keytable -p $PROTOCOL -t; human_button_pusher).
Signed-off-by: Martin Blumenstingl
---
drivers/media/rc/keymaps/Makefile | 1
On Mon, Jan 9, 2017 at 1:45 AM, Dieter Miosga wrote:
> Here's the result of the lsusb on the HanfTek 15f4:0135
This USB ID is not registered with the cx231xx driver yet - thus the
driver simply ignores your device.
The basics steps for adding support for your card would be:
1. add new "#define CX2
Hello Dieter,
(I CC'ed the linux-media mailing list so other users can look this up
when they run into the same problem)
On Sun, Jan 8, 2017 at 7:27 PM, Dieter Miosga wrote:
> Happy 2017!
>
> One of the parts that were placed under my imaginary Christmas tree was an
> Astrometa Hybrid TV DVB-T/T
ns to keep it in line with
> dvb logarithm functions.
>
> Move all statistic logic to mn88473_read_status() function.
>
> Use regmap_bulk_read() for reading multiple registers as a one go.
>
> And many more and less minor changes.
>
> Cc: Martin Blumenstingl
> Signed-of
)
- signal strength seems to be too low (compared to my em28xx device)
- I am not sure whether my implementation for bit errors and block
errors is correct
[0] https://www.linuxtv.org/wiki/index.php/Panasonic_MN88472
Martin Blumenstingl (1):
media: mn88473: add DVBv5 statistics support
drivers
Implement DVBv5 statistics support for DVB-T, DVB-T2 and DVB-C. All
information was taken from the LinuxTV wiki, where Benjamin Larsson has
documented all registers:
https://www.linuxtv.org/wiki/index.php/Panasonic_MN88472
Signed-off-by: Martin Blumenstingl
---
drivers/media/dvb-frontends
This adds the IR remote receiver to the AO domain devices.
Signed-off-by: Martin Blumenstingl
Reviewed-by: Kevin Hilman
---
drivers/pinctrl/meson/pinctrl-meson-gxbb.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/pinctrl/meson/pinctrl-meson-gxbb.c
b/drivers/pinctrl/meson
m/erdoukki/linux-amlogic-1/commit/969b2e2242fb14a13cb651f9a1cf771b599c958b
[1] http://forum.odroid.com/viewtopic.php?f=135&t=20504
Martin Blumenstingl (3):
pinctrl: amlogic: gxbb: add the IR remote input pin
ARM64: dts: amlogic: add the input pin for the IR remote
ARM64: dts: meson-gxbb:
m/erdoukki/linux-amlogic-1/commit/969b2e2242fb14a13cb651f9a1cf771b599c958b
[1] http://forum.odroid.com/viewtopic.php?f=135&t=20504
Martin Blumenstingl (3):
pinctrl: amlogic: gxbb: add the IR remote input pin
ARM64: dts: amlogic: add the input pin for the IR remote
ARM64: dts: meson-gxbb:
From: Neil Armstrong
New bindings are needed as the register layout on the newer platforms
is slightly different compared to Meson6b.
Signed-off-by: Neil Armstrong
Signed-off-by: Martin Blumenstingl
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/media/meson-ir.txt | 5 -
1
From: Neil Armstrong
This adds the Infrared Remote Controller node so boards with an IR
remote can simply enable it.
Signed-off-by: Neil Armstrong
Signed-off-by: Martin Blumenstingl
---
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a
Signed-off-by: Martin Blumenstingl
---
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
index 4f42316..96f4574 100644
--- a/arch/arm64/boot/dts/amlogic
Enable the Infrared Remote Controller on boards which have an Infrared
receiver.
Signed-off-by: Martin Blumenstingl
---
arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts | 6 ++
arch/arm64/boot/dts/amlogic/meson-gxbb-p20x.dtsi | 6 ++
arch/arm64/boot/dts/amlogic/meson-gxbb-vega
From: Neil Armstrong
Newer SoCs (Meson 8b and GXBB) are using REG2 (offset 0x20) instead of
REG1 to configure the decoder mode. This makes it necessary to
introduce new bindings so the driver knows which register has to be
used.
Signed-off-by: Neil Armstrong
Signed-off-by: Martin Blumenstingl
il):
Tested-by: Neil Armstrong
[0]
https://github.com/erdoukki/linux-amlogic-1/commit/969b2e2242fb14a13cb651f9a1cf771b599c958b
[1] http://forum.odroid.com/viewtopic.php?f=135&t=20504
Martin Blumenstingl (3):
pinctrl: amlogic: gxbb: add the IR remote pin
ARM64: dts: amlogic: add the pi
This adds the IR remote receiver to the AO domain devices.
Signed-off-by: Martin Blumenstingl
---
drivers/pinctrl/meson/pinctrl-meson-gxbb.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/pinctrl/meson/pinctrl-meson-gxbb.c
b/drivers/pinctrl/meson/pinctrl-meson-gxbb.c
index
From: Neil Armstrong
Newer SoCs (Meson 8b and GXBB) are using REG2 (offset 0x20) instead of
REG1 to configure the decoder mode. This makes it necessary to
introduce new bindings so the driver knows which register has to be
used.
Signed-off-by: Neil Armstrong
Signed-off-by: Martin Blumenstingl
From: Neil Armstrong
This adds the Infrared Remote Controller node so boards with an IR
remote can simply enable it.
Signed-off-by: Neil Armstrong
Signed-off-by: Martin Blumenstingl
---
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a
From: Neil Armstrong
New bindings are needed as the register layout on the newer platforms
is slightly different compared to Meson6b.
Signed-off-by: Neil Armstrong
Signed-off-by: Martin Blumenstingl
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/media/meson-ir.txt | 5 -
1
Signed-off-by: Martin Blumenstingl
---
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
index 4f42316..72df302 100644
--- a/arch/arm64/boot/dts/amlogic
Enable the Infrared Remote Controller on boards which have an Infrared
receiver.
Signed-off-by: Martin Blumenstingl
---
arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts | 6 ++
arch/arm64/boot/dts/amlogic/meson-gxbb-p20x.dtsi | 6 ++
arch/arm64/boot/dts/amlogic/meson-gxbb-vega
Enable the Infrared Remote Controller on boards which have an Infrared
receiver.
Signed-off-by: Martin Blumenstingl
---
arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts | 4
arch/arm64/boot/dts/amlogic/meson-gxbb-p20x.dtsi | 4
arch/arm64/boot/dts/amlogic/meson-gxbb-vega-s95
and enable it on the supported
boards
[0]
https://github.com/erdoukki/linux-amlogic-1/commit/969b2e2242fb14a13cb651f9a1cf771b599c958b
[1] http://forum.odroid.com/viewtopic.php?f=135&t=20504
Martin Blumenstingl (1):
ARM64: dts: meson-gxbb: Enable the the IR decoder on supported boards
Neil A
From: Neil Armstrong
This adds the Infrared Remote Controller node so boards with an IR
remote can simply enable it.
Signed-off-by: Neil Armstrong
Signed-off-by: Martin Blumenstingl
---
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a
From: Neil Armstrong
New bindings are needed as the register layout on the newer platforms
is slightly different compared to Meson6b.
Signed-off-by: Neil Armstrong
Signed-off-by: Martin Blumenstingl
---
Documentation/devicetree/bindings/media/meson-ir.txt | 5 -
1 file changed, 4
From: Neil Armstrong
Newer SoCs (Meson 8b and GXBB) are using REG2 (offset 0x20) instead of
REG1 to configure the decoder mode. This makes it necessary to
introduce new bindings so the driver knows which register has to be
used.
Signed-off-by: Neil Armstrong
Signed-off-by: Martin Blumenstingl
e
(either set by the bootloader or the chip's default, which uses NEC as
it's default) is used.
While here, I also added defines for the protocols which can be decoded
by the hardware (more work is needed to be actually able to use them
though).
Signed-off-by: Martin Blumenstingl
--
According to the reference driver (and the datasheet of the newer
Meson8b/S805 and GXBB/S905 SoCs) there are 14 registers, each 32 bit
wide.
Adjust the register size to reflect that, as register offset 0x20 is
now also needed by the meson-ir driver.
Signed-off-by: Martin Blumenstingl
---
changes
The meson-ir driver uses the wrong offset (at least according to
Amlogic's reference driver as well as the datasheets of the
Meson8b/S805 and GXBB/S905).
This means that we are getting incorrect durations (REG1_TIME_IV)
reported from the hardware.
This problem was also noticed by some people tryin
e
(either set by the bootloader or the chip's default, which uses NEC as
it's default) is used.
While here, I also added defines for the protocols which can be decoded
by the hardware (more work is needed to be actually able to use them
though).
Signed-off-by: Martin Blumenstingl
---
dr
The meson-ir driver uses the wrong offset (at least according to
Amlogic's reference driver as well as the datasheets of the
Meson8b/S805 and GXBB/S905).
This means that we are getting incorrect durations (REG1_TIME_IV)
reported from the hardware.
This problem was also noticed by some people tryin
The rtl2832 demod has 2 sets of PID filters. This patch enables
the filter support when using a slave demod.
Signed-off-by: Benjamin Larsson
Signed-off-by: Martin Blumenstingl
---
changes since v2:
- rebased to make the patch apply again
- removed explicit initialization of dev->slave_ts
T2266
- MEDIA_TUNER_MXL5007T
Signed-off-by: Martin Blumenstingl
---
drivers/media/usb/dvb-usb-v2/Kconfig | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/media/usb/dvb-usb-v2/Kconfig
b/drivers/media/usb/dvb-usb-v2/Kconfig
index 3dc8ef0..fcecbf7 100644
--- a/drivers/media/usb/dvb-usb-v2/Kc
Signed-off-by: Martin Blumenstingl
---
drivers/media/usb/dvb-usb-v2/Kconfig | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/media/usb/dvb-usb-v2/Kconfig
b/drivers/media/usb/dvb-usb-v2/Kconfig
index fcecbf7..524533d 100644
--- a/drivers/media/usb/dvb-usb-v2
Hello,
my "Astrometa AMDVB-T2 v2" is not working on Arch Linux because their
kernel config does not select CONFIG_DVB_MN88473. This is because the
maintainers simply rely on MEDIA_SUBDRV_AUTOSELECT to choose the
required drivers.
This patchset depends on Antti Palosaari's patch
"mn88472: move out
The rtl2832 demod has 2 sets of PID filters. This patch enables
the filter support when using a slave demod.
Signed-off-by: Benjamin Larsson
Signed-off-by: Martin Blumenstingl
---
This patch was originally written by Benjamin Larsson, all I did was
rebasing the patch and to extend the dev_dbg
Hi,
while testing the firmware download for the drxk_terratec_htc_stick I
found that many other firmware downloads are broken.
Here is a list of failing downloads:
cx231xx: Hash of extracted file does not match!
drxk_hauppauge_hvr930c: Hash of extracted file does not match!
sp8870: File does not
Signed-off-by: Martin Blumenstingl
---
Documentation/dvb/get_dvb_firmware | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/dvb/get_dvb_firmware
b/Documentation/dvb/get_dvb_firmware
index 32bc56b..543054a 100755
--- a/Documentation/dvb/get_dvb_firmware
+++ b
Signed-off-by: Martin Blumenstingl
---
Documentation/dvb/get_dvb_firmware | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/dvb/get_dvb_firmware
b/Documentation/dvb/get_dvb_firmware
index 32bc56b..543054a 100755
--- a/Documentation/dvb/get_dvb_firmware
+++ b
Hi,
I forgot to add some clarification:
- the "HTC USB XS HD" uses the same firmware as the "HTC Stick HD".
- both have different GPIO and reg init sequences
- I tested my changes only with DVB-C, but I guess DVB-T will work
fine (unfortunately
I can't test that, but it was working fine on the "
Signed-off-by: Martin Blumenstingl
---
drivers/media/dvb-frontends/drxk_hard.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/media/dvb-frontends/drxk_hard.c
b/drivers/media/dvb-frontends/drxk_hard.c
index 8b4c6d5..894b6eca 100644
--- a/drivers/media/dvb
Signed-off-by: Martin Blumenstingl
---
drivers/media/usb/em28xx/em28xx-cards.c | 13 -
drivers/media/usb/em28xx/em28xx-dvb.c | 84 -
drivers/media/usb/em28xx/em28xx.h | 1 +
3 files changed, 94 insertions(+), 4 deletions(-)
diff --git a/drivers/media
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
---
drivers/media/dvb
Hi,
here's an updated patch, rebased for the changes in patch 1.
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 http://vger.kernel.org/majordomo-info.html
nd takes 4 parameters. Some firmwares in the ROM
might also use it.
The drxk instances in the em28xx-dvb driver were also updated to
silence the warnings.
If no qam_demod_parameter_count is given in the drxk_config struct,
then the correct number of parameters will be auto-detected.
Signed-off-
Hi,
here's an updated patch which fixes the style issues (sorry for that).
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 http://vger.kernel.org/majordomo-info.html
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
---
drivers/media/dvb
nd takes 4 parameters. Some firmwares in the ROM
might also use it.
The drxk instances in the em28xx-dvb driver were also updated to
silence the warnings.
If no qam_demod_parameter_count is given in the drxk_config struct,
then the correct number of parameters will be auto-detected.
Signed-off-
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 http://vger.k
Hi,
> I didn't tell "old command", or at least not in the sense of old firmware. I
> told
> that the first drivers (ddbridge and mantis), based on drxk_ac3.mc firmware,
> use the
> 4-parameters variant, while the other drivers use the 2-parameters variant.
Oh sorry, I must have gotten that wrong
Hi Ralph,
> are you sure about this?
> From what I have been told, the 2 parameter command is in the
> firmware ROM and older loadable/patch firmwares.
> Newer firmwares provided the 4 parameter command.
The firmwares in the ROM are a good point.
I discussed with Mauro Carvalho Chehab before I s
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
---
drivers/media/dvb
duplicated code.
Signed-off-by: Martin Blumenstingl
---
drivers/media/dvb/ddbridge/ddbridge-core.c | 1 +
drivers/media/dvb/frontends/drxk.h | 6 +++-
drivers/media/dvb/frontends/drxk_hard.c| 44 ++
drivers/media/dvb/frontends/drxk_hard.h| 3 +-
drivers/
Hi,
this little patch series cleans up the dmesg when using the drxk driver.
The first patch fixes a warning regarding the wrong QAM demodulator
command (this depends on the drxk's firmware). These warnings were
spamming my dmesg.
The second patch just fixes some partially incorrect dprintk's/prin
Hi Soren,
I'm just CC'ing the linux-media mailing list ;)
For the record, here's what Soren wrote a few minutes ago:
> thank you for your help and tests. I tried to avoid this, but now I
> installed the windows software of this HTC stick. I see the same reception
> problems in windows, too. So thi
Hi Soren,
I just tested DVB-C (we got some local provider here).
> Correct. My Cinergy HTC Stick is not working for DVB-C with older drivers,
> too. (I didn't test DVB-T, since there are cheaper sticks for that and vdr
> opens the HTC stick for dvb-c)
Here's the first difference: it worked with a
Hi Sven,
> I tested the patchset on linux-3.4.2, unfortunately DVB-C is not working
> here (DVB-T not tested).
> If you have further patches or other suggestions what to test, I would be
> happy to try it.
That's sad.
I guess it was also not working with the old version, right?
Do you get any erro
Hi,
this patch-set tries to improve compatibility with the Terratec Cinergy HTC
Stick HD.
It includes a completely new GPIO and analog decoder setup, which is now
similar to what the driver on windows does.
I also disabled LNA by default as it's what the windows-driver seems to do.
This should a
it worked quite well.
Signed-off-by: Martin Blumenstingl
---
drivers/media/video/em28xx/em28xx-cards.c |7 +--
drivers/media/video/em28xx/em28xx-dvb.c | 83 -
2 files changed, 83 insertions(+), 7 deletions(-)
diff --git a/drivers/media/video/em28xx/em28xx
Signed-off-by: Martin Blumenstingl
---
drivers/media/video/em28xx/em28xx-i2c.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/video/em28xx/em28xx-i2c.c
b/drivers/media/video/em28xx/em28xx-i2c.c
index 185db65..1683bd9 100644
--- a/drivers/media/video/em28xx/em28xx-i2c.c
As of June 2012 it uses the same firmware as the Hauppauge WinTV HVR 930C.
Signed-off-by: Martin Blumenstingl
---
Documentation/dvb/get_dvb_firmware | 20 +++-
1 file changed, 19 insertions(+), 1 deletion(-)
diff --git a/Documentation/dvb/get_dvb_firmware
b/Documentation/dvb
Hi,
> When sending new versions of a patch you should mark them as [PATCH
> v2], [PATCH v3], etc in the subject.
> This way maintainers can follow the patch evolution.
Thanks for the hint.
I just noticed that I spammed the patchwork system with my patch-mess too.
I should probably also always rep
Hello,
thanks to Fabio and Ezequiel for the suggestions.
This is the latest version of my patch.
It basically shows this when connecting my stick
(of course only if I remove my other patch):
[ 1597.796028] em28xx #0: chip ID is em2884
[ 1597.849321] em28xx #0: Identified as Terratec Cinergy HTC S
This simply shows a little warning if the board does not have remote
control support. This should make it easier for users to see if they
have misconfigured their system or if the driver simply does not have
rc-support for their card (yet).
Signed-off-by: Martin Blumenstingl
---
drivers/media
you think about using dev_warn but still including the driver name
and the board number?
On Tue, May 29, 2012 at 11:28 PM, Fabio Estevam wrote:
> On Tue, May 29, 2012 at 6:26 PM, Martin Blumenstingl
> wrote:
>> Hello Fabio,
>>
>> I can use dev_err if you want.
>
>
Hello Fabio,
I can use dev_err if you want.
And sorry for sending the patch twice.
I messed up the git send-email command here - sorry for that.
Regards,
Martin
> On Tue, May 29, 2012 at 11:22 PM, Fabio Estevam wrote:
>> On Tue, May 29, 2012 at 6:08 PM, Martin Blumenstingl
>>
Hello everyone,
sorry for the first reply - I messed up the git send-email command.
This is the correct version of the patch (including my signed-off-by
and a whitespace fix).
Regards,
Martin
On Tue, May 29, 2012 at 11:19 PM, Martin Blumenstingl
wrote:
> The Cinergy HTC Stick HD uses the s
This simply shows a little warning if the board does not have remote
control support. This should make it easier for users to see if they
have misconfigured their system or if the driver simply does not have
rc-support for their card (yet).
Signed-off-by: Martin Blumenstingl
---
drivers/media
The Cinergy HTC Stick HD uses the same remote control as the TerraTec
Cinergy XS products. Thus the same keymap could be re-used.
Signed-off-by: Martin Blumenstingl
---
drivers/media/video/em28xx/em28xx-cards.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/video/em28xx
This simply shows a little warning if the board does not have remote
control support. This should make it easier for users to see if they
have misconfigured their system or if the driver simply does not have
rc-support for their card (yet).
Signed-off-by: Martin Blumenstingl
---
drivers/media
This simply shows a little warning if the board does not have remote
control support. This should make it easier for users to see if they
have misconfigured their system or if the driver simply does not have
rc-support for their card (yet).
Signed-off-by: Martin Blumenstingl
---
drivers/media
This simply shows a little warning if the board does not have remote
control support. This should make it easier for users to see if they
have misconfigured their system or if the driver simply does not have
rc-support for their card (yet).
---
drivers/media/video/em28xx/em28xx-input.c |3 +++
The Cinergy HTC Stick HD uses the same remote control as the TerraTec
Cinergy XS products.
---
drivers/media/video/em28xx/em28xx-cards.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/video/em28xx/em28xx-cards.c
b/drivers/media/video/em28xx/em28xx-cards.c
index 20a7e24..8e32
Hello,
some days ago I purchased a "TerraTec Cinergy HTC Stick HD".
Unfortunately the remote control (which came bundled) did not
work.
I found out that there's no remote control support for that
stick/board in the em28xx driver.
Thus I wrote two patches:
The first one adds remote control suppor
81 matches
Mail list logo
