From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
"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:09:24 +0100 [thread overview]
Message-ID: <20080706190924.652e7cde@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20080706200033.0b833508@linux360.ro>
> But isn't it incorrect to assume that sharing protocols allow multiple
> separate users? Why not have an userspace server mux/demux requests?
Why do that ?
> The parallel port itself is not designed to be shared, so even if the
> device supports it, it does not mean we should allow independent
> access. We really should have an userspace lib/server to do this.
I suggest you look at the actual hardware examples in more detail. Most of
them are happy to share but need to own the port temporarily. The manner
in which they lock/unlock their use of the port tends to be very specific
to the device so it makes sense to have the current desgign.
next prev parent reply other threads:[~2008-07-06 18:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 13:21 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
2008-07-06 16:08 ` Alan Cox
2008-07-06 17:00 ` Eduard - Gabriel Munteanu
2008-07-06 18:09 ` Alan Cox [this message]
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=20080706190924.652e7cde@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ebiederm@xmission.com \
--cc=eduard.munteanu@linux360.ro \
--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 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®