Development process for drivers
Chris Double
correct process for running and testing it to use the service command
to bring it up?
service up /home/chris/mydriver/mydriver
And then shut it down when wanting to change it? Or is it sufficient to
rebuild it and use 'refresh'?
Is there anything else that needs to be configured for Minix to know
about the driver?
Do driver developers usually test their drivers seperate to running it
like the above (just running the process with stubs for
sending/receiving messages for example)?
Chris.
--
http://www.minixtips.com
Philip Homburg
Chris Double <chris....@gmail.com> wrote:
>Once the code for driver is written and compiles successfuly, is the
>correct process for running and testing it to use the service command
>to bring it up?
>
> service up /home/chris/mydriver/mydriver
Drivers that provide block or character special devices also need the
'-dev' option.
>And then shut it down when wanting to change it? Or is it sufficient to
>rebuild it and use 'refresh'?
Yes.
>Is there anything else that needs to be configured for Minix to know
>about the driver?
For block and chracter specials you also need to tell FS about the major
device.
For ethernet drivers, you need to tell inet (using /etc/inet.conf)
--
That was it. Done. The faulty Monk was turned out into the desert where it
could believe what it liked, including the idea that it had been hard done
by. It was allowed to keep its horse, since horses were so cheap to make.
-- Douglas Adams in Dirk Gently's Holistic Detective Agency
tyskdi...@yahoo.se
document: