From: Richard Smith <rsmith@bitworks.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Rage Mobility M1 devid 4c52
Date: Thu, 15 Jan 2004 01:44:16 -0600 [thread overview]
Message-ID: <400644D0.1060500@bitworks.com> (raw)
I'm trying to run the atyfb on a board that has a ATI Rage Mobility M1
on it. Grepping the driver source yeilds some refererences to a
Mobility M1 as though its supported but my device id of 0x4c52 does not
show up in the table of known devices and the driver fails to detect my
chip.
If I copy the PCI Rage Mobililty like and change the device ID to 0x4c52
then I get atyfb messages but some of the info is wrong. For example it
says I have 4M of wram but an M1 has 8M of sdram.
Is the Mobility M1 really suppported?
--
Richard A. Smith
rsmith@bitworks.com
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
reply other threads:[~2004-01-15 7:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=400644D0.1060500@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).