On Sun, 28 Apr 2002, Leif Delgass wrote:
> If it works, you should see the same 7 VERTEX_ register values in the
> system log before and after the test.
Sorry, I meant to say that you should see all zeros for the registers
before the transfer and 0x, 0x, etc. after the transfer.
On Sun, 28 Apr 2002, Peter Andersson wrote:
> >
> >
> >Peter, if you set
> >MACH64_VERBOSE to 1 in mach64_drv.h and rebuild the DRM, you should see a
> >debug statement for each register access. This could help us find the
> >problem. That being said though, I don't see where the _vm_dma_nop
>
>
>Peter, if you set
>MACH64_VERBOSE to 1 in mach64_drv.h and rebuild the DRM, you should see a
>debug statement for each register access. This could help us find the
>problem. That being said though, I don't see where the _vm_dma_nopage
>comes in between _dispatch_clear and the missing de
On Sun, 2002-04-28 at 00:00, Leif Delgass wrote:
> On 27 Apr 2002, Michel Dänzer wrote:
>
> > On Sat, 2002-04-27 at 18:31, Leif Delgass wrote:
> > >
> > > When we get the MMIO path working for ppc, I think we'll still have to
> > > make some changes for DMA. When filling the vertex buffers and
On 27 Apr 2002, Michel Dänzer wrote:
> On Sat, 2002-04-27 at 18:31, Leif Delgass wrote:
> >
> > When we get the MMIO path working for ppc, I think we'll still have to
> > make some changes for DMA. When filling the vertex buffers and setting up
> > the descriptor tables, won't we have to conv
On Sat, 2002-04-27 at 21:24, Leif Delgass wrote:
>
> I've just commited the endianess conversion for register reads/writes to
> the branch, so you won't have to keep applying Michel's patch. I used
> le32_to_cpu/cpu_to_le32 since that's what the other drivers use and I
> was getting a compiler w
On Sat, 2002-04-27 at 18:31, Leif Delgass wrote:
>
> When we get the MMIO path working for ppc, I think we'll still have to
> make some changes for DMA. When filling the vertex buffers and setting up
> the descriptor tables, won't we have to convert to little-endian?
Yes, unless the chip can
>> thread). On some PPC's like PReP, the mapping between bus addresses
>> and CPU physical addresses on PCI isn't 1:1 and the system RAM is
>> not mapped at 0 for bus mastering PCI devices. If you use the PCI
>> DMA API, things are ok. If you aren't, then some tweaks may be needed.
>> (See the def
Warning
Unable to process data:
multipart/mixed;boundary="=_NextPart_000_00B4_11E58B6A.C1872E75"
On Sat, 27 Apr 2002, Peter Andersson wrote:
> > Hi,
> >
> > I cvs updated mach64-0-0-4-branch last night and recompiled (previous
> > update was on sunday). Right after starting glxgears the screen switched
> > off (like with xset dpms force off) and the machine hung. The sysrq keys
> > did
Brian Paul wrote:
>
> Geoffrey Broadwell wrote:
> >
> > Unfortunately, I've had no luck with this problem in any of the XFree86
> > places I've tried (the newbie and xpert mailing lists, as well as
> > #xfree86), but I did get a response to try my question here. So here
> > goes:
> >
> > I'm try
> Hi,
>
> I cvs updated mach64-0-0-4-branch last night and recompiled (previous
> update was on sunday). Right after starting glxgears the screen switched
> off (like with xset dpms force off) and the machine hung. The sysrq keys
> didn't work.
>
> Maybe Peter Anderson's problems are not P
On Sat, Apr 27, 2002 at 06:01:14PM +0100, José Fonseca wrote:
> Why do you say virt_to_bus is deprecated? Where can I find more
> information about these APIs?
/usr/src/linux/Documentaion/IO-mapping.txt (right at the top) and
DMA-mapping.txt
--
Michael.
___
>
>
>What PPC machine is this ? (sorry, I missed the beginning of the
>thread).
>
I am using an ibook "blueberry" with a 300mhz powerpc processor and ATI
rage 3D mobility 2X agp graphics board with 4mb of ram.
Peter
___
Dri-devel mailing list
[EM
On Sat, 27 Apr 2002, José Fonseca wrote:
> On 2002.04.27 15:33 Benjamin Herrenschmidt wrote:
> > >
> > >I don't see how. The function in which Leif fixed the big had a debug
> > >output statement which would appear in the kmsg if it was the last one.
> > >
> > > From what I've read the *_nopage f
On 2002.04.27 17:31 Leif Delgass wrote:
> On 27 Apr 2002, Michel Dänzer wrote:
> > ...
> >
> > Isn't it the buglet Leif fixed tonight?
>
> I changed virt_to_phys to virt_to_bus like you suggested, but that's in
> the _dispatch_vertex. In the system log that Peter posted, the last
> message befor
On 2002.04.27 15:33 Benjamin Herrenschmidt wrote:
> >
> >I don't see how. The function in which Leif fixed the big had a debug
> >output statement which would appear in the kmsg if it was the last one.
> >
> > From what I've read the *_nopage functions are associated with
> accessing
> >memory map
On 27 Apr 2002, Michel Dänzer wrote:
> On Sat, 2002-04-27 at 09:50, José Fonseca wrote:
> > On 2002.04.26 12:42 Michel Dänzer wrote:
> > > On Fri, 2002-04-26 at 00:41, Peter Andersson wrote:
> > > >
> > > > I tried the backtrace option but it only produced a bunch of numbers
> > > and
> > > > let
On Fri, Apr 26, 2002 at 11:09:20AM -0700, Ian Romanick wrote:
> Double Buffering --- Yes
...but not page flipping and no single buffer visuals.
> Gamma Control -- No
gamma works in q3/rtcw here - is this something else?
> Page Flipping -- Yes, but I'
>
>I don't see how. The function in which Leif fixed the big had a debug
>output statement which would appear in the kmsg if it was the last one.
>
> From what I've read the *_nopage functions are associated with accessing
>memory maped regions. It could be that the DMA pages aren't being proper
Ian Romanick wrote:
>
> The big issue being backwards
> compatability. We need to not only provide it in the DRI drivers, but we
> need to (try to) provide it in applications that use libGL.so.
Absolutely, and we don't the advantage of having someone like Linus
point this out to us, instead we'
Smitty wrote:
> Ian wrote:
>
> > Page Flipping -- Yes, but I'm not 100% sure.
The FullScreen support was designed for page flipping; however, I don't
know how complete this work is. The drivers I have seen with this
extension supported, including the Radeon, have it disabled wit
> Peter, could you try this so that we could pin point where the fault
> occurred exactly. I don't know if it's needed to recompile the kernel
> to have more symbol information. On the x86 there is a specific option
> for that in the kernel configuration.
>
Sorry i can´t be of more help, but it
On 2002.04.25 23:22 Thomas Winischhofer wrote:
> Keith Whitwell wrote:
> >...
> >
> > It should be fairly easy to examine the differences in interfaces and
> > make only the minimal set of changes. There isn't *that* huge of a
> > difference.
>
> I will take a look. Is there a document on these
On 2002.04.27 09:26 Michel Dänzer wrote:
> On Sat, 2002-04-27 at 09:50, José Fonseca wrote:
> > ...
> > In the mean while I'll try look at the last kmsg debug statements to
> > see if I found any further clue.
>
> Isn't it the buglet Leif fixed tonight?
>
I don't see how. The function in which
On Sat, 2002-04-27 at 09:50, José Fonseca wrote:
> On 2002.04.26 12:42 Michel Dänzer wrote:
> > On Fri, 2002-04-26 at 00:41, Peter Andersson wrote:
> > >
> > > I tried the backtrace option but it only produced a bunch of numbers
> > and
> > > letters, and since i am not exactly sure if i am able t
On 2002.04.26 12:42 Michel Dänzer wrote:
> On Fri, 2002-04-26 at 00:41, Peter Andersson wrote:
> >
> > Vector 800 at pc - d58fb02c , lr -d58fb64
> > mxr - 9032, xp -4200
> > current - c99fc000, pid - 1077, comm -glxgears
> > mon>
> >
> > ...
>
> This is the xmon (simple kernel debugger) promp
27 matches
Mail list logo
