From owner-freebsd-current Mon Oct 19 13:44:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17131 for freebsd-current-outgoing; Mon, 19 Oct 1998 13:44:06 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17073 for ; Mon, 19 Oct 1998 13:43:58 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA01214; Mon, 19 Oct 1998 13:48:22 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810192048.NAA01214@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Julian Elischer cc: current@FreeBSD.ORG Subject: Re: vote:? reversion of BDE change please? In-reply-to: Your message of "Mon, 19 Oct 1998 12:52:49 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Oct 1998 13:48:22 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > A while ago bruce changed config(8) to not create the prototypes of > the interrupt handlers in the generated file ioconf.h. > > I don't understand his reasoning but it causes me quite a bit of grief. > He now has the rather odd idea that all device drivers should have their > interrupt handlers prototyped in isa_device.h. How isa_device.h is > supposed to know about al existing 3rd party drivers is apparenlty left as > an exercise for the reader.... > > This is 'odd' in my opinion because that means that if i want to > add a device driver I need to edit isa_device.h and add an entry for it. > I think this goes in the oposite direction from being able to add drivers > easily to the system. The change is actually in the right direction, as the goal is to remove the prototypes from global scope completely. Instead, ISA device drivers should register their interrupt handlers at attach time. I don't know if there's an example of this at the present time. > Particularly I'd like to know if it breaks tha alpha port, or > the new device framework? > As it is now it certainly breaks several automatic build processes I know > of (including the /usr/share/examples/drivers scripts) IMHO, the followup changes have been too slow coming. The new bus framework should completely obsolete interrupt handler prototypes, which may explain the pedestrian pace of the followups. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message