From: Jon Smirl <jonsmirl@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Re: [linux-2.6.10] radeonfb / oops
Date: Fri, 4 Feb 2005 16:04:20 -0500 [thread overview]
Message-ID: <9e47339105020413047ada9b2c@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0502042042120.25309@pentafluge.infradead.org>
On Fri, 4 Feb 2005 20:42:48 +0000 (GMT), James Simmons
<jsimmons@www.infradead.org> wrote:
>
> > > plain text document attachment (.config)
> >
> > You seem to have built both the old and new radeonfb's ... can you
> > remove the old one ?
>
> Plus a whole bunch of other drivers. BTW would you consider it time to
> kill off the old radeon fbdev driver?
Last time I checked the new radeonfb driver could not set modes on an
analog LCD panel. Something is mess up in how it computes the closest
mode to what you ask for. If the mode isn't an exact match it won't
set the mode. Old driver does not have this problem.
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-02-04 21:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 8:25 [linux-2.6.10] radeonfb / oops Paweł Sikora
2005-02-04 5:59 ` Benjamin Herrenschmidt
2005-02-04 20:42 ` James Simmons
2005-02-04 21:04 ` Jon Smirl [this message]
2005-02-04 21:17 ` Otto Wyss
2005-02-04 21:59 ` James Simmons
2005-02-05 0:36 ` Jon Smirl
2005-02-05 10:40 ` Otto Wyss
2005-02-04 20:42 ` James Simmons
-- strict thread matches above, loose matches on Subject: below --
2005-02-12 15:39 Paweł Sikora
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=9e47339105020413047ada9b2c@mail.gmail.com \
--to=jonsmirl@gmail.com \
--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).