Philip Brown wrote:
> Hi folks,
>
> could someone take 1 minute and run through agpgart.h,
> just taking a look at the structs for the ioctls,
> and add comments for which "page" fields are ADDRESSES, vs which
> page fields are INDEXES/page-counts. My head's beginning to spin.
> I'll narrow it
> Make the enable/disable configurable by an environment variable, like
> so:
>
> if ( getenv( "LIBGL_DISABLE_MULTITEXTURE" ) ) {
> gl_extensions_disable( ctx, "GL_ARB_multitexture" );
> }
> if ( getenv( "LIBGL_ENABLE_TEXTURE_ENV_ADD" ) ) {
> gl_extensions_enab
On Tue, Dec 11, 2001 at 07:28:54PM -0500, Leif Delgass wrote:
>
> I think the point is (but I could be wrong) whether this is
> user-configurable without recoding/recompiling anything, and it seems the
> answer is no. The driver can enable/disable extensions for all apps using
> the driver, or a
On Tue, 11 Dec 2001, Brian Paul wrote:
> "Sergey V. Udaltsov" wrote:
> >
> > Hi all
> >
> > Is it possible to turn on/off some particular GL extenstions in Mach64
> > driver? Is mesa.conf in any help here? I would like to play with
> > texture-related extensions (probable, turning GL_ARB_multit
Hi folks,
could someone take 1 minute and run through agpgart.h,
just taking a look at the structs for the ioctls,
and add comments for which "page" fields are ADDRESSES, vs which
page fields are INDEXES/page-counts. My head's beginning to spin.
I'll narrow it down for ya:
typedef struct _agp_s
"Sergey V. Udaltsov" wrote:
>
> Hi all
>
> Is it possible to turn on/off some particular GL extenstions in Mach64
> driver? Is mesa.conf in any help here? I would like to play with
> texture-related extensions (probable, turning GL_ARB_multitextures off
> would solve my problems in celestia?)
Y
El Mar 11 Dic 2001 15:51, Michael Thaler escribió:
> On Tue, Dec 11, 2001 at 12:45:59PM +, Jose Fonseca wrote:
> > Me neither. That's not a problem, just login as anonymous:
> >
> > cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri login
> >
> > Press enter for password and then
> >
> > cvs -z3 -d
On Tue, Dec 11, 2001 at 01:27:12PM -0600, Jorge Luis Williams wrote:
> On Tue, 2001-12-11 at 09:06, Keith Whitwell wrote:
> > Keith Whitwell wrote:
> > >
> > > Keith Whitwell wrote:
> > > >
> > > > Jorge Luis Williams wrote:
> > > > >
> > > > > Hello,
> > > > >
> > > > > I've run into what appear
On Tue, 2001-12-11 at 09:06, Keith Whitwell wrote:
> Keith Whitwell wrote:
> >
> > Keith Whitwell wrote:
> > >
> > > Jorge Luis Williams wrote:
> > > >
> > > > Hello,
> > > >
> > > > I've run into what appears to be a dead-lock while running tessellation
> > > > demo by David Blythe which is incl
Hi all
Is it possible to turn on/off some particular GL extenstions in Mach64
driver? Is mesa.conf in any help here? I would like to play with
texture-related extensions (probable, turning GL_ARB_multitextures off
would solve my problems in celestia?)
Cheers,
Sergey
___
On Mon, 10 Dec 2001, Michael Thaler wrote:
> I downloaded the trunk and the mach64 branch from CVS. I compiled
> everything with make world and loaded the mach64 module into the
> kernel. I used XFree 4.10 from debian unstable to test the driver.
Did you find the ati_dri.so and put it in /usr/X1
On Tue, 2001-12-11 at 14:51, Michael Thaler wrote:
> On Tue, Dec 11, 2001 at 12:45:59PM +, Jose Fonseca wrote:
>
> > Me neither. That's not a problem, just login as anonymous:
> >
> > cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri login
> >
> > Press enter for password and then
> >
> > cvs
Keith Whitwell wrote:
>
> Keith Whitwell wrote:
> >
> > Jorge Luis Williams wrote:
> > >
> > > Hello,
> > >
> > > I've run into what appears to be a dead-lock while running tessellation
> > > demo by David Blythe which is included in the Glut-3.7 source
> > > distribution (glut-3.7/progs/advanced
On Tue, Dec 11, 2001 at 12:45:59PM +, Jose Fonseca wrote:
> Me neither. That's not a problem, just login as anonymous:
>
> cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri login
>
> Press enter for password and then
>
> cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri co -r
> mach64-0-0-2-b
Keith Whitwell wrote:
>
> Jorge Luis Williams wrote:
> >
> > Hello,
> >
> > I've run into what appears to be a dead-lock while running tessellation
> > demo by David Blythe which is included in the Glut-3.7 source
> > distribution (glut-3.7/progs/advanced/tes.c)
> >
> > I've been able to reproduc
On Tue, 2001-12-11 at 12:14, Michael Thaler wrote:
> On Tue, Dec 11, 2001 at 11:52:59AM +, Jose Fonseca wrote:
>
> >
> > cvs -z3 [EMAIL PROTECTED]:/cvsroot/dri co -r
> > mach64-0-0-2-branch xc
>
> I don't have a login so I can only download as an anonymous user. I
> followed the instructio
> From: Keith Whitwell [mailto:[EMAIL PROTECTED]]
>
> Just look at /proc/pci or similar on a linux box. All the
> pci cards have
> memory ranges assigned to them - that's where your on-card
> memory lives in the
> physical address space. The pci bus hardware diverts memory
> accesses in this
On Tue, Dec 11, 2001 at 11:52:59AM +, Jose Fonseca wrote:
>
> cvs -z3 [EMAIL PROTECTED]:/cvsroot/dri co -r
> mach64-0-0-2-branch xc
I don't have a login so I can only download as an anonymous user. I
followed the instructions of the compilation guide but I am not
familiar with CVS so maybe
On Tue, 2001-12-11 at 10:45, Sergey V. Udaltsov wrote:
> > mkdir /usr/X11R6-DRI
> > lndir /usr/X11R6 /usr/X11R6-DRI
> It's already done, thanks to binaries you gave me:)
>
> > Setting the ProjectRoot in /usr/X11R6-DRI isn't even necessary since is
> > the default already.
> Really? In which file?
On Tue, 2001-12-11 at 10:54, Michael Thaler wrote:
> On Mon, Dec 10, 2001 at 03:09:35PM +, Jose Fonseca wrote:
>
> > I don't know what particular version of XFree 4.10 you have used but you
> > must also install the X server from the mach64 build tree. The usual way
> > is to 'lndir' your /us
On Mon, Dec 10, 2001 at 03:09:35PM +, Jose Fonseca wrote:
> I don't know what particular version of XFree 4.10 you have used but you
> must also install the X server from the mach64 build tree. The usual way
> is to 'lndir' your /usr/X11R6/ dir to /usr/X11R6-DRI/ and then 'make
> install'. Th
> mkdir /usr/X11R6-DRI
> lndir /usr/X11R6 /usr/X11R6-DRI
It's already done, thanks to binaries you gave me:)
> Setting the ProjectRoot in /usr/X11R6-DRI isn't even necessary since is
> the default already.
Really? In which file? site.def contains ProjectRoot /usr/X11R6 but
host.def contains /usr/
Jorge Luis Williams wrote:
>
> Hello,
>
> I've run into what appears to be a dead-lock while running tessellation
> demo by David Blythe which is included in the Glut-3.7 source
> distribution (glut-3.7/progs/advanced/tes.c)
>
> I've been able to reproduce the problem on two different Intel Pen
>
>Can't you just map an empty region of (accessible) address space and then do
>this bind (ie fault in) the physical pages as they are accessed?
That's more or less what we do with the hacked version for userland mappings,
the DRM installs a vm nopage() handler that maps in pages as they are
a
On 2001.12.10 23:17 Sergey V. Udaltsov wrote:
> > Try the tunnel demo. For me it went from 0.7fps to 25fps.
> For me, numbers are similar. Though, there are problems with fog: tunnel
> cannot turn it on (in fact, nothing happens on "f" - the fog is always
> off). For pre-pre-pre-alpha, this is no
Philip Brown wrote:
>
> On Mon, Dec 10, 2001 at 12:05:47PM +0200, Abraham vd Merwe wrote:
> > ...
> > It is not always necessary to memory map the device. For instance with the
> > I810 driver, just plain 2D, there is no need to mmap the device, but the GTT
> > (or GATT if you wish) must be popul
Philip Brown wrote:
>
> On Mon, Dec 10, 2001 at 05:53:32PM -0800, Gareth Hughes wrote:
> > On Mon, Dec 10, 2001 at 05:33:09PM -0800, Philip Brown wrote:
> > > ...
> > > But... isnt there a straightforward mmap type way to access the RAM on
> > > board the card, then?
> > > Or is it usually "load
> Please, beware of another problem with AGP. Several chipsets including
> Apple's UniNorth or some ia64 ones can't let the CPU access the AGP
> aperture. So the kernel has to map real physical memory pages into
> the process space when mmap'ing bits of the aperture. That makes
> very difficult t
>Chipsets of the motherboard, or chipset of the card?
>Does the agp code still support that type of direct mapping for those
>cards, and could you point me to the place in the driver code where that is
>done?
>It looks like the latest linux agpgart_be.c only uses gatt tables, which
>seems to imply
Hi dri-devel,
There has been some discussion in the dri-user mailing list about the
3D capabilities of the Mach64 driver so I thought that maybe some of you
guys working on the dri driver have a word about it :-)
Has the Mach64 chipset onboard of ATI Mobility cards hardw
30 matches
Mail list logo
