diff options
| author | Mauro Carvalho Chehab <mchehab@redhat.com> | 2011-07-24 09:25:39 -0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@redhat.com> | 2012-01-21 13:45:25 -0200 |
| commit | da989e0bc7f2b3db3fea417c0bae3c20c6455995 (patch) | |
| tree | 4952ca6344a8a6bdff7409ed21a1e1c3743b188b /drivers/media/dvb/ddbridge/ddbridge-core.c | |
| parent | f2ba9e5dda2afd4615dbd3c48afe64fe2ce70d4e (diff) | |
| download | op-kernel-dev-da989e0bc7f2b3db3fea417c0bae3c20c6455995.zip op-kernel-dev-da989e0bc7f2b3db3fea417c0bae3c20c6455995.tar.gz | |
[media] drxk: Don't assume a default firmware name
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 <mchehab@redhat.com>
Diffstat (limited to 'drivers/media/dvb/ddbridge/ddbridge-core.c')
| -rw-r--r-- | drivers/media/dvb/ddbridge/ddbridge-core.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/media/dvb/ddbridge/ddbridge-core.c b/drivers/media/dvb/ddbridge/ddbridge-core.c index 2f31648..243dbb3 100644 --- a/drivers/media/dvb/ddbridge/ddbridge-core.c +++ b/drivers/media/dvb/ddbridge/ddbridge-core.c @@ -578,6 +578,7 @@ static int demod_attach_drxk(struct ddb_input *input) struct drxk_config config; memset(&config, 0, sizeof(config)); + config.microcode_name = "drxk_a3.mc"; config.adr = 0x29 + (input->nr & 1); fe = input->fe = dvb_attach(drxk_attach, &config, i2c); |
