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
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
>
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
> If you have any other suggestions on projects, articles, etc. on Linux User
> Space Device Drivers, I would greatly appreciate the information.
>
A suggestion:
UIO: user-space drivers, since kernel version 2.6.21
http://lwn.net/Articles/232575/
Regards,
--
Leon
--
To unsubscribe from this
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...)?
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
If you have any other suggestions on projects, articles, etc. on Linux User
Space Device Drivers, I would greatly appreciate the information.
A suggestion:
UIO: user-space drivers, since kernel version 2.6.21
http://lwn.net/Articles/232575/
Regards,
--
Leon
--
To unsubscribe from this
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
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
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
10 matches
Mail list logo