On Sun, 7 Sep 2003, David Young wrote:

> I propose that the platform-independent Atheros HAL header files go
> into src/sys/contrib/dev/ath/, and the i386-dependent objects go into
> src/sys/contrib/arch/i386/dev/ath/.
>
> Just to be perfectly clear, here is the FreeBSD layout (left column)
> and the NetBSD layout that I propose (right column) for comparison,
>
> FreeBSD src/sys/contrib	 	-->		NetBSD src/sys/contrib
> -----------------------				----------------------
> dev/ath/COPYRIGHT					dev/ath/COPYRIGHT
> dev/ath/README						dev/ath/README
> dev/ath/ah.h						dev/ath/ah.h
> dev/ath/ah_desc.h					dev/ath/ah_desc.h
> dev/ath/ah_devid.h					dev/ath/ah_devid.h
> dev/ath/version.h					dev/ath/version.h
> dev/ath/freebsd/ah_osdep.c          dev/ath/ah_osdep.c
> dev/ath/freebsd/ah_osdep.h          dev/ath/ah_osdep.h
> dev/ath/freebsd/opt_ah.h			dev/ath/opt_ah.h

That file looks a lot like the ones config makes. Can it have a different
name?

Would it make more sense to have these under dev/ath/netbsd/... ?

> dev/ath/freebsd/ah_if.m				dev/ath/ah_if.m
> dev/ath/freebsd/i386-elf.hal.o.uu	arch/i386/dev/ath/i386-elf.hal.o.uu
>
> As the HAL becomes available for new architectures, I will add
> arch/macppc/dev/ath/, etc.

Will there be more than one file per architecture? It might be fine to
have arch/i386/dev/i386-elf.hal.o.uu.

Take care,

Bil