From: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>
To: Sebastian Frias <sf84@laposte.net>
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: Tue, 8 Nov 2016 00:53:24 +0100 [thread overview]
Message-ID: <fe33933b-c2ae-e3c6-0a17-f86d5e144e63@maciej.szmigiero.name> (raw)
In-Reply-To: <58207746.2020802@laposte.net>
On 07.11.2016 13:44, Sebastian Frias wrote:
> On 10/29/2016 01:12 AM, Maciej S. Szmigiero wrote:
>>> Would you mind sharing the laptop's model?
>>
>> This is Elitebook model 8570p.
>
> That seems like a fairly recent laptop:
>
> http://www.notebookcheck.net/Review-HP-EliteBook-8570p-B6Q03EA-ABD-Notebook.82291.0.html
>
> and it has a true parallel port?
It has parallel port on address 0x378/0x778, IRQ 5 by default which is
realized by Super IO chip.
In PnP config also available for selection are addresses 0x278/0x678,
0x3bc/0x7bc, IRQ 7 and ISA DMA channels 1 and 3.
Although I have never used this port personally it looks like what can
be considered a "true" parallel port.
> Thanks a lot for the pointer!
You are welcome.
Maciej
next prev parent reply other threads:[~2016-11-07 23:53 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
2016-10-28 23:12 ` Maciej S. Szmigiero
2016-11-07 12:44 ` Sebastian Frias
2016-11-07 23:53 ` Maciej S. Szmigiero [this message]
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=fe33933b-c2ae-e3c6-0a17-f86d5e144e63@maciej.szmigiero.name \
--to=mail@maciej.szmigiero.name \
--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 \
--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.