Re: RPX Classic/Lite and byte ordering

[mferrell@mvista.com]

[-- Attachment #1: Type: text/plain, Size: 1890 bytes --]

I was talking with some people who work with the Embeded Planet RPX stuff and
apparently a couple of chips on the system are wired backwards.  The
developers could remember "exacly" which models they ran across that where
wired this way, but he remembered that it only showed up when dealing with
double words.  Dunno if that helps.

As far as the PPC stuff, a few can be little endian, but under linux they are
all big endian so far.


On Tue, Apr 03, 2001 at 11:16:11AM +1000, Brendan J Simon wrote:
> Nope.  A powerpc cross compiler *should* produce *exactly* the same code 
> as a naitive compiler.  This assumes you are using exactly the same 
> version of gcc, gas and glibc.  Having said that, I just remembered that 
> the PowerPC architecture can be big endian or little endian.  There must 
> be a configuration option when building the compilers that sets the 
> default.  You should be able to specify which you want, either in the 
> spec file or on the command line.
> 
> I've had a look at my spec file.  Try the -mbig-endian (or -mbig) for 
> big endian.  Try -mlittle-endian (or -mlittle) for little endian.  I 
> prefer -mbig-endian or -mlittle-endian because they are a lot clearer 
> than -mbig or -mlittle.
> 
> My spec file has the following:
> 
> *multilib_defaults:
> mbig mcall-linux
> 
> *cpp_endian_default:
> %(cpp_endian_big)
> 
> *cc1_endian_default:
> %(cc1_endian_big_spec)
> 
> 
> Regards,
> Brendan Simon.
> 
> 
> 
> Tim Bowman wrote:
> 
> > Would cross-compiling the kernel on an x86 produce different ordering
> > than compiling natively on a PowerPC (which is how I am building it)? 
> > Maybe I need to build it on an x86?
> 
> 
> 
> 
> 
> To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

-- 
Mark Ferrell <mferrell@mvista.com>
Monta Vista Software Inc. <http://www.mvista.com>

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]