linux-kernel - Re: [PATCH v2] cirrus-logic-framebuffer-i2c-support.patch

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:	Fri, 28 Jul 2006 12:05:20 +0200
From:	Krzysztof Halasa <khc@...waw.pl>
To:	Jean Delvare <khali@...ux-fr.org>
Cc:	"Antonino A. Daplas" <adaplas@...il.com>,
	Andrew Morton <akpm@...l.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] cirrus-logic-framebuffer-i2c-support.patch

Hi,

Jean Delvare <khali@...ux-fr.org> writes:

> In practice, I would guess that both X and the framebuffer drivers only
> use the I2C/DDC channel to read the monitor's EDID at initialization
> time, so the risk of concurrent accesses is thin.

Yes. It's a bit different when I log console messages to the EEPROM
(connected to VGA DDC pins), but still... I don't have X on this
machine :-)

Looks like this very small project gets bigger.
-- 
Krzysztof Halasa
-
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/