--- Fernando Pablo Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
> On Mon, 2004-08-23 at 11:43, Fernando Pablo Lopez-Lezcano wrote:
> > On Mon, 2004-08-23 at 11:30, Ingo Molnar wrote:
> > > i'll put the patch below into the -P8 patch. (change
> voluntary_resched()
> > > to cond_resched() if you apply t
On Mon, 2004-08-23 at 11:30, Ingo Molnar wrote:
> i'll put the patch below into the -P8 patch. (change voluntary_resched()
> to cond_resched() if you apply this to a vanilla kernel.)
I'll start a kernel build to test this on top of P7... (I was about to
ask "what about the other places in radeon_c
On Mon, 2004-08-23 at 11:43, Fernando Pablo Lopez-Lezcano wrote:
> On Mon, 2004-08-23 at 11:30, Ingo Molnar wrote:
> > i'll put the patch below into the -P8 patch. (change voluntary_resched()
> > to cond_resched() if you apply this to a vanilla kernel.)
>
> I'll start a kernel build to test this o
On Sun, 2004-08-22 at 22:09, Mike Mestnik wrote:
> --- Jon Smirl <[EMAIL PROTECTED]> wrote:
>
> > Michel pointed out that all IOCTL calls hold the big kernel lock.
> > Releasing this lock is sure to case problems since the DRM code is not
> > designed to be reentrant. I don't know what it will tak
> Last two weeks are there :
> http://icps.u-strasbg.fr/~marchesin/perso/20040816.txt
> http://icps.u-strasbg.fr/~marchesin/perso/20040823.txt
>
> Please, soemone put these logs with the others, that's a very interesting read
> when you're a beginner (and I mean it : I found lots of valuable infor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 24 August 2004 18:01, Ronny V. Vindenes wrote:
> tir, 24,.08.2004 kl. 13.40 -0700, skrev Ian Romanick:
> > Ronny V. Vindenes wrote:
> > Of course, once we get to that point, I think we should get the existing
> > TCL paths and run everything
tir, 24,.08.2004 kl. 13.40 -0700, skrev Ian Romanick:
> Ronny V. Vindenes wrote:
>
> > tir, 24,.08.2004 kl. 16.08 +0100, skrev Keith Whitwell:
> >
> >>Has anyone had a chance to try out Philipp's changes? I haven't & don't want
> >>to break the driver by commiting them without a little testing
Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://freedesktop.org/bugzilla/show_bug.cgi?id=1003
--- Additional Comments From [EMAIL PROTECTED] 2004-08-24 14:18 ---
Andreas, th
Ronny V. Vindenes wrote:
tir, 24,.08.2004 kl. 16.08 +0100, skrev Keith Whitwell:
Has anyone had a chance to try out Philipp's changes? I haven't & don't want
to break the driver by commiting them without a little testing of my own.
I haven't tested it yet either, but it struck me that if we're go
Ronny V. Vindenes schrieb:
I haven't tested it yet either, but it struck me that if we're going to
add support for "non-essential" software-only extensions then we
probably should add a driconf option to enable/disable such extensions
since their existence can affect which code paths clients take?
tir, 24,.08.2004 kl. 16.08 +0100, skrev Keith Whitwell:
> Philipp Klaus Krause wrote:
> > Some time ago I sent patches that enable vertex program support
> > in the r200 driver (software only though) to this list.
> > Now I wonder if they will be integrated into the driver and how this
> > process
Alex Deucher wrote:
On 23 Aug 2004 18:30:01 -, Ian Romanick <[EMAIL PROTECTED]> wrote:
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 conver
Philipp Klaus Krause wrote:
Some time ago I sent patches that enable vertex program support
in the r200 driver (software only though) to this list.
Now I wonder if they will be integrated into the driver and how this
process works. Do the driver maintainers read this list, lok at the
patches and de
Some time ago I sent patches that enable vertex program support
in the r200 driver (software only though) to this list.
Now I wonder if they will be integrated into the driver and how this
process works. Do the driver maintainers read this list, lok at the
patches and decide what they integrate? Wi
On 23 Aug 2004 18:30:01 -, Ian Romanick <[EMAIL PROTECTED]> wrote:
>
> 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 a
On Mon, 23 Aug 2004 15:38:33 +0200
May THO <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I made a small patch to port Linux DRM module to FreeBSD. I'm wondering nobody
> has made it before...
Apparently you are the first one to try the Savage driver on BSD. :)
Thanks for your interest in the Savage dri
> On Mon, 2004-08-23 at 22:58, Thomas Hellström wrote:
>> Hi!
>>
>> Mike Mestnik wrote:
>> > --- Eric Anholt <[EMAIL PROTECTED]> wrote:
>> >
>> >
>> > > On Mon, 2004-08-23 at 15:24, Ian Romanick wrote:
>> > >
>> > > > Thomas Hellström wrote:
>> > > >
>> > > >
>> > > > > As some of you might have re
Okay I've merged back the drmfntbl-0-0-2 branch back to the DRM trunk,
this gets rid of the REALLY_HAVE_AGP, HAVE_AGP, REALLY_HAVE_MTRR,
HAVE_MTRR, HAVE_DMA, HAVE_IRQ, HAVE_CTX_BITMAP, HAVE_VBL_IRQ, HAVE_SG,
HAVE_PCI_DMA, HAVE_DMA_WAITQUEUE, HAVE_DMA_RECLAIM, MUST_HAVE_AGP,
HAVE_DMA_QUEUE, HAVE_
Dave Airlie wrote:
Previously all of the IOCTL calls were protected by the Big Kernel
Lock. If we break that aren't we allowing multiple callers into the
IOCTL code on SMP machines that weren't allowed in before? Doesn't
that mean that we have to check everything to make sure it is SMP
safe?
as Ala
John Lightsey schrieb:
I gave up on specviewperf after waiting over half an hour for the Voodoo 5 to
run it. It's just too time consuming. Are there one or two tests that stand
out in particular?
I'd propose 3dsmax-02, ugs-03 and proe-02 since in the Radeon driver
comparison done by Ronald Sc
20 matches
Mail list logo
