Re: [Dri-devel] Radeon 8500, XFree86 CVS vs DRI..

2002-09-20 Thread Michel Dänzer

On Don, 2002-09-19 at 17:49, Linus Torvalds wrote: 
 
 Gatos does fix real bugs, and I don't see why people are so down on it.  
 There seems to be some feeling among the XFree86 people that the Gatos
 people are rogue, just because they aren't as strict about checkin
 criteria as XFree86 is.
 
 But I suspect that exactly _because_ they aren't as strict, they sometimes 
 get more done. Certainly faster.
 
 ( Yes, the Gatos people do not share some of the same concerns the XFree86
   people do. I know XFree86 people must sometimes be frustrated with the
   fast-and-lose just get it working approach of some of the Gatos code,
   but I bet that the Gatos people are frustrated about the fact that
   sometimes the XFree86 people don't seem to care about some things
   _working_ at all.
 
   Stability of a code-base that doesn't do what people need it to do is
   simply not very relevant sometimes. )

I can only speak for myself, but it's my impression that the GATOS folks
don't really want to merge their stuff with XFree86 but are quite happy
to have their own project and draw people to it. A phenomenon that you
should be quite familiar with from my reading of Kernel Traffic. :)


-- 
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] Radeon 8500, XFree86 CVS vs DRI..

2002-09-19 Thread Sven LUTHER

On Wed, Sep 18, 2002 at 11:42:35PM -0700, Linus Torvalds wrote:
 
 Is there any reason why the DRI tree isn't tracking the XFree86 CVS tree
 more? On my Radeon 8500, the DRI tree apparently still doesn't do the Xv
 extension correctly, even though XFree86 CVS has done it for ages (thanks
 to Keith for getting the relevant bits off Gatos). So I have to have two
 different X servers, depending on whether I want to watch DVD's or whether
 I want to check 3D behaviour.
 
 (The XFree86 CVS tree also has that funky red-cursor-with-a-shadow thing, 
 which I've not yet decided if I like or dis-like ;)

Because, as i understand it, the developpment cycle of Xfree/DRI is as
follows :

  o XFree does a new release.
  o At this point DRI and Xfree are in sync, so DRI development is done
  in the DRI CVS, based on the lastly released XFree tree.
  o XFree developpment is done in the XFree CVS.
  o Sometimes near the end of the XFree development cycle, the two trees
  are synced by hand once the sync is done in a satisfactory way, 
  o XFree does a new release, and all begins again.

I think one of the reasons this is so is because the DRI tree is not
complete, and needs XFree to build and work correctly, and it is easier
for people building from DRI CVS to have the 4.2.0 tarball installed,
and build from that.

I guess people will try to merge usefull fixes from the XFree tree to
the DRI tree if they feel they need them or so, thus making things
easier for the folk doing the final sync.

Friendly,

Sven Luther


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] Radeon 8500, XFree86 CVS vs DRI..

2002-09-19 Thread Jens Owen

Sven LUTHER wrote:
 On Wed, Sep 18, 2002 at 11:42:35PM -0700, Linus Torvalds wrote:
 
Is there any reason why the DRI tree isn't tracking the XFree86 CVS tree
more?

Linus,

Think of the DRI trunk as a 3D development branch of XFree86.  For the 
8500, we've been focused on developing the 3D driver with full TCL 
support.  Other non-3D enhancements have been happening in the main 
branch (XFree86).  The 3D enhancements will be merged into the main 
development branch of XFree86 before 4.3 goes out.

On my Radeon 8500, the DRI tree apparently still doesn't do the Xv
extension correctly, even though XFree86 CVS has done it for ages (thanks
to Keith for getting the relevant bits off Gatos). So I have to have two
different X servers, depending on whether I want to watch DVD's or whether
I want to check 3D behaviour.

A word of caution about DRM compatability and Gatos.  I'm not certain 
how much of the Gatos functionality Keith P. has integrated into 
XFree86, but they have been releasing DRM drivers that are not backwards 
compatible with old XFree86 releases.

My understanding of the problem is the Gatos guys need a modified DRM 
memory map layout and have not been focused on the compatability issue. 
  I'm confident this issue could be resolved if someone interested (and 
