From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Manuel Lauss <manuel.lauss@gmail.com>
Cc: Matt Turner <mattst88@gmail.com>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: what is the purpose of the following LE->BE patch to arch/mips/include/asm/io.h?
Date: Sat, 21 Feb 2015 03:27:15 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.11.1502210325450.8996@localhost> (raw)
In-Reply-To: <CAOLZvyFKc4fu6F5qOuzaAJg9wvkKhYrFcV35Vn1Hzo_sYVYfvQ@mail.gmail.com>
On Sat, 21 Feb 2015, Manuel Lauss wrote:
> On Sat, Feb 21, 2015 at 9:11 AM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> >
> > has anyone else ever needed to do this? or is this some weird,
> > one-off hack that perhaps applies *only* to some bizarre feature of
> > this board?
>
> My guess is that the peripherals attached to the internal bus
> only undestand little endian, and the bus doesn't do byte swaps when
> the core isn't configured for LE. I.e. the BE feature is only
> implemented in the mips core and the rest was designed for LE only.
ok, that makes sense ... so it's very likely a "issue with *this*
particular board and setup" kind of thing. thanks.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2015-02-21 8:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 9:53 what is the purpose of the following LE->BE patch to arch/mips/include/asm/io.h? Robert P. J. Day
2015-02-21 4:00 ` Matt Turner
2015-02-21 4:04 ` Matt Turner
2015-02-21 8:11 ` Robert P. J. Day
2015-02-21 8:23 ` Manuel Lauss
2015-02-21 8:27 ` Robert P. J. Day [this message]
2015-02-21 20:00 ` Maciej W. Rozycki
2015-02-21 21:03 ` Kevin Cernekee
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=alpine.LFD.2.11.1502210325450.8996@localhost \
--to=rpjday@crashcourse.ca \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@gmail.com \
--cc=mattst88@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 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.