Linux MS DOS discussions
 help / color / mirror / Atom feed
From: Bart Oldeman <bartoldeman@users.sourceforge.net>
To: Ryan Underwood <nemesis-lists@icequake.net>,
	gnupic@linuxhacker.org, linux-msdos@vger.kernel.org
Subject: Re: PICs on Linux
Date: Mon, 08 Nov 2004 14:21:16 +1300	[thread overview]
Message-ID: <418eca0c.17.4429.1500450417@ihug.co.nz> (raw)

Hello,

> The printer driver and DOSEMU's port passing cannot share
> the physical printer port.  Therefore you need to disable
> the printer driver if you want to use DOSEMU's port
> passing, either temporarily or permanently.
>
> Yes, and remember to use 'fast' unless you want to do
> debugging/tracing: $_ports = "fast range 0x378 0x37a"
>
> means pass through 0x378-0x37a in fast mode.
>
> You have to start DOSEMU as root or use sudo in order for
> port/irq passing to work.

It's still a bit tricky. This is the nature of direct
hardware access under Linux, the jail around you (protected
mode OS) needs to be partially broken down. There are
security issues to deal with, etc etc. -- this is why we can
never let this happen out of the box for a normal (non-root)
user.

This is not unique to Linux, under Windows XP there are even
people trying to make a buck selling direct hardware access.
http://www.zeecube.com/ParPort2004.htm
we don't ask for $19.95 but you have to pay in other ways
(trickier setup) so to speak.

However:
Linux 2.4 and 2.6 kernels provide a ppdev device driver that
allows raw parallel port access via /dev/parports/0 etc.
DOSEMU could virtualize the parallel port hardware and
re-route it through that device thereby avoiding the root
issue. I don't have any parallel port hardware to play with
but it could be a nice little project to implement in DOSEMU
one day.

Speed shouldn't be such a big deal: according to
http://www.ussg.iu.edu/hypermail/linux/kernel/0303.0/0978.html
you can only do about 300000 inb's and outb's per second
anyway.

Bart

             reply	other threads:[~2004-11-08  1:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08  1:21 Bart Oldeman [this message]
2004-11-11 21:38 ` PICs on Linux Ryan Underwood
     [not found] <20041111213944.GD32418@dbz.icequake.net>
2004-11-12  3:11 ` Bill Couture
  -- strict thread matches above, loose matches on Subject: below --
2004-11-08  2:03 Bart Oldeman
     [not found] <20041107041204.513276C@mail.icequake.net>
2004-11-07 23:02 ` Ryan Underwood

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=418eca0c.17.4429.1500450417@ihug.co.nz \
    --to=bartoldeman@users.sourceforge.net \
    --cc=gnupic@linuxhacker.org \
    --cc=linux-msdos@vger.kernel.org \
    --cc=nemesis-lists@icequake.net \
    /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