Date: Sat, 26 Jun 1999 22:06:53 -0600 From: Warner Losh <imp@harmony.village.org> To: arch@freebsd.org Subject: Directory layouts revisited Message-ID: <199906270406.WAA08237@harmony.village.org>
next in thread | raw e-mail | index | archive | help
I posted the following to -committers and realized that this is a more appropriate forum for such discussions. I'll redirect any discussions there to this list. In general, yes, I am trying to minimize the trivial differences between the various *BSD oses, at least when it comes to some aspects of driver code. I'm working on a newconfig shim, which if successful, will allow any driver to be imported from NetBSD/OpenBSD with, hopefully, no or very few changes. Warner To: committers@freebsd.org Subject: Moving isa to dev/isa Date: Sat, 26 Jun 1999 19:00:07 -0600 From: Warner Losh <imp@harmony.village.org> What are the objections to moving isa -> dev/isa and pci -> dev/pci. As I see it there is very little down side (some extra junk in the attic), while on the positive side it makes it easier to import new config style drivers if we have the same hierarchy as other systems. I think this will outweigh the minor inconvenience in the repository move. I ask this because I'm finding that importing newconfig drivers in the pccard work I'm doing needlessly complicated by the current directory structure. Since I really want to have a set of working sims within newbus for new-config based drivers, I see this as an issue that I must raise. The exact consequences of this are a need to place a lot of ugly #ifdef __FreeBSD__ around the includes of dev/isa/* and dev/pci/* in all .c or .h files that I'm trying to bring in. I've done that in my tree, but I'd like to minimize trivial differences like this if I can at all avoid them. Comments? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906270406.WAA08237>