Re: new to driver coding

[ Available lists | Index of freebsd-hackers | Month of Mar 1999 | Week of 10 Mar 1999 | Raw email | View thread | Wrap long lines | Reply | Tag ]
From
Julian Elischer <julian@whistle.com>
Date
10 Mar 1999 18:24:51
Subject
Re: new to driver coding
Message-ID
Pine.BSF.3.95.990310181853.1249K-100000@current1.whistle.com

In reply to
Replies

[ Hide this part ]
check out /usr/share.examples/drivers/psuedo[mumble]
this is a shellscript that writes a dummy driver, and even links it into
the kernel and compile sit for you..

edit to taste..

(I haven't run it for 6 months so it may need a few slight cleanups to
work on a new system)

julian


On Wed, 10 Mar 1999, Wayne Cuddy wrote:

>
>
> I have been reading any information I can find, which is very little, on
> writing unix device drivers. Specifically I would like information on
> FreeBSD;)
>
> I really want to start simple by writing a character driver that is not
> attached to a REAL device but just holds on to some memory and allows me to
> writing some bytes in (write()) and read them back (read()).
>
> I don't think this will be very difficult but I need some detailed information
> specific to FreeBDS on what header files I need to include and how to build my
> driver as part of the kernel. What directory should I build my driver in?
> What entry point will the kernel call when the system boots so I can print a
> pretty little string from my driver showing a sample initialization.
>
>
> I am kinda in the dark here to specifics of this so ALL help is greatly
> appreciated.
>
> Thanks,
> Wayne
>
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message
>



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message



Elapsed time: 0.138 seconds