From: Sven Luther <sven.luther@wanadoo.fr>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: kronos@kronoz.cjb.net, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] 0/3 Add I2C/DDC support to radeonfb (resend)
Date: Mon, 25 Aug 2003 11:40:32 +0200 [thread overview]
Message-ID: <20030825094032.GA3327@iliana> (raw)
In-Reply-To: <1061595832.1259.41.camel@thor.holligenstrasse29.lan>
On Sat, Aug 23, 2003 at 01:43:53AM +0200, Michel Dänzer wrote:
> On Fri, 2003-08-22 at 19:09, Kronos wrote:
> >
> > i2c bus is registered in radeonfb_pci_register and unregistered in
> > radeonfb_pci_unregister. I'm a bit concerned about XFree that uses the
> > same bus...
>
> If there was an interface to userspace, the X driver could use that?
>
>
> BTW, regarding the EDID discussion, I'm not sure that a list of modes
> will cut it - e.g., the EDID of the panel in this TiBook only contains
> the native mode, but the chip can scale up pretty much any lower
> resolution.
Which is a good thing, compared to my sony SDM-X52, which in digital
mode only supports the native resolution, but the EDID erroneously
reports the mode supported by the digital connection in both case.
The EDID should report only the supported (native) mode, and the chip,
knowing what it can scale or not, should handle the other cases, no ?
Friendly,
Sven Luther
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0
next prev parent reply other threads:[~2003-08-25 9:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-22 17:09 [PATCH] 0/3 Add I2C/DDC support to radeonfb (resend) Kronos
2003-08-22 23:43 ` Michel Dänzer
2003-08-23 13:42 ` Kronos
2003-08-25 9:40 ` Sven Luther [this message]
2003-08-25 10:22 ` Michel Dänzer
2003-08-23 11:47 ` Geert Uytterhoeven
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=20030825094032.GA3327@iliana \
--to=sven.luther@wanadoo.fr \
--cc=kronos@kronoz.cjb.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=michel@daenzer.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).