mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Nico Schottelius <nico-kernel@schottelius.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Parallel Port: Settings PINs on?
Date: Wed, 1 Jun 2005 12:13:58 +0200	[thread overview]
Message-ID: <20050601101358.GP2417@lug-owl.de> (raw)
In-Reply-To: <20050601101022.GE3690@DervishD>

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

On Wed, 2005-06-01 12:10:22 +0200, DervishD <lkml@dervishd.net> wrote:
>  * Nico Schottelius <nico-kernel@schottelius.org> dixit:
> > Is it possible to select (in userspace) which pins
> > should be enabled or do I have to write a kernel driver
> > for that?
> 
>     Userspace will do. Take a look at programs like 'parapin', 'k74',
> 'libieee1284', 'libparportled', or similars. Look in FreshMeat. As
> far as I know, all them runs in userspace, although you can find some
> Linux drivers for performing pin control of parallel port.

Just for the records: some programs that access the parport use
non-portable inb/outb at PCish I/O addresses to control the parport
line. Though, I haven't checked the programs mentioned above.

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-06-01 10:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01 10:01 Nico Schottelius
2005-06-01 10:10 ` DervishD
2005-06-01 10:13   ` Jan-Benedict Glaw [this message]
2005-06-01 10:12 ` Jan-Benedict Glaw

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=20050601101358.GP2417@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico-kernel@schottelius.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

all inboxes | Powered by JetHome®