On Oct 09, 07 18:38:59 +0200, Syren Baran wrote:
> Am Dienstag, den 09.10.2007, 18:01 +0200 schrieb Matthias Hopf:
> > Unfortunately, you guys had to cope with not having docs at all, so you
> > didn't have that luxury...
> I know this is off topic ..., but to much luxury tends to soften
> people.
Am Montag, den 08.10.2007, 18:23 +0200 schrieb Jerome Glisse:
> As
> side note i don't think anybody will accept security flow just to allow
> few apps to play with the GPU.
Well, i heard rumors of people using PC´s and even connecting them to
the interweb instead of placing it in a safe and dump
Am Dienstag, den 09.10.2007, 18:01 +0200 schrieb Matthias Hopf:
> Unfortunately, you guys had to cope with not having docs at all, so you
> didn't have that luxury...
I know this is off topic ..., but to much luxury tends to soften
people. ;)
And if you ever spend a week chasing a bug in you own
On Oct 09, 07 17:44:36 +0200, Jerome Glisse wrote:
> Take r300 dri source and use ctm to update fragprog field see r300_reg.h
> (all swizzle handle natively plus some others additions) and you should
> be near to some usable 3d driver.
But that's the thing: we want docs first, in order to complete
Syren Baran wrote:
> Am Dienstag, den 09.10.2007, 12:58 +0200 schrieb Matthias Hopf:
> Hmm, we are talking about the sdk´s here?
> Having used neither i dont what the differences are.
>
> But one thing puzzling me now. If the fglrx package does not include an
> ati specific elf, they must be doing
On Oct 09, 07 16:28:10 +0200, Syren Baran wrote:
> It also states that it uses a 32bit address range. This 32bit range is
> virtual, so knowing where $address points to physicly gives know sure
> knowledgle as to where $address+1 points to. So 0x-0x0fff
> could point to graphics memory
Am Dienstag, den 09.10.2007, 12:58 +0200 schrieb Matthias Hopf:
> On Oct 08, 07 23:53:12 +0200, Syren Baran wrote:
> > Am Montag, den 08.10.2007, 15:08 +0200 schrieb Matthias Hopf:
> > > I don't see the limitation here. Remember, only talking about the
> > > command processor, not the SPUs.
> > And
On Oct 08, 07 23:53:12 +0200, Syren Baran wrote:
> Am Montag, den 08.10.2007, 15:08 +0200 schrieb Matthias Hopf:
> > I don't see the limitation here. Remember, only talking about the
> > command processor, not the SPUs.
> And how do you prevent an executing program from accessing system
> memory? T
Am Montag, den 08.10.2007, 15:08 +0200 schrieb Matthias Hopf:
> On Oct 08, 07 11:02:05 +0200, Syren Baran wrote:
> > > > As long as the command processor cannot be programmed from user space,
> > > > this scenario can be made secure for complete user space programming.
> > While the security advant
Syren Baran wrote:
> Am Montag, den 08.10.2007, 11:17 +0200 schrieb Nicolas Trangez:
>> On Mon, 2007-10-08 at 11:02 +0200, Syren Baran wrote:
>>> Waiting for 3D docs will result in an infinite loop (at least if you
>>> are
>>> looking for registers to write something like "turn this object by x
>>>
On Oct 08, 07 11:02:05 +0200, Syren Baran wrote:
> > > As long as the command processor cannot be programmed from user space,
> > > this scenario can be made secure for complete user space programming.
> While the security advantages of this approach are obvious it severly
> limits the GPUs use. Qu
On Mon, 2007-10-08 at 12:35 +0200, Syren Baran wrote:
> The R580 has (depending on modell) 48 processors each executing the same
> command on different memory locations (though some may be sleeping,
> depending on flow control).
> The instruction set is very different from architectures i know.
> A
Am Montag, den 08.10.2007, 11:17 +0200 schrieb Nicolas Trangez:
> On Mon, 2007-10-08 at 11:02 +0200, Syren Baran wrote:
> > Waiting for 3D docs will result in an infinite loop (at least if you
> > are
> > looking for registers to write something like "turn this object by x
> > degrees").
> > The re
On Mon, 2007-10-08 at 11:02 +0200, Syren Baran wrote:
> Waiting for 3D docs will result in an infinite loop (at least if you
> are
> looking for registers to write something like "turn this object by x
> degrees").
> The relevant document is
> http://ati.amd.com/companyinfo/researcher/documents/ATI
Am Sonntag, den 07.10.2007, 00:05 +0200 schrieb Syren Baran:
> Am Freitag, den 05.10.2007, 14:15 +0200 schrieb Matthias Hopf:
> > On Oct 05, 07 00:22:09 +0200, Syren Baran wrote:
> > > I personaly dont know how the ATI architecture differs that a kernel
> > > module might be unnecesarry. Fglrx also
15 matches
Mail list logo
