Masanori Kakimoto (kaki++at++kaki.nsg.sgi.com)
Wed, 11 Oct 1995 17:13:30 +0900
On Oct 11, 7:09am, Angus Dorbie wrote:
> Subject: Re: Synchronizing HW pipes
> Try sharing PFCHAN_SWAPBUFFERS, you don't need a swapready on a single
> host (PFCHAN_SWAPBUFFERS_HW), but you should genlock the pipes, setmon -g
PFCHAN_SWAPBUFFERS should be shared by default among a channel group. Do
we have to explicitly call pfChanShare to share PFCHAN_SWAPBUFFERS?
By default, PFCHAN_VIEW is also shared. But the customer calls pfChanView
for each channel instead of using pfChanViewOffsets and PFCHAN_VIEW
advantage.
> + wiring. Also try changing the pfPhase to a mode which works for a
> synchronous swap.
pfPhase(PFPHASE_LOCK) is called after pfConfig.
> I also noticed you don't update the eye position or animation in the loop,
> incase it isn't an omition you should do this in the applicaion, somewhere
> in this loop and not in a callback in cull or draw.
They do call pfChanView in the loop as I commented in the source code
skeleton.
> > while (running) {
> > switch (eventHandling()) { /* pfChanView is called under this. */
The view change is done before pfSync rather than between pfSync and pfFrame.
This may cause a minor problem in the response to events. But I doubt whether
it affects the synchronization among pipes.
I also pointed out to the customer that there might be some possibility that a
pfFrame intervenes between pfChanView(middle, ) and pfChanView(left or right, )
under some input condition. But they say that does not happen.
The important point of the problem is below:
> > When they, instead of multipipe, tried using single pipe and multichannel
> > with MCO, they do NOT have the problem.
# Sorry for the tense inconsistency of the above sentense.
-- Masanori Kakimoto mailto:kaki++at++nsg.sgi.com East Asia Technology Center, Tokyo Office, c/o Nihon Silicon Graphics K.K. TEL:+81-3-5488-1852 FAX:+81-3-5420-2397 Voicemail:5-7465
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:51:57 PDT