Garrett D'Amore wrote: > Btw, I would normally discourage creation of a new block device driver > -- there are lots of interaction issues with block devices and bits of > userland code (hal, vold, format, etc.) that have knowledge of specific > device drivers. While the kernel code is relatively straight-forward, > you wind up having to touch a bunch of userland bits of code if you want > to support regular filesystems on them.
Other than my aio_cancel64 issue, I am working pretty hard trying to get mkfs operational. I am having to fill out tons of structures and support all sorts of IOCTLs. > This also allows you to elide a lot of code from your driver, since you > only need to provide generic block read/write routines, and can skip the > whole question about labeling, formatting, etc. Of course, to do this, > your driver has to be integrated in ON, since the blk2scsa interfaces > are Consolidation Private at the moment. I am reticent to change horses mid-stream here. But I where would I even begin to learn how to do this? Thanks for the advice. -Adam _______________________________________________ driver-discuss mailing list driver-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/driver-discuss
