Hi,
After many tests and reboot i have a set of register that
may influence 9800 lockups. Unfortunetly i don't know
how to play with this register as they doesn't seems to be
used anywhere (nor X driver, dri, drm if i trust my grep :))
RADEON_LATENCY the most likely to help to resolve the
On Friday 10 June 2005 18:10, Vladimir Dergachev wrote:
On Fri, 10 Jun 2005, Aapo Tahkola wrote:
Someone, I believe it was Aapo, said that they see white lines across
the
screen when the framerate is fairly high. I didn't see this up until
yesterday
when I had to change from my
On 6/12/05, Nicolai Haehnle [EMAIL PROTECTED] wrote:
On Friday 10 June 2005 18:10, Vladimir Dergachev wrote:
On Fri, 10 Jun 2005, Aapo Tahkola wrote:
Someone, I believe it was Aapo, said that they see white lines across
the
screen when the framerate is fairly high. I didn't see this
On Sun, 12 Jun 2005, Jerome Glisse wrote:
Hi,
After many tests and reboot i have a set of register that
may influence 9800 lockups. Unfortunetly i don't know
how to play with this register as they doesn't seems to be
used anywhere (nor X driver, dri, drm if i trust my grep :))
On 6/12/05, Vladimir Dergachev [EMAIL PROTECTED] wrote:
On Sun, 12 Jun 2005, Jerome Glisse wrote:
Hi,
After many tests and reboot i have a set of register that
may influence 9800 lockups. Unfortunetly i don't know
how to play with this register as they doesn't seems to be
used
Thx for the info but seems that the most important (at least to me :))
RADEON_LATENCY have no specs ?
I really think, nearly convinced that this the key register to solve the
lockup. I dump the reg after a cold boot with xorg r300, then
i quit xorg r300 and launch x with fglrx don't launch
Btw Daniels suggest me that this could be a mirror of
the latency reg register(0xd) of PCI. If it is should i expect
it to change overtime or should it keeps its value ?
Jerome Glisse
---
This SF.Net email is sponsored by: NEC IT Guy Games.
I've found myself in the unfortunate ownership of many of these pitiful
SiS315-based cards and boards with onboard SiS video. I may be interested
in reverse-engineering, as I rather like that sort of tedious work.
however, after seeing as much as I have seen from these short-sighted
companies, I
It's not only RADEON_LATENCY if i set PCI latency to 0xff
i still got the lockup i am pretty disappointed as it seemed
to be the winning register. Anyway here is a longer list of
reg that may play role (i will try to find a place on the web
to put the dump thus anyone interested could look at them
I'm rather interested in starting a project to reverse engineer these
blasted chips, but I'm somewhat more inclined to start a boycott of them
instead.
For reverse engineering, I *think* the DLL has an EULA that doesn't let
you do any sort of peeking into it, so for legal reasons, we might not be
Jerome Glisse wrote:
Does the following differences means that the
fglrx driver load another microcode ?
Last I checked, Yes.
Rune Petersen
---
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How
Someone explain to me why an organised boycott of SiS graphics chips
would somehow ENCOURAGE them to help?
Reducing their sales means they have a vat of new excuses for not
supporting you.
--
Matt Sealey [EMAIL PROTECTED]
Manager, Genesi, Developer Relations
-Original Message-
On 6/12/05, Rune Petersen [EMAIL PROTECTED] wrote:
Jerome Glisse wrote:
Does the following differences means that the
fglrx driver load another microcode ?
Last I checked, Yes.
But when reloading r300 (radeon module) the fglrx
microcode is overwritten no ?
Jerome Glisse
Jerome Glisse wrote:
On 6/12/05, Rune Petersen [EMAIL PROTECTED] wrote:
Jerome Glisse wrote:
Does the following differences means that the
fglrx driver load another microcode ?
Last I checked, Yes.
But when reloading r300 (radeon module) the fglrx
microcode is overwritten no ?
yes.
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=2241
[EMAIL PROTECTED] changed:
What|Removed |Added
Does the following differences means that the
fglrx driver load another microcode ?
I've written a hw_script that reads back the microcode from fglrx,
I've already replaced my microcode to see if my issues were with it (they
weren't..)
I've added a hw_scripts directory to r300_driver with 3
On Sun, 12 Jun 2005, Rune Petersen wrote:
Jerome Glisse wrote:
On 6/12/05, Rune Petersen [EMAIL PROTECTED] wrote:
Jerome Glisse wrote:
Does the following differences means that the
fglrx driver load another microcode ?
Last I checked, Yes.
But when reloading r300 (radeon module) the
On Sun, 12 Jun 2005, Matt Sealey wrote:
Someone explain to me why an organised boycott of SiS graphics chips
would somehow ENCOURAGE them to help?
If all other things have been tried why not ?
At least the boycott also makes sure that people who follow it don't have
hardware we can't
18 matches
Mail list logo
