From: Mauro Carvalho Chehab <mchehab@brturbo.com.br>
To: Michael Krufky <mkrufky@linuxtv.org>
Cc: Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-dvb-maintainer@linuxtv.org,
Mac Michaels <wmichaels1@earthlink.net>,
Michael Krufky <mkrufky@m1k.net>
Subject: Re: [PATCH] DVB: lgdt330x frontend: some bug fixes & add lgdt3303 support
Date: Mon, 08 Aug 2005 09:33:06 -0300 [thread overview]
Message-ID: <1123504387.17427.9.camel@localhost> (raw)
In-Reply-To: <42F6A294.90300@linuxtv.org>
This should't be applied to 2.6.13. It does contain a hack at V4L code,
since mute_tda9887 is implemented outside tda9887.c module and could
potentially cause troubles since there are some work to provide it on a
correct way.
It should be applied to -mm and go to mainstream only after provided a
correct implementation.
Mkrufky,
Please avoid trying to submit yet experimental patches to mainstream.
Mauro.
Em Dom, 2005-08-07 às 20:08 -0400, Michael Krufky escreveu:
> For 2.6.13, if possible. Patch generated against 2.6.13-rc6
>
> anexo documento em texto simples (lgdt330x-structure-update.patch)
> diff -u linux-2.6.13/drivers/media/dvb/frontends/lgdt330x.c linux/drivers/media/dvb/frontends/lgdt330x.c
> +
> +#ifdef MUTE_TDA9887
> +static int i2c_write_ntsc_demod (struct lgdt330x_state* state, u8 buf[2])
> +{
> + struct i2c_msg msg =
> + { .addr = 0x43,
> + .flags = 0,
> + .buf = buf,
> + .len = 2 };
> + int err;
> +
> + if ((err = i2c_transfer(state->i2c, &msg, 1)) != 1) {
> + printk(KERN_WARNING "lgdt330x: %s error (addr %02x <- %02x, err = %i)\n", __FUNCTION__, msg.buf[0], msg.buf[1], err);
> + if (err < 0)
> + return err;
> + else
> + return -EREMOTEIO;
> + }
> + return 0;
> +}
> +
> +static void fiddle_with_ntsc_if_demod(struct lgdt330x_state* state)
> +{
> + // Experimental code
> + u8 buf0[] = {0x00, 0x20};
> + u8 buf1[] = {0x01, 0x00};
> + u8 buf2[] = {0x02, 0x00};
> +
> + i2c_write_ntsc_demod(state, buf0);
> + i2c_write_ntsc_demod(state, buf1);
> + i2c_write_ntsc_demod(state, buf2);
> +}
> +#endif
next prev parent reply other threads:[~2005-08-08 12:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 0:08 [PATCH] DVB: lgdt330x frontend: some bug fixes & add lgdt3303 support Michael Krufky
2005-08-08 0:55 ` [PATCH] DVB: lgdt330x frontend: trivial text cleanups Michael Krufky
2005-08-08 12:33 ` Mauro Carvalho Chehab [this message]
2005-08-08 13:20 ` [PATCH] DVB: lgdt330x frontend: some bug fixes & add lgdt3303 support Michael Krufky
2005-08-08 14:47 ` Mauro Carvalho Chehab
2005-08-09 3:10 ` Mac Michaels
2005-08-08 13:51 ` Michael Krufky
2005-08-08 14:32 ` Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1123504387.17427.9.camel@localhost \
--to=mchehab@brturbo.com.br \
--cc=akpm@osdl.org \
--cc=linux-dvb-maintainer@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkrufky@linuxtv.org \
--cc=mkrufky@m1k.net \
--cc=wmichaels1@earthlink.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox