From owner-freebsd-current Tue Nov 24 18:09:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11769 for freebsd-current-outgoing; Tue, 24 Nov 1998 18:09:45 -0800 (PST) (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 SAA11759 for ; Tue, 24 Nov 1998 18:09:43 -0800 (PST) (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 SAA02557; Tue, 24 Nov 1998 18:07:15 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811250207.SAA02557@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Rabson cc: "Norman C. Rice" , Bruce Evans , mjacob@feral.com, current@FreeBSD.ORG Subject: Re: Location for driver includes (was Re: Breakage in -current for theALPHA) In-reply-to: Your message of "Tue, 24 Nov 1998 11:14:53 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Nov 1998 18:07:15 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is it worth sorting includes based on the type of bus which the hardware > is attached to? Something like: > > sys/dev/include non-bus-specific includes > sys/dev/include/isa isa bus includes > sys/dev/include/pci pci bus includes > ... I don't think so; there's always the case where one device with several different bus interfaces but a consistent user-space presentation will spanner the works. IMHO, device-driver headers fall into two categories: - headers consumed only by the driver These should live with the driver source files. - headers consumed by users-space driver users These should be installed in a single location. They might want to live with the driver source files as well, although this may complicate the install process slightly. There should be a clear logical division between the two types of files, even if they're kept together. I don't see any actual virtue in separating the user-consumed headers from the driver source other than to make the install process easier. -- \\ 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