Philip Brown [EMAIL PROTECTED] wrote:
On Sun, Mar 02, 2003 at 10:33:15PM +, Martin Spott wrote:
I don't know _why_ this works
because you're not using DRI.
DRI essentially for Xserver-side stuff. The X server is on the SGI.
That's quite clear ;-)
DRI is not involved here. You're just
Title: ::M::Vjggtxegnukhnwrtfgbdyjluhtlbpetkvnjfhgqdwh
sdf
dyshBFLkhCSiov4Oj4JjPMU4Ho
6512wtMx1-854PPBY4595l20+,~wzf¢+,¦ì¢·o$áyyézW(ëhç¤
æ¯zxm¶ÿ¶§Ê&þÇî'^½éfj)b b²ÐëׯzYb²Û,¢êÜyú+éÞ¶m¦Ïÿ+-²Ê.Ç¢¸ ë+-³ùb²Ø§~Ý®'^½é
On Mon, 2003-03-03 at 07:43, Philip Brown wrote:
Could someone explain what exactly DRM_READMEMORYBARRIER is supposed to do,
in the kernel driver level, please?
I was initially thinking that it did some kind of
enable bus memory mapping OS call.
However, it is used inconsistently.
On Sun, Mar 02, 2003 at 01:35:08PM +, Ian Molton wrote:
On Sun, 2 Mar 2003 11:58:44 + José Fonseca
[EMAIL PROTECTED] wrote:
To me, thats arse backwards. It should be that the documentation
eases people into develpoing the code. not the other way round.
But there *are* specs
On Mon, 3 Mar 2003 14:58:01 +
José Fonseca [EMAIL PROTECTED] wrote:
You can get
back now to your dri-has-no-docs-and-developers/ihvs-are-elitists
speech for all I care.
No thanks. I'll just continue reverse engineering my e740.
---
Not too many updates this time.
There are a few issues that I really want to discuss work out before
any coding begins.
1. Felix Kuhling asked, basically, how does a process manage the memory
blocks that it has claimed. The issue is that each process owns a set
of memory_blocks that may or
On Mon, Mar 03, 2003 at 02:48:32PM +0100, Michel Dänzer wrote:
...
Besides which, DRM(ioremap) seems to do the *actual* mapping to kernel
space which still leaves the question of, what does
DRM_READMEMORYBARRIER() do?
As the name says, it issues a memory barrier. :)
I beg to
On Mon, Mar 03, 2003 at 02:58:01PM +, José Fonseca wrote:
...
An existing DRI driver has much more relevant information for a
developer than the hardware specs.
except for the fact that the dri cvs tree, seems to have some sort of
auto-applied strip for source code on commit.
As strip
Hello all.
I'm going to be fairly late for today's meeting. I have an appointment
at 1:00PST, so I probably won't be there until about 2:30PST. There are
a couple things that I'd *REALLY* like to talk about. I'll be on the
channel, so I'll have any disucssion that I miss in my log.
1. I'd
This is just a friendly reminder that the weekly dri-devel IRC meeting will
be starting in the #dri-devel channel on irc.freenode.net at 2100 UTC (or
4:00PM EST or 1:00PST, if you prefer).
Time zone conversion available at:
http://www.timezoneconverter.com/cgi-bin/tzc.tzc
Logs of previous IRC
On Sun, 2 Mar 2003 19:34:27 -0500 (EST)
Mike A. Harris [EMAIL PROTECTED] wrote:
On Sun, 2 Mar 2003, Smitty wrote:
OK but here is my take on it, people will work on what they are
interested in, so if someone wants to work on R128 and ATI does
give out docs for that chip then they should give
On Mon, 3 Mar 2003, Smitty wrote:
I'd love to see more vendors providing specs, and doing so more
openly, and preferably without NDAs. Ragging on vendors who do
permit access to docs under NDA to people of their choosing, for
not providing them to the world, is more likely to dry up access
On Mon, 03 Mar 2003 10:38:40 -0800
Ian Romanick [EMAIL PROTECTED] wrote:
Not too many updates this time.
There are a few issues that I really want to discuss work out before
any coding begins.
1. Felix Kuhling asked, basically, how does a process manage the memory
blocks that it has
On Mon, 2003-03-03 at 09:25, Alan Cox wrote:
On early athlon you prefetch non cached memory and the cpu corrupts its
cache, on PII, PII mmap frame buffer against a cached page, but the
right kind of instruction in a loop with the instruction bridging the
two memory types and run it in a tight
On Mon, 2003-03-03 at 20:38, Mike A. Harris wrote:
On Mon, 3 Mar 2003, Ian Molton wrote:
You can get
back now to your dri-has-no-docs-and-developers/ihvs-are-elitists
speech for all I care.
No thanks. I'll just continue reverse engineering my e740.
e740, or i740? AFAIK, i740 has
On Mon, 3 Mar 2003 10:48:54 -0800 Philip Brown [EMAIL PROTECTED] wrote:
But anyway, sounds like I can NOP it out, I guess.
You may be able to NOP it if your platform does not require
it. I know the Alpha uses memory barriers. I think PPC may
use them too.
On Mon, Mar 03, 2003 at 05:42:24PM -0800, Alan Young wrote:
On Mon, 3 Mar 2003 10:48:54 -0800 Philip Brown [EMAIL PROTECTED] wrote:
But anyway, sounds like I can NOP it out, I guess.
You may be able to NOP it if your platform does not require
it. I know the Alpha uses
An existing DRI driver has much more relevant information for a
developer than the hardware specs.
except for the fact that the dri cvs tree, seems to have some sort of
auto-applied strip for source code on commit.
As strip binaryname strips out debug information, this auto-strip
seems
On 04 Mar 2003 00:06:48 +
Alan Cox [EMAIL PROTECTED] wrote:
On Mon, 2003-03-03 at 20:38, Mike A. Harris wrote:
On Mon, 3 Mar 2003, Ian Molton wrote:
You can get
back now to your dri-has-no-docs-and-developers/ihvs-are-elitists
speech for all I care.
No thanks. I'll just
19 matches
Mail list logo
