Re: [PATCH] media: ddbridge: better handle optional spin locks at the code

Mauro Carvalho Chehab writes: > Em Wed, 11 Apr 2018 18:03:15 +0200 > Daniel Scheller escreveu: > > > Am Wed, 11 Apr 2018 08:03:37 -0400 > > schrieb Mauro Carvalho Chehab : > > > > > Currently, ddbridge produces 4 warnings on sparse: >

Re: [PATCH V2 0/3] Add timers to en50221 protocol driver

Hi Jasmin, Jasmin J. writes: > Hallo Ralph! > > > 1. The SW bit is cleared too early during the whole buffer size > > negotiation. > > This should be fixed. > I will look into this when I have time again. Probably end of next week. > > > 2. IRQEN = CMDREG_DAIE = 0x80 is always set in

Re: [PATCH V2 0/3] Add timers to en50221 protocol driver

Hi Jasmin, Jasmin J. writes: > Hi! > > Please hold on in merging this series, because I have to investigate a hint > I got related to the buffer size handshake of the protocol driver: > https://www.linuxtv.org/pipermail/linux-dvb/2007-July/019116.html > > BR, >Jasmin So, there

[PATCH 0/2] Support Physical Layer Scrambling

o make use of the new property. > > Those commits based on discussion previously made on the mailling list. > https://www.mail-archive.com/linux-media@vger.kernel.org/msg122600.html > > I would like to thanks Ralph Metzler (r...@metzlerbros.de) for the > great help and id

[bug report] drx: add initial drx-d driver

Hello Dan Carpenter, Dan Carpenter writes: > Hello Ralph Metzler, > > The patch 126f1e618870: "drx: add initial drx-d driver" from Mar 12, > 2011, leads to the following static checker warning: > > drivers/media/dvb-frontends/drxd_hard.c:1305 SC_WaitFor

Re: [PATCH 0/2] Add timers to en50221 protocol driver

Yes, acked-by: Ralph Metzler <r...@metzlerbros.de> Jasmin J. writes: > Hi! > > > I don't know if you are also waiting for a comment from me. > All positive ones are welcome ;) > > > I am fine with those changes. They are even desperately needed > >

Re: [PATCH 0/2] Add timers to en50221 protocol driver

Hi, I don't know if you are also waiting for a comment from me. I am fine with those changes. They are even desperately needed to get some "problem CAMs" working. Regards, Ralph Jasmin J. writes: > Ping 2! > > On 10/15/2017 03:59 PM, Jasmin J. wrote: > > Ping! > > -- --

Re: DVB-S2 and S2X API extensions

Hi, Mauro Carvalho Chehab writes: > Em Thu, 9 Nov 2017 16:28:18 +0100 > Ralph Metzler <r...@metzlerbros.de> escreveu: > > > Hi, > > > > I have a few RFCs regarding new needed enums and > > properties for DVB-S2 and DVB-S2X: > > > >

DVB-S2 and S2X API extensions

Hi, I have a few RFCs regarding new needed enums and properties for DVB-S2 and DVB-S2X: - DVB-S2/X physical layer scrambling I currently use the inofficial DTV_PLS for setting the scrambling sequence index (cf. ETSI EN 300 468 table 41) of the physical layer scrambling in DVB-S2 and DVB-S2X.

[PATCH] [media] dvb-frontends/stv0910: prevent consecutive mutex_unlock()'s

Daniel Scheller writes: > From: Daniel Scheller > > When calling gate_ctrl() with enable=0 if previously the mutex wasn't > locked (ie. on enable=1 failure and subdrivers not handling this properly, > or by otherwise badly behaving drivers), the i2c_lock could be

Re: [PATCH] [media] ddbridge: add IOCTLs

Daniel Scheller writes: > Am Sun, 20 Aug 2017 08:53:56 -0300 > schrieb Mauro Carvalho Chehab : > > > Em Sun, 20 Aug 2017 13:08:55 +0200 > > Daniel Scheller escreveu: > > > > > From: Daniel Scheller > > > > > >

Re: DD support improvements (was: Re: [PATCH v3 00/13] stv0367/ddbridge: support CTv6/FlexCT hardware)

Mauro Carvalho Chehab writes: > Em Mon, 26 Jun 2017 11:45:08 +0200 > Ralph Metzler <r...@metzlerbros.de> escreveu: > > > Mauro Carvalho Chehab writes: > > > Em Thu, 22 Jun 2017 23:35:27 +0200 > > > Ralph Metzler <r...@metzlerbros.de> escreveu

Re: [PATCH 00/14] ddbridge: bump to ddbridge-0.9.29

Daniel Scheller writes: > Am Mon, 10 Jul 2017 10:11:01 +0200 > schrieb Ralph Metzler <r...@metzlerbros.de>: > > > Daniel Scheller writes: > > > Stripped functionality compared to dddvb: > > > > > > - DVB-C modulator card support removed

