> Greeting kernel-builders,
> 
> Making changes to driver code, and rebooting to test is
> very time consuming. I have been doing some code testing under
> MacOS for the ADB code, but this is often plagued by problems
> because I have to be careful not to conflict with anything it's
> doing either.
> 
> So the question is:
> 
> Is there anyway to compile a code snippet from with NetBSD,
> and then run it, as if it was part of the kernel? That means
> access to all memory, etc. That way, perhaps I won't have to
> reboot twice for every little change I attempt with the ADB
> code.
> 
> Any insight is appreciated.
> 
>       --John

Uh-Uhh...

I've asked a similar question some time ago wrt. IWM access and even got
a reply from you, remember? And I have exactly the same problem right
now. No, not exactly: the IWM driver stubs don't hurt anything else
unless I run them so the rest of the kernel remains stable.

The only alternative that comes to mind is an LKM. But LKM support is
sparse and hasn't grown much since Terry Lambert left the project. Right
now someone is ripping things like file systems out of the kernel to
make them loadable, but I haven't found anything close enough to a
device driver. There is a Japanese LKM version of pc-vt, but it's i386
specific.

Learn all about LKMs and then explain things to me, will you? ;-)

        hauke

-- 
"It's never straight up and down"  (DEVO)