From: Javier Villavicencio <jvillavicencio@arnet.com.ar>
To: DuDe <dude68@tiscali.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Radeon 9600 triplex
Date: Thu, 23 Oct 2003 18:06:08 -0300 [thread overview]
Message-ID: <3F9842C0.10206@arnet.com.ar> (raw)
In-Reply-To: <200310232251.12780.dude68@tiscali.it>
DuDe wrote:
> Hi list, i would like add 9600 radeon support on radeonfb driver, now i have
> successfully add a limited support on radeonfb driver, but i have some
> problem, the system boot, i see 2 penguin logo but the cursor is scared, and
> if use fbset to set resolution, i cant get resolution function but only a
> square area of the crt are in hires, the rest is dirty.
>
> Where i can find infos about howto add support in radeonfb?
>
> Many thanks
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
I did something similar taking parts of the radeonfb driver from
2.4.23-preX (maybe 6) into 2.6, hard coding the resolution into the code
I have 1024x768 and a ugly big cursor on console, fbtv and links on
framebuffer works fine, but when I switch back from XFree (using fglrx
drivers from ati) the console is completely unusable no matter what can
I do with fbset (seems that I missed some clock setting for the RV350).
So the very first source of support for 9600 is the working driver on 2.4.23
Greetings
Javier Villavicencio.
next prev parent reply other threads:[~2003-10-23 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 22:51 Radeon 9600 triplex DuDe
2003-10-23 21:06 ` Javier Villavicencio [this message]
2003-10-23 21:09 ` Javier Villavicencio
2003-10-23 22:42 ` James Simmons
2003-10-23 23:06 ` Javier Villavicencio
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=3F9842C0.10206@arnet.com.ar \
--to=jvillavicencio@arnet.com.ar \
--cc=dude68@tiscali.it \
--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.