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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 14 Dec 2013 20:17:20 -0500
From:	Devin Heitmueller <dheitmueller@...nellabs.com>
To:	Connor Behan <connor.behan@...il.com>
Cc:	Mauro Carvalho Chehab <m.chehab@...sung.com>,
	Frederik Himpe <fhimpe@...enet.be>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Linux Media Mailing List <linux-media@...r.kernel.org>,
	stable@...r.kernel.org
Subject: Re: stable regression: tda18271_read_regs: [1-0060|M] ERROR:
 i2c_transfer returned: -19

> My basic problem is
>
> __tda18271_write_regs: [1-0060|M] ERROR: idx = 0x0, len = 39, i2c_transfer returned: -32
>
> where it attaches lgdt3305 before tda18271. Do you know a similar patch
> that could help me?

It's a totally different issue.  The problem with the US Exeter has to
do with the lgdt3305 wedging the I2C bus after initialization because
there's a timing window where you have to strobe the reset after chip
powerup.

I had a patch kicking around which fixed part of the issue, but it
didn't completely work because of the lgdt3305 having AGC enabled at
chip powerup (which interferes with analog tuning on the shared
tuner), and the internal v4l-dvb APIs don't provide any easy way to
reset the AGC from the analog side of the device.

In short, it's been a known issue for almost three years and nobody's
gotten around to fixing it, and it sees unlikely anyone with the
appropriate level of knowledge of the device will anytime soon.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux - Powered by OpenVZ