From: Richard Smith <rsmith@bitworks.com>
To: fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Confused about atyfb status.
Date: Fri, 16 Jan 2004 22:26:00 -0600 [thread overview]
Message-ID: <4008B958.7010104@bitworks.com> (raw)
In-Reply-To: <200401170123.23351.alex.kern@gmx.de>
I'm trying to use the atyfb on a Rage Mobility M1 but I'm confused on
which source tree has the best chance of getting to work.
Grepping through both the 2.4.24 and 2.6.1rc3 tree I find that the
2.4.24 tree has several references to a mobility M1 in the comments.
The 2.6.1rc3 tree does not.
Neither tree however has an entry for my device. Neither will detect my
device which has an id of 0x4c52.
If I copy one of the "3D RAGE Mobility" id lines and change the clocks
to what I think they should be the device gets detected but various
specifications (like ammount and type of RAM) are incorrect.
So if I am about to start hacking on a tree to figure out whats wrong
what tree should I use? Where is the most advanced tree for the atyfb
located?
--
Richard A. Smith
rsmith@bitworks.com
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-01-17 4:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 0:23 Fwd: [PATCH] ATI Mach64 accelerated imgblit (sligthly improved) Alexander Kern
2004-01-17 4:26 ` Richard Smith [this message]
2004-01-17 6:38 ` Confused about atyfb status Jon Smirl
2004-01-17 7:31 ` Richard Smith
2004-01-17 12:03 ` Alexander Kern
2004-01-18 22:52 ` Benjamin Herrenschmidt
2004-01-20 1:48 ` still ..Confused about atyfb and M1 Richard Smith
2004-01-28 0:07 ` Richard Smith
2004-01-30 21:47 ` James Simmons
2004-02-03 19:16 ` Richard Smith
2004-02-04 9:06 ` Geert Uytterhoeven
2004-02-04 15:16 ` Richard Smith
2004-02-04 15:35 ` Geert Uytterhoeven
2004-02-05 17:55 ` Richard Smith
2004-02-05 20:16 ` Geert Uytterhoeven
2004-02-05 21:37 ` Richard Smith
2004-02-05 22:57 ` Benjamin Herrenschmidt
2004-02-06 0:22 ` Richard Smith
2004-02-06 9:17 ` Geert Uytterhoeven
2004-02-06 20:13 ` Richard Smith
2004-02-07 17:54 ` Geert Uytterhoeven
2004-02-08 20:42 ` Alexander Kern
2004-02-09 22:51 ` Richard Smith
2004-02-06 23:30 ` James Simmons
2004-02-06 23:42 ` Richard Smith
2004-02-04 15:18 ` Richard Smith
2004-02-04 15:36 ` Geert Uytterhoeven
2004-02-04 23:29 ` Benjamin Herrenschmidt
2004-02-03 22:18 ` Richard Smith
2004-01-17 18:36 ` Confused about atyfb status Geert Uytterhoeven
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=4008B958.7010104@bitworks.com \
--to=rsmith@bitworks.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).