linux-kernel - Re: [GIT PULL for 2.6.37-rc1] V4L/DVB updates

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4CC858B1.6090408@redhat.com>
Date:	Wed, 27 Oct 2010 14:52:01 -0200
From:	Mauro Carvalho Chehab <mchehab@...hat.com>
To:	Jiri Slaby <jirislaby@...il.com>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Media Mailing List <linux-media@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Michael Krufky <mkrufky@...nellabs.com>
Subject: Re: [GIT PULL for 2.6.37-rc1] V4L/DVB updates

Em 27-10-2010 14:38, Jiri Slaby escreveu:
> On 10/27/2010 06:36 PM, Mauro Carvalho Chehab wrote:
>> Basically, af9015 broke due to (3), as .small_i2c = 1 means nothing. It should be using
>> .small_i2c = TDA18271_16_BYTE_CHUNK_INIT, instead.
>>
>> What I don't understand is why a patch doing this change didn't fix the issue. Please
>> test the patch I posted on the original -next thread. Let's try to identify why
>> tda18271_write_regs() is not breaking the data into smaller writes.
> 
> It helps, but one needs to unplug and replug the device. So care to
> respin the pull request with the patch included?

AH! Yes, this is sometimes needed on some hardware: when a longer or wrong I2C transaction
is received, the hardware simply stops working. You need to replug it for it to return to
life.

Ok, I'll add the patch that changes it to .small_i2c = TDA18271_16_BYTE_CHUNK_INIT
to the series.

Thanks,
Mauro.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/