From owner-cvs-all Mon May 7 17:38:11 2001 Delivered-To: cvs-all@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 7DD1337B43C; Mon, 7 May 2001 17:38:07 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f480bnG95927; Mon, 7 May 2001 17:37:50 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200105072355.f47NtpB14404@hak.lan.Awfulhak.org> Date: Mon, 07 May 2001 17:33:36 -0700 (PDT) From: John Baldwin To: Brian Somers Subject: Re: cvs commit: src/sys/dev/digi digi.c digi.h digi_isa.c digi_p Cc: cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-May-01 Brian Somers wrote: >> On 07-May-01 John Baldwin wrote: >> Well, having checked the code, it seems you don't use fast interrupt >> handlers, >> so you didn't need COM_LOCK to begin with and you don't need the mutex you >> are >> using right now. tty drivers won't be locked until the tty subsystem is >> locked >> and we figure out how we are going to lock tty data structures. > > So should I just pull out the mutex stuff for now ? Yes, please. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message