From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Loeliger <jdl@jdl.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] Remove CPU_FTR_NEED_COHERENT for 7448.
Date: Sat, 05 May 2007 08:25:26 +1000 [thread overview]
Message-ID: <1178317526.6353.106.camel@localhost.localdomain> (raw)
In-Reply-To: <E1HjzWH-0001Wg-Ps@jdl.com>
On Fri, 2007-05-04 at 10:16 -0500, Jon Loeliger wrote:
> So, like, the other day Benjamin Herrenschmidt mumbled:
> >
> > I still maintain it should be a runtime thing tho :-)
> >
> > Ben.
>
> So, could you comment on my proposed solution doing
> things exactly this way? Speifically, would folks
> prefer the dynamic
>
> number_of_cpus() == 1
Sorry I don't remember the actual patch, must have missed it... I
suppose we could have generic code in early_init_devtree set the default
for this based on cpu_possible_map() containing more than one bit and
have platforms using one of those broken bridges force the bit in from
their probe routine.
Ben.
next prev parent reply other threads:[~2007-05-04 22:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 21:34 [PATCH] Remove CPU_FTR_NEED_COHERENT for 7448 Jon Loeliger
2007-05-03 10:17 ` Adrian Cox
2007-05-03 10:53 ` Benjamin Herrenschmidt
2007-05-03 16:13 ` Jon Loeliger
2007-05-03 17:07 ` Adrian Cox
2007-05-03 17:38 ` Jon Loeliger
2007-05-03 21:36 ` Benjamin Herrenschmidt
2007-05-04 15:16 ` Jon Loeliger
2007-05-04 22:25 ` Benjamin Herrenschmidt [this message]
2007-05-05 13:25 ` Adrian Cox
2007-05-07 17:31 ` Loeliger Jon-LOELIGER
2007-05-04 20:19 ` Kumar Gala
2007-05-03 11:02 ` Paul Mackerras
2007-05-03 16:04 ` Jon Loeliger
2007-05-03 23:34 ` Paul Mackerras
2007-05-04 15:13 ` Jon Loeliger
2007-05-10 16:17 ` Kumar Gala
2007-05-10 16:44 ` Jon Loeliger
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=1178317526.6353.106.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=jdl@jdl.com \
--cc=linuxppc-dev@ozlabs.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).