Dave Airlie wrote:
I need the original source of the rumour so I can find out if its true
That would be me.
Well I've be spreading the rumour from IRC logs..
http://dri.sourceforge.net/IRC-logs/20040628.txt
From Erdi Chen: erdi the Via unichrome chip supports system memory to
framebuffer DMA
On Iau, 2004-08-12 at 21:27, Erdi Chen wrote:
I have some working test code that implements AGP ring buffers (the
current DRI code waits for engine idle and ping pongs between two big
buffers). For multiple clients, each client would have its private
buffer allocate it system memory. The
On Mer, 2004-08-11 at 02:00, Mike Mestnik wrote:
--- Dave Airlie [EMAIL PROTECTED] wrote:
Can the VIA DRI stuff get pushed through to the kernel with the S3
stuff please, even if we mark VIA as experimental
the DRM stuff? We need to mark as insecure, I really don't want anything
On Mer, 2004-08-11 at 01:29, Dave Airlie wrote:
Can the VIA DRI stuff get pushed through to the kernel with the S3
stuff please, even if we mark VIA as experimental
the DRM stuff? We need to mark as insecure, I really don't want anything
that the authors consider insecure to go anywhere
On Mer, 2004-08-11 at 02:20, Dave Airlie wrote:
the VIA/mach64/savage DRM when setup by the current DDXs all allow evil
things from my current understanding, that is why they're DDXs haven't got
the DRI support turned on by default in Xorg, so those DRMs are not to be
built into a release, I
Hi!
On Mer, 2004-08-11 at 02:20, Dave Airlie wrote:
the VIA/mach64/savage DRM when setup by the current DDXs all allow evil
things from my current understanding, that is why they're DDXs haven't
got
the DRI support turned on by default in Xorg, so those DRMs are not to
be
built into a
On Mer, 2004-08-11 at 13:53, Thomas Hellstrm wrote:
When I did some cleaning up of the via drm code I noticed that the memory
manager seems identical to the SiS one, so if there is a problem with
that, then there is a problem with the via driver.
Yeah I know about one.
Also the unichrome 2d
Alan Cox wrote:
On Mer, 2004-08-11 at 01:29, Dave Airlie wrote:
Can the VIA DRI stuff get pushed through to the kernel with the S3
stuff please, even if we mark VIA as experimental
the DRM stuff? We need to mark as insecure, I really don't want anything
that the authors consider insecure to go
Alan Cox wrote:
On Mer, 2004-08-11 at 13:53, Thomas Hellstrm wrote:
When I did some cleaning up of the via drm code I noticed that the memory
manager seems identical to the SiS one, so if there is a problem with
that, then there is a problem with the via driver.
Yeah I
Mach64 isn't entirely secure. Yes we know that the author said so. The
via one I'm still trying to track down but its entirely A said B said
C thought D considered it insecure.
I need the original source of the rumour so I can find out if its true
Well I've be spreading the rumour from IRC
On Mer, 2004-08-11 at 21:59, Dave Airlie wrote:
From Erdi Chen: erdi the Via unichrome chip supports system memory to
framebuffer DMA bitblt, currently the DRI driver maps the IO registers to
user space, that maybe a problem
Now that statement is enough for me to block it going anywhere
On Maw, 2004-08-10 at 06:23, Kevin E Martin wrote:
On today's release wranglers call, someone asked if there were any new
fixes from the DRI or Mesa projects that should be included in the next
X.Org release. If there are any, could you please let us know? Thanks!
Can the VIA DRI stuff get
Can the VIA DRI stuff get pushed through to the kernel with the S3
stuff please, even if we mark VIA as experimental
the DRM stuff? We need to mark as insecure, I really don't want anything
that the authors consider insecure to go anywhere outside the DRM...
If it allows the user to control
--- Dave Airlie [EMAIL PROTECTED] wrote:
Can the VIA DRI stuff get pushed through to the kernel with the S3
stuff please, even if we mark VIA as experimental
the DRM stuff? We need to mark as insecure, I really don't want anything
that the authors consider insecure to go anywhere
the DRM stuff? We need to mark as insecure, I really don't want anything
that the authors consider insecure to go anywhere outside the DRM...
Just for calarity.
The DRM stuff is insecure, it should not go anywhere outside CVS.
the VIA/mach64/savage DRM when setup by the current DDXs all
15 matches
Mail list logo
