Date: Tue, 24 Nov 1998 18:07:15 -0800 From: Mike Smith <mike@smith.net.au> To: Doug Rabson <dfr@nlsystems.com> Cc: "Norman C. Rice" <nrice@emu.sourcee.com>, Bruce Evans <bde@zeta.org.au>, mjacob@feral.com, current@FreeBSD.ORG Subject: Re: Location for driver includes (was Re: Breakage in -current for theALPHA) Message-ID: <199811250207.SAA02557@dingo.cdrom.com> In-Reply-To: Your message of "Tue, 24 Nov 1998 11:14:53 GMT." <Pine.BSF.4.01.9811241056140.21711-100000@herring.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811250207.SAA02557>