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
Title: AW: [Dri-devel] matrox parhelia vs. opensource?
A'rpi,
besides from the open/closed source issue, what are your experiences with the closed source driver in regard to 3d.
Johannes
-Ursprüngliche Nachricht-
Von: Arpi [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 18.
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
Hi,
besides from the open/closed source issue, what are your experiences with
the closed source driver in regard to 3d.
I have no such card - so i have no experiences at all.
Anyway, there is no 3D support in the closed source driver, according
to their release notes. It only provides 2d
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
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
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
Hi,
What is the preferred debugging method used for debugging loadable
DRM kernel modules?
Has anyone successfully used kgdb for debugging their driver? Any
insight into this
would be appreciated.
Please CC me as I'm not subscribed to the list yet.
Thanks,
--
Bhavana Nagendra
Bhavana Nagendra wrote:
Hi,
What is the preferred debugging method used for debugging loadable
DRM kernel modules?
Has anyone successfully used kgdb for debugging their driver? Any
insight into this
would be appreciated.
I believe kprintf is the usual method.
Please CC me as I'm not