capable) of understanding the Gatos modifications and the DRI backward 
compatability issues were to dig into this issue.  However, to date, 
nobody has successfully addressed this issue.

(The XFree86 CVS tree also has that funky red-cursor-with-a-shadow thing, 
which I've not yet decided if I like or dis-like ;)
 
 
 Because, as i understand it, the developpment cycle of Xfree/DRI is as
 follows :
 
   o XFree does a new release.
   o At this point DRI and Xfree are in sync, so DRI development is done
   in the DRI CVS, based on the lastly released XFree tree.
   o XFree developpment is done in the XFree CVS.
   o Sometimes near the end of the XFree development cycle, the two trees
   are synced by hand once the sync is done in a satisfactory way,

The syncing can and has actually happened more frequently than once per 
release.

   o XFree does a new release, and all begins again.
 
 I think one of the reasons this is so is because the DRI tree is not
 complete, and needs XFree to build and work correctly, and it is easier
 for people building from DRI CVS to have the 4.2.0 tarball installed,
 and build from that.
 
 I guess people will try to merge usefull fixes from the XFree tree to
 the DRI tree if they feel they need them or so, thus making things
 easier for the folk doing the final sync.
 
 Friendly,
 
 Sven Luther
 
 
 ---
 This sf.net email is sponsored by:ThinkGeek
 Welcome to geek heaven.
 http://thinkgeek.com/sf
 ___
 Dri-devel mailing list
 [EMAIL PROTECTED]
 https://lists.sourceforge.net/lists/listinfo/dri-devel
 
 



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



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] Radeon 8500, XFree86 CVS vs DRI..

2002-09-19 Thread Keith Packard


Around 9 o'clock on Sep 19, Jens Owen wrote:

 A word of caution about DRM compatability and Gatos.  I'm not certain 
 how much of the Gatos functionality Keith P. has integrated into 
 XFree86, but they have been releasing DRM drivers that are not backwards 
 compatible with old XFree86 releases.

I haven't really integrated any of the Gatos code into XFree86.  I worked 
with Kevin Martin to get all of the Radeon chips doing YUV overlays, but 
that took register settings from the Gatos code along with some additional 
fixes.  The Gatos project code supports significantly more video 
functionality, but remains somewhat limited in other dimensions, such as 
card support and video mode selection.

Kevin has also been busy integrating 2D code from ATI for the Radeon chips 
into the XFree86 tree.  That's certainly helping a lot of people; I can 
finally safely restart my X server.

The large number of different Radeon chips has made universal support 
for all features very difficult; few developers have access to all of the 
variations, especially the laptop versions.  My understanding is that ATI 
does make developer AGP boards with laptop chips; it seems like it might 
be useful to try and get some of those for the DRI developers to do a bit 
more testing.

The other dimension of variation is that we have three separate groups 
working on various ATI features; XFree86 does 2D graphics, Gatos does 
video and DRI does 3D graphics.  I don't see how we can expect each team 
to track the other two on an ongoing basis; merging source pools takes 
time away from other more interesting development.

 (The XFree86 CVS tree also has that funky red-cursor-with-a-shadow thing, 
 which I've not yet decided if I like or dis-like ;)

Yeah, it's a pretty lame effort at a consistent cursor theme.  I haven't 
every been known for my graphic artistry.  Of course, additional sample 
cursor themes would be really nice to have.

Keith PackardXFree86 Core TeamHP Cambridge Research Lab




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] Radeon 8500, XFree86 CVS vs DRI..

2002-09-19 Thread Adam K Kirchhoff


On Thu, 19 Sep 2002, Linus Torvalds wrote:

 ( Yes, the Gatos people do not share some of the same concerns the XFree86
   people do. I know XFree86 people must sometimes be frustrated with the
   fast-and-lose just get it working approach of some of the Gatos code,
   but I bet that the Gatos people are frustrated about the fact that
   sometimes the XFree86 people don't seem to care about some things
   _working_ at all.
 
   Stability of a code-base that doesn't do what people need it to do is
   simply not very relevant sometimes. )

I feel that I should point out that functionality of a code-base that 
isn't stable is simply not very relevant sometimes, too. :-)

Adam



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel