Someone should really fix this so it no longer refers to the
sourceforge CVS server:
http://dri.sourceforge.net/doc/cvs.html
- dri.sourceforge.net
+ dri.freedesktop.org
I assume that is correct.
Liam
---
This sf.net email is sponsored
Good day José
First off I am using http://dri.sourceforge.net/wiki which resolves to:
http://dri.sourceforge.net/cgi-bin/moin.cgi/
I assume this is correct, if not ignore me. g
First off looking good, looking useful.
There does seems to be some recursive linking going on ie pages linking
to
Now I am reading intel northbridge 440BX spec(look page 88:Memory
System Address Space) And i have a box with 440BX
I look /proc/iomem,i find that Framebuffer's size is 16MB(i open vesa
before kernel using vga=788) And the local Graphics Memory's size is
64MB(through PMBASE Reg (24h) ;Dev
On Fri, 19 Sep 2003 12:20:53 +0100
José Fonseca [EMAIL PROTECTED] wrote:
On Thu, Sep 18, 2003 at 06:52:23PM +0200, Alexander Stohr wrote:
i want to propose to integrate a link
to the new WIKI pages to the Help FAQ
section of the DRI homepage.
I've added a link to the Wiki next to the
I updated the configuration design document to reflect the current
state of the implementation. The new document is available at
http://user.cs.tu-berlin.de/~felixyz/dri/dri_config_design_rev4.txt if
anyone is still interested given a mostly complete implementation. ;-)
Maybe someone wants
Been real busy lately, so I'm going to unsubscribe from dri-users, and
filter out bugzilla-daemon to delete without reading.
Otherwise I just won't be able to read all the posts, this makes it a
third less emails I have to read.
Although now that I look at it, while dri-devel seems to be
On Wed, 16 Jul 2003 15:52:41 -0500
linsblues [EMAIL PROTECTED] wrote:
REMOVE MY NAME FROM YOUR LIST
Chill out man.
Allow me quote 2 lines from teeh email you just sent to the list:
List-Unsubscribe: https://lists.sourceforge.net/lists/listinfo/dri-devel,
mailto:[EMAIL PROTECTED]
I just saw this on extremetech today:
http://www.extremetech.com/article2/0,3973,1101038,00.asp
Looks like SiS is spinning off it's graphics chip division. perhaps
this could mean better access to databooks!
Now might be a good time to ask if they've considered it, get the idea
out there
Pretty much now...
This is just a friendly reminder that the weekly dri-devel IRC meeting
will be starting in the #dri-devel channel on irc.freenode.net at 2100
UTC (or 5:00PM EDT or 2:00PM PDT, if you prefer).
Time zone conversion available at:
I just upgraded my 2x933 p3 to 2x1400 p3-tualatin, and now whenever I
start up Q3A the machine hangs hard.
On one occasion, Q3A started, but the sound was all screwy, and on
exit q3a segfaulted. xmms, however, still played sound just fine.
The other few times I tried, it instantly
on the web page, titled CVS fro the DRI,
linked via CVS Web Page on the documentation page
there is a comment for the mesa-4-0-4-branch
with states:
A Stable branch to be included in XFree86 4.3
XF86 4.3.0 is already out a few months,
so that line obviousely needs an update.
Thanks.
Did anyone else notice this?
No.
http://sourceforge.net/forum/forum.php?forum_id=217795
I'll read it.
Maybe I've been hiding under a rock...but I think this was done 6
months ago and none of us noticed because the only notification was
given to the news column of the DRI projects
Hi Philip
Are you going to put your time where your mouth is? g
I'm sure that having someone who looks after the admin of the
DRI project is a good idea.
If only for the reason as having someone to fiddle with the
website, ie leaving the dri developers more time to code drivers.
Heck I might
You could set up a dummy database for testing?
Yes I could, for teh meomnt I installed apache and php, apache works, php
doesn't, if I get php working then I'll see about a database.
So, which files in doc/ should go into CVS? At a quick glance, only the
files in the doc/ directory itself
http://g7-mac3.fy.chalmers.se/cgi-bin/twiki/view/Forte/WebHome
I haven't looked at it
That was supposed to read: I haven't looked at it *yet*.
That's because the video drivers have had the PCI ID to name
mappings changed from Radeon xxx SDR/DDR to Radeon 7200. To
my knowledge, it is
We don't need to put everything into CVS right away, but the way several
people are editing the same files right now is dangerous.
Somewhat, at least it makes life interesting. g
I'd rather not use CVS myself just for the website, when I mess up a
single character I just ssh onto the
Maybe this is a radical proposal, but it's a thing I've made good
experience with, over the last few months.
http://twiki.org
It is probably not the right thing if you want a perfectly styled
corporate web site. But it is an easy way for everybody to keep
documentation up-to-date. The
I'm not sure what you mean here. If you cvs commit on the webserver, the
only bandwidth you need is for the I/O on your terminal. The CVS
protocol traffic is only between the machine you are logged in on and
the machine the CVS repository is on, both sf.net. And even if you
commit directly
On Tue, 11 Mar 2003 18:34:16 -0700
Brian Paul [EMAIL PROTECTED] wrote:
Smitty wrote:
Hi Brian
In light of your well maintained:
http://dri.sourceforge.net/doc/dri_driver_features.phtml
I think it's about time that:
http://dri.sourceforge.net/doc/dri_radeon_features.html
The DRI website contains a few other inaccuracies about ATI's
Radeon video hardware. Nothing mission critical, but it is
incorrect:
http://dri.sourceforge.net/doc/radeon_naming.html
Radeon VE a.k.a Radeon 7000, is not R100, it is RV100.
So what does this mean for users of DRI?
PS: Editing files like this makes me kind of nervous, we should really
work out a way to handle the website in CVS.
What's the difficulty in having it in CVS? it's extremely trivial to set
up, you just tell the web server to cvs up from the repository every few
hours or so.
The website
On Sun, 2 Mar 2003 19:34:27 -0500 (EST)
Mike A. Harris [EMAIL PROTECTED] wrote:
On Sun, 2 Mar 2003, Smitty wrote:
OK but here is my take on it, people will work on what they are
interested in, so if someone wants to work on R128 and ATI does
give out docs for that chip then they should give
(oh, and please, I prefer being referred to by my first name.)
one Molton many Ian's g
From: Daniel Vogel [EMAIL PROTECTED]
To: Smitty [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: RE: [Dri-devel] Re: future of DRI? - why no one plays with
Glide3. Date: Sat, 1 Mar 2003 16:35:15 -0500
a V3
Can we add this to the FAQ, please?
The FAQ is editable by anyone isn't it?
No, but anyone can add a FAQ, if they could edit / delete them that would
be none too wise, which is why I advise not to mess it up (because then I
have to fix it).
Liam
it depends
OK, I don't exactly want to stir up this hornets nest *again*, but a
couple of things aren't entirely clear to me and I'd appreciate any
clarifications.
As I understand it, the situation is as follows:
The S3TC algorithm is patented and therefore no-one can distribute an
I think spam filtering for dri-devel and dri-users would be a good
solution -- IMO, that would be better than moderation. For
dri-patches, the Reply-To is dri-devel. I'd rather have just commit
messages and nothing else on dri-patches. Any comments/replies to
specific patches, or
Hi Rich
Is there anything that can be done to cut down the spam on dri-devel?
Several other mailing lists I'm on hold submissions by non-subscribers
for approval. I'd even be willing to sort the non-subscribed emails,
so that everyone else could avoid them...
That would be great, its
Is there anything that can be done to cut down the spam on
dri-devel? Several other mailing lists I'm on hold submissions by
non-subscribersfor approval. I'd even be willing to sort the
non-subscribed emails,so that everyone else could avoid them...
That would be great, its really
snip scary plaintext example
1) Requires special parser which is too syntax sensitive
2) Users editing the file could hose it rather easily compared to
existing formats.
Ja I know I was teasing the We want XML crowd by going to the extreme in
the opposite direction, trying to pull them
Howzit?
How about this for something which can be edited by a GUI program which
can change the settings, and which I / you / world+dog can read,
understand and edit easily in a text editor?
GUI *and* CLI editable without having to squint at it.
Anyone see any problems if so feel free to
Hallo
We've been discussing general issues regarding the new DRI configuration
system recently on IRC. The most user-visible issue is the configuration
file format (until there is a GUI tool ;-).
In any case we need a more structured (nested) format than win.ini since
we want to be able to
I think this needs to go to dri-devel. That's where the busy person lurks,
and it seems to be a good start.
Actually there has been some work to create a script which will
identify the card and advise which driver to download, but holiday
season plus busy people does not make these things
Does the quotation below accurately reflect the situation eith kernel
modules or not? If not please spell out the correct situation.
The information on the web site is wrong in that place, and cause me
a great deal of confusion. The kernel modules are now included as
part of the
http://grassomusic.de/english/luefter.htm:
AGPx2 can use lower signal levels if the graphics card asks for it,
1.5V instead of 3.3V (AGPx4 uses 1.5V high state always)
Wonder if this has anything to do with why some cards on some
motherboards work at some AGP multipliers but not others.
Seams to me that SSE support in Mesa-5.0/5.1 brakes several things on
Athlon
systems. On Athlon MMX and 3DNow! are shared. Even SSE is mixed in.
But more parallel...;-)
When did this happen I was under the impression state changes were
required to get between the various instruction
Howzit?
Been real busy until last week with exams, spent the last week clearing
certain backlogs, sorting out problems, etc.
And now am answering DRI email.
Heres a suggestion.
Can people holding non-NDA chipset documentation please all send it to
smitty and he can put it up on the site
Howzit Dieter?
Been real busy until last week with exams, spent the last week clearing
certain backlogs, sorting out problems, etc.
And now am answering DRI email.
Any progress?
With what excatly the guide in the subject line - I've never touched that.
With the website see below.
When will
Hello Bache
Been real busy until last week with exams, spent the last week clearing
certain backlogs, sorting out problems, etc.
And now am answering DRI email.
I've made a small howto for ati radeon 8500 with direct render support.
I want opinions and suggestions, changes that can make the
btw is the DDX Driver what causes the XServer to be single threaded?
I think there are more fundamental reasons.
Better change that back then.
Also sticking up dri_driver_features table by Brian Paul, it may not
be complete but it is full of info already.
Yes, looks good. I'd change
This has been sitting around for a long time, since I got pulled into
the website side of things.
I wish to put this up as high level design documentation.
Any comments?
The two documents look great! Up they go.
They match many of my personal notes about architecture :)
OK then.
btw
This has been sitting around for a long time, since I got pulled into the
website side of things.
I wish to put this up as high level design documentation.
Any comments?
and yes n2s is note to self.
Liam
it depends
dri_flow.tar.gz
Description: Binary data
Hi Brian
Attached is an updated table.
Good work, when everyone stops pointing out typos etc please email
(cc) me a copy, and I'll put it up sometime (wee bit busy atm).
Liam
it depends
---
This sf.net email is sponsored by:ThinkGeek
Why don't you just use
deb http://penguinppc.org/~daenzer/debian/dri-trunk/./
This is new to me,
I guess it wouldn't be a bad idea to mention them somewhere on
dri.sf.net.
Who is them? g
DRI CVS snapshot packages, so based on 4.2.0.
What is it it?
Details are
otherwise alphbetically eg Manufacturers Distros (I'll fix distro's now)
Then you only have to fix status.phtml (Supported Cards) to make it equally to
links.phtml (Graphics Card Manufacturers).
Well spotted, I'll make the status.phtml alphabetical.
cheers
Liam
1. For the mailing list info, there is a link to the old Geocrawler
archives. I think that should probably be removed because SF.net has th=
eir
own archives now and they also include the content from the old Geocraw=
ler
archives. You can already get to the SF.net archives by clicking
Howzit?
Having noticed the spam on this list, when I was working on the Mailing list
page ( subscribe / unsubscribe / preferences ) this struck me as odd:
To send mail to the list send to [EMAIL PROTECTED]
Now is this not vulnerable to email harvesting web bots which makes the list
more likely
Op Saterdag, 28 September 2002 20:27:01 Dieter Nützel het geskryf:
Am Samstag, 28. September 2002 19:57 schrieb Smitty:
What about the main central archive?
http://marc.theaimsgroup.com/?l=3Ddri-develr=3D1w=3D2
It is fast and dany.
I've added your link but, only the one to dri
I would say that Effecting a full scale 'all in one go' transition is
VERY hard. I would suggest letting Liam make the poage official, and
continue refining the layout.
I don't see how a transition in one go is very hard at all. The DRI
website is fairly small, all you have to do is
I think it is much too early for this kind of criticism. While the
updated website is far from perfect and finished, I definetely think it
is a clear improvement with respect to the former version.
I don't see how it is too early for criticism. Liam has indicated
several times that
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/
Sorry I managed to miss a whole bunch of posts, reading
Howzit Frank?
Quite frankly (no pun intended) IRC logs are about the only thing out of
place, and when I look at that page I wonder if I should remove them,
however your idea to split documentation back out of help will draw
attention back to them on that page meaning they can be safely
Ok, I would remove CVS and IRC Logs from that page. They should
re-appear on the Contribute page.
IRC is already gone, I'm leaving CVS there (for now at least) because
you know who you are is working on scripts to pull CVs, compile etc
Why do you need to leave the CVS information
Speaking of the new web site, could someone please remove the section
in the FAQ that says that various NDA'd documentation can be obtained
by becoming an XFree86 Project member.
I'm sure someone could do that, could you point out where this is,
I'm certainly not about to read all the
Speaking of the new web site, could someone please remove the section
in the FAQ that says that various NDA'd documentation can be obtained
by becoming an XFree86 Project member.
I'm sure someone could do that, could you point out where this is,
I'm certainly not about to read all the
Which reminds me /dri/htdocs/ is a real mess and I can't clean it up because
I don't have rights to delete things (I think) because the permisions set are
for the dri / sourceforge *login* not the *group* dri.
I don't understand. As it is now:
% ls -l
drwxrwsr-x2 mdaenzer
Liam
it depends
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Dri-devel mailing list
[EMAIL PROTECTED]
On Sun, 22 Sep 2002 21:24:37 -0700
Frank Worsley [EMAIL PROTECTED] wrote:
That hasn't happened (accepted and moved) so I haven't asked. hint
I think there is two problems here ...
1. Since this is an open-source project there is no single person to
approve the website. Basically I don't
Mike A. Harris wrote:
There's a typo on the Radeon features webpage:
http://dri.sourceforge.net/other/radeon_dri_features.html
At the bottom it has IcDT Gatos
Should be iDCT
(Discreet Cosine Transform)
IIRC I wasn't worried how I spelled it originally as it was RFC stage I put
Howzit?
Thanks to all those who have been helping me, this has got done a lot quicker
than it otherwise would have, and the DRI site is still standing ;-).
Anyhow:
http://dri.sourceforge.net/site_update/
All comments, suggestions, requests are welcome.
Liam
it depends
email me and I will email you the updated version, it is currently less than
70K uncompressed (it uses the existing site) this version may be up to
double that -I'll try to keep it down in size.
Liam
it depends
---
This sf.net email is
This worked for me, but my Radeon 7500 QL is ok with Fast Writes.
What dose this do, just curious?
IIRC an AGP feature which must be supported by both the chipset and the
graphics card, just makes things faster, like side band addressing.
Thanks to the help of Stefan and others I got my
Howzit?
Busy going over the website doing some updating, and have a few requests.
1. have a look at the radeon features list, I think the status of a few of
those features has changed.
2. Anything else on the website that you can spot that needs updating.
Liam
it depends
Which makes perfect sense for Michal Kozlowski problem, old chipset
(no / buggy fast write support) and new graphics card (with fast
write support).
This issue is also present for me, I get the same behaviour (X-server
crashes, and blanks the screen) on my box, even though I've
Howzit?
what is hyper-z? a proprietary texture-compression function of the r200?
well, as you expected, performance is exactly the same after the
checkout as before
HyperZ has 3 components:
Hierarchical Z
Discards hidden pixels instead of sending them to be rendered.
Z-Compression
Performs
#
# List of PCI ID's
#
# Maintained by Martin Mares [EMAIL PROTECTED] and other volunteers from the
# Linux PCI ID's Project at http://pciids.sf.net/. New data are always
# welcome (if they are accurate), we're eagerly expecting new entries,
# so if you have
Great work Keith.
What I've done so far is to extend the existing radeon interfaces to accept
validate the new state required for the r200, and a couple of other minor
changes. This is probably the minimal set of changes to get a working r200
driver.
It would seem that driver development
Hei
some my friends reported that this method still not work for Radeon cards
(Xserver starting but dri not work). Testing in progress... :)
Me neither (I have a radeon) however it works as root / su (even in a
virtual terminal under X logged in as a normal user where it wont work)
which
On Sun, 23 Jun 2002 22:52:09 +0100
Keith Whitwell [EMAIL PROTECTED] wrote:
Smitty wrote:
I want to get started putting up the new site, but no-one has told me
how to access the webspace...
I've given my sourceforge details and been added to the project...
Ian,
I can't help you
Well after beeing told to upgrade to XF4.2 from XF4.1 I did so:
So XF4.2 Indirect rendering
install the latest / last binary package from TG
XF4.2 with direct rendering (no TCL)
compile (not install) the latest binary package (20020623) from SF
copy every file to its proper location except
Also, the frames need a bgcolor in the body. This is a pet peeve of mine,
since I have my default background set to gray.
Well if I can see them then I can grab them and resize them. g
I can also see this line in the old / original site?
Liam
it depends
From: Keith Whitwell [EMAIL PROTECTED]
snip
- There's no easy link to the sourceforge projects page.
yes and add the hosted by SF pic below (with some space) redline2
(finishes off the menu frame nicely)
- The 'status' page has disappeared
change Hardware to Status in the menu frame. (makes
I want to get started putting up the new site, but no-one has told me
how to access the webspace...
I've given my sourceforge details and been added to the project...
Ian,
I can't help you with access details, but I'd like you to stage this
below the current main site until we've
It's just a guess on the agp gart; the IDE and sound both are clones of
the AMD chip, so why not the gart?. The big whiz-bang feature of the
nFORCE chipset is the crossbar memory controller that supposedly doubles
the bandwidth of DDR (double double data rate). Why would they bother
Just upgraded to the latest radeon dri-cvs (using the binary packages
on SF) and now the X server won't start. This used to work fine with
the 20 May TCL snapshot.
The kernel module seems to load OK:
Jun 19 16:30:36 localhost kernel: [drm] AGP 0.99 on Unknown @ 0xec00 64MB
Jun 19
Howzit?
Having a bit of an issue with the packages from:
http://dri.sourceforge.net/snapshots/radeon-20020615-linux.i386.tar.bz2
On a clean install of Linux Mandrake 8.1
XFree 4.1
Kernel 2.4.8 etc
Radeon SDR 32MB / AMD 756/758
Linux Intel x86 Packages:
radeon-20020615-linux.i386.tar.bz2
Using
On Sun, 23 Jun 2002 20:15:35 +0200
Dieter Nützel [EMAIL PROTECTED] wrote:
On Thursday 01 January 1970 00:59, Smitty wrote:
Hallo Dieter
It's just a guess on the agp gart; the IDE and sound both are clones
of the AMD chip, so why not the gart?. The big whiz-bang feature
Howzit?
I see that there is a very active development community and three big projects
in the works (radeon, radeon TL, and mach64).
Yes I've slowly realise that this is what goes on in the DRI project, a thought has
been rattling around in my head of late of a simple list of who is working
1.) MK II:
_
\
+-+ |
| X11/OpenGL Based Application | |
| (Using 3D Direct Rendering) | |
Howzit Jens?
3 Parts to this email.
1.) MK II:
_
\
+-+ |
| X11/OpenGL Based Application | |
| (Using 3D Direct Rendering) | |
Hei Jens
Remember this?
+---+
| X11/OpenGL Based Application|
| (Using 3D Direct Rendering) |
+--++
| OpenGL Library | XLib |
| +++ |
| | GLXLib | |
I've attached the latest WIP of cntrl_flow.png to help show this.
Wasn't paying enough attention. g
Liam
it depends
cntrl_flow.png
Description: Binary data
Howzit Jens?
Did you see the flow chart at
http://dri.sourceforge.net/doc/control_flow_poster.jpg
Yes, and I've worked through it.
I am referring to:
http://dri.sourceforge.net/doc/data_flow.jpg
IMHO it doesnt make it any clearer what happens once the 2D 3D data arrives at the X
Server
Howzit?
A links page was requested and this is what I have so far, have I missed anything, is
anything unneccessary?
If so I think you know what to do about it.
Links to Projects Companies related to DRI:
Chromium Project (The)
http://chromium.sourceforge.net
FbDri
Howzit?
I would like to confirm my understanding of the various data paths between
applications (both direct and indirect rendering) and the graphics hardware.
First I have the path of 3D data between the 3D direct rendering program and the
graphics hardware which is pretty simple.
Direct
Howzit?
On Fri, 2002-05-24 at 19:54, Smitty wrote:
=20
6) What is required in order to produce drivers for other architectures
- If people tell me this, I will add it to the 'help us' section of the
site.
Do you mean other architectures as in other OSs or as in other processor
Howzit?
1) I *NEED* info about what cards have what features supported by DRI,
like the radeon driver does already.
Don't we all. g
2) rehash the voodoo5 glide compilation to a generic voodoo guide
Can not help here.
3) Can people help me compile a list of janitorial tasks that could be
Howzit?
There are a few other documents on the Insights Page that I didn't
bother duplicating on the DRI page. It might be a good idea to do this
now, since the Insights Page might not be around forever. Would that be
ok with VA Linux/Precision Insight regarding copyright issues?
I don't
Hwozt damien?
btw the list is now up on the (card) status page of dri.sourceforge.net.
It would be really good if the status included what features are supported
by the hardware. This may make it easier for interested parties to jump in
and pick up pieces that they want to work on.
I'm
Howzit Ian?
First off, dankie.
snip
Noted, used, and added a few mechanisms to deal with:
I think
Nvidia proprietary
Texture
===
Cache -- Automatically supported by the hardware.
Not according to Michael Ntlworld, and he backed it up.
Oh and I won't post such a
Howzit?
Here is my beta list of features I would apreciate feedback on what should be on the
feature checklist, the grouping and most importantly the *status* of these features.
I would like a bit more input on the status of the features, otherwise I am going to
use what I have and make the
Howzit Ian?
Thanks for your response.
I'm not the most qualified to answer this, but I think most of the more
qualified people are pretty busy adding some of these features. :)
Noted. But if yours is the only response and / or there are no differing answers guess
what, you will become
Howzit?
Here is my alpha list of features I would apreciate feedback on what should be on
the feature checklist, the grouping and most importantly the *status* of these
features.
(I deliberately included everything bar the kitchen sink that I can find so that I
dont have to add them in
Howzit?
aceshardware
First there was the merger announcement by Creative and 3DLabs and the disclosure of
their upcoming 76 million transistor GPU this holiday season.
Then SiS surprised us at CeBit with their new SiS330 series of DirectX 8-compliant 3D
accelerators.
As if that wasn't
Howzit?
System specs:
HW:
AMD 751/756 (750 / Irongate) mother-board (GA-7IXE4)
Radeon 32MB SDR vid card
Duron (Morgan) CPU
SW:
Linux Mandrake 8.1 fresh install
install source RPM
(kernel 2.4.8
Xfree 4.1 with 3d acceleration)
download:
radeon-20020409-i386-Linux.tar.gz
run install script as
Hmm.. Another thing to check - are you sure your power supply is
adequate ? Radeon chip has a fan on it for a reason.
Actually the fan is there to make the Radeon look faster, it runs cool at the .18
process on wich it was manufactured. Power draw I wouldnt know, then again I run my
radeon
with a hopefully easy to read / understand tabel showing the features
and their status.
I'm not looking for flames but the last time I checked the DRI website it had a list
of cards and the status of their support, but no mention of features - I feel that
this would represent an improvement.
cheers
Smitty
How about a directory / database of cards and the motherboards /
Chipsets that are known to work, preferably with some info on how
they were gotten to work eg distro patches applied.
IMHO the biggest problem people seem to have is incompatibilities
between chipset and graphics card, and if
97 matches
Mail list logo
