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-next>] [day] [month] [year] [list]
Message-ID: <1328787865.1909.64.camel@deskari>
Date:	Thu, 09 Feb 2012 13:44:25 +0200
From:	Tomi Valkeinen <tomi.valkeinen@...com>
To:	stable@...nel.org
Cc:	linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org
Subject: OMAP4 HDMI PHY bug work-around for stable

Hi,

There is a hardware bug on OMAP4, which may cause the HDMI output to
break irreversibly. A work-around for the bug has been merged into
mainline, but is missing from stable.

I've backported the necessary patches on top of 3.0, 3.1 and 3.2 stable
trees, and pushed the following branches to:

git://gitorious.org/linux-omap-dss2/linux.git

fixes/for-3.0-stable
fixes/for-3.1-stable
fixes/for-3.2-stable

3.0 and 3.1 branches additionally contain a patch "OMAP: DSS2: HDMI: use
default dividers", which fixes a problem with the HDMI clock divider.
Without that the HDMI output won't start at all on those versions.

The branches contain the following backported patches:

      OMAP: DSS2: HDMI: use default dividers
      OMAP: 4430SDP/Panda: use gpio_free_array to free HDMI gpios
      OMAP: 4430SDP/Panda: rename HPD GPIO to CT_CP_HPD
      OMAPDSS: remove wrong HDMI HPD muxing
      OMAP: 4430SDP/Panda: setup HDMI GPIO muxes
      OMAP: 4430SDP/Panda: add HDMI HPD gpio
      OMAPDSS: HDMI: PHY burnout fix

Of those, the actual fix is in the last one, but as the GPIOs for HDMI
were a mess, they needed some cleanup patches before the fix could be
made.

I'm not familiar with the process with stable kernels, so are the
branches above fine to get them merged? Or should I send the patches
with git-send-email?

 Tomi


Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