All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Hardware specs?
Date: Sat, 20 Aug 2005 19:42:11 -0400	[thread overview]
Message-ID: <1124581331.4877.94.camel@localhost> (raw)
In-Reply-To: <43035F25.5000907@cs.tcd.ie>

On Wed, 2005-08-17 at 17:00 +0100, Keith O'Conor wrote: 
> 
> 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?

I did it basically the way you're doing it, by reading and tweaking
code. :)


> 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? 

Some of us do, yes.

> Are the specs openly available, only under NDA, or not at all?!

Only under NDA, and I'm afraid it's hard to get them even under that
ATM. Your best way forward might be to ask specific questions about
existing code.


-- 
Earthling Michel Dänzer      |     Debian (powerpc), X and DRI developer
Libre software enthusiast    |   http://svcs.affero.net/rm.php?r=daenzer


-------------------------------------------------------
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

  reply	other threads:[~2005-08-20 23:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-17 16:00 Hardware specs? Keith O'Conor
2005-08-20 23:42 ` Michel Dänzer [this message]
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=1124581331.4877.94.camel@localhost \
    --to=michel@daenzer.net \
    --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.