From: Luca Tettamanti <kronos@people.it>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net,
Andrew Morton <akpm@osdl.org>, Dave Airlie <airlied@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Linux-fbdev-devel] [PATCH] nvidiafb: allow ignoring EDID info
Date: Mon, 5 Feb 2007 21:18:24 +0100 [thread overview]
Message-ID: <20070205201824.GA13431@dreamland.darkstar.lan> (raw)
In-Reply-To: <cb7bb73a0702041317u4ca2fbabp45cf56526e57c982@mail.gmail.com>
Il Sun, Feb 04, 2007 at 10:17:08PM +0100, Giuseppe Bilotta ha scritto:
> On 2/4/07, Luca Tettamanti <kronos@people.it> wrote:
> >Giuseppe, can you send me the EDID block of your monitor?
>
> I'd gladly do it, if I knew how to retrieve it ... because apparently,
> get-edid doesn't work, even though both the nv driver for X and
> nvidiafb manage to retrieve it.
get-edid uses the BIOS, while the other two talk directly over the I2C
bus.
Try loading i2c-dev (I2C_CHARDEV); With i2cdump[1] you can read the EDID
block, which resides at address 0x50:
i2cdump N 0x50 (where N is the bus number)
If you are unshure about bus number try with all the available
/dev/i2c-* devices (you may want to unload HW monitor drivers first, so
you don't poke at random stuff).
Luca
[1] lm-sensors package, at least on Debian.
--
La somma dell'intelligenza sulla terra è una costante.
La popolazione è in aumento.
WARNING: multiple messages have this Message-ID (diff)
From: Luca Tettamanti <kronos@people.it>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, Dave Airlie <airlied@gmail.com>,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvidiafb: allow ignoring EDID info
Date: Mon, 5 Feb 2007 21:18:24 +0100 [thread overview]
Message-ID: <20070205201824.GA13431@dreamland.darkstar.lan> (raw)
In-Reply-To: <cb7bb73a0702041317u4ca2fbabp45cf56526e57c982@mail.gmail.com>
Il Sun, Feb 04, 2007 at 10:17:08PM +0100, Giuseppe Bilotta ha scritto:
> On 2/4/07, Luca Tettamanti <kronos@people.it> wrote:
> >Giuseppe, can you send me the EDID block of your monitor?
>
> I'd gladly do it, if I knew how to retrieve it ... because apparently,
> get-edid doesn't work, even though both the nv driver for X and
> nvidiafb manage to retrieve it.
get-edid uses the BIOS, while the other two talk directly over the I2C
bus.
Try loading i2c-dev (I2C_CHARDEV); With i2cdump[1] you can read the EDID
block, which resides at address 0x50:
i2cdump N 0x50 (where N is the bus number)
If you are unshure about bus number try with all the available
/dev/i2c-* devices (you may want to unload HW monitor drivers first, so
you don't poke at random stuff).
Luca
[1] lm-sensors package, at least on Debian.
--
La somma dell'intelligenza sulla terra è una costante.
La popolazione è in aumento.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next prev parent reply other threads:[~2007-02-05 20:18 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-28 10:48 [PATCH] nvidiafb: allow ignoring EDID info Giuseppe Bilotta
2007-01-28 11:05 ` Prakash Punnoor
2007-01-29 0:08 ` Andrew Morton
2007-01-29 0:08 ` Andrew Morton
2007-01-29 0:12 ` [Linux-fbdev-devel] " Dave Airlie
2007-01-29 0:12 ` Dave Airlie
2007-01-29 0:27 ` [Linux-fbdev-devel] " Andrew Morton
2007-01-29 0:27 ` Andrew Morton
2007-01-29 0:29 ` [Linux-fbdev-devel] " Andrew Morton
2007-01-29 0:29 ` Andrew Morton
2007-01-29 0:39 ` [Linux-fbdev-devel] " Dave Airlie
2007-01-29 0:39 ` Dave Airlie
2007-01-29 14:37 ` [Linux-fbdev-devel] " Giuseppe Bilotta
2007-01-30 20:33 ` Luca Tettamanti
2007-01-30 20:33 ` Luca Tettamanti
2007-02-04 20:17 ` [Linux-fbdev-devel] " Luca Tettamanti
2007-02-04 21:17 ` Giuseppe Bilotta
2007-02-05 20:18 ` Luca Tettamanti [this message]
2007-02-05 20:18 ` Luca Tettamanti
2007-02-05 21:28 ` [Linux-fbdev-devel] " Giuseppe Bilotta
2007-02-06 21:22 ` James Simmons
2007-02-06 21:22 ` James Simmons
2007-02-07 23:48 ` [Linux-fbdev-devel] " Luca Tettamanti
2007-02-07 23:48 ` Luca Tettamanti
2007-02-08 0:19 ` [Linux-fbdev-devel] " Giuseppe Bilotta
2007-02-11 18:17 ` Luca Tettamanti
2007-02-11 18:17 ` Luca Tettamanti
2007-02-13 9:25 ` [Linux-fbdev-devel] " Giuseppe Bilotta
2007-02-17 18:14 ` Luca Tettamanti
2007-02-17 18:14 ` Luca Tettamanti
2007-02-17 18:46 ` [Linux-fbdev-devel] " Giuseppe Bilotta
2007-02-08 17:56 ` James Simmons
2007-02-08 17:56 ` James Simmons
2007-02-07 23:57 ` [Linux-fbdev-devel] " Luca Tettamanti
2007-02-07 23:57 ` Luca Tettamanti
2007-02-06 20:37 ` [Linux-fbdev-devel] " James Simmons
2007-02-06 23:08 ` Giuseppe Bilotta
2007-02-21 23:43 ` Antonino A. Daplas
2007-02-21 23:43 ` Antonino A. Daplas
2007-02-22 8:01 ` [Linux-fbdev-devel] " Giuseppe Bilotta
2007-02-22 8:40 ` Antonino A. Daplas
2007-02-22 8:40 ` Antonino A. Daplas
[not found] ` <cb7bb73a0702220548s55380f7fk995726ffd349823b@mail.gmail.com>
[not found] ` <1172153358.4306.17.camel@daplas>
2007-02-22 15:55 ` [Linux-fbdev-devel] " Giuseppe Bilotta
2007-02-22 16:21 ` Antonino A. Daplas
2007-02-22 16:21 ` Antonino A. Daplas
2007-02-22 19:08 ` [Linux-fbdev-devel] " Giuseppe Bilotta
2007-02-22 23:34 ` Antonino A. Daplas
2007-02-22 23:34 ` Antonino A. Daplas
2007-02-23 13:34 ` [Linux-fbdev-devel] " Giuseppe Bilotta
2007-02-23 13:34 ` Giuseppe Bilotta
2007-02-24 7:04 ` [Linux-fbdev-devel] " Antonino A. Daplas
2007-02-24 7:04 ` Antonino A. Daplas
2007-02-24 9:16 ` [Linux-fbdev-devel] " Giuseppe Bilotta
2007-02-24 9:16 ` Giuseppe Bilotta
2007-02-24 21:16 ` [Linux-fbdev-devel] " Antonino A. Daplas
2007-02-25 10:26 ` Giuseppe Bilotta
2007-02-25 10:26 ` Giuseppe Bilotta
2007-02-25 11:10 ` [Linux-fbdev-devel] " Antonino A. Daplas
2007-02-25 11:10 ` Antonino A. Daplas
2007-02-25 13:16 ` [Linux-fbdev-devel] " Giuseppe Bilotta
2007-02-25 13:16 ` Giuseppe Bilotta
2007-02-26 12:46 ` [Linux-fbdev-devel] " Antonino A. Daplas
2007-02-22 17:03 ` Antonino A. Daplas
2007-02-22 20:39 ` Luca Tettamanti
2007-02-22 20:39 ` Luca Tettamanti
2007-02-22 23:34 ` [Linux-fbdev-devel] " Antonino A. Daplas
2007-02-22 23:34 ` 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=20070205201824.GA13431@dreamland.darkstar.lan \
--to=kronos@people.it \
--cc=airlied@gmail.com \
--cc=akpm@osdl.org \
--cc=giuseppe.bilotta@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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.