From: Dan Malek <dan@mvista•com>
To: "Marti, Felix" <fmarti@desanasystems•com>
Cc: "'Troy Benjegerdes'" <hozer@drgw•net>,
Ralph Blach <rcblach@raleigh•ibm.com>,
Linix PPC Emmbedded <linuxppc-embedded@lists•linuxppc.org>
Subject: Re: using the little endian bit 4xx mmu
Date: Fri, 24 Aug 2001 00:26:00 -0400 [thread overview]
Message-ID: <3B85D758.572A0AD8@mvista.com> (raw)
In-Reply-To: 1DF71FB881F4D311A6B700C04FA06A1AC437B4@orca.desanasystems.com
"Marti, Felix" wrote:
>
> I hacked it in a few hours:
> in arch/ppc/kernel/head_4xx.S
Ugh....we have discussed this in the past. What is the advantage
of using this feature? All of the existing drivers and I/O macros
are designed to handle mixing of endian modes depending upon the
processor and I/O device. All this does is complicate a standard
set of programming interfaces that everyone expects to work as they
have in the past.
The ability to set a feature flag in the PTE and transfer that to
the TLB isn't a solution to anything. You are going to have to
rewrite all of the standard functions, macros, and device drivers
to utilize this feature, and we haven't seen any benefit to doing this.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-08-24 4:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-23 18:28 using the little endian bit 4xx mmu Marti, Felix
2001-08-24 4:26 ` Dan Malek [this message]
2001-08-24 10:41 ` Ralph Blach
-- strict thread matches above, loose matches on Subject: below --
2001-08-24 21:21 Marti, Felix
2001-08-23 17:39 Ralph Blach
2001-08-23 17:53 ` Troy Benjegerdes
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=3B85D758.572A0AD8@mvista.com \
--to=dan@mvista$(echo .)com \
--cc=fmarti@desanasystems$(echo .)com \
--cc=hozer@drgw$(echo .)net \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=rcblach@raleigh$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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