Re: [Dri-devel] Questions about current status of DRI

2004-04-18 Thread Michel Dänzer
On Sun, 2004-04-18 at 04:55, Vladimir Dergachev wrote:
 On Sun, 18 Apr 2004, Michel [ISO-8859-1] Dnzer wrote:
 
  On Sun, 2004-04-18 at 03:19, Vladimir Dergachev wrote:
  
 3. Can anyone tell me what changes are required in order to enable
idle DRI for R300 and above ? (I.e. DRM module starts up, 2d
commands go through DRM , but Mesa driver does software rendering).
 
  The infamous CP microcode is needed. AFAIK, Benjamin Herrenschmidt got
  it from ATI.
 
 I might have it too, though one can never tell whether it works without
 experiment (i.e. it might just be a copy of R200 microcode).

No, at least the 3D parts obviously have to be different, and IIRC Adam
Kirchhoff tried the R200 microcode without success even for just 2D.


I might have some success in figuring out CP sequences and present the
result as a user-space library, but I doubt I will have time to dig
inside Mesa.
 
  We have the docs, no need to guess... note that unprivileged user space
  processes can't emit CP commands directly but can only use higher level
  ioctls geared towards the 3D driver. May I ask what goal you are trying
  to achieve?
 
 Well, I wanted to make an example app that exercises as many 3d related
 capability as possible. With the hope that once this is published people
 with more knowledge of Mesa internals would be tempted to make a real
 driver.

Ah. :) Disregard my comment above about CP docs then, I thought you were
talking about R[12]00...

 Also, it is possible to access CP fifo via MMIO registers - if I remember
 this right.

Yes.


 5. I remember there was someone working to merge current GATOS code into
DRI - did these changes made it into DRI CVS ?
 
  The GATOS DRM doesn't have anything that needs merging, does it? For the
  other code, the DRI tree isn't the right target IMHO.
 
 No, I meant the code that makes TV-in work. I was incredibly busy this
 year and did not have time to start porting to 4.4.0 codebase.

You may want to discuss this with the X.Org foundation folks.


-- 
Earthling Michel Dnzer  | Debian (powerpc), X and DRI developer
Libre software enthusiast|   http://svcs.affero.net/rm.php?r=daenzer



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


[Dri-devel] Questions about current status of DRI

2004-04-17 Thread Vladimir Dergachev

Hi guys, I've been busy for a while, but summer is approaching with the
possibility of some spare time, so I have several questions about current
status of DRI:

  1. I could not find a link to the newer ViewCVS interface on the website
- does it exist ?

  2. Is anyone working on accelerated 3d for newer Radeons (R300, etc) ?

  3. Can anyone tell me what changes are required in order to enable
 idle DRI for R300 and above ? (I.e. DRM module starts up, 2d
 commands go through DRM , but Mesa driver does software rendering).

 This is a question about DRI architecture, not hardware. I.e. if
 part of this functionality involves hardware that's changed in R300
 it also falls in idle category.

  4. Are there any examples of user-space applications accessing DRM, the
 same way Mesa driver does, but (hopefully) simpler ? I might have
 some success in figuring out CP sequences and present the result as a
 user-space library, but I doubt I will have time to dig inside Mesa.

  5. I remember there was someone working to merge current GATOS code into
 DRI - did these changes made it into DRI CVS ?

thank you very much !

  Vladimir Dergachev


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [Dri-devel] Questions about current status of DRI

2004-04-17 Thread Michel Dänzer
On Sun, 2004-04-18 at 03:19, Vladimir Dergachev wrote:
 
   1. I could not find a link to the newer ViewCVS interface on the website
 - does it exist ?

http://dri.freedesktop.org/cgi-bin/cvsweb/dri/


   2. Is anyone working on accelerated 3d for newer Radeons (R300, etc) ?

Not that I know of.


   3. Can anyone tell me what changes are required in order to enable
  idle DRI for R300 and above ? (I.e. DRM module starts up, 2d
  commands go through DRM , but Mesa driver does software rendering).

The infamous CP microcode is needed. AFAIK, Benjamin Herrenschmidt got
it from ATI.


   4. Are there any examples of user-space applications accessing DRM, the
  same way Mesa driver does, but (hopefully) simpler ? 

I don't know of any.

  I might have some success in figuring out CP sequences and present the 
  result as a user-space library, but I doubt I will have time to dig 
  inside Mesa.

We have the docs, no need to guess... note that unprivileged user space
processes can't emit CP commands directly but can only use higher level
ioctls geared towards the 3D driver. May I ask what goal you are trying
to achieve?


   5. I remember there was someone working to merge current GATOS code into
  DRI - did these changes made it into DRI CVS ?

