information between the TOD interface and the Eth
interfaces.
Alternatively do you have any suggestion to support the given scenario?
Thanks a lot for my stupid questions.
luigi
--
*Luigi 'Comio' Mantellini*
My Professional Profile <http://www.linkedin.com/in/comio>
*"UNIX is very simp
Richard Cochran <
richardcoch...@gmail.com> ha scritto:
> On Tue, Oct 27, 2020 at 08:03:34PM +0100, Luigi 'Comio' Mantellini wrote:
> > Dear All,
> >
> > I'm trying to understand if I can support the G.8271 Annex A.1.3 directly
> > via LinuxPTP.
>
> My copy do
le ore 17:30 Richard Cochran <
richardcoch...@gmail.com> ha scritto:
> On Wed, Nov 04, 2020 at 09:43:52AM +0100, Luigi 'Comio' Mantellini wrote:
> > The announce message should br managed by protocol as a normal PTP
> Announce
> > message to handle the BMC and select the grand
mer 11 nov 2020 alle ore 13:26 Richard Cochran <
richardcoch...@gmail.com> ha scritto:
> On Wed, Nov 11, 2020 at 10:04:46AM +0100, Luigi 'Comio' Mantellini wrote:
> > This is an aspect really interesting for me, because in my environment I
> > haven't true linux interfaces a
day, thanks for this.
ciao
luigi
Il giorno mer 28 ott 2020 alle ore 18:31 Richard Cochran <
richardcoch...@gmail.com> ha scritto:
> On Wed, Oct 28, 2020 at 09:35:36AM +0100, Luigi 'Comio' Mantellini wrote:
> > thanks for your reply. I'm referring to G.8271/Y.1366 docu
ated.
Thanks a lot in advance,
luigi
Il giorno mer 28 ott 2020 alle ore 18:55 Richard Cochran <
richardcoch...@gmail.com> ha scritto:
> On Wed, Oct 28, 2020 at 06:47:29PM +0100, Luigi 'Comio' Mantellini wrote:
>
> > The idea under the Annex A is to propagate some informa
This patch introduces
- "enable" configuration flag at port level
- support for ENABLE_PORT and DISABLE_PORT TLV commands
---
clock.c | 6 +++-
config.c | 1 +
designated_fsm.c | 36 ---
e2e_tc.c | 11 +++
fd.h | 1 +
p2p_tc.c
---
pmc_common.c | 51 +++
1 file changed, 51 insertions(+)
diff --git a/pmc_common.c b/pmc_common.c
index c5cd992..c7d8bed 100644
--- a/pmc_common.c
+++ b/pmc_common.c
@@ -57,6 +57,7 @@
static void do_get_action(struct pmc *pmc, int action, int
This patch introduces
- "enable" configuration flag at port level
- support for ENABLE_PORT and DISABLE_PORT TLV commands
---
clock.c | 8 +-
config.c | 1 +
designated_fsm.c | 36 ---
e2e_tc.c | 11 +++
fd.h | 1 +
p2p_tc.c
---
pmc_common.c | 51 +++
1 file changed, 51 insertions(+)
diff --git a/pmc_common.c b/pmc_common.c
index c5cd992..c7d8bed 100644
--- a/pmc_common.c
+++ b/pmc_common.c
@@ -57,6 +57,7 @@
static void do_get_action(struct pmc *pmc, int action, int
any way to run without
> giving -d option?
>
> Thanks,
> Ruby Bhati
> ___
> Linuxptp-devel mailing list
> Linuxptp-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
>
--
*Luigi 'Comi
[edited]
pmc uses the domainNumber = 0 as default and you needn't "-d 0". If
you omit the option, the default will be used instead.
To use a different domainNumber you have two options:
1) use -d XX
2) specify domainNumber into a configuration file in [global] section.
You can use the ptp4l
vel mailing list
> Linuxptp-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
--
Luigi 'Comio' Mantellini
My Professional Profile
"UNIX is very simple, it just needs a genius to understand its
simplicity." [cit.]
_
o, but I soon ran into corner cases in the code
> that spoiled everything. It is one of the weaknesses of linuxptp.
>
> As practical matter, in my own projects I simply re-start the start
> when the configuration changes. Although not ideal, that is easier
> than re-working linuxptp
22 apr 2021 alle ore 18:43 Jacob Keller <
jacob.e.kel...@intel.com> ha scritto:
>
>
> On 4/22/2021 8:46 AM, Luigi 'Comio' Mantellini wrote:
> > Generally speaking and in my opinion should be interesting to have the
> > following features:
> > - asynchronou
_CLEARED;
else if ((p->link_status == (LINK_DOWN | LINK_STATE_CHANGED)) ||
(p->link_status & TS_LABEL_CHANGED))
return EV_FAULT_DETECTED;
else
return EV_NONE;
raising a EV_FAULT_DETECT on LINK_DOWN
Is my observation correct?
Thanks in advanc
ONE : EV_STATE_DECISION_EVENT;
}
break;
(or...
case ANNOUNCE:
if (!p->master_only && process_announce(p, msg))
event = EV_STATE_DECISION_EVENT;
break;
)
Thanks for your opinion,
ciao
luigi
--
Luigi 'Comio' Mantellini
My Professional Profile
"UNIX is v
is
case we lost time with logging and blocking the main loop.
My 2Eurocents.
ciao
luigi
Il giorno mar 4 mag 2021 alle ore 14:02 Richard Cochran
ha scritto:
>
> On Mon, May 03, 2021 at 06:52:02PM +0200, Luigi 'Comio' Mantellini wrote:
> > I noticed that the Announce messages receiv
Hi Richard,
not a problem, of course. I'm just speaking about code cleanup.
luigi
Il giorno mar 4 mag 2021 alle ore 14:00 Richard Cochran <
richardcoch...@gmail.com> ha scritto:
> On Mon, May 03, 2021 at 06:45:56PM +0200, Luigi 'Comio' Mantellini wrote:
> > /*
> > *
Yes, it works for me.
thanks
luigi
Il giorno mar 23 mar 2021 alle ore 15:06 Richard Cochran <
richardcoch...@gmail.com> ha scritto:
> On Mon, Mar 15, 2021 at 12:38:58PM +0100, Luigi 'Comio' Mantellini wrote:
> > Inside port_synchronize() I noticed this:
> >
Il giorno dom 14 mar 2021 alle ore 16:58 Richard Cochran <
richardcoch...@gmail.com> ha scritto:
> On Sun, Mar 14, 2021 at 10:30:31AM +0100, Luigi 'Comio' Mantellini wrote:
> > The failures are part of the test and after the HW restoring I'm pretty
> > sure that the protoc
>
> That doesn't make any sense to me. You need to find the root cause
> and fix it.
>
> HTH,
> Richard
>
>
--
*Luigi 'Comio' Mantellini*
My Professional Profile <http://www.linkedin.com/in/comio>
*"UNIX is very simple, it just needs a genius to understand
continuing:
In your opinion, can a servo->curr_offset_values =
servo->num_offset_values call inside clock_udpdate_slave() help?
ciao
luigi
Il giorno lun 15 mar 2021 alle ore 12:38 Luigi 'Comio' Mantellini
ha scritto:
>
> Hi Richard,
>
> sorry again to continue this
From: Luigi Mantellini
The step_window functionality should be defined at the port level because
we cannot assume that different ports have the same sync message rate.
---
clock.c| 13 +
clock.h| 5 +++--
config.c | 2 +-
port.c | 18
port.twoStepFlag.
When -1, inherit the global twoStepFlag value, otherwise enable two-step mode
for sync messages on port basis. One-step mode can be used only with hardware
time stamping. The default is -1 (as global twoStepFlag value).
---
config.c | 1 +
port.c | 40
---
CMakeLists.txt| 189 ++
CMakeModules/CompilerFlags.cmake | 25
CMakeModules/check_features.cmake | 96 +++
CMakeModules/version.cmake| 39 ++
version.c | 4 +
5 files changed, 353
herefore, what is the additional value here compared to
> standard make.
>
> -michael
>
--
*Luigi 'Comio' Mantellini*
My Professional Profile <http://www.linkedin.com/in/comio>
*"UNIX is very simple, it just needs a genius to understand its
simplicity." [cit.]*
__
Hi,
This patch cover my scenario where the timestamper can be aligned once at
second.
Can I suggest to a avoid to touch free_running variable and introduce
another one?
Thanks,
Luigi
Il dom 14 feb 2021, 06:55 ha scritto:
> From: Vincent Cheng
>
> When clock stepping is unable to happen
100, Luigi 'Comio' Mantellini wrote:
> > The only use case that I can suppose is an old device into the network
> that
> > doesn't handle the new protocol version and we need to accommodate. For
> > this reason I was asking to handle at port level.
>
> But older devices c
6PM +0100, Luigi 'Comio' Mantellini wrote:
> > I will suggest to offer two enums to handle 2 or 2.1.
>
> If a justification can be found for "downgrading" the advertised
> version, then yes, it would be better to enumerate the actual released
> and supported ve
HI,
I will suggest to offer two enums to handle 2 or 2.1.
I have a question: is it insane to offer different version on port basis?
Ciao
Luigi
Il dom 21 feb 2021, 16:34 Richard Cochran ha
scritto:
> On Sat, Feb 20, 2021 at 02:26:44PM +0800, Yangbo Lu wrote:
> > IEEE 1588-2019 specified new
---
config.c | 2 +-
port.c | 40 +++-
ptp4l.8 | 9 -
3 files changed, 44 insertions(+), 7 deletions(-)
diff --git a/config.c b/config.c
index 4472d3d..f0e1e07 100644
--- a/config.c
+++ b/config.c
@@ -322,7 +322,7 @@ struct config_item
ant notice: This e-mail and any attachment thereof contain corporate
> proprietary information. If you have received it by mistake, please notify
> us immediately by reply e-mail and delete this e-mail and its attachments
> from your system. Thank you.
>
>
> ____
---
config.c | 2 +-
port.c | 40 +++-
ptp4l.8 | 9 -
3 files changed, 44 insertions(+), 7 deletions(-)
diff --git a/config.c b/config.c
index 4472d3d..f0e1e07 100644
--- a/config.c
+++ b/config.c
@@ -322,7 +322,7 @@ struct config_item
With this patch we introduce the twoStepFlag evaluation at port level.
---
config.c | 2 +-
port.c | 35 ++-
ptp4l.8 | 9 -
3 files changed, 39 insertions(+), 7 deletions(-)
diff --git a/config.c b/config.c
index 4472d3d..f0e1e07 100644
---
vel mailing list
> Linuxptp-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
>
--
*Luigi 'Comio' Mantellini*
My Professional Profile <http://www.linkedin.com/in/comio>
*"UNIX is very simple, it just needs a genius to understand its
> Linuxptp-devel mailing list
> Linuxptp-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
>
--
*Luigi 'Comio' Mantellini*
My Professional Profile <http://www.linkedin.com/in/comio>
*"UNIX is very si
t;
> regards,
> Ramesh
>
>
> ___
> Linuxptp-devel mailing list
> Linuxptp-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
--
Luigi 'Comio' Mantellini
My Professional Profile
"UNIX is very sim
us monitoring.
>
> Simplifies? how?
>
> There is no monitoring of the servo state. This is a purely internal
> state variable.
>
> Thanks,
> Richard
>
>
> ___
> Linuxptp-devel mailing list
> Linuxptp-devel@
; > 0x02 TX Fail on Transmit
> > 0x03 TX Missing Timestamp
>
> Please don't overload the existing rx/tx message counters in this way.
>
> If you really want to count "Bad Message" etc, please create a new
> data structure with fields like "bad_message" etc
t; - if you really want those, please write a stand alone program that
> gathers the statistics from data input via the UDS interface
>
> Thanks,
> Richard
>
--
*Luigi 'Comio' Mantellini*
My Professional Profile <http://www.linkedin.com/in/comio>
*"UNIX is very simple, it
t;
> >>
> >
> >> fup->header.tsmt = PDELAY_RESP_FOLLOW_UP |
> >
> >> p->transportSpecific; - fup->header.ver=
> > PTP_VERSION;
> >
> >> + fup->header.ver
Very interesting.
Thanks for your effort.
Luigi
Il gio 20 ott 2022, 07:42 Devasish Dey ha
scritto:
> Hi All,
>
> SyncMonk is excited to introduce *SyncESMC*, an implementation for
> Ethernet Synchronous Message Channel based on ITU-T G.8264 (03/2018) and
> ITU-T G.781(04/2020) standards as a
able) - TRef
>
>
> https://calnexsolutions.atlassian.net/wiki/spaces/KB/pages/71991334/T-BC+Time+Error+Metrics
>
> Thanks
> Alex
>
> ___
> Linuxptp-devel mailing list
> Linuxptp-devel@lists.sourceforge.net
> https://lists.
s/guile/guide/g
Sorry...
ciao
luigi
Il giorno gio 8 set 2022 alle ore 13:56 Luigi 'Comio' Mantellini <
luigi.mantell...@gmail.com> ha scritto:
> Hi Alex,
>
> some guile line that I follow during my debug sessions:
>
> - Are you using a good cable-delay estimation for
;
>
> ___
> Linuxptp-devel mailing list
> Linuxptp-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
--
Luigi 'Comio' Mantellini
My Professio
TH,
> Richard
>
>
> ___
> Linuxptp-devel mailing list
> Linuxptp-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
>
--
*Luigi 'Comio' Mantellini*
My Profes
if (diff < 0)
> return B_BETTER;
> if (diff > 0)
> @@ -53,7 +64,7 @@ int dscmp2(struct dataset *a, struct dataset *b)
> return 0;
> }
>
> - diff = memcmp
The struct is not in network order because it is already converted to
cpu's endianess before to call the bmca.
The patch works in my setup.
Ciao
Luigi
Il gio 17 nov 2022, 19:04 Geva, Erez ha scritto:
> On Mon, 2022-11-14 at 14:25 +0100, Luigi Mantellini wrote:
> > The PortId is defined as a
Any review on this patchset?
Ciao
Luigi
Il gio 30 mar 2023, 08:08 Luigi Mantellini ha
scritto:
> The actual ptp4l implementation rearms timers after the expiration. This
> approach doesn't permit to have a precise TX SYNC message scheduling.
> During my test the TX SYNC frequency is slightly
Announce messages are randomized using the set_tmo_random() call.
ciao
luigi
Il giorno mer 26 apr 2023 alle ore 04:57 Richard Cochran <
richardcoch...@gmail.com> ha scritto:
> On Tue, Apr 25, 2023 at 06:23:53PM +0200, Luigi 'Comio' Mantellini wrote:
> > Any review on this pa
mness
> to be added to the interval.
>
> --
> Miroslav Lichvar
>
>
--
*Luigi 'Comio' Mantellini*
My Professional Profile <http://www.linkedin.com/in/comio>
*"UNIX is very simple, it just needs a genius to understand its
simplicity." [cit.]*
Hi Miroslav,
find my inline answers.
Il giorno mer 26 apr 2023 alle ore 11:15 Miroslav Lichvar <
mlich...@redhat.com> ha scritto:
> On Wed, Apr 26, 2023 at 10:43:52AM +0200, Luigi 'Comio' Mantellini wrote:
> > Hi Miroslav,
> >
> > Sync is already sent using a co
TCH 6/6] Use periodic timer for TX SYNC timeout
>>
>>
>>
>> ___
>> Linuxptp-devel mailing list
>> Linuxptp-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
>>
>
--
Thanks... i will produce a v3 after some feedback
> Sorry I forgot another hint. Please use the 'git format-patch' with the patch
> seria iteration flag '-v '. So we can differentiate the mails as newer :-)
> This will change the subject to something like "Subject: [PATCH v2 0/6] "
f->scaledLastGmPhaseChange =
> htonl(f->scaledLastGmPhaseChange);
> + f->scaledLastGmFreqChange =
> htonl(f->scaledLastGmFreqChange);
> break;
> }
> } else if (0 == memcmp(o
Thanks for your time.
What do you mean with "PUSH" message?
I agree with you in order to keep it simple.
ciao
luigi
Il giorno ven 10 nov 2023 alle ore 17:58 Richard Cochran <
richardcoch...@gmail.com> ha scritto:
> On Fri, Nov 10, 2023 at 07:58:14AM +0100, Luigi 'Comi
57 matches
Mail list logo
