linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Svensson <petersv@psv.nu>
To: Eric Lammerts <eric@lammerts.org>
Cc: Uwe Reimann <linux-kernel@pulsar.homelinux.net>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Direct access to parport
Date: Wed, 5 Mar 2003 07:49:23 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.44.0303050746220.16313-100000@cheetah.psv.nu> (raw)
In-Reply-To: <Pine.LNX.4.52.0303042329450.18334@ally.lammerts.org>

On Tue, 4 Mar 2003, Eric Lammerts wrote:

> On Tue, 4 Mar 2003, Uwe Reimann wrote:
> > I'd like to connect some self made hardware to the parallel port and
> > read the values of the dataline using linux. Can this be done in
> > userspace or do I have to write kernel code to do so? I'm currently
> > thinking of writing a device like lp, which in turn uses the parport
> > device. Does this sound like a good idea?
> 
> >From userspace it's quite simple:

[ioperm-based suggestion removed]

A better idea may be to use ppdev - the portable and safe way to access a 
paralell port directly. This driver is in the stock kernels. This prevents 
races between the kernel and userland over control for the paralell port.

Peter
--
Peter Svensson      ! Pgp key available by finger, fingerprint:
<petersv@psv.nu>    ! 8A E9 20 98 C1 FF 43 E3  07 FD B9 0A 80 72 70 AF
------------------------------------------------------------------------
Remember, Luke, your source will be with you... always...



  reply	other threads:[~2003-03-06 11:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-04  8:15 Direct access to parport Uwe Reimann
2003-03-04 22:31 ` Eric Lammerts
2003-03-05  6:49   ` Peter Svensson [this message]
2003-03-05 11:24   ` Dmitrii Tisnek

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=Pine.LNX.4.44.0303050746220.16313-100000@cheetah.psv.nu \
    --to=petersv@psv.nu \
    --cc=eric@lammerts.org \
    --cc=linux-kernel@pulsar.homelinux.net \
    --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;
as well as URLs for NNTP newsgroup(s).