Date: Fri, 19 Nov 2010 17:20:15 +0100 From: Hans Petter Selasky <hselasky@c2i.net> To: freebsd-usb@freebsd.org Cc: Lev Serebryakov <lev@serebryakov.spb.ru> Subject: Re: Two questions: how to specify module-load function for driver module and which name of driver is better (according to "standards") Message-ID: <201011191720.15402.hselasky@c2i.net> In-Reply-To: <441397602.20101119185527@serebryakov.spb.ru> References: <441397602.20101119185527@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 19 November 2010 16:55:27 Lev Serebryakov wrote: > Hello, Freebsd-usb. > > I've implemented driver (ucom-subdriver) for MosChip 7820 and 7840 > USB2COM multiport bridges. I have two questions: > Hi, > (1) How should I specify module-load function? DRIVER_MODULE() > doesn't help much. I need to run some code only once, at very > beginning, not for each probe/attach. GEOM modules have methods for > it, but I can not find such methods for drivers. Look at ubt_modevent in sys/netgraph/bluetooth/drivers/ubt/ng_ubt.c. Or use a so-called SYSINIT() or SYSUNINIT(). > > (2) Which name should I choose? Working name of module/driver/device > is "mos7840", but it seems, that it is bad name: > (a) All existing ucom-based drivers is "uXXXcom" > (b) Driver instances looks ugly (like "mos78400") umos78400 ? > > Is "umos7840com" good name or it is too long? :) We have "umoscom" > driver for older MosChip chip in base already. Maybe someone else has some comments. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201011191720.15402.hselasky>