On Thu, 30 Sep 1999 [EMAIL PROTECTED] wrote:
> Hi !
>
> > Here is a interesting question which I hope you have the answer to. For
> > cards that lock when you acccess the framebuffer and accel engine. Does
> > this happen when you access any part of the framebuffer while the accel
> > engine is running or only when you access the area of the framebuffer
> > which the accel engine is trying also to update?
>
> Can be any. This behaviour is usually a bug.
> I'll explain it a little further below:
Well that kills that idea. I was hoping that often the poblem was that the
accel engine was updating area that another process was access via the
framebuffer. If this was the case then I was going to steal a piece of the
framebuffer from the process owning it and add it the process address
space that opened /dev/gfx. This way the process owns the accel engine and
the possible offending framebuffer region. Then I can put the
current process which would own those regions to sleep just before accel
access. The accel engine could go on its merry way while the process that
could acccess the framebuffer would be put to sleep. Other process could
run. Once the accel engine is done I could wake upthe process.
