From: Keith O'Conor <Keith.OConor@cs.tcd.ie>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Hardware specs?
Date: Wed, 17 Aug 2005 17:00:37 +0100 [thread overview]
Message-ID: <43035F25.5000907@cs.tcd.ie> (raw)
Hi everyone,
I'm in the position of needing to write a Radeon driver for a new system
board being built here at our university. I figured my first steps would
be to try and reproduce the radeonfb driver to change the resolution,
and go from there.
Up until now I've been only developing graphics applications, so alot of
these things are new to me - pixel clocks, horizontal timings, PLL, MTRR
etc.etc.... it's all quite overwhelming. I've been reading as much as I
can, but there are still big gaps in my understanding - how did everyone
else get up to speed in this area?
My main problem is that although it's fairly easy to follow the radeonfb
source and the fb in general, when it comes to what register does what
I'm completely lost. Did the people who wrote the driver have technical
specs from ATI telling them which did what? Are the specs openly
available, only under NDA, or not at all?!
I'd really appreciate any tips anyone could give me on where I should be
looking.
Thanks,
Keith
--
_____________
Keith O'Conor
Image Synthesis Group
Computer Science Department
University of Dublin, Trinity College
http://isg.cs.tcd.ie/keith
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next reply other threads:[~2005-08-17 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 16:00 Keith O'Conor [this message]
2005-08-20 23:42 ` Hardware specs? Michel Dänzer
2005-08-22 16:46 ` Keith O'Conor
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=43035F25.5000907@cs.tcd.ie \
--to=keith.oconor@cs.tcd.ie \
--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 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.