linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 7 Nov 2016 13:44:54 +0100	[thread overview]
Message-ID: <58207746.2020802@laposte.net> (raw)
In-Reply-To: <5461ac01-6054-e222-f707-0b475c24276d@maciej.szmigiero.name>

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? Thanks a lot for the pointer!

>> 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?
> 
> Only a serial port socket is built-it, parallel port socket is
> available only via a port replicator.
> 
> According to description of this replicator it is compatible with
> a lot of different Elitebooks and Probooks:
> http://h30094.www3.hp.com/product.aspx?sku=10432928&mfg_part=A7E34AA&pagemode=ca
> 
> I wasn't able find any note in this replicator description that port
> availability depends on connected laptop model.
> You can try to search for particular laptop model schematics, even
> if it is available only for sale sometimes there is a preview
> page with block diagram which clearly show where the parallel port
> is connected (this is true for my laptop model for example).
> 
> However, whether the port is on standard I/O address and interrupt
> line requires some more digging.

Thanks for the information.

>> 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?
> 
> If you want to use them under Linux then everything should be taken
> care of by kernel's PnP support.
> It can be problem if you want to use them under pure DOS.
> 

I see, thanks.

  reply	other threads:[~2016-11-07 12:44 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 [this message]
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=58207746.2020802@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 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).