linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Misbah khan <misbah_khan@engineer.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: (no subject)
Date: Thu, 3 Jan 2008 02:34:48 -0800 (PST)	[thread overview]
Message-ID: <14594687.post@talk.nabble.com> (raw)
In-Reply-To: <22A704B880BBD94A9E52BD6FA90C63D702F4483A@BUDMLVEM08.e2k.ad.ge.com>


I can tell you from Software point of view ....There should be One Time
Master and others as time slave data would be transmitted via Ethernet and
PPS through OFC ...Ntp should be runing ...I guess this is a way in which we
could Sync all the other boards ....

----Misbah <><

Awad, Sinan (GE Healthcare) wrote:
> 
> Hello all
>  
> I'm trying to understand if we need to move from MPC8347 to MPC8360 in
> our boards.
> One of the features that most attracts, is the eTSEC which includes
> support for IEEE 1588 PTP time synchronization.
> I need to synchronize the clock of 3 boards via ethernet, I need a time
> resolution of under 1ms.
>  
> Has anyone had the pleasure of playing around with time synchronization
> ?
> Do I really need the hardware capabilities for this type of time
> resolution ? or can I implement it in software ?
>  
> Thanks in advance.
> Sinan
>  
> 
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 

-- 
View this message in context: http://www.nabble.com/%28no-subject%29-tp14593723p14594687.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.

  reply	other threads:[~2008-01-03 10:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-03  8:33 Awad, Sinan (GE Healthcare)
2008-01-03 10:34 ` Misbah khan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-12-27 14:59 [PATCH v2 2/3] arm64: Support huge vmalloc mappings Kefeng Wang
2021-12-27 17:35 ` (No subject) William Kucharski
2021-12-28  1:36   ` Kefeng Wang
2006-07-06 12:21 (no subject) Jochen Maes
     [not found] <20051227010004.D4C7568950@ozlabs.org>
2005-12-27 15:29 ` siman
2005-12-03 18:40 Otavio Salvador
2005-10-03  1:00 Bob Brose
2005-10-03  7:07 ` Andreas Schwab
2005-09-27 13:53 ÏÄÓê 
2005-09-27 16:07 ` Wolfgang Denk
2005-06-29  6:21 董晓凡
2005-06-29 16:22 ` evilninja
2005-06-27 12:25 FLAMENT David
2005-06-13 11:38 colui77
2005-04-12 19:38 Eric N. Johnson (ACD)
2005-04-12 21:13 ` Wolfgang Denk
2005-02-13 12:28 Support for Adder875 in Linux 2.4 Markus Westergren
2005-02-14  6:45 ` Yuli Barcohen
2005-02-14 19:44   ` Markus Westergren
2005-02-15  9:35     ` (no subject) Yuli Barcohen
2004-11-22 19:23 Ratin Kumar
2004-11-22 22:53 ` 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=14594687.post@talk.nabble.com \
    --to=misbah_khan@engineer.com \
    --cc=linuxppc-embedded@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).