Date: Tue, 6 Jan 1998 14:31:38 -0300 From: daniel_sobral@voga.com.br To: mike@smith.net.au Cc: hackers@FreeBSD.ORG Subject: Re: Device Driver Message-ID: <83256584.005F6BFE.00@papagaio.voga.com.br>
next in thread | raw e-mail | index | archive | help
> > * My device driver should be used mainly by other > > kernel routines. How should I proceed? Is there a > > standard interface or something? > You need to be more specific about this before it's > possible to give a really useful answer. Look at the > network drivers and disk drivers for two sorts of > drivers that are used primarily by other kernel code. My mind got a panic with the Too Many Files error, and, unfortunately, its debugging tools are almost non-existant, and very time-consuming to use... ;-) Anyway, bpf.c helped with my first question (how to deal with the sloooooow i/o), and Julian's answer dealt with the third. So, let's put the second question (above) in another way. The card I'm writing a device for is a cryptography card. It will be using by networking code (not mine) directly in kernel. So, the device will be accessed most of the time from other parts of the kernel. Now, I understand cdevsw and bdevsw provide a standard interface between the device and userland processes, but is there any kind of standard interface for use by other routines in-kernel? -- Daniel C. Sobral (8-DCS) Daniel_Sobral@voga.com.br
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?83256584.005F6BFE.00>