All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: VESA, EDID & flat panels
Date: Tue, 04 Oct 2005 15:59:34 +0800	[thread overview]
Message-ID: <43423666.8090001@gmail.com> (raw)
In-Reply-To: <1128407961.31063.50.camel@gaston>

Benjamin Herrenschmidt wrote:
>> It think it's because the (basic) EDID is retrieved with (basic) DDC
>> (address 0x50).  If I'm not mistaken, E-EDID is retrieved with E-DDC
>> (address 0xa0). I don't exactly know the protocol (E-DDDC specs are not
>> freely available), but try probing your i2c busses with:
>>
>> i2cdump 0,1,2,etc 0xa0 
>>
>> and see if you get anything.
> 
> Are you sure we aren't talking about the same address here ? Address
> 0xa0 _is_ 0x50 shifted one bit left ... (The low bit of an i2c address
> is the RW bit). i2cdump takes shifted addresses, thus you can't pass it
> anything above 0x7f, thus passing it 0x50 is what gives you address
> 0xa0 :)
> 
> Ben.
> 
> 
> 

Here's a snippet from the HDMI specs. Not sure how helpful this is

"8.4.3 Segment pointer
 Enhanced DDC allows access of up to 32 Kbytes of data. This is accomplished
 using a combination of the 0xA0/0xA1 address pair and a segment pointer. For
 each value of the segment pointer, 256 bytes of data are available at the
 0xA0/0xA1 address pair. An unspecified segment pointer references the same
 data as when the segment pointer is zero. Each successive value of the
 segment pointer allows access to the next two blocks of E-EDID (128 bytes
 each). The value of the segment pointer register cannot be read since it is
 reset at the completion of each command."

Tony



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

  parent reply	other threads:[~2005-10-04  8:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-03 22:53 VESA, EDID & flat panels Benjamin Herrenschmidt
2005-10-03 23:18 ` Richard Smith
2005-10-04  3:43   ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2005-10-04  6:27     ` Antonino A. Daplas
2005-10-04  6:39       ` Benjamin Herrenschmidt
2005-10-04  6:56         ` Antonino A. Daplas
2005-10-04  7:59         ` Antonino A. Daplas [this message]
2005-10-04  8:50           ` Benjamin Herrenschmidt
2005-10-04 12:04             ` Antonino A. Daplas
2005-10-04 12:35             ` Richard Smith
2005-10-10  5:50               ` Benjamin Herrenschmidt
2005-10-04  0:03 ` Antonino A. Daplas
2005-10-10  8:43 ` Egbert Eich

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=43423666.8090001@gmail.com \
    --to=adaplas@gmail.com \
    --cc=benh@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.