linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL for 2.6.37-rc1] V4L/DVB updates
Date: Wed, 27 Oct 2010 13:41:58 -0200	[thread overview]
Message-ID: <4CC84846.6020304@redhat.com> (raw)
In-Reply-To: <4CC84597.4000204@gmail.com>

Hi Jiri,

Em 27-10-2010 13:30, Jiri Slaby escreveu:
> On 10/27/2010 04:32 PM, Mauro Carvalho Chehab wrote:
>> Linus,
>>
>> Please pull from
>> 	ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6.git v4l_for_linus
> ...
>> Mauro Carvalho Chehab (72):
> ...
>>       [media] tda18271: allow restricting max out to 4 bytes
> 
> Even though you know this one breaks at least one driver you want it merged?

We need to fix that issue with af9015, but, without this patch, cx231xx is broken, as it
doesn't accept more than 4 bytes per I2C transfer. I tested the patch here with some possible
restrictions for I2C size. Also, Mkrufky tested it with other different hardware.

What I don't understand is that the only change that this patch caused for af9015 is to change
the I2C max size that used to be 16. The patch I sent you reverted this behaviour, by using
the proper macro value, instead of a magic number, but you reported that this didn't fix your
problem.

So, we need to figure out what af9015 is doing different than the other patches, and add patch 
the issue with af9015. It shouldn't be hard to fix. I'll keep working with you in order to solve
the issue, although I don't have any af90xx hardware here, so, I need your help with the tests.

Cheers,
Mauro.


  reply	other threads:[~2010-10-27 15:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-27 14:32 [GIT PULL for 2.6.37-rc1] V4L/DVB updates Mauro Carvalho Chehab
2010-10-27 15:30 ` Jiri Slaby
2010-10-27 15:41   ` Mauro Carvalho Chehab [this message]
2010-10-27 15:48     ` Devin Heitmueller
2010-10-27 16:46       ` Mauro Carvalho Chehab
2010-10-27 17:52         ` Devin Heitmueller
2010-10-27 15:53     ` Jiri Slaby
2010-10-27 16:36       ` Mauro Carvalho Chehab
2010-10-27 16:38         ` Jiri Slaby
2010-10-27 16:52           ` Mauro Carvalho Chehab
2010-10-27 17:39 ` Hans de Goede
2010-10-27 17:52   ` 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=4CC84846.6020304@redhat.com \
    --to=mchehab@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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;
as well as URLs for NNTP newsgroup(s).