> places where the lock is needed will be less than now (I think), only when
> the DMA buffers are flushed via a BusMaster operation.
> So, I think that we must not worry about the interlock while the DMA work
> is not finished.
That would be my take on things.
> Frank, how is it goi
driver going so that I can move to another project
involving that chip.
--
Frank Earl
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
On Thursday 25 October 2001 04:43, Sunny Dubey wrote:
> actually ... you can .. (on specific dell laptops)
>
> http://groups.yahoo.com/group/linux-dell-laptops/message/6356
>
> odd isn't it??
About time- if only the other brands would follow sui
, not everybody can use your employer's gear, Gareth... :->
(When they come up with something like "miniAGP" for laptops, I'll be
impressed... :-)
--
Frank Earl
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
rations to not work at all. Do
you have to set bits 1 and 2 every time you want a DMA pass or is it just
with the first time you do it?
--
Frank Earl
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
space when I was testing most of the games out there against the Utah-GLX
drivers. Peak perfomance is from 640x480@16 or 640x480@32- anything higher
in pixel resolution is accordingly slower.
--
Frank Earl
___
Dri-devel mailing list
[EMAIL PROTECTED]
h
GLX code's got a good example of this- just check to make sure that
the DRM infrastructure code (in the drm* files) isn't the one doing the
loading and it's the Mach64 code doing it.
> Anyway, what I'm impatient to see is the results with the DMA working.
> Frank, whe
re actually really
close to what the GGI people were asking for- without it being named GGI/KGI.
--
Frank Earl
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
loaded, we probably ought to do something like Utah-GLX does for textures,
etc. so that we can get this off the ground for people with PCI setups while
we look into what it'd take to do PCIGART type work for this driver.
--
Frank Earl
___
Dri-de
at DMA operations (It's just the way Gareth was coding it at
the time he was working on it)- we'll get to it shortly. Right now, we're
migrating what's already there to use the DRM properly (since it's just doing
direct
ys. As soon
> > as I have access (if i'ts not too late here in Spain) I will proceed.
Since I'm going to be working on the actual DMA bits, I'd like to ask for CVS
access as well:
SourceForge Account: svartalf
--
Frank Earl
___
o check and do some further cleanups with the 2D driver
so that we don't have other "surprises". Thanks for the code.
--
Frank Earl
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
that actually makes the card go,
including the DMA support, is in the closed source GLX driver. Look
carefully at the "source" for the GLX module. There's no C, C++, or any
other language files in that source RPM.
--
Frank Earl
__
coded to get around the problem
(and that is what I plan on starting this weekend...).
--
Frank Earl
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
compiles, etc. up at work... :-)
--
Frank Earl
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
p, but someone could check and see if it's the
same problem.
--
Frank Earl
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
from CVS here.. especially
since the libs are hosed for a full server install is beyond me.
I haven't had a decent compile of DRI from CVS since early August.
Frank
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
Solved that problem.
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
ctory `/usr/DRI-CVS/build/xc/config/makedepend'
make[1]: *** [depend.bootstrap] Error 2
make[1]: Leaving directory `/usr/DRI-CVS/build/xc'
make: *** [World] Error 2
Any other ideas?
Thanks,
Frank
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
on = 1.0.0
Module class: XFree86 Font Renderer
ABI class: XFree86 Font Renderer, version 0.3
Symbol mcount from module /usr/X11R6-DRI/lib/modules/fonts/libbitmap.a
is unresolved!
How to fix this would be helpful.
Thanks,
Frank
___
Dri-devel ma
tle, if anything. The CyberBlade are very similar indeed, apart
> from the E4 which is a bit more different.
Cool. This means I'm not going to be guessing too blindly when I get to
working on a DRI driver...
--
Frank Earl
___
Dri-devel mailing
On Wednesday 19 September 2001 04:42, Alan Hourihane wrote:
> What's the problem Frank. I don't believe I've ever had a report from you
> on problemsor if you have, can you refresh my memory on what these
> problems are...(Oh, and which CyberBlade is it ?)
Never file
course wide open forums are alway preferred, but when dealing
> with NDA info from 3D chipmakers, they'll be more likely to help
> under NDA and private lists than on open lists.
If that. You'd be amazed at how little help you get from many of these
outfits, even WITH
g out bogus code...). Your pick...
--
Frank Earl
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
master and I am
willing to keep doing that. However, I am not in any way qualified to be a
contact person for any other issues. A couple of other people come to my
mind though .. how about Frank Earl or Manuel Tiera? Both of you have been
active on the Rage Pro driver ... or maybe somebody else wh
On Sunday 16 September 2001 23:53, Brian Paul wrote:
> Anyway, those are my hunches. I could probably play devil's advocate
> and come up with more issues but those are the first that come to mind.
Those are the ones that come immediately to mind whenever I've actually
gotte
, can somebody answer my question ... what is so secret about the specs
for old hardware??? And why would companies _not_ want volunteers to work on
old drivers?
- Frank
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
On Saturday 15 September 2001 07:08, you wrote:
> Frank, one more time, I would like to have your work to take a look on it.
> Perhaps with more eyes looking at the problem we could find something. And
> if you could release your changes we could test it in another machines and
> s
ve to be in your position- but the number of jobs for
that sort of thing are limited and I couldn't relocate anyhow. So, I guess,
for now at least, I'll settle for working on the old junk- someone's got to
do it, right? :->
Again, I'm thrilled that you go
cause some hardware vendor decided that something's too old or a software
vendor did the same- I suspect a lot of us aren't either, Gareth.
--
Frank Earl
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
ts on scoring your new employment- I'd hoped you'd get on with
someplace worthwhile.
--
Frank Earl
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
using it as a sort of crib-sheet for the in-progress drivers, but it's
not terribly useful for end-user purposes.
--
Frank Earl
___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
llation. That could be based on the install script.
Also, Alan has been working on DRIsetup which does similiar stuff. I don't
think he has worked on it lately, but that is also a good tool to run when
you are having problems. Maybe somebody is interested in working on it some
more?
- Frank
___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
This descriptor table can
be any size up to 64 or 128k (can't remember exactly and I'm at work right
now so I can't look at my reference books...) in increments of 16k. The
descriptor table _must_ be aligned on a boundary matching the size you
specify for the table- 16k on
This descriptor table can
be any size up to 64 or 128k (can't remember exactly and I'm at work right
now so I can't look at my reference books...) in increments of 16k. The
descriptor table _must_ be aligned on a boundary matching the size you
specify for the table- 16k on
I have an Asus A7V with a Rage Fury Pro (Rage128 Pro, AGP, 32megs). I am running it
with no problems at AGP 4x. But maybe I have a later revision of the KT133 chipset?
You should also try downloading a bios update from the Asus site. That might fix it.
- Frank¸z÷¥¨¥x%ËC®'^½
thought about this before?
- Frank
___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
body wants to tackle this I will help you out with
PHP/MySQL if you need it. But I wont start it alone.
- Frank
___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
ction of lots of little articles that could eventually be
combined into a larger document.
I am not saying you should write a novel here. Just write one or two pages
whenever you figure something out that you feel would be valuable to other
people.
Ok, that's all I have to say. Cheers...
- Frank
___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
at would fit with the 3D theme then you could just slap the letters "DRI"
somewhere on there and it would also be a cool logo!
So, to sum up, make some cool logos people. We could even make some DRI
image buttons or whatever. Right now we have 5 logos in total, if more come
in I will setu
ce card I have.
I dunno. If we relink libGL to the correct one in /usr/X11R6/lib it
shouldn't really be a problem.
- Frank
___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
since we symlink libGL.so
and libGL.so.1 to the correct library.
But maybe we should still try to remove/backup all old libGLs?
This is also a problem on Redhat were such a libGL sticks around in /usr/lib .. they
get installed from the Mesa RPMS.
- Frank
¸z÷¥¨¥x%ËC®'^½éeËl²«qçè®
atrix explaining this on the site would be very cool. In
the meantime I will add a FAQ item explaining the problem.
-
Frank ëׯzYX§X¬´:âuëÞX¬¶Ë(º· ~àzwÛiÿùb²Û,¢êÜyú+éÞ·ùb²Û?+-wèýÚâuëÞ
knows about it feels like putting together a matrix listing the
supported resolutions according to color depth/memory available for the
faq.
Thanks.
-
Frank
you to the other already existing
documentation.
You can take a look at it here: http://dri.sourceforge.net/doc/DRIbeginner.html
If you think it's good enough I can add it to the Documentation page.
- Frank
___
Dri-devel mailing list
[EMAIL
write without prompting or something like
that.
Anyway, I will update the readme.
- Frank
___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
the driver module and kernel modules have matching versions?
- Frank
___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
y the current Rage 128 driver? If
it is I would like to add that to the list too.
One last thing, which drivers support AGP/PCI ... and should I add that to
the chipset list description?
- Frank
___
Dri-devel mailing list
[EMAIL PROTECTED]
Ok, after thinking about this some more I guess there's no point in keeping
the page going as it is, since it doesn't make much sense.
I've made a generic listing of cards, check it out at
http://dri.sourceforge.net/status2.phtml and if it's ok I will replace the
cu
whether it matches your legend key table.
>
Yes, I know.
Nick Leippe and me are working on something like that, but we're too busy
right now. So until it's done I figured I would at least update the old page
a little bit.
- Frank
___
I've updated the status page a little bit. Could the developers please take
a look at it and let me know if the information is accurate. Especially the
information about supported buses.
Temporary page is at: http://dri.sourceforge.net/status2.phtml
Thanks.
-
On Saturday 21 April 2001 19:48, Gareth Hughes wrote:
> Frank, did you ever try the aligned-DMA-descriptors fix?
Not yet. I just today found time to get a build started of the stuff Richard
Cognot handed me that makes the RagePRO support close to what's in the trunk.
As soon as
nother go (which Gareth alludes
to...).
> I have a perfectly good Xpert98 AGP sitting here collecting dust :)
I know what you mean. Utah-GLX can deal with many things, but it just
doesn't work for XFree86 4.0.X and doesn't quite have the oomph for things
like Tribes 2 (which I&#
now as I type this, I'm starting to sort through
the process of learning how to get the build process for DRI drivers going.
Once I've got that done, I plan on picking up the work done by Gareth
followed by Richard Cognot to get RagePRO support u
more info.
- Frank
___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
Don't hesitate to send any messages to the mailing lists! If you are
interested in development subscribe to the dri-devel list.
I've forwarded your message to the list.
- Frank
- Original Message -
From: "David Gaarenstroom" <[EMAIL PROTECTED]>
To: <[EMA
#x27;t there anymore now.
Alan, what's the deal?
- Frank
___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
I've put together a readme file for the installation script. It's already on
the webpage, but I've also included it below.
- Frank
DRI INSTALLATION SCRIPT README FILE
By Frank Worsley <[EMAIL PROTECTED]>
CONTENTS
1. Introduction
2. Insta
playing fullscreen)! That is quite nice.
All in all, this is a hell of a lot better. Great work guys. Now if I could
only get it to be smooth at 1024x768.
- Frank
___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo
ase let me know - my email address is [s
d y @ z i l b e r . o r g] (spaces inserted to foil spam-bots).
Steve
- Frank
___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
ugly breakage.
Right now it just copies drm/*o. I guess that should be changed to use the
DRV_MODULES variable to only copy relevant kernel modules.
- Frank
___
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
101 - 161 of 161 matches
Mail list logo
