public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Hounschell <markh@compro.net>
To: linux-msdos@vger.kernel.org
Cc: Paul Crawford <psc@sat.dundee.ac.uk>
Subject: Re: Serial port slow on Linux dosemu
Date: Tue, 10 Jan 2012 11:20:47 -0500	[thread overview]
Message-ID: <4F0C655F.5070508@compro.net> (raw)
In-Reply-To: <4F0C5D79.4030907@sat.dundee.ac.uk>

On 01/10/2012 10:47 AM, Paul Crawford wrote:
>> When using the 2 config entries below "and" the -s option "as root" the
>> serial port speeds up to almost what it should be. It now takes 2
>> seconds to test the cable. That is good however, using the -s option
>> seems to force some sort of full screen and the "ega" graphics is then
>> broken. Without the -s option my window is as I define it in the config
>> file and "ega" graphics works OK.
>>
>>
>> $_ports = " device /dev/null range 0x3f8 0x3ff fast"
>> # $_com1 = "/dev/ttyS0"
>>
>> Please help
>
> If you attempt to get direct hardware access to any of the PC's I/O
> ports (such as the UART for this case) you need to use -s for dosemu and
> have it running with root privileges (e.g. adding it to sudo list, etc).
>
> Just using '-s' should not break the graphics as such, unless your
> software is also trying direct graphics card I/O access and that is
> being passed through.
>

My $_ports entry should only allow serial stuff direct access through right?

I am running KDE and starting dosemu in a konsole terminal. When I do 
not use the -s option it opens in a small 640x350 window on my big 
screen and the dos "ega" graphics works. But the serial stuff is way too 
slow. Any time I use the -s option it opens in a window of max size and 
the ega stuff does not work but the serial stuff works well. The 
application screen at this point is all amiss. Even though it is mostly 
text. It acts this way when I run from a Virtual console also. IE tty2. 
Whether or not I use the -s option. From any tty1-6, 8-12 it does this.

Is there a bug that causes the -s to use direct graphics card I/O 
access, even though the $_ports is not specifying it?

Regards
Mark

  reply	other threads:[~2012-01-10 16:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09 21:58 Serial port slow on Linux dosemu Mark Hounschell
2012-01-10 12:48 ` Mark Hounschell
2012-01-10 15:13 ` Mark Hounschell
2012-01-10 15:47   ` Paul Crawford
2012-01-10 16:20     ` Mark Hounschell [this message]
2012-01-11 13:40       ` Mark Hounschell

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=4F0C655F.5070508@compro.net \
    --to=markh@compro.net \
    --cc=linux-msdos@vger.kernel.org \
    --cc=psc@sat.dundee.ac.uk \
    /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