From: gaxt <gaxt@rogers.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: WINE + Galciv + Con Kolivar's 09 patch to 2.6.0-test1-mm2
Date: Mon, 28 Jul 2003 17:40:44 -0400 [thread overview]
Message-ID: <3F25985C.2090109@rogers.com> (raw)
In-Reply-To: <200307271205.59230.kernel@kolivas.org>
260-test2-vanilla works fine with a little stutter playing the avis
260-test2-O10 causes horrible stutter and loss of input to system
260-test2-mm1 causes horrible stutter and loss of input to system
NOTE: Instead of re-setting, by switching consoles by pressing Alt F7
then Alt-F1 back and forth (ie from X to virtual console) it seems I
could prod wine+galciv into edging forward, stalling, edging forward
etc. through the opening AVIs. ie. I would hear the sounds of the movie
advance each time I switched into Alt-F1.
Once into the turn-based game itself (after opening animations) ability
to input was restored again and the game can be played and windows moved
around etc.
So it seems the playing of the little movies is what really locks up the
whole system using the O10/mm1 scheduling???
next prev parent reply other threads:[~2003-07-28 21:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 21:49 WINE + Galciv + Con Kolivar's 09 patch to 2.6.0-test1-mm2 gaxt
2003-07-27 2:05 ` Con Kolivas
2003-07-28 5:17 ` 260test2+O10int breaks : " gaxt
2003-07-28 21:40 ` gaxt [this message]
2003-07-28 21:39 ` Con Kolivas
2003-07-29 2:30 ` gaxt
2003-07-29 3:25 ` Con Kolivas
2003-07-29 12:48 ` WINE + Galciv + Con Kolivas's 011 patch to 2.6.0-test2 gaxt
2003-07-29 12:46 ` Con Kolivas
2003-07-29 20:59 ` gaxt
2003-07-29 21:09 ` gaxt
2003-07-29 21:13 ` gaxt
2003-08-08 20:04 ` 2.6.0-test2-mm5 + July Wine + Galciv gaxt
2003-08-12 14:42 ` WINE + Galciv + 2.6.0-test3-mm1-O15 gaxt
2003-08-12 14:40 ` Con Kolivas
2003-08-12 18:24 ` Mike Galbraith
2003-08-12 18:44 ` Timothy Miller
2003-08-12 18:48 ` Mike Galbraith
2003-08-13 3:34 ` Con Kolivas
2003-08-13 12:47 ` Mike Galbraith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F25985C.2090109@rogers.com \
--to=gaxt@rogers.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).