[PATCH 1/4] [media] dvb-frontends: MaxLinear MxL5xx DVB-S/S2 tuner-demodulator driver

Daniel Scheller writes: > From: Daniel Scheller > > This adds the frontend driver for the MaxLinear MxL5xx family of tuner- > demodulators, as used on Digital Devices MaxS4/8 four/eight-tuner cards. > > The driver was picked from the dddvb vendor driver package and -

[PATCH 10/14] [media] ddbridge: remove unreachable code

ve it and update > ddb_attrs_snr[] to not reference it anymore. > > Cc: Ralph Metzler <r...@metzlerbros.de> > Signed-off-by: Daniel Scheller <d.schel...@gmx.net> > --- > drivers/media/pci/ddbridge/ddbridge-core.c | 27 --- > 1 file cha

[PATCH 09/14] [media] ddbridge: fix possible buffer overflow in ddb_ports_init()

t;p" is greater than zero before checking for > "dev->port[].type == DDB_CI_EXTERNAL_XO2". > > Cc: Ralph Metzler <r...@metzlerbros.de> > Signed-off-by: Daniel Scheller <d.schel...@gmx.net> > --- > drivers/media/pci/ddbridge/ddbridge-core.c | 2 +

[PATCH 3/4] [media] ddbridge: fix buffer overflow in max_set_input_unlocked()

b.voltage' 4 <= 255 > > Fix this by clamping the .lnb.voltage array access to 0-3 by "& 3"'ing > dvb->input. > > Cc: Ralph Metzler <r...@metzlerbros.de> > Signed-off-by: Daniel Scheller <d.schel...@gmx.net> > --- > drivers/media/pci/

[PATCH 00/14] ddbridge: bump to ddbridge-0.9.29

Daniel Scheller writes: > Stripped functionality compared to dddvb: > > - DVB-C modulator card support removed (requires DVB core API) not really besides one device name entry. > - OctoNET SAT>IP server/box support removed (requires API aswell) > - with this, GT link support was removed

Re: DD support improvements (was: Re: [PATCH v3 00/13] stv0367/ddbridge: support CTv6/FlexCT hardware)

Daniel Scheller writes: > Am Mon, 26 Jun 2017 11:59:20 +0200 > schrieb Ralph Metzler <r...@metzlerbros.de>: > > > Mauro Carvalho Chehab writes: > > > > > > Splitting it is OK. Including a *.c file no. It shouldn't be hard > >

Re: [PATCH 4/9] [media] dvb-frontends/stv0910: Fix signal strength reporting

Mauro Carvalho Chehab writes: > Em Mon, 26 Jun 2017 10:55:34 +0200 > Ralph Metzler <r...@metzlerbros.de> escreveu: > > > Daniel Scheller writes: > > > From: Daniel Scheller <d.schel...@gmx.net> > > > > > > Original co

Re: DD support improvements (was: Re: [PATCH v3 00/13] stv0367/ddbridge: support CTv6/FlexCT hardware)

Mauro Carvalho Chehab writes: > Em Sun, 25 Jun 2017 19:52:59 +0200 > Daniel Scheller <d.scheller@gmail.com> escreveu: > > > Am Sat, 24 Jun 2017 13:50:01 -0300 > > schrieb Mauro Carvalho Chehab <mche...@s-opensource.com>: > > > > >

Re: DD support improvements (was: Re: [PATCH v3 00/13] stv0367/ddbridge: support CTv6/FlexCT hardware)

Mauro Carvalho Chehab writes: > Em Thu, 22 Jun 2017 23:35:27 +0200 > Ralph Metzler <r...@metzlerbros.de> escreveu: > > > Daniel Scheller writes: > > > Am Tue, 20 Jun 2017 16:10:43 -0300 > > > schrieb Mauro Carvalho Chehab <mche...@s-opensour

[PATCH 4/9] [media] dvb-frontends/stv0910: Fix signal strength reporting

Daniel Scheller writes: > From: Daniel Scheller > > Original code at least has some signed/unsigned issues, resulting in > values like 32dBm. I will look into that. > Change signal strength readout to work without asking > the attached tuner, and use a lookup table

Re: DD support improvements (was: Re: [PATCH v3 00/13] stv0367/ddbridge: support CTv6/FlexCT hardware)

Daniel Scheller writes: > Am Tue, 20 Jun 2017 16:10:43 -0300 > schrieb Mauro Carvalho Chehab : > ... > > > - Maybe for 4.14: Support for the CineS2 V7 and FlexV4 line of > > > cards/modules. This mainly involves a new demod driver (stv0910) and > > > a new tuner

Re: [media-workshop] [ANNOUNCE] Linux Kernel Media mini-summit on Oct, 16-17 in Düsseldorf, Germany

