[email protected] wrote: > From: Stefan Ringel <[email protected]> > > Signed-off-by: Stefan Ringel <[email protected]> > --- > drivers/media/common/tuners/tuner-xc2028.c | 7 ++++++- > 1 files changed, 6 insertions(+), 1 deletions(-) > > diff --git a/drivers/media/common/tuners/tuner-xc2028.c > b/drivers/media/common/tuners/tuner-xc2028.c > index ed50168..fcf19cc 100644 > --- a/drivers/media/common/tuners/tuner-xc2028.c > +++ b/drivers/media/common/tuners/tuner-xc2028.c > @@ -1114,7 +1114,12 @@ static int xc2028_set_params(struct dvb_frontend *fe, > > /* All S-code tables need a 200kHz shift */ > if (priv->ctrl.demod) { > - demod = priv->ctrl.demod + 200; > + if ((strcmp (priv->ctrl.fname, "xc3028L-v36.fw") == 0) && > + (priv->ctrl.demod == XC3028_FE_ZARLINK456) && > + ((type & DTV78) || (type & DTV8))) > + demod = priv->ctrl.demod; > + else > + demod = priv->ctrl.demod + 200; > /* > * The DTV7 S-code table needs a 700 kHz shift. > * Thanks to Terry Wu <[email protected]> for reporting this
The idea behind this patch is right, but you should be testing it against priv->firm_version, instead comparing with a file name. Also, this will likely cause regressions on other drivers, since the offsets for v3.6 firmwares were handled on a different way on other drivers. I prefer to postpone this patch and the discussion behind it after having tm6000 driver ready, since it makes no sense to cause regressions or request changes on existing drivers due to a driver that is not ready yet. So, please hold your patch on your queue for now. My suggestion is that you should use git and have this patch on a separate branch where you do your tests, having a branch without this patch for upstream submission. -- Cheers, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
