kernel/git/stable/linux.git/drivers/media/dvb/ngene, branch master

[media] Rename media/dvb as media/pci

2012-08-14T02:30:06+00:00

The remaining dvb drivers are pci, so rename them to match the bus. Signed-off-by: Mauro Carvalho Chehab

[media] move the dvb/frontends to drivers/media/dvb-frontends

2012-08-14T02:13:41+00:00

Raise the DVB frontends one level up, as the intention is to remove the drivers/media/dvb directory. Signed-off-by: Mauro Carvalho Chehab

[media] dvb: move the dvb core one level up

2012-08-14T02:08:14+00:00

just like the V4L2 core, move the DVB core to drivers/media, as the intention is to get rid of both "video" and "dvb" directories. Signed-off-by: Mauro Carvalho Chehab

[media] dvb: use %*ph to hexdump small buffers

2012-08-13T19:39:33+00:00

Signed-off-by: Andy Shevchenko Signed-off-by: Mauro Carvalho Chehab

[media] ngene: add support for Terratec Cynergy 2400i Dual DVB-T

2012-08-12T02:27:00+00:00

This code is based on ngene initial check-in (dae52d009fc950b5c209260d50fcc000f5becd3c) Signed-off-by: Patrice Chotard Signed-off-by: Mauro Carvalho Chehab

[media] drxk: Make the QAM demodulator command parameters configurable

2012-07-06T17:54:43+00:00

Currently there are two different implementations (in the firmware) for the QAM demodulator command: one takes 4 and the other takes 2 parameters. The driver shows an error in dmesg When using the 4-parameter command with firmware that implements the 2-parameter command. Unfortunately this happens every time when chaning the frequency (on DVB-C). This patch simply makes configurable, how many command parameters will be used. All existing drxk_config instances using the "drxk_a3.mc" were updated because this firmware is the only loadable firmware where the QAM demodulator command 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. [mchehab@redhat.com: Fix a small CodingStyle issue at one comment] Signed-off-by: Martin Blumenstingl Tested-by: Mauro Carvalho Chehab Signed-off-by: Mauro Carvalho Chehab

[media] ngene: remove an unneeded condition

2012-04-26T18:29:23+00:00

"stat" is always zero here. The condition used to be needed, but we shifted stuff around in 0f0b270f90 "[media] ngene: CXD2099AR Common Interface driver". This doesn't change how the code works, it's just a bit tidier. Signed-off-by: Dan Carpenter Signed-off-by: Mauro Carvalho Chehab

[media] drxk: Don't assume a default firmware name

2012-01-21T15:45:25+00:00

Move the ngene/ddbridge firmware into their drivers. There are two reasons for that: 1) The firmware used there didn't work for a few devices I tested here (Terratec H5, H6 and H7); 2) At least Terratec H7 doesn't seem to require a firmware for it to work. After this change, if firmware is not specified, the driver will use a rom-based firmware (this seems to be the case for Terratec H7, although I need to better check the USB dumps to be sure about that). In any case, the firmware seems to be optional, as the DRX-K driver don't return the firmware load error. Signed-off-by: Mauro Carvalho Chehab

[media] drxk: create only one frontend for both DVB-C and DVB-T

2012-01-05T18:44:09+00:00

Instead of creating two DVB frontend entries for the same device, create just one entry, and fill the delivery_system according with the supported standards. Signed-off-by: Mauro Carvalho Chehab

staging: Move media drivers to staging/media

2011-11-03T09:59:03+00:00

In practice, it is being hard to distinguish when a patch should go to staging tree or to the media tree. Better to distinguish it, by putting the media drivers at a separate staging directory. Newer staging drivers that include anything with "dvb*.h", "v4l2*.h" or "videodev2.h" should go to the drivers/staging/media tree. Acked-by: Greg Kroah-Hartman Signed-off-by: Mauro Carvalho Chehab