Sven Luther wrote:
On Thu, Dec 12, 2002 at 07:14:45PM -0800, Philip Brown wrote:
On Thu, Dec 12, 2002 at 01:02:30PM +, Alan Cox wrote:
...
It takes two to tango so its not just what I need its also what do they
need.
What I would like to see would be:
A single definitive source for the
On Fri, Dec 13, 2002 at 10:18:44AM +, Keith Whitwell wrote:
...
It's clear that both the drm and the 3d clientside drivers have a life outside
XFree86, but what isn't clear is how to express this in a reasonable
development environment or set of CVS trees.
Well, lets work on making
On Thu, 12 Dec 2002, Alan Hourihane wrote:
On Thu, Dec 12, 2002 at 02:50:39PM +0100, Dieter Nützel wrote:
Some apps only run smooth with 2.5.49+ kernels due to Linus latest work.
Nothing of it in XFree or DRI, yet.
Linus should submit it here for inclusion - simple. I doubt any of us
On Wed, 2002-12-11 at 22:11, D. Hageman wrote:
Alan,
What would you like to see be implemented to help get the job done. In
other words, what do you need from the DRI team?
It takes two to tango so its not just what I need its also what do they
need.
What I would like to see would be:
On Thu, Dec 12, 2002 at 01:02:30PM +, Alan Cox wrote:
On Wed, 2002-12-11 at 22:11, D. Hageman wrote:
Alan,
What would you like to see be implemented to help get the job done. In
other words, what do you need from the DRI team?
It takes two to tango so its not just what I need
Alan Cox wrote:
On Wed, 2002-12-11 at 22:11, D. Hageman wrote:
Alan,
What would you like to see be implemented to help get the job done. In
other words, what do you need from the DRI team?
It takes two to tango so its not just what I need its also what do they
need.
What I would like to
On Thu, Dec 12, 2002 at 12:53:46PM +, Keith Whitwell wrote:
Alan Hourihane wrote:
On Thu, Dec 12, 2002 at 01:02:30PM +, Alan Cox wrote:
On Wed, 2002-12-11 at 22:11, D. Hageman wrote:
Alan,
What would you like to see be implemented to help get the job done. In
other words,
Alan Hourihane wrote:
On Thu, Dec 12, 2002 at 01:02:30PM +, Alan Cox wrote:
On Wed, 2002-12-11 at 22:11, D. Hageman wrote:
Alan,
What would you like to see be implemented to help get the job done. In
other words, what do you need from the DRI team?
It takes two to tango so its not
Am Donnerstag, 12. Dezember 2002 13:58 schrieb Alan Hourihane:
On Thu, Dec 12, 2002 at 12:53:46PM +, Keith Whitwell wrote:
Alan Hourihane wrote:
On Thu, Dec 12, 2002 at 01:02:30PM +, Alan Cox wrote:
On Wed, 2002-12-11 at 22:11, D. Hageman wrote:
Alan,
What would you like to
Sorry, but I think this is much to slow/few.
Look at the current kernel (drm) source.
There are daily changes/fixes and we should use the latest XFree (DRI)
DRM? Currently I'm under the impression that nobody (only a few) of the
XFree/DRI developers pay attention about SMP and/or latency where
On Thu, Dec 12, 2002 at 02:50:39PM +0100, Dieter Nützel wrote:
Am Donnerstag, 12. Dezember 2002 13:58 schrieb Alan Hourihane:
On Thu, Dec 12, 2002 at 12:53:46PM +, Keith Whitwell wrote:
Alan Hourihane wrote:
On Thu, Dec 12, 2002 at 01:02:30PM +, Alan Cox wrote:
On Wed,
On Don, 2002-12-12 at 14:50, Dieter Nützel wrote:
Look at the current kernel (drm) source.
There are daily changes/fixes and we should use the latest XFree (DRI)
DRM? Currently I'm under the impression that nobody (only a few) of the
XFree/DRI developers pay attention about SMP and/or
On Thu, Dec 12, 2002 at 12:49:37PM +, Keith Whitwell wrote:
It seems that changes get inserted to the drm code in the kernel from time to
time. Is the expectation that we monitor the kernel drm and periodically
merge (or otherwise) those random or worthy changes back to this
On Thu, Dec 12, 2002 at 02:09:18PM +, Alan Hourihane wrote:
Some apps only run smooth with 2.5.49+ kernels due to Linus latest work.
Nothing of it in XFree or DRI, yet.
Linus should submit it here for inclusion - simple. I doubt any of us
are tracking 2.5.x that closely at the
Dave Jones wrote:
On Thu, Dec 12, 2002 at 02:09:18PM +, Alan Hourihane wrote:
Some apps only run smooth with 2.5.49+ kernels due to Linus latest work.
Nothing of it in XFree or DRI, yet.
Linus should submit it here for inclusion - simple. I doubt any of us
are tracking 2.5.x that
Am Donnerstag, 12. Dezember 2002 15:09 schrieb Alan Hourihane:
On Thu, Dec 12, 2002 at 02:50:39PM +0100, Dieter Nützel wrote:
Latest trunk with 2.4.20 kernel DRM or the DRI DRM module stutters like
hell for some apps on my SMP system.
Forget the DRI trunk for a second, what does 2.4.20 do
On Thu, 12 Dec 2002, Keith Whitwell wrote:
Right now for 2.4 I'm juggling too many conflicting balls, if its all in
the DRM CVS then merging stuff added to DRM cvs is a real nobrainer, and
since I can do it item by item as it changes its also easy to know when
something bad happens.
I've
Dave Jones wrote:
On Thu, Dec 12, 2002 at 12:49:37PM +, Keith Whitwell wrote:
It seems that changes get inserted to the drm code in the kernel from time to
time. Is the expectation that we monitor the kernel drm and periodically
merge (or otherwise) those random or worthy changes
Dave Jones wrote:
On Thu, Dec 12, 2002 at 12:49:37PM +, Keith Whitwell wrote:
It seems that changes get inserted to the drm code in the kernel from time to
time. Is the expectation that we monitor the kernel drm and periodically
merge (or otherwise) those random or worthy changes
On Thu, 12 Dec 2002, Alan Hourihane wrote:
On Thu, Dec 12, 2002 at 01:02:30PM +, Alan Cox wrote:
On Wed, 2002-12-11 at 22:11, D. Hageman wrote:
Alan,
What would you like to see be implemented to help get the job done. In
other words, what do you need from the DRI team?
On Thu, Dec 12, 2002 at 01:02:30PM +, Alan Cox wrote:
...
It takes two to tango so its not just what I need its also what do they
need.
What I would like to see would be:
A single definitive source for the DRM code, one where contributions go
back from Linux, from *BSD, from core
On Thu, Dec 12, 2002 at 11:11:13AM -0600, D. Hageman wrote:
On Thu, 12 Dec 2002, Alan Hourihane wrote:
For 'stable DRM' you need to stick with XFree86 4.2.0 and the DRM modules
that ship with 4.2.0. For 'DRM of the day' use the DRI trunk.
I admit that your logic is sound, but answer me
On Thu, 2002-12-12 at 12:40, Alan Hourihane wrote:
The ability to track changes to that with reasons so that we can keep a
stable DRM and also the 'DRM of the day' visible to the kernel people -
perhaps the devel kernel tree having an option for Development DRM
(XFree86 4.4) (Y/M/N).
On 12 Dec 2002, Alan Cox wrote:
Date: 12 Dec 2002 18:22:10 +
From: Alan Cox [EMAIL PROTECTED]
To: Alan Hourihane [EMAIL PROTECTED]
Cc: D. Hageman [EMAIL PROTECTED], [EMAIL PROTECTED]
Content-Type: text/plain
List-Id: dri-devel.lists.sourceforge.net
Subject: Re: [Dri-devel] DRM Kernel
On Thu, 2002-12-12 at 12:49, Keith Whitwell wrote:
A single definitive source for the DRM code, one where contributions go
back from Linux, from *BSD, from core XFree86 as well as from the DRI
project.
My feeling is that the dri cvs should be that place. What workable
alternatives
On Thu, 12 Dec 2002, Alan Hourihane wrote:
The ability to track changes to that with reasons so that we can keep a
stable DRM and also the 'DRM of the day' visible to the kernel people -
perhaps the devel kernel tree having an option for Development DRM
(XFree86 4.4) (Y/M/N).
On Thu, 12 Dec 2002, Mike A. Harris wrote:
On Thu, 12 Dec 2002, Alan Hourihane wrote:
The ability to track changes to that with reasons so that we can keep a
stable DRM and also the 'DRM of the day' visible to the kernel people -
perhaps the devel kernel tree having an option for
On Thu, Dec 12, 2002 at 07:14:45PM -0800, Philip Brown wrote:
On Thu, Dec 12, 2002 at 01:02:30PM +, Alan Cox wrote:
...
It takes two to tango so its not just what I need its also what do they
need.
What I would like to see would be:
A single definitive source for the DRM code,
Alan,
What would you like to see be implemented to help get the job done. In
other words, what do you need from the DRI team?
On Wed, 11 Dec 2002, Alan Cox wrote:
On Wed, 2002-12-11 at 20:12, D. Hageman wrote:
I have noticed some feedback from Alan and Linus already on this list. Is
29 matches
Mail list logo
