On Thu, 4 Apr 2002 01:56:22 +0100
José Fonseca <[EMAIL PROTECTED]> wrote:
> On 2002.04.03 23:50 Sergey V. Udaltsov wrote:
> > > He!He!.. you missed!! It's a mix of variant 1 and 2..! :)
> > Cool. At least 1+2 is the answer (call it 5). Thanks.
> >
> > > As Leif previously said is his reply, it c
"Marcelo E. Magallon" wrote:
>
> >> José Fonseca <[EMAIL PROTECTED]> writes:
>
> > +#if 0
> > #define DIV255(X) (((X) << 8) + (X) + 256) >> 16
> > +#else
> > +const GLint temp;
> > +#define DIV255(X) (temp = (X), ((temp << 8) + temp + 256) >> 16)
>
> That function introduces an
Thomas Kunze wrote:
> On Saturday 23 March 2002 04:31, you wrote:
> > Tony,
> >
> > I've just commited a simple change to remove the AGP requirement in the
> > mach64-0-0-3-branch, as suggested by Michel. This is rather preliminary
> > and I'm not sure if it's enough to get it running on a PCI Ma
Jens Owen wrote:
> Robert Boucher has graciously stepped up to test the i810. The i830 and
> sis drivers have been removed from the list.
>
> That just leaves r128, mga and gamma. Any testing volunteers?
Thanks to all who responded to this request. I've got three initial
turnon testers line
On Tue, Apr 02, 2002 at 07:49:59 -0700, Jens Owen wrote:
> Alan,
>
> I've committed a slew of header file changes. Mostly, I've seperated
> any device dependencies from drm.h and the automatic include of all the
> _drm.h files. This results in a drm.h which does not have any
> of the driver spe
> > Maybe i am on error with you, and you might want to enlighten
> > me what successful computer projects on earth are a result of
> > your bold mind. (dont exclude computer projects for space crafts.)
>
> Now the above is something a bit 'trollish'. Kindly address
> the arguments, not the arg
Looks good. I'll forward them tomorrow.
-Jeff
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Bjorn Helgaas
Sent: Monday, April 01, 2002 2:23 PM
To: Jeff Hartmann
Cc: [EMAIL PROTECTED]
Subject: [Dri-devel] [PATCH] agpgart support for HP ZX1
The attac
> Hey Raystonn,
>
> Oh my godness, who fed that trolls. ;-)
Please refrain from calling me a troll. A troll is really someone who
flames others. He is someone who attempts to attack the messenger rather
than address the message. Thusfar the only one to do this is you.
> Lets still assume, yo
Hey Raystonn,
Oh my godness, who fed that trolls. ;-)
Lets still assume, you havent had the facts handy
(due to your age, education, place of birth or current location)
for seeing clear in all the subjects you are trying to adress.
I would be much happier if i did feel that you were really wor
On 2002.04.03 23:50 Sergey V. Udaltsov wrote:
> > He!He!.. you missed!! It's a mix of variant 1 and 2..! :)
> Cool. At least 1+2 is the answer (call it 5). Thanks.
>
> > As Leif previously said is his reply, it can be done in hardware by
> > messing the colors of the vertex to incorporate the fog
> He!He!.. you missed!! It's a mix of variant 1 and 2..! :)
Cool. At least 1+2 is the answer (call it 5). Thanks.
> As Leif previously said is his reply, it can be done in hardware by
> messing the colors of the vertex to incorporate the fog (as software Mesa
> used to do in 3.x) but it's non-c
On Tue, Apr 02, 2002 at 12:49:54PM -0700, Jens Owen wrote:
> I don't currently have any of this hardware in my posession, so I'm
> looking for volunteers to test the converted driver suite. If anyone is
> real ambitious they could even take a stab at the interface conversion,
> too.
I can test t
Dieter Nützel wrote:
>
> One more:
> Brian, is the latest Mesa-4.0.2 stuff already merged?
The trunk is has the latest 4.0.2 code now.
-Brian
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
On 2002.04.03 14:43 Sergey V. Udaltsov wrote:
> After all these interesting and informative discussions, everyone has
> forgotten the start of the thread:) Basically, there should one answer
> to the question whether and how "blending+fog" can be implemented .
> Possible variants:
> 1. Yes, it ca
This is a subject more related to the dri-devel mailing list.
On 2002.02.27 00:44 xinghui wrote:
> I know there are many HW device drivers in DRI mode .How to write
> the device driver in GLX indirect mode ?
>
To have hardware acceleration in indirect rendering you don't need a
different
On 2002.04.03 13:07 Marcelo E. Magallon wrote:
> [are the mailing lists having hiccups? I sent something yesterday and it
> didn't show up]
>
> >> José Fonseca <[EMAIL PROTECTED]> writes:
>
> > +#if 0
> > #define DIV255(X) (((X) << 8) + (X) + 256) >> 16
> > +#else
> > + const GLint te
Hi!
Several weeks ago I reported that on "initialization of screen" (q3, epsxe),
my machine freezes with about 10% probability. I got no meaningful reply, so I
upgraded the machine from rh 7.1 to 7.2 (including gcc), kernel to 2.4.19-pre5
and it still happens.
New hints?
Bye,
Peter Surda (Shur
On Die, 2002-04-02 at 21:49, Jens Owen wrote:
> The following driver suites still need to be converted to the new
> drmCommand interface before the drmcommand-0-0-1-branch can be merged to
> the trunk:
>
> gamma
> i810
> i830
> mga
> r128
> sis
>
> I don't currently have any of this
On Wed, Apr 03, 2002 at 06:27:06PM +0200, Dieter Nützel wrote:
> There is still one 3DNow! bug (texture related)
There is one bug gcc-2.95.3 related, IIRC patch is on sf project page.
I think it's good idea to create completly patched version of glide on put it
in .tar.gz on sf project page or o
On Wed, Apr 03, 2002 at 10:47:28 -0700, Jens Owen wrote:
> Jens Owen wrote:
> >
> > The following driver suites still need to be converted to the new
> > drmCommand interface before the drmcommand-0-0-1-branch can be merged to
> > the trunk:
> >
> > gamma
> > i810
> > i830
> > mga
> >
On Wed, Apr 03, 2002 at 01:28:46PM +0200, Timothee Besset wrote:
> Not sure if that's related, but Q3 shaders don't do any bump mapping.
>
> TTimo
Hrm..ok, so then it's not the bumpmaps that are missing. :) In any case,
the walls look perfectly smooth, and they didn't used to. I'll send a
pict
Jens Owen wrote:
>
> The following driver suites still need to be converted to the new
> drmCommand interface before the drmcommand-0-0-1-branch can be merged to
> the trunk:
>
> gamma
> i810
> i830
> mga
> r128
> sis
>
> I don't currently have any of this hardware in my posession,
I have a question regarding the i810 sarea private declarations.
Looking at the i810 driver's sarea, I see something strange. All the
other drivers have identical definitions for both their user space
declaration (SAREAPrivRec) and their kernel space declaration
(drm__sarea_t). However, the i81
On Tuesday, 4. March 2002 23:09:28, Brain Paul wrote:
> Daniel Kulesz wrote:
> >
> > Hi,
> >
> > I wanted to ask whether development of the 3dfx-drivers is still going on
> > or whether it has already come to an end what would be bad news to me :( I
> > tried downloading & compiling the newest gli
Dieter Nützel wrote:
>
> One more:
> Brian, is the latest Mesa-4.0.2 stuff already merged?
Not yet - I plan to do it pretty soon, maybe today.
-Brian
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
Keith Whitwell wrote:
>
> On Tue, 02 Apr 2002 20:19:31 -0700
> Jens Owen <[EMAIL PROTECTED]> wrote:
>
> > David,
> >
> > I've been making some changes to the drm interface and noticed some
> > interesting things about your FFB driver. I'm working off a recent
> > branch of the main trunk in the
One more:
Brian, is the latest Mesa-4.0.2 stuff already merged?
Thanks.
Dieter
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
I'm not sure they are the "official" maintainers, but as far as I
recall,
Thomas Winischhofer has done a lot with Sis and DRI, etc. (like make
the driver actually work) (http://www.webit.com/tw/linuxsis630.shtml),
and Matthew Sottek has done much of the work for i810/830.
Alex
---
I would do some maintainance on the I830, but unfortunately I don't have
hardware anymore. I have a driver here thats mostly the way to Mesa 3.5 and
I would assume getting it to 4.0 wouldn't be hard. If anyone wants to send
or loan me a production I830, I can work on getting this port done.
---
Jeff Hartmann wrote:
>
> You found a bug, it isn't serious because the private part of the sarea
> isn't really manipulated in the ddx driver after initialization if I
> remember correctly. The client side driver will make sure there are sane
> values in there.
> The client side fyi uses the ker
David Dawes wrote:
>
> On Tue, Apr 02, 2002 at 07:49:59PM -0700, Jens Owen wrote:
> >Alan,
> >
> >I've committed a slew of header file changes. Mostly, I've seperated
> >any device dependencies from drm.h and the automatic include of all the
> >_drm.h files. This results in a drm.h which does n
You found a bug, it isn't serious because the private part of the sarea
isn't really manipulated in the ddx driver after initialization if I
remember correctly. The client side driver will make sure there are sane
values in there.
The client side fyi uses the kernel defination (on the I810 anyhow
"Marcelo E. Magallon" wrote:
>
> [are the mailing lists having hiccups? I sent something yesterday and it
> didn't show up]
I've been seeing some serious delays...up to 5 days for some of the mail
on the xpert list.
-- /\
Jens Owen/ \/\ _
On Tue, Apr 02, 2002 at 07:49:59PM -0700, Jens Owen wrote:
>Alan,
>
>I've committed a slew of header file changes. Mostly, I've seperated
>any device dependencies from drm.h and the automatic include of all the
>_drm.h files. This results in a drm.h which does not have any
>of the driver specifi
After all these interesting and informative discussions, everyone has
forgotten the start of the thread:) Basically, there should one answer
to the question whether and how "blending+fog" can be implemented .
Possible variants:
1. Yes, it can be done with hardware acceleration. DRI team knows how.
>> José Fonseca <[EMAIL PROTECTED]> writes:
> +#if 0
> #define DIV255(X) (((X) << 8) + (X) + 256) >> 16
> +#else
> +const GLint temp;
> +#define DIV255(X) (temp = (X), ((temp << 8) + temp + 256) >> 16)
That function introduces an small error (off by +-1) in about 50% of
the tim
On Sat, Mar 30, 2002 at 08:11:31AM -0700, Jens Owen wrote:
> Ian Romanick wrote:
>
> > The bad news is that it dies shortly thereafter with an assertion failure in
> > Mesa. The only seems to happen when I re-size the window. Maya seems to
> > expect 1280x1024, but I'm running @ 1152x864. If I
"David S. Miller" wrote:
>
>From: Jens Owen <[EMAIL PROTECTED]>
>Date: Tue, 02 Apr 2002 20:19:31 -0700
>
>Perhaps, you'd be interested in moving your FFB DRM kernel module
>upstream to the DRI repository.
>
> Does the DRI repository even build kernel modules on non-x86 platforms
On Tue, 02 Apr 2002 20:19:31 -0700
Jens Owen <[EMAIL PROTECTED]> wrote:
> David,
>
> I've been making some changes to the drm interface and noticed some
> interesting things about your FFB driver. I'm working off a recent
> branch of the main trunk in the DRI CVS repository.
>
> I noticed your
From: Jens Owen <[EMAIL PROTECTED]>
Date: Tue, 02 Apr 2002 20:19:31 -0700
Perhaps, you'd be interested in moving your FFB DRM kernel module
upstream to the DRI repository.
Does the DRI repository even build kernel modules on non-x86 platforms
correctly? Ie. does it add all the neces
> > The only thing video
> > cards have today that is really better than the main processor is
massive
> > amounts of memory bandwidth.
>
> That is far from the truth - they have internal pipelining
> and parallelism. Their use of silicon can be optimised to balance
> the performance of just one
On Tue, Apr 02, 2002 at 08:01:04 -0700, Jens Owen wrote:
> Just FYI.
>
> I noticed the i830 and SiS 3D drivers are not being built on the trunk.
> If they aren't supported enough to have them on by default, then I'll
> skip converting them to the new drmCommand interface. If they are ever
> sup
Brian Paul wrote:
>
> Ian Romanick wrote:
> >
> > On Sat, Mar 30, 2002 at 08:11:31AM -0700, Jens Owen wrote:
> > > Ian Romanick wrote:
> > > >
> > > > On Thu, Mar 28, 2002 at 12:53:06PM -0800, Ian Romanick wrote:
> > > >
> > > > > #0 0x4309fb0a in CreateContext (dpy=0x8075708, vis=0x0, shareList
David,
I've been making some changes to the drm interface and noticed some
interesting things about your FFB driver. I'm working off a recent
branch of the main trunk in the DRI CVS repository.
I noticed your FFB 3D driver is being built for the x86 platform. I
don't know if this is intentiona
Just FYI.
I noticed the i830 and SiS 3D drivers are not being built on the trunk.
If they aren't supported enough to have them on by default, then I'll
skip converting them to the new drmCommand interface. If they are ever
supported, the maintainer can make the updates.
Regards,
Jens
--
Alan,
I've committed a slew of header file changes. Mostly, I've seperated
any device dependencies from drm.h and the automatic include of all the
_drm.h files. This results in a drm.h which does not have any
of the driver specific IOCTLs, and the need to explicitly include the
_drm.h files whe
[are the mailing lists having hiccups? I sent something yesterday and it
didn't show up]
>> José Fonseca <[EMAIL PROTECTED]> writes:
> +#if 0
> #define DIV255(X) (((X) << 8) + (X) + 256) >> 16
> +#else
> +const GLint temp;
> +#define DIV255(X) (temp = (X), ((temp << 8) + temp + 2
I'm using the Radeon TCL CVS from this morning, and q3tourney4 is not
rendering properly. It looks like the bumpmaps are not being used. I'm
using Q3A v1.31.
Also, when the head of Stripe is displayed in the upper right, the texture
rolls (like it's lost vertical hold).
I have't yet done more
48 matches
Mail list logo
