From 4caccc456d0a0b0d7fd775ba074f7da6d811b1e1 Mon Sep 17 00:00:00 2001 From: Rudolf Cornelissen Date: Thu, 20 Aug 2009 16:41:39 +0000 Subject: [PATCH] modified the 100kHz timing inside the DDC common accelerant code. If delays with values near the timer resolution are required, the values should always have one resolution step added since otherwise the minimum delay isn't quaranteed. the 400khz timing needs fixing as well I guess... This modification fixes at least ticket #4084 where a DDC monitor isn't detected otherwise. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@32540 a95241bf-73f2-0310-859d-f6bbb57e9c96 --- src/add-ons/accelerants/common/i2c.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/add-ons/accelerants/common/i2c.c b/src/add-ons/accelerants/common/i2c.c index 0e62f6e2a1..0ade11e5ca 100644 --- a/src/add-ons/accelerants/common/i2c.c +++ b/src/add-ons/accelerants/common/i2c.c @@ -33,10 +33,10 @@ const static i2c_timing kTiming100k = { .low = 5, .high = 4, .su_sta = 5, - .hd_dat = 0, - .su_dat = 1, - .r = 1, - .f = 1, + .hd_dat = 1, + .su_dat = 2, + .r = 2, + .f = 2, .su_sto = 4, // as these are unspecified, we use half a clock cycle as a safe guess