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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <AANLkTimS2FwZfruag0rBnbpEQoqTEUSXf14XGpZYQdAO@mail.gmail.com>
Date:	Wed, 27 Oct 2010 13:52:34 -0400
From:	Devin Heitmueller <dheitmueller@...nellabs.com>
To:	Mauro Carvalho Chehab <mchehab@...hat.com>
Cc:	Jiri Slaby <jirislaby@...il.com>,
	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

On Wed, Oct 27, 2010 at 12:46 PM, Mauro Carvalho Chehab
<mchehab@...hat.com> wrote:
> The original code is broken, as it doesn't properly honour a max size of 8.
> Even if we do some optimization at cx231xx, we still need to fix the tda18271
> code, as it is trying to use more than 8 bytes on some writes.
>
> Also, as you noticed, the way cx231xx sends large firmwares to xc5000 is a hack:
> it requires to identify that the I2C device is a xc5000 and do an special
> treatment for it.

Yes, it does currently only get run if it's an xc5000, but I believe
that code path could be used for *all* devices.  There is no reason
that it needs to be a hack as that behavior should be the default case
(presumably Conexant just didn't want to retest against other
devices).

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com
--
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/