From: "Chris Friesen" <cfriesen@nortel.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Chris Friesen <chris.friesen@genband.com>,
Scott Wood <scottwood@freescale.com>,
paulus@samba.org, timur@freescale.com, linuxppc-dev@ozlabs.org
Subject: Re: linux support for freescale e5500 core?
Date: Thu, 16 Sep 2010 16:26:20 -0600 [thread overview]
Message-ID: <4C92998C.7000903@nortel.com> (raw)
In-Reply-To: <1284674628.30449.98.camel@pasglop>
On 09/16/2010 04:03 PM, Benjamin Herrenschmidt wrote:
> On Thu, 2010-09-16 at 15:44 -0600, Chris Friesen wrote:
>> Right. We currently use a 970-series cpu and have implemented a
>> per-process flag to indicate whether 32-byte mode is needed or not.
>> We'd have to do something similar with the new cpu.
>
> Sounds like a candidate for upstreaming the patch :-)
As I recall we proposed upstreaming it a while back but there wasn't a
lot of interest since it's most useful in supporting poorly-written
legacy apps. :)
Chris
--
The author works for GENBAND Corporation (GENBAND) who is solely
responsible for this email and its contents. All enquiries regarding
this email should be addressed to GENBAND. Nortel has provided the use
of the nortel.com domain to GENBAND in connection with this email solely
for the purpose of connectivity and Nortel Networks Inc. has no
liability for the email or its contents. GENBAND's web site is
http://www.genband.com
next prev parent reply other threads:[~2010-09-16 22:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 20:06 linux support for freescale e5500 core? Chris Friesen
2010-09-16 21:39 ` Scott Wood
2010-09-16 21:44 ` Chris Friesen
2010-09-16 22:03 ` Benjamin Herrenschmidt
2010-09-16 22:26 ` Chris Friesen [this message]
2010-09-17 0:03 ` Benjamin Herrenschmidt
2010-09-17 5:17 ` Kumar Gala
2010-09-17 5:33 ` Benjamin Herrenschmidt
2010-09-17 6:36 ` Chris Friesen
2010-09-17 7:39 ` Kumar Gala
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=4C92998C.7000903@nortel.com \
--to=cfriesen@nortel.com \
--cc=benh@kernel.crashing.org \
--cc=chris.friesen@genband.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=scottwood@freescale.com \
--cc=timur@freescale.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.