linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Chris Friesen <cfriesen@nortel.com>
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: Fri, 17 Sep 2010 10:03:52 +1000	[thread overview]
Message-ID: <1284681832.30449.101.camel@pasglop> (raw)
In-Reply-To: <4C92998C.7000903@nortel.com>

On Thu, 2010-09-16 at 16:26 -0600, Chris Friesen wrote:
> > 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. :) 

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 :-)

Cheers,
Ben.

  reply	other threads:[~2010-09-17  0:04 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 [this message]
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=1284681832.30449.101.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=cfriesen@nortel.com \
    --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 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).