2010/2/3 Stephane Marchesin :
> Really if you have such lockups they may also happen on x86, did you
> try the card there?
Hello,
I had some free time. So I've tried my FireGL X1 adapter on x86
hardware, no problem.
I don't know if it can provide valuable information, but I've also
tried an AGP
2010/2/4 Jerome Glisse :
> IIRC old radeon drm doesn't have any thing to dump GPU command stream.
> Look at http://www.x.org/docs/AMD/R5xx_Acceleration_v1.4.pdf to see
> what radeon GPU stream command looks like (packet pm4 stuff)
Interesting read for the parts I can understand. But a lot of this
2010/2/8 Alex Deucher :
> Does AGP work at all on ia64? I know on some alphas there were cache
> coherency issues or something like that that more or less prevented
> AGP from be usable at all. It was mostly there to accommodate AGP
> form factor cards.
I would say that AGP works on ia64, or at
On Sun, Feb 7, 2010 at 12:18 PM, Émeric Maschino
wrote:
> 2010/2/7 Stephane Marchesin :
>> From what I recall, all the ia64 AGP chipsets (well the zx1 and the
>> 460) have to be run:
>> - without side band adressing
>> - without fast writes
>> - at 4x speed
>> otherwise they're unstable.
>>
>> I t
2010/2/7 Émeric Maschino :
> I've no idea about sideband addressing. Is there a way to check
> whether it's enabled or not? And is there a way to disable it?
lspci -vv gives:
80:00.0 VGA compatible controller: ATI Technologies Inc Radeon R300 NG
[FireGL X1] (rev 80) (prog-if 00 [VGA controller])
2010/2/7 Dave Airlie :
>> This would thus narrow my investigation path to the AGP code
>> of the radeon driver, right?
>
> No it narrows it down the to the AGP hardware in your machine along with
> the probable lack of info on it, and maybe some tweaks that we know
> nothing about.
By AGP hardware
2010/2/7 Stephane Marchesin :
> From what I recall, all the ia64 AGP chipsets (well the zx1 and the
> 460) have to be run:
> - without side band adressing
> - without fast writes
> - at 4x speed
> otherwise they're unstable.
>
> I think by default agpgart puts them at AGP 1x with fast writes...
Wi
On Sat, Feb 6, 2010 at 11:47, Émeric Maschino wrote:
> 2010/2/4 Jerome Glisse :
>> IIRC old radeon drm doesn't have any thing to dump GPU command stream.
>> Look at http://www.x.org/docs/AMD/R5xx_Acceleration_v1.4.pdf to see
>> what radeon GPU stream command looks like (packet pm4 stuff). Note tha
> Anyway, I don't know whether this is due to PCI mode or not, but
> OpenGL performances, although there's no more GPU lockup, are poor.
> And serious OpenGL applications, as simulated by the SPECviewperf test
> suite, have very irregular frame rates. If I'm not mistaken, the
> BusType option is s
On Sat, Feb 6, 2010 at 2:47 PM, Émeric Maschino
wrote:
> 2010/2/4 Jerome Glisse :
>> IIRC old radeon drm doesn't have any thing to dump GPU command stream.
>> Look at http://www.x.org/docs/AMD/R5xx_Acceleration_v1.4.pdf to see
>> what radeon GPU stream command looks like (packet pm4 stuff). Note t
2010/2/4 Jerome Glisse :
> IIRC old radeon drm doesn't have any thing to dump GPU command stream.
> Look at http://www.x.org/docs/AMD/R5xx_Acceleration_v1.4.pdf to see
> what radeon GPU stream command looks like (packet pm4 stuff). Note that
> dump GPU command stream can quickly eat Gigs of data an
On Thu, Feb 04, 2010 at 03:37:58PM +0100, Émeric Maschino wrote:
> 2010/2/3 Stephane Marchesin :
> > No, you are right they don't trigger MCA. Hmm I didn't have any of
> > those back then, my lockups came from the bus mostly...
>
> Thank you for clarifying this point.
>
> > Really if you have suc
2010/2/3 Stephane Marchesin :
> No, you are right they don't trigger MCA. Hmm I didn't have any of
> those back then, my lockups came from the bus mostly...
Thank you for clarifying this point.
> Really if you have such lockups they may also happen on x86, did you
> try the card there?
Yes, I ha
On Tue, Feb 2, 2010 at 13:19, Émeric Maschino wrote:
> 2010/2/1 Stephane Marchesin :
>> If an ia64 machine lockups, it will usually store an MCA telling you
>> about why it locked/where in the code this happened.
>> This is how I got ia64 DRI going a bunch of years ago. For what it's
>> worth, mos
2010/2/1 Stephane Marchesin :
> If an ia64 machine lockups, it will usually store an MCA telling you
> about why it locked/where in the code this happened.
> This is how I got ia64 DRI going a bunch of years ago. For what it's
> worth, most of the bugs were:
> - pci resources casted to 32 bit in th
On Mon, Feb 1, 2010 at 13:17, Émeric Maschino wrote:
> 2010/1/31 Jerome Glisse :
>>>
>>> Eventually, strace log is flooded with
>>> ioctl(4, 0xc0106451, 0x6fd530f8) = 0
>>> roughly at the time the CPU charge increases. This is consistent with
>>> what is recorded in syslog:
>>> Jan 29 21:
2010/1/31 Jerome Glisse :
>>
>> Eventually, strace log is flooded with
>> ioctl(4, 0xc0106451, 0x6fd530f8) = 0
>> roughly at the time the CPU charge increases. This is consistent with
>> what is recorded in syslog:
>> Jan 29 21:16:03 longspeak kernel: [ 318.611783] [drm:drm_ioctl],
>> pid
On Sun, Jan 31, 2010 at 02:28:39PM +0100, Émeric Maschino wrote:
> Hello,
>
> I really don't know where to start, so feel free to redirect me to the
> right mailing list if this one is not the correct one.
>
> [Summary]
> I'm trying to help revive 3D hardware acceleration on ia64
> architecture.
Hello,
I really don't know where to start, so feel free to redirect me to the
right mailing list if this one is not the correct one.
[Summary]
I'm trying to help revive 3D hardware acceleration on ia64
architecture. This is a very long story that started in 2006
(http://bugs.freedesktop.org/show_
19 matches
Mail list logo
