Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 20 Jan 2006 08:24:55 +0100
From:      "Norbert Koch" <NKoch@demig.de>
To:        "Kimberly Davis" <kimblydavis@yahoo.com>, "John Baldwin" <jhb@freebsd.org>, <freebsd-drivers@freebsd.org>
Subject:   RE: Interrupt Handlers and Driver to Driver Communication
Message-ID:  <000101c61d92$9ca927c0$4801a8c0@ws-ew-3.demig.intra>
In-Reply-To: <20060119213555.28899.qmail@web30003.mail.mud.yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
 
> 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?




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000101c61d92$9ca927c0$4801a8c0>