From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 21 11:26:55 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3425106566C for ; Wed, 21 Sep 2011 11:26:55 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.c2i.net [212.247.154.66]) by mx1.freebsd.org (Postfix) with ESMTP id 52E518FC13 for ; Wed, 21 Sep 2011 11:26:54 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=yVKV3zusvCapyMfYJBNW2j35FMEuTKq6vh/tt/1L5+g= c=1 sm=1 a=SvYTsOw2Z4kA:10 a=d1FtHp7U9EQA:10 a=WQU8e4WWZSUA:10 a=Q9fys5e9bTEA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=uLdibwT2YJnq9gv0iqYA:9 a=PUjeQqilurYA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe03.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 14396916; Wed, 21 Sep 2011 13:26:52 +0200 From: Hans Petter Selasky To: freebsd-hackers@freebsd.org, geoffrey levand Date: Wed, 21 Sep 2011 13:24:01 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.2-STABLE; KDE/4.4.5; amd64; ; ) References: <201109202202.19481.hselasky@c2i.net> In-Reply-To: X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq, NwSZ4V"|LR.+tj}g5 %V,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( :AuzV9:.hESm-x4h240C`9=w MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201109211324.01978.hselasky@c2i.net> Cc: Subject: Re: Sharing device driver between kernel and user space X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Sep 2011 11:26:55 -0000 On Wednesday 21 September 2011 08:05:25 geoffrey levand wrote: > I think you misunderstood what i need. If i got it right then cuse4bsd > allows user applications to create char devices, right ? I do not want to > create character devices from user space. My VUART kernel module should > provide the character device for user space. What i need is a way to > synchronize access to VUART data between kernel and user space. The kernel > device driver should provide 2 interfaces: one for user space (through > char dev) and the other for kernel land. The problem is how to synchronize > the access to VUART data between 2 lands because VUART cannot be shared by > both simultaneously. Ok, I'm not a PS3 expert. --HPS