From: Dan Malek <dan@embeddededge.com>
To: Luca Risso <Luca.Risso@marconi.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: head_8xx.S
Date: Fri, 06 Feb 2004 13:48:53 -0500 [thread overview]
Message-ID: <4023E195.6050601@embeddededge.com> (raw)
In-Reply-To: OFBF7609F1.4667B3D5-ONC1256E32.002AD496@uk.marconicomms.com
Luca Risso wrote:
> With some further investigation I bypassed the problem removing the "tophys"...
There are some subtle VM changes in 2.6 that require code changes to the
TLB exception handlers and a few other places. I know what they are, I just
don't have any active 8xx projects right now so I have to find time and boards
to get this done and tested.
Thanks.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-06 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 8:08 head_8xx.S Luca Risso
2004-02-06 18:48 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-03 18:39 head_8xx.S Luca Risso
2004-02-05 20:02 ` head_8xx.S Dan Malek
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=4023E195.6050601@embeddededge.com \
--to=dan@embeddededge.com \
--cc=Luca.Risso@marconi.com \
--cc=linuxppc-dev@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).