Hello,
I am new to DRI hacking, and I am looking for some guidance. I am trying to
get the Neverwinter Nights Toolset to work under wine (http://nwwine.beergeek.net). I
have hacked wine a bit to get it working for most people, but I am having problems
with the r128 drivers that other
Brian Paul wrote:
>
> Mesa should handle rendering into any visual, including overlay planes.
That's right, I forgot you upgraded the SW rasterizers to handle just
about any visual up to a certain depth.
-- /\
Jens Owen/ \/\ _
[EMAIL PROTE
Has anyone taken a peak at these patches?
Stefan Dirsch wrote:
>
> Hi
>
> Just as introduction. I'm maintaining the XFree86 packages at SuSE and
> therefore I'm also responsible for XFree86 4.x/DRI support on SuSE Linux.
>
> I would like to let you know about some pte/highmem changes in the Su
Tim Rowley wrote:
>
> Jens Owen wrote:
> > It would be interesting to hear more details from their developers
> > regarding the comment they put in their README: "If an OpenGL
> > application is forcibly terminated by closing the X connection then
> > there may be leftovers on the desktop. This
Thanks for the report! Concerning textures: the AGP texturing code is
kind of a proof-of-concept and isn't very efficient yet. We need to work
on reducing the amount of texture swapping that is happening. You can try
AGP 2x, use Option "AgpMode" "2" in the Device section of XF86Config.
Also,
On Monday 27 May 2002 8:22 pm, Michael scribed numinously:"
> On Sun, May 26, 2002 at 06:50:11PM +0100, Tim Smith wrote:
> > The tcl-0-0-branch really doesn't like 2D menus being popped up over
> > the 3D drawing area; it locks up after a few of these with or without
> > RADEON_NO_TCL and with or
x27;s a holiday here in the US, so I don't know how many people
we'll get today.
May 27 17:05:58 --> jrfonseca (~[EMAIL PROTECTED])
has joined #dri-devel
May 27 17:06:04 Hi gang!
May 27 17:06:08 jrfonseca: hello
May 27 17:06:36 radeon-20020527-linux.i386.tar
Well, here's my small contribution to the mach64 dev (sorry but I'm FAR away beyond
you in programming, especially compared to people like Jose,Leif or Linus :)).
So with mach64-0-0-4-branch checked out and compiled monday morning (french time), a
Mobility M1 with 8Mo, athlon-4 900Mhz, running
On 27 May 2002, Sergey V. Udaltsov wrote:
> Hi all
>
> Just took the latest (27.05) drm binary snapshot for Mach64. And cannot
> get DRI working any more. In XFree86.0.log I see:
>
> drmOpenDevice: minor is 0
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 7, (OK)
>
Ian Molton wrote:
> On Mon, 27 May 2002 15:01:47 -0600
> Jens Owen <[EMAIL PROTECTED]> wrote:
>
>
>>1) We loosen security requirements for 3D drivers. This will allow
>>far less data copying, memory mapping/unmapping and system calls.
>>Many modern graphics chips can have their data managed co
On Mon, 27 May 2002 15:01:47 -0600
Jens Owen <[EMAIL PROTECTED]> wrote:
> 1) We loosen security requirements for 3D drivers. This will allow
> far less data copying, memory mapping/unmapping and system calls.
> Many modern graphics chips can have their data managed completely in a
> user space
José Fonseca wrote:
>
> On 2002.05.27 16:28 Jens Owen wrote:
> > ...
> >
> > If we do get some type of indirect rendering path working quicker, then
> > perhaps we could tighten up these defaults so that the usage model
> > required explicit administrative permision to a user before being
> > all
Keith Packard wrote:
> We had a big display-list vs immediate-mode war around 1990 and immediate
> mode won. It's just a lot easier to send the whole frame worth of
> polygons each time than to try an edit display lists. Of course, this
> particular battle was framed by the "scientific visualiz
Hi all
Just took the latest (27.05) drm binary snapshot for Mach64. And cannot
get DRI working any more. In XFree86.0.log I see:
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/d
On Sun, May 26, 2002 at 06:50:11PM +0100, Tim Smith wrote:
> The tcl-0-0-branch really doesn't like 2D menus being popped up over
> the 3D drawing area; it locks up after a few of these with or without
> RADEON_NO_TCL and with or without page flipping enabled. Following
> Michel's suggestion I've
Around 18 o'clock on May 27, Keith Whitwell wrote:
> I think the multiplayer aspects of the game are a separate issue. Talking
> about the difference between a big display list with the whole quake level in
> it and the visibility/bsp-tree/whatever-new-technique coding that quake &
> other g
Mesa should handle rendering into any visual, including overlay planes.
I think we just have to add some missing bits to the server-side GLX/Mesa
code to support overlay rendering. But I don't have any hardware (such
as FireGL) to test/fix this.
Stand-alone Mesa has supported overlay rendering
>
From a game standpoint, think "quake engine". The actual game doesn't need
>>>to tell the GX engine everything over and over again all the time. It
>>>tells it the basic stuff once, and then it just says "render me". You
>>>don't need DRI for sending the "render me" command, you need DRI b
Ian Molton wrote:
>On Mon, 27 May 2002 15:53:49 +0200
>roussel jerome <[EMAIL PROTECTED]> wrote:
>
>>I am translating the DRI FAQ in french and I am trying do correct it
>>or simplify it.
>>
>
>Do bear in mind that I am re-doing the website.
>
>I will accept any other translations of documents yo
On Mon, 27 May 2002, Keith Whitwell wrote:
> Linus Torvalds wrote:
> >
> > Much heavier. For some yet unexplained reason, a P4 takes about 1us to do
> > a simple system call. That's on a 1.8GHz system, so it basically implies
> > that a P4 takes 1800 cycles to do a "int 0x80 + iret", which is j
On Mon, 27 May 2002 15:53:49 +0200
roussel jerome <[EMAIL PROTECTED]> wrote:
>
> I am translating the DRI FAQ in french and I am trying do correct it
> or simplify it.
Do bear in mind that I am re-doing the website.
I will accept any other translations of documents you wish to do also.
__
Alexander Stohr wrote:
>
> Good fix Felix.
>
> I do "hate" local function prototypes.
> Its just bad coding style and laziness.
> Further it shows a critical lack of
> knowledge for the header file organisation.
>
> They are never verified against the
> implementation by the compiler and
> migh
On 2002.05.27 16:28 Jens Owen wrote:
> ...
>
> If we do get some type of indirect rendering path working quicker, then
> perhaps we could tighten up these defaults so that the usage model
> required explicit administrative permision to a user before being
> allowed access to direct rendering.
>
Felix Kühling wrote:
>
> Hi,
>
> I had trouble when compiling DRI with g++ 3.0.4 and -O3 related to
> function inlining. The function swap is declared static globally in
> quicksort.cc. In function quicksort it is redeclared. The redeclaration
> prevents g++ from inlining the swap function. Inst
Keith Whitwell wrote:
>
> Linus Torvalds wrote:
> >
> > On Mon, 27 May 2002, Jens Owen wrote:
> >
> >>This is an education for me, too. Thanks for the info. Any idea how
> >>heavy IOCTL's are on a P4?
> >>
> >
> > Much heavier. For some yet unexplained reason, a P4 takes about 1us to do
> > a s
On 2002.05.27 14:53 roussel jerome wrote:
> Hello
>
>
> I am translating the DRI FAQ in french and I am trying do correct it or
> simplify it. I don't really understand why there is 2 parts on Mesa: one
> on Mesa 3.4 and one on 4.x because there are very similar. I don't
> really see what are
Hello
I am translating the DRI FAQ in french and I am trying do correct it or
simplify it. I don't really understand why there is 2 parts on Mesa: one
on Mesa 3.4 and one on 4.x because there are very similar. I don't
really see what are the differences because it is too long. It would be
be
On Sun, May 26, 2002 at 01:22:46PM -0400, David Dawes wrote:
> On Fri, May 24, 2002 at 01:54:52PM -0700, Keith Packard wrote:
>
> >We have an agreement in principle for DRI to use the XFree86 CVS tree
> >instead of their separate tree on sourceforge, but that hasn't happened
> >for reasons I do
Linus Torvalds wrote:
>
> On Mon, 27 May 2002, Jens Owen wrote:
>
>>This is an education for me, too. Thanks for the info. Any idea how
>>heavy IOCTL's are on a P4?
>>
>
> Much heavier. For some yet unexplained reason, a P4 takes about 1us to do
> a simple system call. That's on a 1.8GHz syst
Jens Owen wrote:
> It would be interesting to hear more details from their developers
> regarding the comment they put in their README: "If an OpenGL
> application is forcibly terminated by closing the X connection then
> there may be leftovers on the desktop. This appears to be a problem in
> t
On Mon, 27 May 2002, Jens Owen wrote:
>
> This is an education for me, too. Thanks for the info. Any idea how
> heavy IOCTL's are on a P4?
Much heavier. For some yet unexplained reason, a P4 takes about 1us to do
a simple system call. That's on a 1.8GHz system, so it basically implies
that a
31 matches
Mail list logo
