I have a question about an odd setup--I just want to know
a) if it is even possible
b) if so, how difficult would it be (a few hours or several months)
c) is there a better way of achieving an equivalent
My motivation:
I recently acquired an SGI 1600SW lcd display at surplus. I lucked out
and
On Wednesday 13 August 2003 01:10 pm, Ian Romanick wrote:
> Nicholas Leippe wrote:
> > So, here's my odd question:
> >
> > Is it possible to put the older (pci) card in the system w/the
> > radeon, have the radeon render to a texture, and have the older card
>
On Sunday 29 June 2003 07:51 am, Jacek Popławski wrote:
> There are many places in code like:
>
> if (R200_DEBUG & DEBUG_PRIMS)
>
> but I don't see how to disable debugging at all from binaries. Should not
> these ifs be in:
Just:
#define R200_DEBUG 0
#define DEBUG_PRIMS 0
The compiler should op
Okay, I found and fixed the problem.
Turns out it had nothing to do with agp mode at all. I just needed to
recompile my emu10k1.o module. Runs great at apg 4x.
Nick
---
This SF.net email is sponsored by: Etnus, makers of TotalView, The be
On Thursday 05 June 2003 01:25 pm, [EMAIL PROTECTED] wrote:
> On Thursday 05 June 2003 11:18 am, Michel Dänzer wrote:
> > On Thu, 2003-06-05 at 11:24, [EMAIL PROTECTED] wrote:
> > > I just upgraded my 2x933 p3 to 2x1400 p3-tualatin, and now whenever I
> > > start up Q3A the machine hangs hard.
> >
On Thursday 20 March 2003 02:53 pm, you wrote:
> Why not simply have a second CVS repository, where most development
> would take place under, while the current repository would be the one
> used for (pre-/post-) releases with coarse-grain commits. Like stable
> and development branches, but with t
On Friday 14 March 2003 05:50 am, you wrote:
> On Don, 2003-03-13 at 20:49, Smitty wrote:
> >
> > If I can do a CVS commit when I've been changing things on the webserver
> > from the webserver that would be good.
>
> You can, but that should be the exception because otherwise the only
> improvem
On Saturday 08 March 2003 05:02 pm, Leif Delgass wrote:
> BTW, I changed the PHP tags from ' since the short versions didn't work when testing on my local system with
> PHP 4.1.2, and the PHP docs indicate the short versions are deprecated
> since they don't work well with XHTML.
Good catch. I di
On Saturday 08 March 2003 11:05 am, Brian Paul wrote:
> I've merged the Mesa website with the Mesa/docs/ directory and updated much
of
> the content. I think everything's better organized now and the
redundancies
> between the website and docs/ directory are history. A few pages are still
>
On Saturday 08 March 2003 11:25 am, you wrote:
> I think that if you want to get into more detail about hw vs. sw features,
etc
> that it should be put below in the "Driver-specific Notes" section below.
But
> if someone feels strongly about it and will do all the work to do something
> fanci
On Thursday 06 March 2003 08:26 am, Suzy Deffeyes wrote:
> Who is the audience for the table? Is it the end user checking to see if a
> feature is available and/or has some form of HW acceleration? Or is the
> audience the DRI developer, looking to see what pieces need implementing?
> That might
Brian,
I scratched an itch and made this dynamic. You can see it at:
http://lfm.sourceforge.net/dritest/dri_driver_features.phtml
and of course grab it if you want from:
/home/groups/l/lf/lfm/htdocs/dritest/dri_driver_features.phtml
I was thinking it would be nice to color code it even more and
On Wednesday 05 March 2003 12:28 pm, Felix Kühling wrote:
[snip]
> The developer may as well implement his own container types as
> templates. My point is that STL seems quite bloated and often a bit
> clumsy to use. The code I wrote using STL was never exactly well
> readable (maybe my own fault).
On Wednesday 05 March 2003 10:54 am, Felix Kühling wrote:
> If you use the standard library you have to start worrying about ABI
> compatibility issues. How much trouble is it to write C++ code that can
> be linked without the standard library. I mean avoiding things like
> std::cout is no problem.
On Wednesday 05 March 2003 10:31 am, Linus Torvalds wrote:
> Also note that if you don't allow exceptions (which I would _strongly_
> encourage), you can't really use "new" - unless you think it's ok to
> SIGSEGV under low-mem circumstances. Which it might be, of course, in some
> situations.
I
On Wednesday 05 March 2003 12:10 am, Ian Romanick wrote:
> Jens Owen wrote:
> > Jose,
> >
> > I've been on the road for the last few days, so I haven't had a chance
> > to express my concern for porting the DRI to C++. Please take these
> > concerns with a grain of salt as I am definitely in th
On Thursday 27 February 2003 03:01 pm, you wrote:
> Without starting starting to think about 3D now, what
> will Linux's response to Longhorn be when it ships in
> a year or two?
IMO it may as well be ignored. There's no sense in keeping up with the
Jones's if the Jones's aren't doing anything f
On Monday 30 December 2002 07:33 pm, R Deepak wrote:
> Greets!
>
> I'm having trouble with (using the latest cvs)
>
> make World
>
> on my linuxfromscratch system. There is no previous installation of X on
> the system.
You need to install a full X first. (I also do lfs, just grab X 4.2.1
so
On Thursday 19 December 2002 11:39 pm, you wrote:
> Couldn't this be a "general" API to get missing stuff (e.g. ATI's "Smooth
> Vision", "HyperZ" etc.) into the DRI? Something like to get (binary) addon
> modules into the tree.
>
> What do you think?
Probably a very good idea--then vendors coul
On Wednesday 18 December 2002 11:20 pm, you wrote:
> On Wed, Dec 18, 2002 at 08:10:30PM -0800, Linus Torvalds wrote:
> >
> > You have to balance things out. Yes, the US is litiginous, and clearly way
> > too much so. Is the answer to just cower in a hole and hope it passes?
> > Maybe. And maybe no
On Wednesday 11 December 2002 07:51 pm, you wrote:
> XFree86 4.3 is going to go with a Mesa 4.0.x-based DRI because of time
> constraints and stability concerns. I know that this complicates things
> a little, but I don't see a practical alternative.
>
> I've created a branch called "mesa-4-0-4-b
On Wednesday 04 December 2002 01:06 pm, you wrote:
>
> I basically see three camps in this discussion:
>
> 1. Users should be able to configure default behavior using configuration
> files (which would be selected based on argv[0] or similar)
>
> 2. Users should be able to configure default beha
On Tuesday 03 December 2002 12:35 pm, you wrote:
> On Tue, Dec 03, 2002 at 10:14:45AM -0800, Linus Torvalds wrote:
> |
> | Why? I don't understand this reluctance to just admit that the _user_ may
> | be right.
>
> I note your use of the word "may." Sometimes the user can happily
> express a si
On Monday 25 November 2002 06:12 pm, you wrote:
> 1. start X or system start (init 5)
> 2. rcxdm stop
> 3. rrmod radeon
> 4. restart X (rcxdm start)
>
> What happens:
> * Screen corruption in several upper lines (the KDE panel)
> * a copy of the graphical screen on console 1, 2, 3, etc. but withou
On Monday 25 November 2002 04:16 pm, Dieter Nützel wrote:
> Am Montag, 25. November 2002 23:00 schrieb Nicholas Leippe:
> > On Monday 25 November 2002 09:11 am, Michel Dänzer wrote:
> > > On Mon, 2002-11-25 at 10:51, Nicholas Leippe wrote:
> > > > Latest CVS pull (&l
On Monday 25 November 2002 09:11 am, Michel Dänzer wrote:
> On Mon, 2002-11-25 at 10:51, Nicholas Leippe wrote:
> > Latest CVS pull (<12 hrs ago)
> > Radeon r100 64MB vivo @ AGP 4x
> > 2.4.19 SMP kernel
> > via chipset (asus cuv4x-d)
> > 2x Intel p3 933
>
Latest CVS pull (<12 hrs ago)
Radeon r100 64MB vivo @ AGP 4x
2.4.19 SMP kernel
via chipset (asus cuv4x-d)
2x Intel p3 933
1GB ram
w/o himem, it works fine--q3a plays, etc.
w/ himem, q3a hangs the machine completely, no ping, no vt switching,
nothing.
Nick
Latest CVS, 1GB ram, w/highmem enabled Q3A causes some fabulous hangs. It
doesn't immediately hang the machine, but Q3A itself hangs, then subsequently
any attempt at using ps hangs, and random other processes begin dying, and
eventually kaboom--the machine is unuseable at all. (Haven't tried
Hi,
I just pulled the latest CVS, and now my mouse does not work in Q3A. It gets
button events, but no mouse movement at all.
quake does report:
XF86DGA Mouse (Version 2.0) initialized
I've tried both PS/2 and IMPS/2 protocols, neither work. I have a logitech
optical USB-PS/2 wheelmouse.
Th
On Sunday 27 October 2002 03:58 pm, you wrote:
> Felix Kühling wrote:
> > Hi,
> >
> > I had my Xserver running for about 24 hours straight and noticed that it
> > was using about 220M virtual memory. Even after closing all clients and
> > logging out the memory usage didn't drop significantly. Aft
On Tuesday 08 October 2002 08:30 am, you wrote:
> Hi,
>
> I was quite interested to see this in the changelog of the latest Quake3
> point release:
>
> - SMP support in the renderer. Detects CPU count, r_smp 1 default if
> available. (thanks to Gareth Hughes for contributing this)
>
> Starting
On Sunday 06 October 2002 05:08 pm, you wrote:
> On Son, 2002-10-06 at 20:26, Nicholas Leippe wrote:
> > On Sunday 06 October 2002 06:50 am, you wrote:
> > > >>>>> "j" == j r fonseca writes:
> > >
> > > j> There have been q
On Sunday 06 October 2002 06:50 am, you wrote:
> > "j" == j r fonseca writes:
>
> j> There have been quite a few problems with the snapshots lately (more
> j> specificaly a XAA binary incompatability, being compiled with gcc-3.2
> j> and against glibc-2.3) but all these problems
On Sunday 29 September 2002 10:13 pm, Jason Cook wrote:
> Nicholas,
>
> I have followed the advice that others gave you in their replies and
> have been able to find the info on environmental variables but I have
> not looked in the right place for XF86Config Options. Do you know
> where to find
On Sunday 29 September 2002 03:42 pm, José Fonseca wrote:
> Check http://dri.sourceforge.net/doc/faq/testing.html#AEN1637 .
> If you see any other 'knobs' worthy to mention (even not necessarily
> environment vars) then I would appreciate that you forward them to me so
> that I can add them to the
Hi,
I was wondering if some dev out there could spend say 2-5 minutes
and post an email that lists all of the possible knobs that can
be turned. I know there's a bunch, but they're scattered though
several postings and hard to find.
For example:
ENV VARS
LIBGL_DEBUG # enable debuggin
On Sunday 22 September 2002 10:24 pm, you wrote:
> I would also recommend that you work together with Nick Leippe.
>
Just a quick note to say that I'm still here and happy to help.
My modified version is up for grabs to pick and choose from still at
http://lfm.sourceforge.net/dritest/
If you a
On Tuesday 14 May 2002 05:05 pm, Ian Molton wrote:
> Hi
>
> I am looking for information resembling
>
> http://dri.sourceforge.net/other/radeon_dri_features.html
>
> For ofther cards in the dri project.
>
> please can people direct me to where this information can be found?
Liam (Smitty <[EMAIL P
On Monday 15 April 2002 12:46 pm, you wrote:
> On Mon, 2002-04-15 at 00:15, Allen H. Ibara wrote:
> > > Hmm. Can you try without AGP? You'll have to rebuild the DRM kernel
> > > module and the 2D driver with the #define PCIGART_ENABLED active for
> > > that to work, and apparently there are other
> We have massive reports of VT switching hangs in XFree86 4.2.0
> with almost all Radeon hardware, but with other hardware as well.
> This problem has occured aparently since the prereleases 4.1.99.*
> and up through to the final release of 4.2.0. The kernel version
> doesn't seem to make any di
This isn't really DRI specific, but I don't know where else
to ask.
I just built + installed X from cvs, and it didn't build
the pex5 or xie libs. I'm not even really sure what these
do, but my other machine that I built a while back with
X + DRI from DRI cvs has them both.
What should I look f
I've read that the most current DRI code is now
in the XFree86 CVS. Is there any particular
tag that is considered stable since 4.1.0 ?
Should I just get 4.1.0?
I'd like in particular the latest ATI Radeon code
that will work with the gatos atixv stuff, and
the latest/best Matrox G400 code.
Are
On Friday 06 April 2001 05:50 pm, you wrote:
> I had to patch the source to get the module to load into my kernel -
> routines in drm_scatter.h were not being compiled.
Alan already fixed this a different way just last night.
Might need to revert it.
--
Nobody will ever need more than 640 kB R
The latest trunk needs these 1 liner fixes otherwise
DRM(sg_cleanup)() ends up as an unresolved symbol
rather than an inlined function in both .o and
_drv.o for mga, tdfx, gamma, and i810. Both
r128 and radeon already had it.
add:
#include "drm_scatter.h"
-- kudos --
This latest pull gets me
I've gotten into the habit of just doing
a 'make install', since the xserver is
pretty stable for my card. But what/where
are all the files (binaries/libs/modules)
that get overwritten when I do 'make install'
that I should be concerned about backing up?
Nick
--
Nobody will ever need more than
On Thursday 05 April 2001 08:25 am, Jeff Epler wrote:
>
> It's likely due to Linux' lack of page coloring.
>
> Let's see if I can get the explanation right ... The L2 cache is typically
> physically mapped, and so for some value N the addresses A and A+N alias
> to the same cache line. N is some
On Thursday 05 April 2001 03:08 am, Mike Lincoln wrote:
> Could it be some buffer is some times allocated (word/page/whatever)
> aligned and sometimes not?? Tends to make a big difference on Intel..
>
> Mike
Well, I thought about this. But looking at the source (it's pretty
straight forward) th
On Wednesday 04 April 2001 06:07 pm, Brian Paul wrote:
> This isn't really unexpected. Benchmarking any application on
> a time-sharing operating system can reveal some variation in
> performance. You never know when another process or the kernel
> itself will need some CPU cycles.
>
>
> -Brian
This may be opening a pointless can of worms,
but, I'm really curious as to how to explain
the behavior I'm seeing. Each time I run
gears, it is perfectly consistent in it's
speed (+/- .5 FPS) for that instance. But,
each time I run gears, it is consistent around
a different value that ranges fr
Sorry, I follow the list religiously, but
am not clear. Would someone mind briefly
explaining the current relationship between
X4.0.3, the dri cvs-trunk and kernel 2.4.3?
I know that 4.0.3 came out right before a
dri->X cvs merge and some aa/render changes
were added to 4.0.3, and also that ther
I did the work-arounds suggested for compiling with
aa/render support, but I'm still getting compilation
errors. This seems unrelated to the aa/render stuff:
ranlib libxnest.a
rm -f Xnest._man
/lib/cpp -undef -traditional -D__filemansuffix__=5x -D__miscmansuffix__=7
-D__drivermansuffix__=4 -D_
51 matches
Mail list logo
