From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Simmons <jsimmons@infradead.org>
Cc: Florin Iucha <florin@iucha.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Framebuffer updates.
Date: 26 Mar 2003 14:16:11 +0100 [thread overview]
Message-ID: <1048684571.10476.40.camel@zion.wanadoo.fr> (raw)
In-Reply-To: <Pine.LNX.4.44.0303252049550.6228-100000@phoenix.infradead.org>
On Tue, 2003-03-25 at 21:50, James Simmons wrote:
> Try using stty. I see most people will continue to use fbset so I guess I
> need to patch it up to do the right thing.
Well, I don't like the fbdev magially picking modes like this,
those modes may just not be supported by the display. At least,
fbset allows me to setup the proper timings for 'special'
displays like iMac fixed hoziontal frequency for example.
Ultimately, we really need a "monitor" driver on top of the
fbdev that does DDC/EDID when the low level fbdev can provide
an i2c bus or EDID information via some different way and
that can be tweaked to deal with special monitors when we
know we are using these.
Ben.
next prev parent reply other threads:[~2003-03-26 13:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 17:57 Framebuffer updates James Simmons
2003-03-25 18:20 ` Jens Axboe
2003-03-25 18:47 ` James Simmons
2003-03-25 18:27 ` Florin Iucha
2003-03-25 20:50 ` James Simmons
2003-03-26 13:16 ` Benjamin Herrenschmidt [this message]
2003-03-26 20:08 ` James Simmons
2003-03-26 14:03 ` Scott Robert Ladd
2003-03-26 20:07 ` James Simmons
-- strict thread matches above, loose matches on Subject: below --
2003-03-18 17:16 James Simmons
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=1048684571.10476.40.camel@zion.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=florin@iucha.net \
--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 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).