On Fri, 26 Oct 2001, Manuel Teira wrote:
> I have been looking to the register caching. I don't know if this caching has
> sense once the DRI is also writing directly to some of the registers. I saw
> seldom times this in my XFree log file:
> .. $REGISTER_NAME write cache disabled!
I've notice
El Vie 26 Oct 2001 20:21, Leif Delgass escribió:
> I haven't done an extensive look at this, but I've noticed a couple of
> things. The 2D driver seems to use a caching scheme for register writes.
> Also, at one point I had a nasty lockup trying to switch to a vt from
> fullscreen quake, but I ha
I haven't done an extensive look at this, but I've noticed a couple of
things. The 2D driver seems to use a caching scheme for register writes.
Also, at one point I had a nasty lockup trying to switch to a vt from
fullscreen quake, but I haven't tried it with my latest build yet. I've
noticed
Hello.
I was investigating on how to allow both 2D and 3D acceleration in the
Mach64. So I'm a little confused:
First of all, I looked at the R128 and RADEON drivers and they are only doing
a DRILock/DRIUnlock in the LeaveVT and EnterVT functions. Does this mean that
those cards can do 3D and
El Mié 17 Oct 2001 11:44, R C escribió:
> On Sat, Oct 13, 2001 at 10:08:50PM +0200, Manuel Teira wrote:
>
> Regarding theories on DMA and Mach64 and XFree 4.10:
>
> I just finished a module that uses the System DMA unit for video capture
> transfers, and it works fine under a (highly hacked) XFree
On Wed, 17 Oct 2001 [EMAIL PROTECTED] wrote:
> Thanks for your comments, guys. In three or four hours (if no new 'browns')
> we'll have the answer. It would be nice if this were the only problem. ;-)
> Anyway, I think it won't be the problem, because nobody have had success
> with the Mach64 Bus
Mike Westall writes:
> I spent an incredibly frustrating 4 weeks trying to
> get the DRI to work with r128 and g400 cards on Dell
> precision workstation only to find that my problem
> was precisely because bus mastering was NOT enabled
> on boot! As soon as I fixed that everything worked
> fin
On Wed, Oct 17, 2001 at 11:45:39AM +, [EMAIL PROTECTED] wrote:
> Thank you very much. I'll try to see what is missing in the GUI DMA test
> in the DRI code.
> At a first glance, I don't remember to have seen a pci_set_master call
> anywhere in the DRI code. It seems important, doesn't it?
On Wed, 17 Oct 2001, Mike Westall wrote:
> I spent an incredibly frustrating 4 weeks trying to
> get the DRI to work with r128 and g400 cards on Dell
> precision workstation only to find that my problem
> was precisely because bus mastering was NOT enabled
> on boot! As soon as I fixed that ev
I spent an incredibly frustrating 4 weeks trying to
get the DRI to work with r128 and g400 cards on Dell
precision workstation only to find that my problem
was precisely because bus mastering was NOT enabled
on boot! As soon as I fixed that everything worked
fine. Apparently different BIOSes WIL
On Wed, 17 Oct 2001 [EMAIL PROTECTED] wrote:
>
> R C writes:
>
> > On Sat, Oct 13, 2001 at 10:08:50PM +0200, Manuel Teira wrote:
> >
> > Regarding theories on DMA and Mach64 and XFree 4.10:
> >
> > I just finished a module that uses the System DMA unit for video capture
> > transfers, and i
R C writes:
> On Sat, Oct 13, 2001 at 10:08:50PM +0200, Manuel Teira wrote:
>
> Regarding theories on DMA and Mach64 and XFree 4.10:
>
> I just finished a module that uses the System DMA unit for video capture
> transfers, and it works fine under a (highly hacked) XFree 4.1.0 server.
>
> Syst
On Sat, Oct 13, 2001 at 10:08:50PM +0200, Manuel Teira wrote:
Regarding theories on DMA and Mach64 and XFree 4.10:
I just finished a module that uses the System DMA unit for video capture
transfers, and it works fine under a (highly hacked) XFree 4.1.0 server.
System: Dual 550 Celeron, All-in-W
On Sun, 14 Oct 2001, Manuel Teira wrote:
> Hello again.
>
> First of all, I think that Jouko success putting to work the old mach64
> branch points that there must be some difference in the 2D card
> initialization. I'll try to look deeper in the 2D driver issues.
Actually Manuel, I'm working f
Hello again.
First of all, I think that Jouko success putting to work the old mach64
branch points that there must be some difference in the 2D card
initialization. I'll try to look deeper in the 2D driver issues.
The second point is that I've migrated the mach64 changes to a fresh DRI
trun
> BTW. Somebody said that the mach64 driver crashed under 2.4.10 kernel (I
> don't remember who said it). I've made all these tests under 2.4.12 without
> problems.
That was me. I had enabled some of the new kernel debugging options,
including CONFIG_DEBUG_SLAB and CONFIG_DEBUG_IOVIRT. After re
Hello.
I've been very busy lately at work, and have sadly checked that there have
been no progress in the mach64 work, or at least it wasn't posted in this
list.
Today I've tried to make gears work under the mach64 drm code. Well, gears
just shows a window with rests of KDE initialization s
Hello. I'm working in adapting the mach64 drm driver to the new template
structure. I have a pair of questions:
What is the meaning of the __HAVE_SG define? I've set it to zero in the
mach64 driver, but I'm not sure about this supposition.
In the mach64_dma.c , the following line:
dev_priv->s
18 matches
Mail list logo
