From: Simon Bridger <623402@despammed.com>
To: linux-msdos@vger.kernel.org
Subject: Re: Changing an app to use linux framebuffer
Date: Tue, 3 Dec 2002 21:49:35 +1300 [thread overview]
Message-ID: <200212032149.35061.623402@despammed.com> (raw)
In-Reply-To: <Pine.SOL.4.44.0212021640590.8159-100000@math.ohio-state.edu>
Thanks Bart,
the xinit .... gets it up on its own terminal nicely.
Does xdos accept vesa mode 0x140 (1400x1050)?
I can't get seem to get this mode going. (or any mode greater than 1024x768)
I tried increasing the xframebuffer size from 2048K, but that had no effect.
Does the x_framebuffer size affect speed at all? (ie having it unnecesarily
big)
> Use Ctrl-Alt-Home to have the mouse trapped (and again to de-trap it).
> Set
> $_X_mgrab_key = "Home"
> in dosemu.conf if ctrl-alt-home didn't work.
>
I haven't been able to get it to trap the mouse at all.
dosemu.conf does contain the line $_X_mgrab_key = "Home"
I am using a laptop, does this affect the key mapping?
Can I just force mouse trapping when I start, rather than by using the
keyboard?
> The way xdos works is to update the contents of the video buffer (dirty
> pages) periodically. So a video driver would play nice with DOSEMU if
> it updates the video buffer in chunks localized in pages (4k in size),
It currently writes in 32k windows of course, and the drivers try to minimise
page changes. This could be changed to 32 blocks perhaps.
Perhaps the autotrax driver should be changed to explicitly tell dosemu when a
page should be updated?
> There are various options in dosemu.conf you can play with, too.
I'm game
Simon
next prev parent reply other threads:[~2002-12-03 8:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-02 9:55 Changing an app to use linux framebuffer Simon Bridger
2002-12-02 21:59 ` Bart Oldeman
2002-12-03 8:49 ` Simon Bridger [this message]
2002-12-03 16:31 ` Bart Oldeman
-- strict thread matches above, loose matches on Subject: below --
2002-12-02 11:21 Stas Sergeev
2002-12-01 12:21 Stas Sergeev
2002-12-01 3:49 Simon Bridger
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=200212032149.35061.623402@despammed.com \
--to=623402@despammed.com \
--cc=linux-msdos@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