From: Kronos <kronos@kronoz.cjb.net>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: fb-devel <linux-fbdev-devel@lists.sourceforge.net>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: Some thoughts on Rage128/Radeon EDID
Date: Sun, 17 Aug 2003 16:45:28 +0200 [thread overview]
Message-ID: <20030817144528.GA843@dreamland.darkstar.lan> (raw)
In-Reply-To: <20030817063234.75420.qmail@web14910.mail.yahoo.com>
Il Sat, Aug 16, 2003 at 11:32:34PM -0700, Jon Smirl ha scritto:
> Somewhat complete I2C driver code exists in the KATOS
> project.
> http://www.core.binghamton.edu/~insomnia/gatos/katos/src/katos-0.5.tar.gz
Cool. I'm coding something like this but I'm unable to get an ACK back
from the card. I'll look at this code and see if I can speak to my
board.
> These next thoughts just apply to 2.6, not 2.4.
>
> There are a lot of things on the I2C bus on the these
> cards: EDID, video capture, teletext, tv out and mpeg
> decoding control, etc..
>
> 1) How about making the fb driver register itself as
> an I2C bus so that it appears in /proc/bus/I2C? I've
> never touched I2C code so I don't know what this
> involves.
Well, on 2.6 the device model will handle this pretty well. The devices
and the driver will show up in /sys/bus/i2c (sysfs).
> 2) Making the card appear in /proc/bus/I2C makes it
> easy to get to from user space. A user level app can
> read the EDID info, diff it off against card
> capabilities and IOCTL the new mode in. Maybe modify
> fbset.
Sure, we can expose EDID and other infos to user space. Maybe we can use
sysfs to set a new mode. I think that Greg KH is working on it.
Luca
--
Reply-To: kronos@kronoz.cjb.net
Home: http://kronoz.cjb.net
Windows NT: Designed for the Internet. The Internet: Designed for Unix.
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
next prev parent reply other threads:[~2003-08-17 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-17 6:32 Some thoughts on Rage128/Radeon EDID Jon Smirl
2003-08-17 8:05 ` Benjamin Herrenschmidt
2003-08-17 14:45 ` Kronos [this message]
2003-08-17 17:34 ` EDID through sysfs Jon Smirl
2003-08-17 23:36 ` Ville Syrjälä
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=20030817144528.GA843@dreamland.darkstar.lan \
--to=kronos@kronoz.cjb.net \
--cc=benh@kernel.crashing.org \
--cc=jonsmirl@yahoo.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=paulus@samba.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 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).