linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@jdl.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 5/9 v3] Add the MPC8641 HPCN platform files.
Date: Mon, 19 Jun 2006 17:38:35 -0500	[thread overview]
Message-ID: <E1FsSOB-0000CE-2o@jdl.com> (raw)
In-Reply-To: Your message of "Tue, 20 Jun 2006 00:06:43 +0200." <F34E213C-B073-4D85-A323-644340E3C09D@kernel.crashing.org>

So, like, the other day Segher Boessenkool mumbled:
> 
> Btw, IMNSHO, it should be the firmware's job to synchronise
> the timebases, even before the kernel gets started; at least
> as the default.  We don't want to have millions of separate
> GPIO thingies, one for every board, unless really necessary,
> I think?

The second CPU isn't even running in the firmware.
It is in hard-reset until Linux says "Hey, start that
secondary CPU for me!".

Thanks,
jdl

  reply	other threads:[~2006-06-19 22:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-17 22:52 [PATCH 5/9 v3] Add the MPC8641 HPCN platform files Jon Loeliger
2006-06-18  3:07 ` Benjamin Herrenschmidt
2006-06-19 14:04   ` Jon Loeliger
2006-06-19 22:06     ` Segher Boessenkool
2006-06-19 22:38       ` Jon Loeliger [this message]
2006-06-19 22:44         ` Segher Boessenkool
2006-06-19 23:11           ` Jon Loeliger
2006-06-19 23:18             ` Segher Boessenkool
2006-06-19 23:32               ` Jon Loeliger
2006-06-19 23:36                 ` Segher Boessenkool
2006-06-19 23:52                   ` Jon Loeliger
2006-06-18  3:14 ` Benjamin Herrenschmidt
2006-06-19 14:09   ` Jon Loeliger
2006-06-18 14:28 ` 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=E1FsSOB-0000CE-2o@jdl.com \
    --to=jdl@jdl.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=segher@kernel.crashing.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).