From: Antonino Daplas <adaplas@pol.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jak <rfjak@eircom.net>, James Simmons <jsimmons@infradead.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: rivafb "Badness" using fbdev.diff.gz and 2.5.5[45]
Date: 21 Jan 2003 19:31:24 +0800 [thread overview]
Message-ID: <1043148630.1199.30.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.GSO.4.21.0301211126490.24563-100000@vervain.sonytel.be>
On Tue, 2003-01-21 at 18:29, Geert Uytterhoeven wrote:
> On 21 Jan 2003, Antonino Daplas wrote:
> > The only problem right now is how do you pass the monitor info to the
> > driver? The best way is to parse the EDID block and use I2C/DDC.
> > Personally, I think passing the monitor info as a boot/module option is
> > the simplest and safest method.
>
> Through sysfs? echo MY_MONITOR_LIMITS > /proc/...?
>
> Since ioctls are considered evil these days, changing the resolution etc. could
> work in a similar way as well.
>
True, but I prefer having the monitor limits at driver load time so I
can immediately go into a high resolution.
Tony
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next prev parent reply other threads:[~2003-01-21 11:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-11 13:30 rivafb "Badness" using fbdev.diff.gz and 2.5.5[45] Jak
2003-01-15 0:43 ` James Simmons
2003-01-18 20:28 ` Jak
2003-01-19 15:40 ` Antonino Daplas
2003-01-20 19:09 ` Jak
2003-01-20 22:44 ` Antonino Daplas
2003-01-21 10:29 ` Geert Uytterhoeven
2003-01-21 11:31 ` Antonino Daplas [this message]
2003-01-24 22:53 ` James Simmons
2003-01-25 9:00 ` Geert Uytterhoeven
2003-01-30 23:00 ` Antonino Daplas
2003-02-12 20:13 ` James Simmons
2003-01-21 0:08 ` Antonino Daplas
2003-01-24 20:14 ` James Simmons
2003-01-30 23:01 ` Antonino Daplas
2003-02-12 20:15 ` James Simmons
2003-02-12 23:37 ` Antonino Daplas
2003-01-24 19:09 ` James Simmons
-- strict thread matches above, loose matches on Subject: below --
2003-01-19 11:29 Fredrik Noring
2003-01-19 15:41 ` Antonino Daplas
2003-01-19 16:42 ` Fredrik Noring
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=1043148630.1199.30.camel@localhost.localdomain \
--to=adaplas@pol.net \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=rfjak@eircom.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).