linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Adrian Bunk <bunk@kernel.org>
Cc: "Jaursch, Bill" <bjaursch@aeshen.com>, linux-kernel@vger.kernel.org
Subject: Re: FW: Guidance on resources for User Space Device Drivers on 2.6 kernel
Date: Thu, 06 Dec 2007 13:38:19 +0100	[thread overview]
Message-ID: <4757ED3B.1000703@s5r6.in-berlin.de> (raw)
In-Reply-To: <20071206114912.GL15974@stusta.de>

Adrian Bunk wrote:
> On Wed, Dec 05, 2007 at 01:29:23AM -0500, Jaursch, Bill wrote:
>> I have am in the process of writing a driver that is software only.
>> I would like to avoid the caveats of a kernel mode installable module.
>>...
> 
> What is "a driver that is software only"
> (all kernel code is also software only...)?
> 
> You must describe what you want to do for people being able to actually 
> help you.

Although "software only" is a wrong term here, it's certainly clear from
context what he meant.  However, what's missing is information about the
kind of device he plans to support.  Is it a USB device or is it sitting
behind a similar bus?  Or is it a device on a local bus like PCI?  In
the latter case, is DMA involved?

>> I found FUSD (http://svn.xiph.org/trunk/fusd/), but would like to know
>> if this is a stable project.

This question should be directed to the authors or maintainers of FUSD.
 Note, AFAIU from its documentation, FUSD is not a means to implement
arbitrary kinds of device drivers in userspace.  It allows for "proxying
*device file* callbacks into user-space, allowing *device files* to be
implemented by" userspace programs (emphasis is mine).  I.e. FUSD gives
userspace programs only the ability to supply a character special file
to other userspace programs.  In order to drive real hardware, the FUSD
client would additionally need to access other userspace interfaces of
the kernel, provided by actual kernelspace drivers.
-- 
Stefan Richter
-=====-=-=== ==-- --==-
http://arcgraph.de/sr/

  reply	other threads:[~2007-12-06 12:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-05  6:29 FW: Guidance on resources for User Space Device Drivers on 2.6 kernel Jaursch, Bill
2007-12-06 11:49 ` Adrian Bunk
2007-12-06 12:38   ` Stefan Richter [this message]
     [not found]     ` <32A49E5BEBD67A4F877032926EFAA4D2092CCABF@ms08.mse3.exchange.ms>
2007-12-06 19:29       ` Stefan Richter
2007-12-06 19:33         ` Jaursch, Bill
2007-12-06 12:21 ` Leon Woestenberg

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=4757ED3B.1000703@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=bjaursch@aeshen.com \
    --cc=bunk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).