Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: ppopov@embeddedalley.com
To: Prashant Viswanathan <vprashant@echelon.com>
Cc: 'Manish Lachwani' <mlachwani@mvista.com>, linux-mips@linux-mips.org
Subject: Re: Big Endian au1550
Date: Wed, 27 Apr 2005 20:57:23 -0700	[thread overview]
Message-ID: <42705F23.3000402@embeddedalley.com> (raw)
In-Reply-To: <5375D9FB1CC3994D9DCBC47C344EEB590165465B@miles.echelon.echcorp.com>

Prashant Viswanathan wrote:

>>Prashant Viswanathan wrote:
>>
>>    
>>
>>>Is there a reason why the default configuration file doesn't support Big
>>>Endian for the dbAu1550?
>>>
>>>Even if I edit .config to set the endianness to "BIG" it seems to change
>>>      
>>>
>>to
>>    
>>
>>>"Little Endian" every time a make is run.
>>>
>>>Thanks
>>>Prashant
>>>
>>>
>>>
>>>
>>>      
>>>
>>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.
>>
>>So, it appears that if you have SOC_AU1X00 set, it will always be
>>configured little endian.
>>    
>>
>
>Is there a reason for this? 
>  
>
It's the more common configuration.

>Many months ago I was able to build a big-endian image and load it on my
>dbAu1550 (also configured to be BE). I just decided to update and now I find
>that it is almost as if it is not meant to be built BE.
>  
>
BE should be fine too.  We should fix this in Kconfig.

Pete

  reply	other threads:[~2005-04-28  3:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28  3:44 Big Endian au1550 Prashant Viswanathan
2005-04-28  3:57 ` ppopov [this message]
2005-04-28  8:56   ` JP
  -- strict thread matches above, loose matches on Subject: below --
2005-04-28 18:18 Prashant Viswanathan
2005-04-28  2:14 Prashant Viswanathan
2005-04-28  2:23 ` Manish Lachwani
2005-02-23 18:30 Prashant Viswanathan
2005-02-23 11:22 JP Foster
2005-02-23 11:23 ` Ralf Baechle
     [not found] ` <000301c5199d$3154ad40$0300a8c0@Exterity.local>
2005-02-23 12:05   ` JP Foster
2005-02-23 13:17     ` Ralf Baechle
2005-02-23 15:03     ` Dan Malek
2005-02-23 15:06       ` Ralf Baechle
2005-02-23 17:02         ` Dan Malek
2005-03-04 20:23           ` Ralf Baechle
2005-03-04 20:44             ` Dan Malek
2005-02-23 16:57       ` Thomas Sailer
2005-02-23 17:47         ` Pete Popov
     [not found]         ` <000001c519d1$84d9c250$0300a8c0@Exterity.local>
2005-02-24 10:04           ` JP Foster
2005-02-24 16:15             ` Peter Popov
2005-02-24 17:09               ` JP Foster
2005-02-25 17:29               ` JP Foster
2005-02-24 16:19             ` Clem Taylor

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=42705F23.3000402@embeddedalley.com \
    --to=ppopov@embeddedalley.com \
    --cc=linux-mips@linux-mips.org \
    --cc=mlachwani@mvista.com \
    --cc=vprashant@echelon.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox