All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Frias <sf84@laposte.net>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: philb@gnu.org, Jean Delvare <jdelvare@suse.com>,
	linux-parport@lists.infradead.org, tim@cyberelk.net,
	linux-i2c@vger.kernel.org
Subject: True Parallel Port Interface for Bit-banging?
Date: Tue, 25 Oct 2016 13:21:38 +0200	[thread overview]
Message-ID: <580F4042.5070201@laposte.net> (raw)

Hi,

(NOTE: I also included "I2C over Parallel Port" maintainers in CC because
it seems they do bit-banging for it)

I would guess this question may have been asked before but I did not find references
to an answer, sorry for repeating if that's the case.

I have a legacy application that requires a True Parallel port (ISA compatible)
for bit-banging.
As you know, most computers nowadays do not include a True Parallel port anymore.

There are ExpressCard adaptors, but their base address is not ISA compliant
(378h, 278h).

The legacy application is DOS, so I was thinking of virtualising it under Linux
so that Linux works at ExpressCard address, hoping that the port would end up
being exposed to the virtualised DOS at the right (ISA-legacy) address.

Would that make sense and/or be feasible? Are there better/easier solutions?

Alternatively, does anybody knows if the Parallel Port available thru Laptop
docking stations (Dell, HP, Thinkpad, etc.) are True Parallel Ports (ISA
compatible)?

Thanks in advance.
Best regards,

Sebastian

             reply	other threads:[~2016-10-25 11:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-25 11:21 Sebastian Frias [this message]
2016-10-25 12:09 ` True Parallel Port Interface for Bit-banging? Wolfram Sang
2016-10-25 14:20   ` Sebastian Frias
2016-10-25 14:29     ` Wolfram Sang
2016-10-25 14:56       ` Sebastian Frias
2016-10-25 17:17         ` Wolfram Sang
2016-10-26  0:04         ` Maciej S. Szmigiero
2016-10-26  5:20           ` [Linux-parport] " Jan Kandziora
2016-10-28 10:25           ` Sebastian Frias
2016-10-28 23:12             ` Maciej S. Szmigiero
2016-11-07 12:44               ` Sebastian Frias
2016-11-07 23:53                 ` Maciej S. Szmigiero
2016-10-25 13:22 ` Jean Delvare
2016-10-25 16:12   ` Sebastian Frias

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=580F4042.5070201@laposte.net \
    --to=sf84@laposte.net \
    --cc=jdelvare@suse.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-parport@lists.infradead.org \
    --cc=philb@gnu.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=tim@cyberelk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.