The GATOS DRM doesn't have anything that needs merging, does it? For the
other code, the DRI tree isn't the right target IMHO.


-- 
Earthling Michel Dnzer  | Debian (powerpc), X and DRI developer
Libre software enthusiast|   http://svcs.affero.net/rm.php?r=daenzer



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [Dri-devel] Questions about current status of DRI

2004-04-17 Thread ajax
On Saturday 17 April 2004 20:19, Vladimir Dergachev wrote:

   4. Are there any examples of user-space applications accessing DRM, the
  same way Mesa driver does, but (hopefully) simpler ? I might have
  some success in figuring out CP sequences and present the result as a
  user-space library, but I doubt I will have time to dig inside Mesa.

tests/drmstat.c in the drm/ module perhaps?

(It strikes me that those won't build at all right now since they've been 
moved...)

- ajax


---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [Dri-devel] Questions about current status of DRI

2004-04-17 Thread Vladimir Dergachev


On Sun, 18 Apr 2004, Michel [ISO-8859-1] Dnzer wrote:

 On Sun, 2004-04-18 at 03:19, Vladimir Dergachev wrote:
 
1. I could not find a link to the newer ViewCVS interface on the website
  - does it exist ?

 http://dri.freedesktop.org/cgi-bin/cvsweb/dri/


Thank you !



3. Can anyone tell me what changes are required in order to enable
   idle DRI for R300 and above ? (I.e. DRM module starts up, 2d
   commands go through DRM , but Mesa driver does software rendering).

 The infamous CP microcode is needed. AFAIK, Benjamin Herrenschmidt got
 it from ATI.


I might have it too, though one can never tell whether it works without
experiment (i.e. it might just be a copy of R200 microcode).


   I might have some success in figuring out CP sequences and present the
   result as a user-space library, but I doubt I will have time to dig
   inside Mesa.

 We have the docs, no need to guess... note that unprivileged user space
 processes can't emit CP commands directly but can only use higher level
 ioctls geared towards the 3D driver. May I ask what goal you are trying
 to achieve?

Well, I wanted to make an example app that exercises as many 3d related
capability as possible. With the hope that once this is published people
with more knowledge of Mesa internals would be tempted to make a real
driver.

Also, it is possible to access CP fifo via MMIO registers - if I remember
this right. That was going to be my second choice, with the preference of
connecting to DRM module directly.



5. I remember there was someone working to merge current GATOS code into
   DRI - did these changes made it into DRI CVS ?

 The GATOS DRM doesn't have anything that needs merging, does it? For the
 other code, the DRI tree isn't the right target IMHO.

No, I meant the code that makes TV-in work. I was incredibly busy this
year and did not have time to start porting to 4.4.0 codebase.

 best

Vladimir Dergachev



 --
 Earthling Michel Dnzer  | Debian (powerpc), X and DRI developer
 Libre software enthusiast|   http://svcs.affero.net/rm.php?r=daenzer



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70alloc_id638op=click
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [Dri-devel] Questions about current status of DRI

2004-04-17 Thread Dave Airlie

 The infamous CP microcode is needed. AFAIK, Benjamin Herrenschmidt got
 it from ATI.

the BeOS driver has some r300 microcode in its sources...
http://www.bebits.com/appver/2938
download the r5 source at look at CPMicroCode.h in the file...

no idea what it is of course it might be 2d only or something wierd..

Dave.

-- 
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
pam_smb / Linux DECstation / Linux VAX / ILUG person



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [Dri-devel] Questions about current status of DRI

2004-04-17 Thread Vladimir Dergachev


On Sun, 18 Apr 2004, Dave Airlie wrote:


  The infamous CP microcode is needed. AFAIK, Benjamin Herrenschmidt got
  it from ATI.

 the BeOS driver has some r300 microcode in its sources...
 http://www.bebits.com/appver/2938
 download the r5 source at look at CPMicroCode.h in the file...

 no idea what it is of course it might be 2d only or something wierd..

Yep, it matches the code I see in the DDK. So it appears that the only
thing left to get 3d working is to find/verify packets for CP engine.

 best

Vladimir Dergachev


 Dave.

 --
 David Airlie, Software Engineer
 http://www.skynet.ie/~airlied / airlied at skynet.ie
 pam_smb / Linux DECstation / Linux VAX / ILUG person



 ---
 This SF.Net email is sponsored by: IBM Linux Tutorials
 Free Linux tutorial presented by Daniel Robbins, President and CEO of
 GenToo technologies. Learn everything from fundamentals to system
 administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
 --
 ___
 Dri-devel mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/dri-devel



---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
--
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel