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 18:11:39 -0500 [thread overview]
Message-ID: <E1FsSuB-0000Qc-P6@jdl.com> (raw)
In-Reply-To: Your message of "Tue, 20 Jun 2006 00:44:35 +0200." <A609CF22-66E8-404C-A6F2-528BE097BF57@kernel.crashing.org>
So, like, the other day Segher Boessenkool mumbled:
>
> In that case you obviously need to sync the timebases, sure.
> The firmware could be smart and do the sync at CPU start-up
> time though.
I am investigating this and, as I indicated to Ben, submit
a follow up patch to implement it if I figure out to do it.
> In
> some cases the kernel explicitly tells the firmware to start/
> stop the timebases, that's better than the kernel having to
> handle the nitty-gritty details itself already.
>
> Thoughts?
Well, by the time Linux is running, there is no more firmware
available. Linux is essentially autononomous at this stage,
and I think it will have to arrange for the TB sync itself.
jdl
next prev parent reply other threads:[~2006-06-19 23:11 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
2006-06-19 22:44 ` Segher Boessenkool
2006-06-19 23:11 ` Jon Loeliger [this message]
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=E1FsSuB-0000Qc-P6@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 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.