From: Kumar Gala <galak@kernel.crashing.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org,
Chris Friesen <chris.friesen@genband.com>,
paulus@samba.org, Scott Wood <scottwood@freescale.com>,
timur@freescale.com
Subject: Re: linux support for freescale e5500 core?
Date: Fri, 17 Sep 2010 00:17:08 -0500 [thread overview]
Message-ID: <7EDBB1DD-BB9D-417D-8F4E-B9D5D9E030EF@kernel.crashing.org> (raw)
In-Reply-To: <1284681832.30449.101.camel@pasglop>
On Sep 16, 2010, at 7:03 PM, Benjamin Herrenschmidt wrote:
> On Thu, 2010-09-16 at 16:26 -0600, Chris Friesen wrote:
>>> Sounds like a candidate for upstreaming the patch :-)
>>=20
>> 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. :)=20
>=20
> Heh. Well as long as only 970 had that bit ... but with e5500 coming =
up
> with that too, I suppose it makes -some- sense. Let's at least look at
> the approach you took and we can decide based on how invasive/ugly it
> is :-)
Not sure how the 970 bit worked, but this seems a bit problematic for =
switching between kernel and application for how we do this on =
e500mc/e5500. We'd have to touch the control bit on every exception =
path which seems ugly to me.
- k=
next prev parent reply other threads:[~2010-09-17 5:17 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
2010-09-17 0:03 ` Benjamin Herrenschmidt
2010-09-17 5:17 ` Kumar Gala [this message]
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=7EDBB1DD-BB9D-417D-8F4E-B9D5D9E030EF@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--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.