On 2002.04.21 21:13 Leif Delgass wrote:
> On Sun, 21 Apr 2002, Leif Delgass wrote:
> > ...
> >
> > Yes, I think waiting for idle here is overkill. According to the
> > programmer's guide, you only need to wait for idle when reading a
> register
> > or bit field updated by the draw engine, or when
I'm looking at getting PCI card support for FreeBSD, and I have some
questions about the DRM's memory use and what it expects. Does any of
the code (in the entire DRM) rely on memory being physically
contiguous? Does __get_free_pages return pages that will be physically
contiguous? Why aren't v
On Sun, 21 Apr 2002, José Fonseca wrote:
> On 2002.04.21 19:40 Leif Delgass wrote:
> > On Sun, 21 Apr 2002, José Fonseca wrote:
> >
> > > > We just need to add the fifo check now.
> > >
> > > I've just add it but it makes gears drop from 222 to 185 fps in my
> > system.
> > > I don't know if thi
Ian,
> I filed a bug report with all the text from the message. The bug is #546281.
>
>
>http://sourceforge.net/tracker/index.php?func=detail&aid=546281&group_id=387&atid=100387
I commented on this bug now, you can download the log from FlightGear
from the url I supplied.
Good luck...
An
On 2002.04.21 19:40 Leif Delgass wrote:
> On Sun, 21 Apr 2002, José Fonseca wrote:
>
> > > We just need to add the fifo check now.
> >
> > I've just add it but it makes gears drop from 222 to 185 fps in my
> system.
> > I don't know if this is caused by droped triangles when there is no
> FIFO
>
On Sun, 2002-04-21 at 20:34, José Fonseca wrote:
> I just found a typo in radeon_accel.c:456. Instead of
>
> #if defined(XF86_DRI)
>
> it should be
>
> #if defined(XF86DRI)
>
> This is rather harmless, it seems to affect PowerPC architectures only,
> and should most probably result in a compi
On Sun, 21 Apr 2002, José Fonseca wrote:
> > We just need to add the fifo check now.
>
> I've just add it but it makes gears drop from 222 to 185 fps in my system.
> I don't know if this is caused by droped triangles when there is no FIFO
> check, or if the FIFO check makes a big overload. So
I just found a typo in radeon_accel.c:456. Instead of
#if defined(XF86_DRI)
it should be
#if defined(XF86DRI)
This is rather harmless, it seems to affect PowerPC architectures only,
and should most probably result in a compile error in that case.
José Fonseca
___
On 2002.04.21 17:43 Felix Kühling wrote:
> Yeah, I thought about that, too. But it is always hard to know how much
> time you need for your test. And in the end it might be faster to reboot
> the machine :). Thanks, anyway.
Take a look to /usr/src/linux-2.4/Documentation/sysrq.txt. I believe that
On 2002.04.21 17:41 Felix Kühling wrote:
> On Sun, 21 Apr 2002 09:36:35 +0100
> José Fonseca <[EMAIL PROTECTED]> wrote:
> > ...
>
> I had a look at the radeon and r128 drivers. They both don't lock when
> switching the mode. But in LeaveVT and EnterVT they do
> RADEONCP_STOP/R128CCE_STOP after DR
On Sun, 21 Apr 2002 09:36:35 +0100
José Fonseca <[EMAIL PROTECTED]> wrote:
> > Ok, I checked aticonsole.c. The existing locks seem to be in the right
> > places. If I understand the problem correctly I will have to make sure
> > that the hardware is in 2d state when the X-server has the lock. Thi
On 2002.04.21 07:56 Leif Delgass wrote:
> Well, I knocked one item off the list. I implemented sequential
> multi-register writes in the primitive functions. Seems to help my
> framerate a bit even with pseudo-DMA. I changed the primitive functions
> to supply the register addresses as the memo
On 2002.04.21 03:35 Robert Lunnon wrote:
> On Wednesday 17 April 2002 09:46, José Fonseca wrote:
> > ...
> >
> > As the thread proceeded it become clear that there wasn't really a
> > interest in a long-term solution for 3D graphics on Solaris, and (after
> > reading the Utah-GLX archives) I also
On 2002.04.21 02:31 Felix Kühling wrote:
> ...
>
> OK, I checked the mach64-0-0-4-branch out tonight and compiled it. It
> runs surprisingly usable. The only big difference to mach64-0-0-3 which I
> noticed is that all the CPU load is in the kernel now :)
>
Good. I guess that I can start making
Warning
Unable to process data:
multipart/mixed;boundary="=_NextPart_000_00C8_76A68E6B.E1300C11"
15 matches
Mail list logo
