linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: sven.luther@wanadoo.fr
Subject: monitor detection through ddc/edid stuff.
Date: Fri, 10 Sep 2004 13:16:27 +0200	[thread overview]
Message-ID: <20040910111627.GA14811@pegasos> (raw)

Hello,

I am currently working on a 3dlabs wildcat vp fbdev driver (my 560 died, but i
got a 880 Pro :). And i have some questions with the monitor detection and
ddc/edid stuff.

I have looked over fbmon.c, and foung that it contains code for parsing the
EDID data, but not for actually reading it, apart the get_EDID_from_firmware
which is rather primitive, and doesn't actually do anything (i suppose that
the edid_info.dummy is read from the x86 bios in some other function).

I also have quickly overviewed the radeon driver, which has a function to read
the EDID either from the BIOS or the pmac OF. There seem to be no code
whatsoever that adds proper EDID reading through the graphic card directly,
like it is done in XFree86, where one can do in the individual drivers (using
i2c stuff also) :

	...
	pBus->BusName = "DDC";
	pBus->I2CUDelay = WildcatVPI2CUDelay;
	pBus->I2CPutBits = WildcatVPI2CPutBits;
	pBus->I2CGetBits = WildcatVPI2CGetBits;

These three being smallish functions to delay a bit, and to put/get bits in
the DCC Clock/Data Out/In registers.

And then :

	pMon = xf86DoEDID_DDC2(pScrn->scrnIndex, pBus);

There is also a DCC1 function i think, or something such.

Would it make sense to implement such a feature in fbmon.c ? Is fbmon.c the
right place for this ? Is this already implemented somewhere else, or maybe in
some private tree somewhere ? 

As i understand this, we would need some place to set the those three
function, and then a common function to actually do a real EDID reading
through the graphic card (get_EDID_from_harware ?).

Does this make sense ? Any hint on how to best implement this ? 

Friendly,

Sven Luther




-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php

             reply	other threads:[~2004-09-11  2:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-10 11:16 Sven Luther [this message]
2004-09-10 11:44 ` monitor detection through ddc/edid stuff Sven Luther
2004-09-11 15:36 ` Kronos
2004-09-11 16:52   ` Jon Smirl
2004-09-12  8:42   ` Sven Luther
2004-09-12  9:32     ` Antonino A. Daplas
2004-09-12 10:04       ` Sven Luther
2004-09-12 10:11         ` Antonino A. Daplas
2004-09-12 10:31           ` Sven Luther
2004-09-12 13:54           ` Sven Luther
2004-09-12 21:00             ` Antonino A. Daplas
2004-09-12 14:36           ` Sven Luther
2004-09-12 21:16             ` Antonino A. Daplas

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=20040910111627.GA14811@pegasos \
    --to=sven.luther@wanadoo.fr \
    --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).