From: "Linux powerpc" <linuxppcleo@gmail.com>
To: "Rune Torgersen" <runet@innovsys.com>
Cc: Paul Mackerras <paulus@samba.org>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc:Fix rheap alignment problem
Date: Sat, 1 Jul 2006 14:35:07 +0800 [thread overview]
Message-ID: <a0bc9bf80606302335p7ba227afwf69dc42e2eada64b@mail.gmail.com> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B07B36E@ismail.innsys.innovsys.com>
[-- Attachment #1: Type: text/plain, Size: 778 bytes --]
Yes, it was used for allocating dual port RAM for CPM. And now we are
adding QE support to powerpc arch which need to use rheap(QE is next
generation for CPM). Please see the patches I <leoli@freescale.com> just
posted for 8360epb support. Moreover, previous CPM support is adding to
powerpc arch too.
--
Leo
Freescale Semiconductor
On 7/1/06, Rune Torgersen <runet@innovsys.com> wrote:
>
> From: Benjamin Herrenschmidt
>
> >What is this used for ? This rheap allocator ?
>
> It is used for allocating dual port RAM on 8xx and 82xx. (and probably
> others that have a CPM)
> Most/all usage is still in ppc.
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
>
[-- Attachment #2: Type: text/html, Size: 1527 bytes --]
next prev parent reply other threads:[~2006-07-01 6:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 13:02 [PATCH] powerpc:Fix rheap alignment problem Li Yang-r58472
2006-06-30 23:13 ` Benjamin Herrenschmidt
2006-07-01 4:13 ` Rune Torgersen
2006-07-01 6:35 ` Linux powerpc [this message]
2006-07-01 7:21 ` Benjamin Herrenschmidt
2006-07-01 10:25 ` Christoph Hellwig
2006-07-01 14:34 ` Kumar Gala
2006-07-01 14:50 ` Pantelis Antoniou
2006-07-02 3:54 ` Rune Torgersen
2006-07-02 5:18 ` Pantelis Antoniou
2006-07-03 11:08 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2006-07-03 6:49 Li Yang-r58472
2006-07-03 12:19 Li Yang-r58472
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=a0bc9bf80606302335p7ba227afwf69dc42e2eada64b@mail.gmail.com \
--to=linuxppcleo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=runet@innovsys.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).