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]
Date:	Mon, 16 Aug 2010 11:13:51 -0400
From:	Adam Jackson <ajax@...hat.com>
To:	Andy Lutomirski <luto@....edu>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	intel-gfx@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
	DRI mailing list <dri-devel@...ts.freedesktop.org>
Subject: Re: [Intel-gfx] Intel graphics CPU usage - SDVO detect bogosity?

On Mon, 2010-08-16 at 10:27 -0400, Andy Lutomirski wrote:

> But that's really the problem, because intel_sdvo_dvi_init contains:
> 
>          connector->polled = DRM_CONNECTOR_POLL_CONNECT | DRM_CONNECTOR_POLL_DISCONNECT;
> 
> I don't know if SDVO is supposed to send hotplug interrupts because
> that section of the docs is incomplete.

SDVO can generate interrupts, although a particular SDVO output type
might not.  (The G45 docs are missing this section, but the 965 docs are
applicable.)  We don't have that turned on, of course, because that
would be entirely too sensible.

You'd probably need to uncomment the #if 0'd intel_sdvo_set_hotplug() in
intel_sdvo.c, and call that from the appropriate bit of
intel_sdvo_init().  For pre-gen4 you'd probably also need to set
SDVO_INTERRUPT_ENABLE in the appropriate SDVOx register, but in gen4+
that bit is used for bpc selection.

Having done that you'd then need to wait the inevitable six months to
find out which SDVO devices actually have functioning hotplug and which
ones are just plain lying about it.

- ajax

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