From: Matthias Schniedermeyer <ms@citd.de>
To: Greg KH <greg@kroah.com>
Cc: Matt Porter <mporter@embeddedalley.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC] Simple userspace interface for PCI drivers
Date: Wed, 30 Aug 2006 23:01:27 +0200 [thread overview]
Message-ID: <44F5FCA7.3080509@citd.de> (raw)
In-Reply-To: <20060830175529.GB6258@kroah.com>
Greg KH wrote:
> On Wed, Aug 30, 2006 at 09:34:10AM -0500, Matt Porter wrote:
>>Well, if it's focused on industrial controls like it appears from
>>the code here then the name is fine. If it's a starting point to
>>become someting more generic then User Space Driver (USD) subsystem
>>might be nice.
>>
> It's not focused on industrial controls at all, that just happens to be
> the name of it right now, as that is why it was written. It is much
> more generic than that.
>
> "USD" is a bit too close to "USB" for a name. Any other ideas?
DFU - Drivers for Userspace
DFU - Driver from Userspace
DFUF - Drivers for Userspace Framework
DIFUS - Drive It From Userspace :-)
FUD - Framework (for) Userspace Drivers ;-)
GUDI - Generic Userspace Driver Interface
UDF - Userspace Driver Framework :-)
UDI - Userspace Driver Interface :-)
UUDI - Unified Userspace Driver Interface
UFD - Userspace Framework (for) Drivers
...
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
next prev parent reply other threads:[~2006-08-30 21:01 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 6:23 [RFC] Simple userspace interface for PCI drivers Greg KH
2006-08-30 10:09 ` Thomas Gleixner
2006-08-30 14:34 ` Matt Porter
2006-08-30 16:25 ` Thomas Gleixner
2006-08-30 17:55 ` Greg KH
2006-08-30 20:32 ` Foli Ayivoh
2006-08-30 21:01 ` Matthias Schniedermeyer [this message]
2006-08-30 21:25 ` linux-os (Dick Johnson)
2006-08-30 22:08 ` Greg KH
2006-09-01 1:36 ` Brice Goglin
2006-09-01 3:22 ` Greg KH
2006-09-01 3:37 ` Brice Goglin
2006-09-01 4:27 ` Greg KH
2006-08-31 13:49 ` Andi Kleen
2006-09-01 18:16 ` Greg KH
2006-08-30 17:07 ` Manu Abraham
2006-08-30 17:52 ` Greg KH
2006-08-30 22:50 ` Manu Abraham
2006-08-31 0:17 ` Greg KH
2006-08-31 13:24 ` Manu Abraham
2006-08-31 22:42 ` Greg KH
2006-08-31 7:40 ` Andrew Morton
2006-08-31 8:05 ` Thomas Gleixner
2006-08-31 8:30 ` Xavier Bestel
2006-08-31 20:39 ` Lee Revell
2006-08-31 20:53 ` Chris Friesen
2006-08-31 21:39 ` Greg KH
2006-08-31 20:58 ` Xavier Bestel
2006-08-31 21:12 ` Lee Revell
2006-08-31 21:18 ` Xavier Bestel
2006-08-31 21:33 ` Manu Abraham
2006-08-31 21:40 ` Greg KH
2006-09-01 21:17 ` Pavel Machek
2006-09-03 8:34 ` Thomas Gleixner
2006-09-12 19:47 ` Sam Ravnborg
2006-09-14 5:57 ` Greg KH
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=44F5FCA7.3080509@citd.de \
--to=ms@citd.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mporter@embeddedalley.com \
--cc=tglx@linutronix.de \
/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