Guennadi Liakhovetski writes: I'll likely be able to attend too. ATM I'm working on camera support in Android. I think Hans discussed related topics at the previous summit in the US too, which I didn't manage to attend unfortunately. I'll try to double-check results of those discussions

Re: ddbridge -- kernel 3.15.6

Antti Palosaari writes: Most hardest part mainlining all that stuff is absolutely API issues. Designing new APIs is a lot of work. Due to that I decided remove all the problematic stuff in order to proceed. API related issues: * DVB modulator API Yes, we definitely need a general

DVB Modulator API

Hi, Dave Chapman writes: Given the recent patches by Maik Broemme adding support for a DVB-C modulator, I thought I would mention that I'm working on a driver for a DVB-T modulator and would like to open a discussion regarding how to integrate modulator support into the existing DVB

Re: [PATCH 01/12] dvb-frontends: Support for DVB-C2 to DVB frontends

Mauro Carvalho Chehab writes: Em Sun, 3 Nov 2013 01:24:25 +0100 Maik Broemme mbroe...@parallels.com escreveu: Added support for DVB-C2 to DVB frontends. It will be required by cxd2843 and tda18212dd (Digital Devices) frontends. Signed-off-by: Maik Broemme mbroe...@parallels.com

Re: [PATCH 00/12] DDBridge 0.9.10 driver updates

Maik Broemme writes: Hi Mauro, Mauro Carvalho Chehab m.che...@samsung.com wrote: Em Sun, 3 Nov 2013 01:22:35 +0100 Maik Broemme mbroe...@parallels.com escreveu: I've updated the current DDBridge to latest version 0.9.10 from Ralph Metzler available at: http

Re: DVB-C2

Antti Palosaari writes: On 03.11.2013 13:31, Mauro Carvalho Chehab wrote: Em Wed, 23 Oct 2013 00:57:47 +0200 Ralph Metzler r...@metzlerbros.de escreveu: I am wondering if anybody looked into API extensions for DVB-C2 yet? Obviously, we need some more modulations, guard intervals, etc

DVB-C2

Hi, I am wondering if anybody looked into API extensions for DVB-C2 yet? Obviously, we need some more modulations, guard intervals, etc. even if the demod I use does not actually let me set those (only auto). But I do need to set the PLP and slice ID. I currently set them (8 bit each) by

Re: ddbridge v0.8

is that so? It's a good driver. You should ask Ralph Metzler (added to CC) as he wrote the driver I think or atleast maintains it. I wrote the driver but I never submitted it to the kernel myself. I got frustrated with that process years ago. Oliver Endriss took care of it and necessary

Re: [dvb] Question on dvb-core re-structure

Mauro Carvalho Chehab writes: Em Thu, 10 Jan 2013 13:49:52 +0200 Hamad Kadmany hkadm...@codeaurora.org escreveu: On 01/10/2013 1:13 PM, Antti Palosaari wrote: I could guess that even for the SoCs there is some bus used internally. If it is not one of those already existing, then

[PATCH 1/2] [media] drxk: Make the QAM demodulator command configurable.

Martin Blumenstingl writes: Currently there are two different commands: the old command which takes 4 parameters, and a newer one with just takes 2 parameters. Hi, are you sure about this? From what I have been told, the 2 parameter command is in the firmware ROM and older loadable/patch

Re: [media] DRX-K: Initial check-in

Dan Carpenter writes: On Sun, Jun 10, 2012 at 09:42:22PM +0200, Ralph Metzler wrote: Dan Carpenter writes: Hello Ralph Metzler, The patch 43dd07f758d8: [media] DRX-K: Initial check-in from Jul 3, 2011, leads to the following warning: drivers/media/dvb/frontends

Re: [patch RFC] [media] staging: solo6x10: fix | vs

