, Matt Thomas <email@example.com>
From: Ignatios Souvatzis <firstname.lastname@example.org>
Date: 08/15/2000 21:46:30
On Sat, Jul 22, 2000 at 02:07:58PM -0700, Jason R Thorpe wrote:
> On Sat, Jul 22, 2000 at 12:44:40PM -0700, Matt Thomas wrote:
> > I'd like to propose that the definition and use of
> > <machine/foo.h> be changed/modified. Currently
> > machine points to the port specific include directory
> > and then there's a <$arch$/foo.h> which points to the
> > machine archtecture files.
> The problem, of course, is kernel source files that do, e.g.:
> #include <machine/bus.h>
> Those are port-specific, not arch-specific.
> I think what we really want is:
> #include <arch/foo.h>
> #include <machine/foo.h>
> Userland sources should be changed to use <arch/foo.h>, kernel sources
> must still be able to do <machine/foo.h>.
> The <machine/...> API should not be accessible from userland, i.e. the
> symlink in /usr/include should go away, in favor of the <arch/...> link.
What about binaries that are in one machine and not the other, calling
ioctls for hardware that is only available in one or a few of the machines
in an arch? (e.g., some stuff used by Xamiga).