From: Wolfgang Grandegger <wg@grandegger.com>
To: Ben Nizette <bn@niasdigital.com>
Cc: Marco Stornelli <marco.stornelli@coritel.it>,
Alessio Igor Bogani <abogani@texware.it>,
Bill Gatliff <bgat@billgatliff.com>,
"Douglas, Jim (Jim)" <jdouglas@avaya.com>,
Embedded Linux mailing list <linux-embedded@vger.kernel.org>
Subject: Re: UIO - interrupt performance
Date: Tue, 21 Oct 2008 12:28:49 +0200 [thread overview]
Message-ID: <48FDAEE1.9080503@grandegger.com> (raw)
In-Reply-To: <1224581853.3954.127.camel@moss.renham>
Ben Nizette wrote:
> On Tue, 2008-10-21 at 11:30 +0200, Marco Stornelli wrote:
>> I could agree, but "the facto" due to UIO license condition, a company
>> often uses UIO drivers, regardless performance, debug, etc, only as not
>> to public the code under GPL.
>
> It sounds to me like you think that driver authors can sit down and
> decide whether they want to implement their driver in userspace or
> kernel space. For 99% of drivers that's simply not true. You *cannot*
> write userspace drivers for most hardware, the hooks just aren't
> available. UIO is Userspace I/O, not a set of general hooks for
> userspace drivers.
I known, fortunately it's not that simple or even feasible. Image a
network driver with I/O multiplexing used by various processes.
> If people want drivers not under the GPL then they can distribute a
> binary-only module (though thank $DEITY there aren't many of those
> left). Userspace I/O exists to provide good performance interfacing to
That's *not* an option, please read the GPL license conditions. At least
it's legal gray area. Note that it's not my intention to start a
discussion on that.
> a family of devices - those which exist just to shuffle data around and
> have an interrupt to tell you when they're done.
>
> Do you have any example of a userspace i/o driver which exists to get
> around licencing constraints?
There will be plenty sooner than later. What you can do currently with
UIO is very limited.
Wolfgang.
next prev parent reply other threads:[~2008-10-21 10:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 9:55 UIO - interrupt performance Douglas, Jim (Jim)
2008-10-20 10:28 ` Ben Nizette
[not found] ` <Pine.LNX.4.58.0810200258210.2562@vlab.hofr.at>
2008-10-20 22:12 ` Ben Nizette
2008-10-21 6:57 ` Wolfgang Grandegger
2008-10-21 9:32 ` Ben Nizette
2008-10-20 10:30 ` Christian SCHWARZ
2008-10-20 11:55 ` Marco Stornelli
2008-10-20 13:20 ` Paul Mundt
2008-10-20 16:13 ` Bill Gatliff
2008-10-21 8:36 ` Marco Stornelli
2008-10-21 9:01 ` Alessio Igor Bogani
2008-10-21 9:30 ` Marco Stornelli
2008-10-21 9:37 ` Ben Nizette
2008-10-21 10:24 ` Marco Stornelli
2008-10-21 10:28 ` Wolfgang Grandegger [this message]
2008-10-21 11:39 ` Bill Gatliff
2008-10-20 12:48 ` Thomas Petazzoni
2008-10-20 16:25 ` Bill Gatliff
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=48FDAEE1.9080503@grandegger.com \
--to=wg@grandegger.com \
--cc=abogani@texware.it \
--cc=bgat@billgatliff.com \
--cc=bn@niasdigital.com \
--cc=jdouglas@avaya.com \
--cc=linux-embedded@vger.kernel.org \
--cc=marco.stornelli@coritel.it \
/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.