On Llu, 2003-07-07 at 07:44, Linus Torvalds wrote:
I'm pretty sure that the futex code is backported at least into the redhat
tree, since the new threading code really really wants it. But yes, it may
not be in any official 2.4.x kernels, and I suspect it's only in the
most recent RH trees
Ian Romanick wrote:
Ian Romanick wrote:
Linus Torvalds wrote:
You _really_ want to use futex'es for any user-space locking. It's
back-ported to 2.4.x, and it gets these cases _right_. There are fair
user-space locks based on futexes as part of modern glibc sources, and
they are _fast_, since all
[ CONFIG_DRM_SIS needs CONFIG_FB_SIS to compile, of course. --RR ]
(OK from maintainer Rik Faith [EMAIL PROTECTED])
From: Geoffrey Lee [EMAIL PROTECTED]
Yep. Take one was pretty silly.
Here's a better one.
-- G.
--
char p[] =
[This e-mail has been automatically generated.]
You have one or more bugs assigned to you in the Bugzilla
bugsystem (http://bugs.xfree86.org/) that require
attention.
All of these bugs are in the NEW state, and have not been touched
in 7 days or more. You need to take a look at
On Llu, 2003-07-07 at 06:41, Rusty Trivial Russell wrote:
[ CONFIG_DRM_SIS needs CONFIG_FB_SIS to compile, of course. --RR ]
(OK from maintainer Rik Faith [EMAIL PROTECTED])
From: Geoffrey Lee [EMAIL PROTECTED]
And the 2.4 config tools cant handle this because of the order problems.
Marcelo
On Mon, 2003-07-07 at 08:12, Ian Romanick wrote:
The one catch that I see is that I don't see support for the futex ioctl
in any 2.4 kernel. I did a 'grep -ri futex include/' in the source for
2.4.21-ac2 and for 2.5.69. The 2.4 kernel didn't have any hits, but the
2.5 kernel did. Of
--- Additional Comments From [EMAIL PROTECTED] 2003-07-06 18:33 ---
Hi Christopher,
The problem isn't that 3D isn't supported by DRI, but rather that the Linux
kernel does not yet support agpgart on Radeon IGP chipsets, and without working
agpgart, you have no DRI. Theoretically
Ronald Baljeu wrote:
On Mon, Jul 07, 2003 at 09:59:15AM +0100, Keith Whitwell wrote:
Ronald Baljeu wrote:
The traditional approach would be to do a binary search to narrow down
which change caused the problems -- probably using the DRI cvs tree.
Keith
Ok, after several days of searching I
[This e-mail has been automatically generated.]
Please do not reply to this email. if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugs.xfree86.org//cgi-bin/bugzilla/show_bug.cgi?id=44
--- Additional Comments From [EMAIL
This is just a friendly reminder that the weekly dri-devel IRC meeting will
be starting in the #dri-devel channel on irc.freenode.net at 2100 UTC (or
5:00PM EDT or 2:00PM PDT, if you prefer).
Time zone conversion available at:
http://www.timezoneconverter.com/cgi-bin/tzc.tzc
Logs of previous
Am 2003.07.06 06:03:54 +0200 schrieb(en) Ian Romanick:
Andreas Stenglein wrote:
how to enable Mesa Verbose Debugging in the DRI-tree?
http://mesa3d.org/debugging.html didnt help much
It depends on the driver. Most of the drivers have an environment
variable that's *_DEBUG (i.e., for
[This e-mail has been automatically generated.]
Please do not reply to this email. if you want to comment on the bug, go to the
URL shown below and enter your comments there.
http://bugs.xfree86.org//cgi-bin/bugzilla/show_bug.cgi?id=44
--- Additional Comments From [EMAIL
On Mon, 7 Jul 2003, Alan Cox wrote:
On Llu, 2003-07-07 at 06:41, Rusty Trivial Russell wrote:
[ CONFIG_DRM_SIS needs CONFIG_FB_SIS to compile, of course. --RR ]
(OK from maintainer Rik Faith [EMAIL PROTECTED])
From: Geoffrey Lee [EMAIL PROTECTED]
And the 2.4 config tools cant handle
Ian Romanick wrote:
The real difference comes at the unlock. When a thread wants to release
the futex, it increments the variable. If the value is greater than
zero, the thread happily continues on. If the value is zero or
negative, the thread calls into the kernel to wake-up the next waiting
He looks to have something here, alright.. the key can be zero, I'm just
updating to trunk at the moment to see if I can reproduce it..
the radeon_dri.c has a similiar issue but it isn't as serious in their
case, they check for freeing the AGP memory if (info-agpMemHandle) they
use the return
and of course
d) revert back to using memory-memory, requires whoever switched us to
key to explain :-)
Okay this was done by David Dawes back in April, and was taken from the
XFree trunk, it looks like it is needed. so one of the other three
approaches is needed...
Dave.
16 matches
Mail list logo
