RE: FW: Guidance on resources for User Space Device Drivers on 2.6 kernel

["Jaursch, Bill" <bjaursch@aeshen.com>]

Your point is well taken.

I will probably end of with a system daemon (User Space), but pass
communication via a Kernel module (Kernel Space).  The application can
call the kernel module, passing data back to the daemon (User Space).
Once I have hw, I may just use the kernel module.

Thanks again.

-----Original Message-----
From: Stefan Richter [mailto:stefanr@s5r6.in-berlin.de] 
Sent: Thursday, December 06, 2007 11:29 AM
To: Jaursch, Bill
Cc: Adrian Bunk; Leon Woestenberg; linux-kernel@vger.kernel.org
Subject: Re: FW: Guidance on resources for User Space Device Drivers on
2.6 kernel

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/