linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jimmy.Jazz@gmx.net
To: Jean Delvare <khali@linux-fr.org>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: radeonfb monid i2c bus
Date: Mon, 09 Jun 2008 00:48:22 +0200	[thread overview]
Message-ID: <484C61B6.8090902@gmx.net> (raw)
In-Reply-To: <20080608162023.431083c7@hyperion.delvare>

Jean Delvare a écrit :
>
> Where is the code handling this? In radeon_monitor.c I can only see
> radeon_probe_i2c_connector() being called on ddc_vga, ddc_dvi and
> ddc_crt2. No reference to ddc_monid.
>
>   
You will find several patches that make use of that functionality.  The 
current radeonfd driver is quite incomplete and is unusable for  the 
never cards that use an atom bios.  The driver needs also to be 
patched.  Some of the ati x800 family cards like the one i own will only 
work with the ddc_monid and  one or more of the patches i mentioned.
> But apparently not all chips have the "monid" bus? Or is it a card
> property, and other cards using the same Radeon 9200 might have it
> while mine doesn't? I wouldn't care about an empty i2c bus, but a
> broken bus as I get now affects the whole i2c subsystem and its users
> in unpleasant ways. That's why I am wondering if there's a way to avoid
> it.
>   
There are certainly many good reasons why the driver will stay 
unchanged. One reason could be, it is stable for most of the users and 
"easily" patchable to fit particular needs. Like me, you need particular 
needs :)




-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php

  reply	other threads:[~2008-06-08 22:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-06 10:01 radeonfb monid i2c bus Jean Delvare
2008-06-06 13:46 ` Alex Deucher
2008-06-06 13:50 ` Benjamin Herrenschmidt
2008-06-08 14:20   ` Jean Delvare
2008-06-08 22:48     ` Jimmy.Jazz [this message]
2008-06-09  5:15     ` Alex Deucher
2008-06-09  7:14       ` Jean Delvare
2008-06-09 13:02         ` Alex Deucher

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=484C61B6.8090902@gmx.net \
    --to=jimmy.jazz@gmx.net \
    --cc=khali@linux-fr.org \
    --cc=linux-fbdev-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;
as well as URLs for NNTP newsgroup(s).