vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Claudio Jeker wrote: > On Sat, Sep 01, 2007 at 08:53:24AM -0400, David H. Lynch Jr. wrote: > >> Jonathan Gray wrote: >> >>> A very brief overview can be found here: >>> http://www.openbsd.org/papers/openco...ers/index.html >>> >>> Most commonly used kernel functions should be documented in section 9 >>> man pages, and there is of course a large body of existing code in the tree >>> which does similiar things. Any specific questions can be addressed to >>> tech@ >>> >> Thank you that provided a good start >> >> Some questions that immediately come to mind: >> >> How doe the load able module driver model relate to the in kernel model? >> Can I just write a Cardbus/PCMCIA driver much as I would for in kernel >> but build it as a module and expect that it will work ? >> >> > > OpenBSD does not support driver modules. > I am a bit gunshy about OpenBSD at the moment having misread the license and then misinterpreted it on misc@openbsd.org. But googling OpenBSD Driver Modules, produces numerous hits and examples. And I am pretty sure I have built and tested an example character device driver. > >> The driver am working with expects to use a small set of minor numbers >> as well as ioctl's. >> >> Am I correct that MAKEDEV seems to be the blessed way of creating the >> /dev entries ? >> > > Yes. > > >> If so how does MAKEDEV know about new drivers ? >> > > By adding them to the script. > > >> After incorporating my driver I can mknod to create the /dev eentries, >> but MAKEDEV does not seem to know about my driver. >> >> Is there any in kernel scheme to automate the creation of /dev entries ? >> >> > > Nope. |