public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Sujoy Ray <raysujoy@yahoo.com>
To: Peter Korsgaard <jacmet@gmail.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] IXP425 Big Endian Mode
Date: Fri, 10 Jun 2005 10:34:00 -0000	[thread overview]
Message-ID: <20050610103437.10287.qmail@web53401.mail.yahoo.com> (raw)
In-Reply-To: <9305ca41050610025175f9a8fe@mail.gmail.com>

Hello Peter,

Thanks for your suggestion!

I am still having one doubt -

When I compare the code(pls read elf file) compiled in
little endian mode with the one in big endian mode
using objdump - I see that bytes are swapped. E.g a
code which looks like E6000021 in little endian mode
becomes 210000E6 in big endian mode. Now, during
instruction fetch and decode cycle, how processor
decodes this big endian instruction, when the state of
the processor is in little endian? Pls note that the
processor is in little endian mode and trying to
execute a big-endian instruction. So, byte 0 for it
will be E6 of the big endian instruction, but the
correct one should be 21. 

I think 'am confused in some way. Please help me to
come out from this confusion.

Regards,
Sujoy Ray.


--- Peter Korsgaard <jacmet@gmail.com> wrote:

> On 6/10/05, Sujoy Ray <raysujoy@yahoo.com> wrote:
> > big-endian order. Now, I have a question - how the
> > processor executes the above mentioned code, when
> it
> > is in little endian mode. I know for sure that
> there
> > is some way to do that because the code works
> fine. I
> > think 'am missing some basic concept - any
> suggestion
> > will be highly appreciated.
> 
> big/little endian mode only matters for 8 and 16bit
> accesses, and the
> instructions are 32bit.
> 
> See
>
http://www.intel.com/design/network/applnots/25423701.pdf
> for details.
> 
> -- 
> Bye, Peter Korsgaard
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2005-06-10 10:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-10  8:41 Sujoy Ray
2005-06-10  9:51 ` Peter Korsgaard
2005-06-10 10:34   ` Sujoy Ray [this message]
2005-06-10 11:04     ` jerzy dyrda
     [not found] <20050918202057.38425.qmail@web53410.mail.yahoo.com>
2005-09-19  4:31 ` Sujoy Ray

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=20050610103437.10287.qmail@web53401.mail.yahoo.com \
    --to=raysujoy@yahoo.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=jacmet@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).