From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: hjk@linutronix.de
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Warnings from matroxfb i2c driver
Date: Sat, 03 Mar 2007 22:31:22 -0800 [thread overview]
Message-ID: <45EA67BA.1040603@vc.cvut.cz> (raw)
In-Reply-To: <200703022100.58028.hjk@linutronix.de>
Hans-Jürgen Koch wrote:
> In my boot logs I find the following warnings:
>
> matroxfb: Matrox G550 detected
> PInS memtype = 5
> matroxfb: MTRR's turned on
> matroxfb: 1280x1024x24bpp (virtual: 1280x4369)
> matroxfb: framebuffer at 0xD4000000, mapped to 0xf8880000, size 33554432
> Console: switching to colour frame buffer device 160x64
> fb0: MATROX frame buffer device
> matroxfb_crtc2: secondary head of fb0 was registered as fb1
> **WARNING** I2C adapter driver [DDC:fb0 #0] forgot to specify physical device;
> fix it!
> **WARNING** I2C adapter driver [DDC:fb0 #1] forgot to specify physical device;
> fix it!
> **WARNING** I2C adapter driver [MAVEN:fb0] forgot to specify physical device;
> fix it!
>
> Kernel is a vanilla 2.6.20.1. Can somebody please explain this to me? Can I
> ignore these warnings?
Yes, they just warn you that in sysfs tree i2c buses for your monitors
will appear under platform and not under your g550 device in device
tree. There is no functionality impact.
Problem is fixed in 2.6.21-rc1 and newer kernels.
Petr
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2007-03-04 6:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 20:00 Warnings from matroxfb i2c driver Hans-Jürgen Koch
2007-03-04 6:31 ` Petr Vandrovec [this message]
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=45EA67BA.1040603@vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=hjk@linutronix.de \
--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).