Dan Carpenter writes: On Sat, Jun 09, 2012 at 10:47:32AM +0300, Dan Carpenter wrote: The test here is never true because '' was used instead of '|'. It was the same as: if (status ((116) (117)) ... Signed-off-by: Dan Carpenter dan.carpen...@oracle.com --- I don't

re: [media] DRX-K: Initial check-in

Dan Carpenter writes: Hello Ralph Metzler, The patch 43dd07f758d8: [media] DRX-K: Initial check-in from Jul 3, 2011, leads to the following warning: drivers/media/dvb/frontends/drxk_hard.c:2980 ADCSynchronization() warn: suspicious bitop condition 2977

Re: DVB nGene CI : TS Discontinuities issues

Anssi Hannula writes: I had it running for an hour and had no discontinuities (except at restarts, might have to look into buffer flushing). I tested it with nGene and Octopus boards on an Asus ION2 board and on a Marvell Kirkwood based ARM board. Should your test code (quoted

Re: CI/CAM support for offline (from file) decoding

Kovacs Balazs writes: Yes, i thought about that, but i need the Hardware CAM + CI, because it's chip paired encryption. It means in my situation that the EMM and ECM is also encrypted so it's hard to use in a SoftCam configuration. I hope there's a solution in the DVB driver space.

RE: [DVB] Digital Devices Cine CT V6 support

Sébastien RAILLARD (COEXSI) writes: CineS2 v6 + 2 CAM Readers ++ Tuner 0 - Input 0 - || | Port 0 - TAB 1 | - Output 0 Tuner 1 - Input 1 - | DVB-S2 |

RE: [DVB] Digital Devices Cine CT V6 support

Sébastien RAILLARD (COEXSI) writes: I've seen a new parameter ts_loop, can you explain how it's working? Is-it for sending the stream from the demodulator directly to the CAM reader? No, it is mainly for testing. It declares one TAB as loopback, which means that the data output is

Re: [PATCH 00/16] New drivers: DRX-K, TDA18271c2, Updates: CXD2099 and ngene

Hi Devin, Devin Heitmueller writes: On Sun, Jul 3, 2011 at 12:31 PM, Oliver Endriss o.endr...@gmx.de wrote: [PATCH 01/16] tda18271c2dd: Initial check-in [PATCH 02/16] tda18271c2dd: Lots of coding-style fixes Oliver, Why the new driver for the 18271c2? There is already such a

Re: [PATCH 00/16] New drivers: DRX-K, TDA18271c2, Updates: CXD2099 and ngene

Devin Heitmueller writes: Hi Ralph, Good to hear from you. AFAIR, there were at least 2 reasons. One was that the existing driver does not accept 2 (or even 4) tuners with the same address (but behind different demods) on the same I2C bus which is the case on duoflex C/T

Re: DVB nGene CI : TS Discontinuities issues

Issa Gorissen writes: On 11/05/11 15:12, Issa Gorissen wrote: From: Ralph Metzler r...@metzlerbros.de Issa Gorissen writes: Could you please take a look at the cxd2099 issues ? I have attached a version with my changes. I have tested a lot of different settings

multiple delivery systems in one device

Hi, since it seems devices with several delivery systems can be queried with one command: Andreas Oberritter writes: Of course it does since it is not feasible to use the same adapter number even on the same card when it provides multi-standard frontends which share dvr and demux

Re: [PATCH] Ngene cam device name

Andreas Oberritter writes: - ca0 would be reached from /dev/dvb/adapter0/ca0 - ca[12], depending on if they are connected to the same physical adapter (PCI, USB, ...), would be reached from /dev/dvb/adapter1/ca[12] or /dev/dvb/adapter1/ca1 and /dev/dvb/adapter2/ca2 and there respective

Re: [PATCH] Ngene cam device name

Andreas Oberritter writes: Of course it does since it is not feasible to use the same adapter number even on the same card when it provides multi-standard frontends which share dvr and demux devices. E.g., frontend0 and frontend1 can belong to the same demod which can be DVB-C and -T

Re: [PATCH] Ngene cam device name

Hi, since I just saw cxd2099 appear in staging in the latest git kernel, a simple question which has been pointed out to me before: Why is cxd2099.c in staging regarding the device name question? It has nothing to do with the naming. Regards, Ralph -- To unsubscribe from this list: send the

Re: [PATCH] Ngene cam device name

Andreas Oberritter writes: Unless you want to move the writing to/reading from the CI module into ioctls of the ci device you need another node. Even nicer would be having the control messages moved to ioctls and the TS IO in read/write of ci, but this would break the old interface.

Re: [PATCH] Ngene cam device name

Andreas Oberritter writes: On 03/11/2011 10:44 PM, Martin Vidovic wrote: Andreas Oberritter wrote: It's rather unintuitive that some CAMs appear as ca0, while others as cam0. Ngene CI appears as both ca0 and cam0 (or sec0). The ca0 node is used as usual, to setup the CAM.

Re: [PATCH] Ngene cam device name

Andreas Oberritter writes: They should be in different adapterX directories. Even on the cards where you can connect up to 4 dual frontends or CAM adapters I currently use one adapter directory for every frontend and CAM. That looks like a hack to me, that may work well for your

Re: [PATCH] Ngene cam device name

Andreas Oberritter writes: On 03/10/2011 04:29 PM, Issa Gorissen wrote: Now, according to Mauro comments, he has put this code into staging because of the usage of sec0 name for a cam device. Please comment on Oliver's explanations from this thread

Sony CXD2099AR support

Issa Gorissen writes: I have read that this CI chip driver is in staging because some questions on how to handle it are still not answered. I volunteer to handle this one. I'm a regular java developer, but I'm willing to put effort in learning linux drivers writing. So Ralph, can