Re: [Dri-devel] mach64 binaries: do work! Was: do not work...

2002-03-15 Thread Sergey V. Udaltsov

 But now that you touched on the subject, why don't you help on the 
 development as well!?
Well, I'd be glad but there are some problems. Unfortunately I am
already involved in 2 projects (my own GSwitchIt and SQL/jEdit) so I
simply has no time for anything else (well, I do not count my family:).
Also, I has no background in 3D development, so the learning curve for
me would be too long. I am trying to do my best in testing but I am
afraid for foreseeble future it is the only way I can afford. Though, at
some point hopefully I'll be happy to join the team. 
BTW, is there a way to get the wonderful DRI devel FAQ as a single
document (in PDF or - better - in HTML format)? I'd like to have it in
my Visor but I could not find it:(

Cheers,

Sergey

___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] mach64 binaries: do work! Was: do not work...

2002-03-15 Thread Jens Owen

Jose Fonseca wrote:
 
 The latest snapshot, works. I've checked it myself.
 
 The problem was libdrm.a which is not as device independent as thought.
 It has some interface functions which in the case of mach64 are new and
 not available in the XFree86 4.x releases.

This has been a sleeper issue for a while.  I'll look into what can be
done to improve this.

Regards,
Jens

-- /\
 Jens Owen/  \/\ _
  [EMAIL PROTECTED]  /\ \ \   Steamboat Springs, Colorado

___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



[Dri-devel] mach64 binaries: do work! Was: do not work...

2002-03-14 Thread Jose Fonseca

The latest snapshot,
http://mefriss1.swan.ac.uk/~jfonseca/dri/packages/bleeding-edge/mach64-20020314-1601-i386-Linux.tar.bz2
 works. I've checked it myself.

The problem was libdrm.a which is not as device independent as thought.
It has some interface functions which in the case of mach64 are new and
not available in the XFree86 4.x releases.

I've changed install.sh to be more permissive regarding missing files in
the package, i.e., just backup/install files that are included in the
package. The result is that a single install.sh can be used to
install/uninstall either a complete or a minimal package.

I also noticed that the snapshots of mach64-0-0-3-branch don't work on
Xfree86 4.1.0, since the 2D driver ABI changed between the releases. I
suppose it's the same for all driver snapshots taken from the trunk,
althought that was not my previous impression.

Sergey, please test once more. If everything is okay, I'll start
uploading the mach64 snapshots to the DRI website as well. (And put a
README describing the current limitations of mach64)

Regards,

Jose Fonseca


___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] mach64 binaries: do work! Was: do not work...

2002-03-14 Thread Bernard Cafarelli

Le 14 Mar 2002 17:07:47 +
Jose Fonseca [EMAIL PROTECTED] a écrit:

 The latest snapshot,
 
http://mefriss1.swan.ac.uk/~jfonseca/dri/packages/bleeding-edge/mach64-20020314-1601-i386-Linux.tar.bz2
 works. I've checked it myself.
 
 The problem was libdrm.a which is not as device independent as thought.
 It has some interface functions which in the case of mach64 are new and
 not available in the XFree86 4.x releases.
 
 I've changed install.sh to be more permissive regarding missing files in
 the package, i.e., just backup/install files that are included in the
 package. The result is that a single install.sh can be used to
 install/uninstall either a complete or a minimal package.
 
 I also noticed that the snapshots of mach64-0-0-3-branch don't work on
 Xfree86 4.1.0, since the 2D driver ABI changed between the releases. I
 suppose it's the same for all driver snapshots taken from the trunk,
 althought that was not my previous impression.
 
 Sergey, please test once more. If everything is okay, I'll start
 uploading the mach64 snapshots to the DRI website as well. (And put a
 README describing the current limitations of mach64)
 
 Regards,
 
 Jose Fonseca
 
 
 ___
 Dri-devel mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/dri-devel
 
I tested it and it works almost perfectly: the modprobe mach64 failed, not finding the 
module. A simple depmod -a did the work, dont know if it's specific to my config. 
Glxgears and Tuxracer run quite well, but I couldn't explore the possibilities, since 
my laptop was needed as a dvd player (thanks to Keith for the mach64 TV-out!)

It's quite easy to switch back to the old config (and get xv back...), but what are 
exactly the difficulties that you run into when trying to enable both 3D and 2D 
acceleration? (according to gatos, there's no problem with production dri drivers).


-- 
Bernard Cafarelli
alias Voyageur
ICQ:66024647



msg03473/pgp0.pgp
Description: PGP signature


Re: [Dri-devel] mach64 binaries: do work! Was: do not work...

2002-03-14 Thread Sergey V. Udaltsov

 The latest snapshot,
 
http://mefriss1.swan.ac.uk/~jfonseca/dri/packages/bleeding-edge/mach64-20020314-1601-i386-Linux.tar.bz2
 works. I've checked it myself.
I checked it too. No installation problems noticed. Everything went
smoothly. glxgears works on 248fps.

 The problem was libdrm.a which is not as device independent as thought.
:( Well, anyway it is not as big as libGL.
 It has some interface functions which in the case of mach64 are new and
 not available in the XFree86 4.x releases.
What's good is that now we know it - so next releases will be more
smooth.

 I also noticed that the snapshots of mach64-0-0-3-branch don't work on
 Xfree86 4.1.0, since the 2D driver ABI changed between the releases. I
 suppose it's the same for all driver snapshots taken from the trunk,
 althought that was not my previous impression.
What about compatibility with 4.0 (or even 3.3)? I guess for brave
testers like me even compatibility with 4.2 is enough...

 Sergey, please test once more. If everything is okay, I'll start
 uploading the mach64 snapshots to the DRI website as well. (And put a
 README describing the current limitations of mach64)
I'd say I have no objections:) It is very cool when someone asks me
permission to upload something (especially - something I did not
develop:)

Regards,

Sergey

___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] mach64 binaries: do work! Was: do not work...

2002-03-14 Thread José Fonseca

On 2002.03.14 20:30 Bernard Cafarelli wrote:
 Le 14 Mar 2002 17:07:47 +
 ...
 
 I tested it and it works almost perfectly: the modprobe mach64 failed,
 not finding the module. A simple depmod -a did the work, dont know if
 it's specific to my config.
 Glxgears and Tuxracer run quite well, but I couldn't explore the
 possibilities, since my laptop was needed as a dvd player (thanks to
 Keith for the mach64 TV-out!)
 
 It's quite easy to switch back to the old config (and get xv back...),
 but what are exactly the difficulties that you run into when trying to
 enable both 3D and 2D acceleration? (according to gatos, there's no
 problem with production dri drivers).
 
 

There is no special difficulty, just work to be done. In fact, on the 
current mach64 driver, work to do is its most outstanding feature!

So until the developers decide to that this is more important than 
enhancing the 3D backend, or some newbie decides to volunteer to do this 
job, it will remain work to be done for quite some time...

 --
   Bernard Cafarelli
   alias Voyageur
   ICQ:66024647

Regards,

José Fonseca

___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel