From: Sebastian Frias <sf84@laposte.net>
To: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>
Cc: Wolfram Sang <wsa@the-dreams.de>,
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: [Linux-parport] True Parallel Port Interface for Bit-banging?
Date: Fri, 28 Oct 2016 12:25:48 +0200 [thread overview]
Message-ID: <581327AC.8060404@laposte.net> (raw)
In-Reply-To: <7bd6ea08-361e-316f-be7f-d400b59aec0d@maciej.szmigiero.name>
On 10/26/2016 02:04 AM, Maciej S. Szmigiero wrote:
>
> I don't have experience with bit-banging parallel port but I do have
> some with bit-banging PC serial ports (which should be very similar)
> and can confirm that old DOS software can be *very* fragile with regard
> to timing.
> I have tried dosemu, dosbox and as far I remember also VirtualBox
> with an old, DOS car service app.
> Wasn't able to make it communicate until I booted true DOS.
> That machine had old-style ISA serial ports so it was possible.
>
Thanks for sharing your experience.
I think it should be related to the latencies Wolfram discussed.
> You also have asked previously whether laptop port would work.
> On my current HP Elitebook ports of both types are wired to Super IO,
> and using PC standard IO port and interrupt numbers.
Would you mind sharing the laptop's model? There are a bunch of
Elitebooks and maybe not all have the ports wired.
Does your laptop has the Parallel Port on the docking or on the laptop
itself?
>
> I also remember that at least on ThinkPads and HP Compaqs that I had
> contact with (these were laptops from 10+ years ago) both serial and
> parallel ports were wired to Super IO chip (including ones available
> only via port replicator).
> So they were also at PC standard resources.
>
Yes, it appears that Thinkad T42 could work:
https://forum.linuxcnc.org/forum/49-basic-configuration/15999-thinkpad-t42-parallel-port-not-working
> However, other issue is that sometimes such ports are inactive by
> default (don't respond) until enabled by PnP.
>
> This is also a problem with PCMCIA cards - they are disabled
> by default.
Do you know the command to enable them thru PnP? Shouldn't loading
the kernel module be enough? Or is it the other way around and
enabling thru PnP triggers the kernel module load process?
> I have Argosy 2xRS232 PCMCIA card and remember it came with
> DOS driver which could enable them on I/O port close to standard
> one - this was one of their major selling points.
> So your ExpressCard would probably need similar software.
>
Thanks for the pointer.
next prev parent reply other threads:[~2016-10-28 10:25 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
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 [this message]
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=581327AC.8060404@laposte.net \
--to=sf84@laposte.net \
--cc=jdelvare@suse.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-parport@lists.infradead.org \
--cc=mail@maciej.szmigiero.name \
--cc=philb@gnu.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=tim@cyberelk.net \
--cc=wsa@the-dreams.de \
/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.