linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Jaursch, Bill" <bjaursch@aeshen.com>
Cc: Adrian Bunk <bunk@kernel.org>,
	Leon Woestenberg <leon.woestenberg@gmail.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 20:29:16 +0100	[thread overview]
Message-ID: <47584D8C.4090000@s5r6.in-berlin.de> (raw)
In-Reply-To: <32A49E5BEBD67A4F877032926EFAA4D2092CCABF@ms08.mse3.exchange.ms>

Jaursch, Bill wrote:
> The reason to even consider a driver for this "Software only" driver
> was to start the work of writing a kernel space driver (loadable
> module).  So more specifically, I wanted to know if there is a way
> to use calls to the kernel to access a loadable module that is
> running code in User Space (to take advantage of libraries, tools,
> prevention of kernel crashes, etc.).

Since you plan to use this for a PCI device eventually, it sounds like
UIO would be of help.

> I am running 2.6.20, so many of the new User Space Driver features
> don't appear to be available (UIO, User Space API, etc.).  And at
> this point I don't expect my end users to upgrade to a newer kernel.

Perhaps you can backport UIO or can get someone to do it for you.
-- 
Stefan Richter
-=====-=-=== ==-- --==-
http://arcgraph.de/sr/

  parent reply	other threads:[~2007-12-06 19:29 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
     [not found]     ` <32A49E5BEBD67A4F877032926EFAA4D2092CCABF@ms08.mse3.exchange.ms>
2007-12-06 19:29       ` Stefan Richter [this message]
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=47584D8C.4090000@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=bjaursch@aeshen.com \
    --cc=bunk@kernel.org \
    --cc=leon.woestenberg@gmail.com \
    --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).