Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 6 Mar 2003 06:48:48 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 6 Mar 2003 06:48:48 -0500 Received: from k7g317-2.kam.afb.lu.se ([130.235.57.218]:50058 "EHLO cheetah.psv.nu") by vger.kernel.org with ESMTP id ; Thu, 6 Mar 2003 06:48:47 -0500 Date: Wed, 5 Mar 2003 07:49:23 +0100 (CET) From: Peter Svensson To: Eric Lammerts cc: Uwe Reimann , Subject: Re: Direct access to parport In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1239 Lines: 30 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: ! 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... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/