From: Nathan Neulinger <nneul@umr.edu>
To: linux-kernel@vger.kernel.org
Subject: Getting idle linux parport to look like idle Win32 parallel port
Date: Fri, 26 Oct 2001 20:14:40 -0500 [thread overview]
Message-ID: <3BDA0A80.25B6554D@umr.edu> (raw)
I've got a device hooked up to the parallel port that seems to behave
differently when hooked up to an idle windows parallel port compared to
an idle linux parallel port.
What is the difference between the two? And is there any way to convince
parport to get the port to look the same? My guess is that some pin is
being held high/low by parport and that isn't being done by windows, or
vice versa.
-- Nathan
------------------------------------------------------------
Nathan Neulinger EMail: nneul@umr.edu
University of Missouri - Rolla Phone: (573) 341-4841
Computing Services Fax: (573) 341-4216
reply other threads:[~2001-10-27 1:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3BDA0A80.25B6554D@umr.edu \
--to=nneul@umr.edu \
--cc=linux-kernel@vger.kernel.org \
/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