From: Matt Porter <porter@cox.net>
To: "Curry, Diane" <dcurry@infiniswitch.com>
Cc: "Linuxppc Newsgroup (E-mail)" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 405GP TLBHI "E" field
Date: Tue, 21 May 2002 10:03:40 -0700 [thread overview]
Message-ID: <20020521100340.A17617@home.com> (raw)
In-Reply-To: <3D296C067098F149B11A8F4FC37C054606F4E8@EXVS1.ops.infiniswitch.com>; from dcurry@infiniswitch.com on Tue, May 21, 2002 at 10:04:21AM -0400
On Tue, May 21, 2002 at 10:04:21AM -0400, Curry, Diane wrote:
>
> Hello,
> I'm running 2.4.14pre3 on a custom ppc405GP board that has a little-endian device
> on the peripheral bus. I've modified the finish_tlb_load code path to recognize the
> physical address of the device and set the "E" bit in the tlb entry for the page.
> The driver and device work fine using this feature, but what I did in finish_tlb_load
> is not a reasonable solution. Is there a kernel interface callable from a driver
> that can be used to specify the endianness of a memory range, and set the "E"
> bit appropriately? If not, are there any plans to implement this capability?
There are no plans (that I've ever heard of) to implement E bit support
because it has no value in Linux. Use read*/write* to access your little
endian device. PPC has lwbrx/stwbrx for a reason...use them...they are
included for free.
Regards,
--
Matt Porter
porter@cox.net
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-05-21 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 14:04 405GP TLBHI "E" field Curry, Diane
2002-05-21 17:03 ` Matt Porter [this message]
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=20020521100340.A17617@home.com \
--to=porter@cox.net \
--cc=dcurry@infiniswitch.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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 NNTP newsgroup(s).