dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 26430] New: [KMS] Hw i2c patch doesn't work fully on rv280
Date: Thu,  4 Feb 2010 10:13:38 -0800 (PST)	[thread overview]
Message-ID: <bug-26430-502@http.bugs.freedesktop.org/> (raw)

http://bugs.freedesktop.org/show_bug.cgi?id=26430

           Summary: [KMS] Hw i2c patch doesn't work fully on rv280
           Product: DRI
           Version: XOrg CVS
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel@lists.sourceforge.net
        ReportedBy: randrik@mail.ru


Using patches from 

http://people.freedesktop.org/~agd5f/

0001-drm-radeon-kms-add-radeon-i2c-algo.patch
0002-drm-radeon-kms-add-support-for-hw-i2c-on-r1xx-r5xx.patch   

on top of mainline kernel (2.6.33-rc6-git2, one with locally reverted idr
commit)

i get strange resolution in X, probably related to

[drm:r100_hw_i2c_xfer], i2c write error 0x04800302
[drm:edid_is_valid] *ERROR* Raw EDID:
<3>00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff  ................
<3>00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff  ................
<3>00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff  ................
<3>00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff  ................
<3>00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff  ................
<3>00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff  ................
<3>00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff  ................
<3>00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff 00 ff  ................


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--

             reply	other threads:[~2010-02-04 18:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-04 18:13 bugzilla-daemon [this message]
2010-02-04 18:14 ` [Bug 26430] [KMS] Hw i2c patch doesn't work fully on rv280 bugzilla-daemon
2010-02-04 18:16 ` bugzilla-daemon
2010-02-04 18:21 ` bugzilla-daemon
2010-02-04 18:43 ` bugzilla-daemon
2010-02-16 10:02 ` bugzilla-daemon
2010-02-16 18:27 ` bugzilla-daemon
2010-02-16 18:30 ` bugzilla-daemon
2010-03-11 14:02 ` bugzilla-daemon
2010-03-11 18:33 ` bugzilla-daemon
2010-03-12  2:52 ` bugzilla-daemon
2010-03-12  2:54 ` bugzilla-daemon
2010-03-12 18:01 ` bugzilla-daemon
2010-03-12 18:02 ` bugzilla-daemon
2010-03-13  6:24 ` bugzilla-daemon
2010-03-13  6:26 ` bugzilla-daemon
2010-03-13  6:26 ` bugzilla-daemon
2010-03-14 15:33 ` bugzilla-daemon
2010-03-14 22:04 ` bugzilla-daemon
2010-03-14 22:05 ` bugzilla-daemon
2010-03-16 18:58 ` bugzilla-daemon
2010-03-17  0:44 ` bugzilla-daemon
2019-11-19  8:10 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-26430-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox