From: Luca Tettamanti <kronos@people.it>
To: James Simmons <jsimmons@infradead.org>
Cc: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>,
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: Thu, 8 Feb 2007 00:48:37 +0100 [thread overview]
Message-ID: <20070207234837.GA27822@dreamland.darkstar.lan> (raw)
In-Reply-To: <Pine.LNX.4.64.0702062118450.9224@pentafluge.infradead.org>
Il Tue, Feb 06, 2007 at 09:22:00PM +0000, James Simmons ha scritto:
>
> > On 2/5/07, Luca Tettamanti <kronos@people.it> wrote:
> > > 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).
> >
> > No luck. i2c-dev and dependencies are loaded
> > """ lsmod | grep i2c reports """
> > i2c_i801 7404 0
> > i2c_isa 5152 0
> > i2c_piix4 8140 0
> > i2c_algo_pcf 6180 0
> > i2c_algo_pca 5380 0
> > i2c_algo_bit 8424 0
> > i2c_dev 8548 0
> > i2c_core 19680 7
> > i2c_i801,i2c_isa,i2c_piix4,i2c_algo_pcf,i2c_algo_pca,i2c_algo_bit,i2c_dev
> > """"
> >
> > There is no such thing as /dev/i2c* UNLESS I load nvidiafb. When I
> > load that, I get three busses (i2c-0, -1, and -2), but i2cdump N 0x50
> > gives me a nice tableau of X's all around, for all values of N. This
> > is using kernel 2.6.18-3 stock Debian kernel. I'll keep trying with
> > some variations, to see if I can get more sensible information.
>
> There is no stand alone nvidia card i2c driver. Its the issue of sharing
> device interfaces with the same hardware problem again!!!
Nah, nvidiafb registers the I2C busses, you can drive them with whatever
you want through the devices exported by I2C core.
The fact the none of them work makes me think that the EDID is coming
from the BIOS, we do VBE calls in real mode during early kernel setup.
Luca
--
Se non sei parte della soluzione, allora sei parte del problema.
WARNING: multiple messages have this Message-ID (diff)
From: Luca Tettamanti <kronos@people.it>
To: James Simmons <jsimmons@infradead.org>
Cc: Andrew Morton <akpm@osdl.org>,
linux-fbdev-devel@lists.sourceforge.net,
Dave Airlie <airlied@gmail.com>,
Giuseppe Bilotta <giuseppe.bilotta@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvidiafb: allow ignoring EDID info
Date: Thu, 8 Feb 2007 00:48:37 +0100 [thread overview]
Message-ID: <20070207234837.GA27822@dreamland.darkstar.lan> (raw)
In-Reply-To: <Pine.LNX.4.64.0702062118450.9224@pentafluge.infradead.org>
Il Tue, Feb 06, 2007 at 09:22:00PM +0000, James Simmons ha scritto:
>
> > On 2/5/07, Luca Tettamanti <kronos@people.it> wrote:
> > > 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).
> >
> > No luck. i2c-dev and dependencies are loaded
> > """ lsmod | grep i2c reports """
> > i2c_i801 7404 0
> > i2c_isa 5152 0
> > i2c_piix4 8140 0
> > i2c_algo_pcf 6180 0
> > i2c_algo_pca 5380 0
> > i2c_algo_bit 8424 0
> > i2c_dev 8548 0
> > i2c_core 19680 7
> > i2c_i801,i2c_isa,i2c_piix4,i2c_algo_pcf,i2c_algo_pca,i2c_algo_bit,i2c_dev
> > """"
> >
> > There is no such thing as /dev/i2c* UNLESS I load nvidiafb. When I
> > load that, I get three busses (i2c-0, -1, and -2), but i2cdump N 0x50
> > gives me a nice tableau of X's all around, for all values of N. This
> > is using kernel 2.6.18-3 stock Debian kernel. I'll keep trying with
> > some variations, to see if I can get more sensible information.
>
> There is no stand alone nvidia card i2c driver. Its the issue of sharing
> device interfaces with the same hardware problem again!!!
Nah, nvidiafb registers the I2C busses, you can drive them with whatever
you want through the devices exported by I2C core.
The fact the none of them work makes me think that the EDID is coming
from the BIOS, we do VBE calls in real mode during early kernel setup.
Luca
--
Se non sei parte della soluzione, allora sei parte del problema.
-------------------------------------------------------------------------
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-07 23:49 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
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 ` Luca Tettamanti [this message]
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=20070207234837.GA27822@dreamland.darkstar.lan \
--to=kronos@people.it \
--cc=airlied@gmail.com \
--cc=akpm@osdl.org \
--cc=giuseppe.bilotta@gmail.com \
--cc=jsimmons@infradead.org \
--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.