From: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Marcin Slusarz <marcin.slusarz@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Frans Pop <elendil@planet.nl>
Subject: Re: [PATCH] parport/ppdev: fix registration of sysctl entries
Date: Sun, 6 Jul 2008 19:22:33 +0300 [thread overview]
Message-ID: <20080706192233.5df9c65b@linux360.ro> (raw)
In-Reply-To: <20080706081126.GA28946@ZenIV.linux.org.uk>
On Sun, 6 Jul 2008 09:11:26 +0100
Al Viro <viro@ZenIV.linux.org.uk> wrote:
> On Sat, Jul 05, 2008 at 11:49:26PM -0700, Eric W. Biederman wrote:
> > So our choices appear to be.
> > - Change the name in sysctl so each parport device always has a
> > unique name.
> > - Only allow one opener of ppdev for a given port.
>
> Can't do - it's a legitimate use of ppdev (several userland programs
> multiplexing the sucker).
How in the world would such a thing work?! I imagine one could
read()/write() there and multiplex data, but isn't the whole point of
ppdev to allow non-standard communication (manually flipping control
and data lines)? I've used it for custom hardware.
IMHO, there is one reason ppdev exists: allow both _safe_ and _raw_
access to the parallel port, and a much better alternative to the iopl
stuff.
Eduard
next prev parent reply other threads:[~2008-07-06 16:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 13:21 [PATCH] parport/ppdev: fix registration of sysctl entries Marcin Slusarz
2008-07-05 23:51 ` Al Viro
2008-07-06 0:11 ` Al Viro
2008-07-06 4:05 ` Al Viro
2008-07-06 6:49 ` Eric W. Biederman
2008-07-06 8:11 ` Al Viro
2008-07-06 9:25 ` Eric W. Biederman
2008-07-06 16:22 ` Eduard - Gabriel Munteanu [this message]
2008-07-06 16:08 ` Alan Cox
2008-07-06 17:00 ` Eduard - Gabriel Munteanu
2008-07-06 18:09 ` Alan Cox
2008-07-06 15:12 ` Marcin Slusarz
2008-07-06 15:07 ` Marcin Slusarz
2008-07-06 16:01 ` Arjan van de Ven
2008-07-06 20:35 ` Al Viro
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=20080706192233.5df9c65b@linux360.ro \
--to=eduard.munteanu@linux360.ro \
--cc=ebiederm@xmission.com \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.slusarz@gmail.com \
--cc=viro@ZenIV.linux.org.uk \
/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.