From owner-freebsd-current Fri May 30 13:23:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA06041 for current-outgoing; Fri, 30 May 1997 13:23:31 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA05991; Fri, 30 May 1997 13:21:14 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-40.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA21505 (5.67b/IDA-1.5); Fri, 30 May 1997 22:08:21 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id WAA05711; Fri, 30 May 1997 22:08:19 +0200 (CEST) X-Face: " Date: Fri, 30 May 1997 22:08:18 +0200 From: Stefan Esser To: Doug Rabson Cc: "Justin T. Gibbs" , Bruce Evans , current@FreeBSD.ORG, gurney_j@resnet.uoregon.edu, Stefan Esser Subject: Re: cvs commit: src/sys/sys interrupt.h src/sys/kern kern_intr.c References: <19970528143223.25591@x14.mi.uni-koeln.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Doug Rabson on Wed, May 28, 1997 at 02:07:33PM +0100 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On May 28, Doug Rabson wrote: > > If we do this, can the interrupt descriptor fiddling happen through a > function call? I don't want drivers to know what is inside this > structure. In fact I would be happiest if intrec wasn't declared in a > public header file at all but was private to kern_intr.c Yes, I agree. The interrupt descriptor is far to critical to be directly manipulated from drivers. It should be opaque to code outside kern_intr.c, and I will change the code into that direction with the next commit in that area. Regards, STefan