On Fri, 2011-02-25 at 15:42 -0500, Phillip Susi wrote:
> On 2/25/2011 3:03 PM, Dave Airlie wrote:
> > How do you know its running in an infinite loop?
>
> Because the gpu temperature is rising to over 80 C, so it is busy doing
> something. And this is booting with init=/bin/bash, so NOTHING is
>
On Fri, 2011-02-25 at 09:38 -0500, Phillip Susi wrote:
> 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
On Fri, Feb 25, 2011 at 6:30 PM, Phillip Susi wrote:
> On 02/25/2011 06:19 PM, Alex Deucher wrote:
>>
>> The memory clock is still running at whatever clock it's set to unless
>> you manually change it. ?Things are like displays are constantly being
>> fed from vram.
>
> Sure, the master clock is
On 02/25/2011 06:19 PM, Alex Deucher wrote:
> The memory clock is still running at whatever clock it's set to unless
> you manually change it. Things are like displays are constantly being
> fed from vram.
Sure, the master clock is still running, but the dac only reads from the
frame buffer so f
On Fri, Feb 25, 2011 at 6:09 PM, Phillip Susi wrote:
> On 02/25/2011 03:56 PM, Dave Airlie wrote:
>>
>> So you made an assumpution you knew how graphics cards worked and
>> derived a theory, unfortunately the assumption was wrong.
>
> How so? ?After studying the R600 documentation I found, it soun
On 02/25/2011 03:56 PM, Dave Airlie wrote:
> So you made an assumpution you knew how graphics cards worked and
> derived a theory, unfortunately the assumption was wrong.
How so? After studying the R600 documentation I found, it sounds like
whatever microcode is in that firmware image is constan
On Fri, Feb 25, 2011 at 6:03 PM, Phillip Susi wrote:
> On 02/25/2011 03:38 PM, Alex Deucher wrote:
>>
>> The CP firmware has nothing to do with the temperature. ?The CP
>> firmware is just a packet parser for reading in command buffers and
>> programming the register backbone. ?Just alike a CPU, t
On 02/25/2011 03:38 PM, Alex Deucher wrote:
> The CP firmware has nothing to do with the temperature. The CP
> firmware is just a packet parser for reading in command buffers and
> programming the register backbone. Just alike a CPU, the GPU runs at
> whatever speed it's clock is set to. You can
I am going to have to get caught up on the development chain. I dropped off
for a while while I pursued my MS degree and concentrated on paying the
bills, but I am going to have to get back into the thick of coding. I am
going through withdrawal. Management courses and systems administration
task
On Fri, Feb 25, 2011 at 6:30 PM, Phillip Susi wrote:
> On 02/25/2011 06:19 PM, Alex Deucher wrote:
>>
>> The memory clock is still running at whatever clock it's set to unless
>> you manually change it. Things are like displays are constantly being
>> fed from vram.
>
> Sure, the master clock is
On 2/25/2011 3:03 PM, Dave Airlie wrote:
> How do you know its running in an infinite loop?
Because the gpu temperature is rising to over 80 C, so it is busy doing
something. And this is booting with init=/bin/bash, so NOTHING is
running that could be keeping it busy.
I had been under the impres
On Fri, Feb 25, 2011 at 9:38 AM, Phillip Susi wrote:
> 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
On 02/25/2011 06:19 PM, Alex Deucher wrote:
The memory clock is still running at whatever clock it's set to unless
you manually change it. Things are like displays are constantly being
fed from vram.
Sure, the master clock is still running, but the dac only reads from the
frame buffer so fast
On Fri, Feb 25, 2011 at 6:09 PM, Phillip Susi wrote:
> On 02/25/2011 03:56 PM, Dave Airlie wrote:
>>
>> So you made an assumpution you knew how graphics cards worked and
>> derived a theory, unfortunately the assumption was wrong.
>
> How so? After studying the R600 documentation I found, it soun
The infinite loop you mentioned sounds like it could be several things. Polling
could explain an infinite loop - "while true {checkForUpdates();}". Such code
was common enough in some videi games, too. I think that mechanism has been
replaced by scheduled and periodic checks in most cases, but y
On 02/25/2011 03:56 PM, Dave Airlie wrote:
So you made an assumpution you knew how graphics cards worked and
derived a theory, unfortunately the assumption was wrong.
How so? After studying the R600 documentation I found, it sounds like
whatever microcode is in that firmware image is constant
On Fri, Feb 25, 2011 at 6:03 PM, Phillip Susi wrote:
> On 02/25/2011 03:38 PM, Alex Deucher wrote:
>>
>> The CP firmware has nothing to do with the temperature. The CP
>> firmware is just a packet parser for reading in command buffers and
>> programming the register backbone. Just alike a CPU, t
On 02/25/2011 03:38 PM, Alex Deucher wrote:
The CP firmware has nothing to do with the temperature. The CP
firmware is just a packet parser for reading in command buffers and
programming the register backbone. Just alike a CPU, the GPU runs at
whatever speed it's clock is set to. You can manua
I am going to have to get caught up on the development chain. I dropped off
for a while while I pursued my MS degree and concentrated on paying the
bills, but I am going to have to get back into the thick of coding. I am
going through withdrawal. Management courses and systems administration
task
On Fri, 2011-02-25 at 15:42 -0500, Phillip Susi wrote:
> On 2/25/2011 3:03 PM, Dave Airlie wrote:
> > How do you know its running in an infinite loop?
>
> Because the gpu temperature is rising to over 80 C, so it is busy doing
> something. And this is booting with init=/bin/bash, so NOTHING is
>
On 2/25/2011 3:03 PM, Dave Airlie wrote:
> How do you know its running in an infinite loop?
Because the gpu temperature is rising to over 80 C, so it is busy doing
something. And this is booting with init=/bin/bash, so NOTHING is
running that could be keeping it busy.
I had been under the impres
On Fri, Feb 25, 2011 at 9:38 AM, Phillip Susi wrote:
> 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
The infinite loop you mentioned sounds like it could be several things. Polling
could explain an infinite loop - "while true {checkForUpdates();}". Such code
was common enough in some videi games, too. I think that mechanism has been
replaced by scheduled and periodic checks in most cases, but y
On Fri, 2011-02-25 at 09:38 -0500, Phillip Susi wrote:
> 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
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
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
On Thu, Feb 24, 2011 at 2:50 PM, Phillip Susi wrote:
> I'm looking for resources I can read to learn more. ?I mostly have some
> basic questions that are probably in a FAQ or something, so if someone
> could point me the right way I'd appreciate it.
>
dri.freedesktop.org has most informations we
On Thu, Feb 24, 2011 at 2:50 PM, Phillip Susi wrote:
> I'm looking for resources I can read to learn more. I mostly have some
> basic questions that are probably in a FAQ or something, so if someone
> could point me the right way I'd appreciate it.
>
dri.freedesktop.org has most informations we
I'm looking for resources I can read to learn more. I mostly have some
basic questions that are probably in a FAQ or something, so if someone
could point me the right way I'd appreciate it.
Specifically some of the things I have been wondering are:
1) It looks like the firmware is in the kernel
I'm looking for resources I can read to learn more. I mostly have some
basic questions that are probably in a FAQ or something, so if someone
could point me the right way I'd appreciate it.
Specifically some of the things I have been wondering are:
1) It looks like the firmware is in the kernel
30 matches
Mail list logo
