From: Phillip Susi <psusi@cfl.rr.com>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Information resources
Date: Fri, 25 Feb 2011 09:38:34 -0500 [thread overview]
Message-ID: <4D67BEEA.3020207@cfl.rr.com> (raw)
In-Reply-To: <AANLkTik+WkYXou=ZWEU==Vw+0OpMD9=Qpxnbrt2fZtBo@mail.gmail.com>
On 2/24/2011 6:03 PM, Jerome Glisse wrote:
> We don't have source of firmware, only nouveau is reverse engineering
> the nvidia one.
Then where does the firmware come from? I've been glancing at the AMD
documentation for the R600 and I'd like to figure out why the firmware
seems to be running in an infinite loop without ever halting, and
driving the temperature of my card over 80 C, but I need the original
assembly code for that.
>> 2) What is a "fence"?
>
> It's what it means, it tell the cpu when the gpu reached some point in
> command stream or resource usage so we know we can free or move memory
> that was previously in use. Or simply to know when gpu is done doing
> somethings.
So it is kind of like a barrier in the IO world? You put a dozen
commands into the pipeline and then a fence, and when they all complete,
the fence gives you feedback so you know?
next prev parent reply other threads:[~2011-02-25 14:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 19:50 Information resources Phillip Susi
2011-02-24 23:03 ` Jerome Glisse
2011-02-25 14:38 ` Phillip Susi [this message]
2011-02-25 20:03 ` Dave Airlie
2011-02-25 20:42 ` Phillip Susi
2011-02-25 20:56 ` Dave Airlie
2011-02-25 21:12 ` Garry Hurley
2011-02-25 23:09 ` Phillip Susi
2011-02-25 23:19 ` Alex Deucher
2011-02-25 23:30 ` Phillip Susi
2011-02-25 23:50 ` Alex Deucher
2011-02-25 20:15 ` Garry Hurley Jr.
2011-02-25 20:38 ` Alex Deucher
2011-02-25 23:03 ` Phillip Susi
2011-02-25 23:06 ` Alex Deucher
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=4D67BEEA.3020207@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=j.glisse@gmail.com \
/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.