From: johan henriksson <jhn98032@gmail.com>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: Radeon xpress 200m and radeonfb kinda work
Date: Wed, 07 Mar 2007 21:58:06 +0100 [thread overview]
Message-ID: <45EF275E.4060300@gmail.com> (raw)
In-Reply-To: <45EEEBC9.1010002@redhat.com>
Chuck Ebbert wrote:
> Johan Henriksson wrote:
>
> > Hi!
> >
> > I have gotten the radeon xpress 200m (the version without dedicated
> > vmem) to work with radeonfb. The attached patch (against
> > linux-2.6.20.1) works for me. Since I don't have any docs for the
> > card I am unsure if the patch is 100% correct. Can someone else
> > with a 200m try it out? (I have tested it by enabling fbcon and
> > radeonfb in the kernel and added "video=radeonfb" to lilo. This
> > gave me a nice 1280x800 console :) )
> >
>
> Works for me as a module on Compaq V2000 notebook. 160x48 is a bit
> small, but looks very clear and crisp.
>
> Is there anything else needed to get this merged?
>
As you can see in the patch I have disabled "Dynamic Clock PM"
since it makes my card freak out (Don't know why :( ).
Is there a reason why the "default_dynclk" parameter only is available
when radeonfb is built as a module or should it be added to radeonfb_setup?
/Johan Henriksson
next prev parent reply other threads:[~2007-03-07 22:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 0:16 Radeon xpress 200m and radeonfb kinda work Johan Henriksson
2007-03-07 16:43 ` Chuck Ebbert
2007-03-07 20:58 ` johan henriksson [this message]
2007-03-08 16:00 ` Chuck Ebbert
2007-03-08 19:24 ` [patch 2.6.20-1] radeonfb: Add support for Radeon xpress 200m johan henriksson
2007-03-09 13:00 ` Benjamin Herrenschmidt
2007-03-09 19:57 ` johan henriksson
2007-03-07 22:39 ` Radeon xpress 200m and radeonfb kinda work Nigel Cunningham
2007-03-07 22:59 ` johan henriksson
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=45EF275E.4060300@gmail.com \
--to=jhn98032@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=cebbert@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.