--93OMjyVt/yVb0YPi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Mar 06, 2006 at 08:27:36AM -0800, Garrett D'Amore wrote:
> Hmm.... we now have some kernel configs in evbmips that do not make
> sense for either big or little endian.
>=20
>     * OMSAL and MTX-1 are always little endian
>     * forthcoming ATHEROS AR531x based systems will always be big endian
>     * DBAU1XXX can be either endian (jumper selectable)
>     * Malta/PB1XXX?  probably also jumper selectable
>=20
> Is there a way to establish stuff in config so that:
>=20
>     1) an attempt to build a kernel with endianness that doesn't make
> sense fails in config(8), AND

I don't really understand that.  How is config(1) supposed to know what
endianness it is supposed to build for?  You want to flag it when it is
compiled?  Currently, config(1) is arch-agnostic, i.e. you can use the
same binary for any arch.

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"When I find the controls, I'll go where I like, I'll know where I want
to be, but maybe for now I'll stay right here on a silent sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.

--93OMjyVt/yVb0YPi
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)

iQEVAwUBRAxlbdgoQloHrPnoAQLWrgf+N3TCCbQXGzJ1FMDa0zGgU6cJpSBQAWzD
M+TJfzaqzKou4jiJcaKzED+dz6KP97QvH6q9EcQXasgwMRNyn3VqkAud6vA0Unxg
eilIiBpQ/Mjqk112lsl780G2U3zLLxTUST4dOeUVDl6D8bMG8aEFAWTfHQX0Mv7G
s+4fAazGMfTsHN0I1NGb1UrmEVWeQSaTPPOvZFiYijduFPHpoQHlAHpuzWYylvki
F5S2MI/BKsIvXmlWLfrfiZjcq4ZuWI1qS3EdX1DjlDxFgYsNrdryA1zTJcz75coW
OTyupFUfjmOrG/CGX9s++R6450fNtwuvDWCCD/nfARJpjJTv3ZGCJA==
=paHi
-----END PGP SIGNATURE-----

--93OMjyVt/yVb0YPi--