From owner-freebsd-drivers@FreeBSD.ORG Fri Jan 20 07:28:03 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE39916A42C; Fri, 20 Jan 2006 07:28:03 +0000 (GMT) (envelope-from NKoch@demig.de) Received: from server.absolute-media.de (server.absolute-media.de [213.239.231.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3485843D48; Fri, 20 Jan 2006 07:28:02 +0000 (GMT) (envelope-from NKoch@demig.de) Received: from localhost (unknown [127.0.0.1]) by server.absolute-media.de (Postfix) with ESMTP id 2E3ECBCE2C; Fri, 20 Jan 2006 08:28:01 +0100 (CET) Received: from server.absolute-media.de ([127.0.0.1]) by localhost (server [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16026-06; Fri, 20 Jan 2006 08:27:55 +0100 (CET) Received: from firewall.demig (p508391F0.dip0.t-ipconnect.de [80.131.145.240]) by server.absolute-media.de (Postfix) with ESMTP id 43DC2B92EE; Fri, 20 Jan 2006 08:27:55 +0100 (CET) Received: from ws-ew-3 (ws-ew-3.demig.intra [192.168.1.72]) by firewall.demig (8.13.5/8.13.4) with SMTP id k0K7OrfO015644; Fri, 20 Jan 2006 08:24:56 +0100 (CET) (envelope-from NKoch@demig.de) From: "Norbert Koch" To: "Kimberly Davis" , "John Baldwin" , Date: Fri, 20 Jan 2006 08:24:55 +0100 Message-ID: <000101c61d92$9ca927c0$4801a8c0@ws-ew-3.demig.intra> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <20060119213555.28899.qmail@web30003.mail.mud.yahoo.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0 Importance: Normal X-Virus-Scanned: by amavisd-new X-Virus-Scanned: by amavisd-new at absolute-media.de Cc: Subject: RE: Interrupt Handlers and Driver to Driver Communication X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2006 07:28:04 -0000 > The results of that test are as follows > > >nm driver1.ko | grep g_status > 00004239 B g_status > > It doesn't make sense to do that for the client_driver (driver2) > since the variable isn't defined there or even externed there. I > use the API from driver1 (driver_one_is_complete) to find out the > value of g_status. So, what about 'nm driver[12].ko | grep driver_one_is_complete' ? Does driver_one_is_complete() do a test-and-reset operation on g_status? Did you have a look at the assembly output of this function? What are your compiler (optimization) settings?