From: Manish Lachwani <mlachwani@mvista.com>
To: ellis@spinics.net
Cc: linux-mips@linux-mips.org
Subject: Re: Little Endian
Date: Wed, 16 Mar 2005 15:10:27 -0800 [thread overview]
Message-ID: <4238BCE3.2030003@mvista.com> (raw)
In-Reply-To: <200503162247.j2GMlXPh017146@localhost.localdomain>
ellis@spinics.net wrote:
>I'm just starting to look at a porting project. The board I'll
>be using is little endian and the CVS version of the kernel
>source doesn't have anything but big endian in the config
>menu. Does little endian work at all and if so, how do I
>select it?
>
>--
>http://www.spinics.net/linux/
>
>
>
When you do "make menuconfig", under "Machine Selection" item, there is
an option called "Generate little endian code". Is this what you are
looking for? This is a config option CONFIG_CPU_LITTLE_ENDIAN. This is
defined in arch/mips/Kconfig:
config CPU_LITTLE_ENDIAN
bool "Generate little endian code"
default y if ACER_PICA_61 || CASIO_E55 || DDB5074 || DDB5476 ||
DDB5477 || MACH_DECSTATION
|| IBM_WORKPAD || LASAT || MIPS_COBALT || MIPS_ITE8172 || MIPS_IVR ||
SOC_AU1X00 || NEC_OSPREY || OLIVETTI_M700 || SNI_RM200_PCI ||
VICTOR_MPC30X || ZAO_CAPCELLA
default n if MIPS_EV64120 || MIPS_EV96100 || MOMENCO_OCELOT ||
MOMENCO_OCELOT_G || SGI_IP22 || SGI_IP27 || SGI_IP32 || TOSHIBA_JMR3927
help
Some MIPS machines can be configured for either little or big
endian
byte order. These modes require different kernels. Say Y if your
machine is little endian, N if it's a big endian machine.
Thanks
Manish Lachwani
next prev parent reply other threads:[~2005-03-16 23:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 22:47 Little Endian ellis
2005-03-16 23:10 ` Manish Lachwani [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-16 1:04 Little endian Nicu Popovici
2000-12-15 18:28 ` Kevin D. Kissell
2000-12-15 18:28 ` Kevin D. Kissell
2000-12-16 11:45 ` Ralf Baechle
2000-12-17 12:51 ` Geert Uytterhoeven
2000-12-17 11:09 ` Carsten Langgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4238BCE3.2030003@mvista.com \
--to=mlachwani@mvista.com \
--cc=ellis@spinics.net \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.