linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Sebastian Frias <sf84@laposte.net>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
	linux-parport@lists.infradead.org, philb@gnu.org,
	tim@cyberelk.net, Jean Delvare <jdelvare@suse.com>,
	linux-i2c@vger.kernel.org
Subject: Re: True Parallel Port Interface for Bit-banging?
Date: Tue, 25 Oct 2016 14:09:51 +0200	[thread overview]
Message-ID: <20161025120951.GL1597@katana> (raw)
In-Reply-To: <580F4042.5070201@laposte.net>

[-- Attachment #1: Type: text/plain, Size: 419 bytes --]


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

Binary patching the DOS application? Port accesses should be easy to
find.

Getting a laptop with parallel port via auction site?

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

The older, the likelier, I'd say :)


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

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

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-25 11:21 True Parallel Port Interface for Bit-banging? Sebastian Frias
2016-10-25 12:09 ` Wolfram Sang [this message]
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=20161025120951.GL1597@katana \
    --to=wsa@the-dreams.de \
    --cc=jdelvare@suse.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-parport@lists.infradead.org \
    --cc=philb@gnu.org \
    --cc=sf84@laposte.net \
    --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 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).