From owner-freebsd-usb@FreeBSD.ORG Tue May 24 21:25:31 2011 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 724F4106566B for ; Tue, 24 May 2011 21:25:31 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe06.c2i.net [212.247.154.162]) by mx1.freebsd.org (Postfix) with ESMTP id BA1538FC20 for ; Tue, 24 May 2011 21:25:30 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=NvrFngl24Vvwb7eBef0tfsytOWEnP/WlkqxQrRnklhk= c=1 sm=1 a=SvYTsOw2Z4kA:10 a=kWWxOIFCDSEA:10 a=WQU8e4WWZSUA:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=VrRaG_UlQmsBQoRoqskA:9 a=wPNLvfGTeEIA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe06.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 130288785; Tue, 24 May 2011 23:25:29 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Tue, 24 May 2011 23:24:15 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.2-STABLE; KDE/4.4.5; amd64; ; ) References: <4DDC20DF.6060805@gmail.com> In-Reply-To: <4DDC20DF.6060805@gmail.com> X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq,NwSZ4V" =?iso-8859-1?q?=7CLR=2E+tj=7Dg5=0A=09=25V?=,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( =?iso-8859-1?q?=0A=09=3AAuzV9=3A=2EhESm-x4h240C=609=3Dw?= MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201105242324.15541.hselasky@c2i.net> Cc: freebsd-drivers@freebsd.org Subject: Re: traditional syscalls with DRIVER_MODULE ???? X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 May 2011 21:25:31 -0000 On Tuesday 24 May 2011 23:19:27 Jim Bryant wrote: > if i add such an interface to the current DRIVER_MODULE version, how > would i go about NOT having DRIVER_MODULE create the devfs entries? i > would prefer to have the devfs entries handled by make_dev, so to have > access to the desired syscalls. Look at /sys/dev/usb/serial/ulpt.c For a simple example. More abstract: "cd /usr/ports/multimedia/cuse4bsd" and "man libusb20" --HPS