>Actually, since gcc automatically defines either __LITTLE_ENDIAN__ or
>__BIG_ENDIAN__, can't we just use that define in endian_machdep.h?

	i used that in sys/arch/evbsh3/include, however, i'm a bit worried
	about the future - if we fetch something from
	ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-1.9/evbsh3/binary/sets,
	will it be big-endian or little?  i think it easier to split
	evbsh3{bl,el} anyways.

itojun