> Vojtech> No. I'm just saying - if you want something that's not in
> Vojtech> the kernel drivers, just write a driver for it. But the
> Vojtech> driver must be able to coexist with the other drivers.
>
> It's easier to write a mouse driver in userspace than in kernel. But
> with the input system in 2.6, I am *forced* to write it in kernel
> space, and reboot and reboot and reboot when it oops. Writing the
> driver in kernel space, I at most get a segfault. Plus I cannot use
> everything from glibc. It simply takes more time and energy to write
> a kernel space driver.
Why not use UML (user mode linux). Jon Smirl was using it to work on fbdev
drivers in userland. Interrupts where tricky to handle but it might
work fine now. I have to give it a try again. Once it is setup you can
develope kernel driver in userland.
On Tue, 01 Jun 2004 22:01:10 BST, [email protected] said:
> Why not use UML (user mode linux). Jon Smirl was using it to work on fbdev
> drivers in userland. Interrupts where tricky to handle but it might
> work fine now. I have to give it a try again. Once it is setup you can
> develope kernel driver in userland.
UML helps the "boot/crash/reboot" cycle (and that sort of debugging was in
fact one of the early design goals of IBM's CP/67 and VM/370 systems). but
it doesn't help the fact that the infrastructure provided to kernel functions
is vastly different than the glibc-based infrastructure available in userspace....