linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: kronos@kronoz.cjb.net,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Jon Smirl <jonsmirl@yahoo.com>
Subject: Re: Re: [RADEON] Connector type
Date: Fri, 29 Aug 2003 01:27:16 +0200	[thread overview]
Message-ID: <1062113236.14324.46.camel@thor.holligenstrasse29.lan> (raw)
In-Reply-To: <1062090156.612.144.camel@gaston>

On Thu, 2003-08-28 at 19:02, Benjamin Herrenschmidt wrote:
> On Thu, 2003-08-28 at 18:20, Kronos wrote:
> > Hi,
> > currently DDCReg in  radeonfb is hardcoded to CRT  port (secondary port,
> > primary DAC).
> > 
> > I've working code to detect connector type. On my board it finds the CRT
> > port  and  DVI  port. The  latter is  ignored  because  dviDisp_type  is
> > MT_NONE. If crtDisp_type is MT_NONE then it will use the DVI port.

BTW, do you do this the same way as or differently than the XFree86
driver?

> > What should I  do if both port  are in use? Read EDID  from primary port
> > and ignore secondary?
> 
> What about a module/kernel option ? In the meantime, I'm working on
> dual head support, though I'm not sure I'll have that finished soon.

How do you plan to handle this, create a second framebuffer device?


-- 
Earthling Michel Dänzer   \  Debian (powerpc), XFree86 and DRI developer
Software libre enthusiast  \     http://svcs.affero.net/rm.php?r=daenzer



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2003-08-28 23:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-28 16:20 [RADEON] Connector type Kronos
2003-08-28 16:43 ` Jon Smirl
2003-08-28 16:56   ` Kronos
2003-08-28 17:03   ` Benjamin Herrenschmidt
2003-08-28 17:02 ` Benjamin Herrenschmidt
2003-08-28 23:27   ` Michel Dänzer [this message]
2003-08-29  7:47     ` Benjamin Herrenschmidt
2003-08-29 15:14     ` Kronos

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=1062113236.14324.46.camel@thor.holligenstrasse29.lan \
    --to=michel@daenzer.net \
    --cc=benh@kernel.crashing.org \
    --cc=jonsmirl@yahoo.com \
    --cc=kronos@kronoz.cjb.net \
    --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).