Subject: Re: evbsh3 -> evbsh3{el,bl}
To: Todd Vierling <tv@wasabisystems.com>
From: None <itojun@iijlab.net>
List: port-sh3
Date: 01/04/2001 09:22:14
>: > it makes me wonder.. does it make sense to have multiple MACHINE_ARCH
>: > under single sys/arch/*?
>: >
>: > sys/arch/sh3 SH3 specific files, like sys/arch/mips
>: > sys/arch/dreamcast MACHINE=dreamcast MACHINE_ARCH=sh3el
>: > sys/arch/mmeye MACHINE=mmeye MACHINE_ARCH=sh3eb
>: > sys/arch/evbsh3 MACHINE=evbsh3 MACHINE_ARCH=sh3eb or sh3el
>: > (depending on kernel config file)
>: Yah, that seems perfectly fine.
>This looks fine to me. MACHINE_ARCH doesn't necessarily determine directory
>names -- it mainly needs to distinguish processor basics (endianness, word
>sizes, etc.).
i remember another thing - arch/evbsh3/include/endian_machdep.h goes
a little bit tricky. is it okay to install endian_machdep_{eb,el}.h
depending on MACHINE_ARCH settings?
itojun