Hardware Timestamp on windows

[Ossama-MOUSTAFA]

Hello. 

I would like to use hardware timestamping on windows, so I try to use this : 

https://learn.microsoft.com/en-us/windows/win32/api/iphlpapi/nf-iphlpapi-getinterfaceactivetimestampcapabilities

But I only get this error : "ERROR_BAD_DRIVER"

(I already tried to update my drivers, on windows 11, and also on windows server 2022.)

I have 2 intel network adapters now : i219-LM and i210-T1. 

Do you know if intel support hardware timestamp on windows please ? 

Or only on linux ? 

https://www.intel.ca/content/www/ca/en/products/sku/82185/intel-ethernet-connection-i219lm/specifications.html 

In this page, specifications indicate that it does support PTP IEEE 1588, 

but it's not specified if it does support only software timestamp on windows or more.

Do you know if any other intel network adapter does support hardware timestamp on windows, please ? 

Kind regards. 

[Peterdoo]

I think that you are wrong. Intel has added support for PTP hardware timestamping for E1R (I210, I211 and I350) based on Microsoft NDIS and driver specs for Windows 10. These boards normally support PTP hardware timestamping under Windows 10, Windows 11, Server 2019 and Server 2022. I could only get it working on the I210-T1, but for some reason not on the I211. I have not tested the I350.

Microsoft has since then added some additional functions only for Windows 11 and Server 2022 (GetInterfaceActiveTimestampCapabilities, CaptureInterfaceHardwareCrossTimestamp and some others). In order to support those additional Windows functions, Intel would have to modify the E1R driver to support the latest Microsoft driver description which would make the additional Windows 11 (and Server 2022) functions working. However, you can use PTP hardware timestamping (receive timestamps for PTP RX and TX) in your Windows programs also without those additional functions. Just a bit less confortable. Enabling PTP hardware timestamping in the driver advanced tab does exactly the same as enabling it in the ProSet utility.

As there apparently is only one Intel driver supporting PTP timestamping and Windows 10 is getting obsolete and Windows 11 and Server 2022 are available for quite some time now, it would be reasonable to expect from Intel that they would extend that one driver to support the few additional Windows 11 / Server 2022 PTP timestamping functions (probably some additional OIDs).

[lexa]

IMHO having timestamps and cross timestamps without knowing their relation (which you get from GetInterfaceActiveTimestampCapabilities) is pretty useless to maintain a PTP synchronized software clock (reading the PHC is not supported and would also be too expensive to just read the current time).

The hard work was done doing the timestamping stuff, so I don't understand why it's such a big deal to support the new GetInterfaceActiveTimestampCapabilities and CaptureInterfaceHardwareCrossTimestamp functions.

The I350 inf sections do not specify PtpHardwareTimestamp, so no hardware timestamping for I350.

I would say after telling us for years that it's Microsoft that has to do the job and standardize a timestamping API in NDIS resp. Windows, I think it's reasonable that Intel updates their drivers for silicon that is capable of hardware timestamping, isn't it?

[Peterdoo]

Windows 10 and Server 2019 support hardware timestamping since 19H1. w32tm time sync which is Windows time synchronization service supports since then Windows time sync with PTP also with the Intel adapters that support hardware timestamping. Apart from the internal PTP client, the API support for timestamping in Windows 10 / Server 2019 is very scarce, so using timestamping from programs running on Windows 10 / Server 2019 is almost impossible.

However under Windows 11 / Server 2022 Windows API support is much better. With the I210-T1 adapter, the functions GetInterfaceSupportedTimestampCapabilities and CaptureInterfaceHardwareCrossTimestamp work. PTP TX and RX packets are delivered with hardware timestamps when PTP hardware timestamping is enabled in adapter properties or using PowerShell. The adapter has to be restarted after enabling PTP hardware timestamping. CaptureInterfaceHardwareCrossTimestamp implementation is wrong at least on the I210-T1. GetInterfaceActiveTimestampCapabilities does not seem to work on Intel adapters, however, you can obtain more or less the same information using GetInterfaceSupportedTimestampCapabilities.

You can test the Windows PTP functionality on Windows 11 / Server 2022 using the following:

w32tm /ptp_monitor /duration:10

I totally agree that it would be time that Intel includes the missing functionality for the new Windows 11 / Server 2022 timestamping functions to work and corrects the bugs. I just don't agree when you say that did not do it correctly until now. They had a project probably back in 2019 to implement what was needed and supported by Windows at that time. You cannot expect them to add back in 2019 the functionality that Microsoft has added and described later (MS articles with descriptions of the new Windows 11 / Server 2022 timestamping add-ons are dated December 2021) and was not specified yet in 2019. This has to be a new project in Intel and it's already time to start it.

In my opinion, Intel has to do the following regarding Windows PTP hardware timestamping:

- Correct the function CaptureInterfaceHardwareCrossTimestamp. At the moment this function returns the HardwareClockTimestamp value for the previous call of this function, which is a value from some time ago and makes this function unusable on Intel adapters at the moment. Looks like a double buffering problem.
- Make the function GetInterfaceActiveTimestampCapabilities working.
- The HardwareClockFrequencyHz reported in GetInterfaceSupportedTimestampCapabilities is off by about 0,5%-1% from the actual frequency. I don't know whether it can be reported more exactly or whether the oscillator on the adapter is so inaccurate.
- Get timestamping to work correctly at least on the adapters where it is supposed to work. I could get it working on I210-T1, but not on an I211. I don't remember whether there were no timestamps or zero timestamps delivered.
- There is no timestamping functionality in the inf file for the i350 adapters.
- Server installation section [E1539.19H1] is missing for the I211 adapter in the inf file or has no timestamping. Only workstation (Win10/11) section is present or has the timestamping for the I211.
- Extend the hardware timestamping functionality support for Windows to other products, like X710 etc.

According to the inf files, the PTP hardware timestamping seems to be configurable for the following Intel adapters:
I210 (E1533, E1536, E1538)
I211 (E1539) Win10/11 only, no server support
E810 (F1591PM, F1592, F1592PM, F1592PM50G, F1593PM, F1593SFP25, F1593SFP28, F159BSFP28PM, F159BSFP28, F1598PM, F1599PM, F159APM, F159BPM, F1593SFP56)
I217 (E153A, E153B)
I218 (E155A, E1559, E15A0, E15A1, E15A2, E15A3)
I219 (E156F, E15B7, E1570, E15B8, E15B9, E15D7, E15E3, E15D8, E15D6, E15BD, E15BB, E15BE, E15BC, E15DF, E15E1, E0D4E, E0D4C, E0D53, E15F9, E15FA, E15FB, E15FC, E15F4, E1A1E, E1A1F, E1A1C, E1A1D, E550A, E550B, E550C, E550D, E0DC5, E0DC6, E0DC7, E0DC8, E15E0, E15E2, E0D4F, E0D4D, E0D55)

[Peterdoo]

Windows 10 and Server 2019 support hardware timestamping since 19H1. w32tm time sync which is Windows time synchronization service supports since then Windows time sync with PTP also with the Intel adapters that support hardware timestamping. Apart from the internal PTP client, the API support for timestamping in Windows 10 / Server 2019 is very scarce, so using timestamping from programs running on Windows 10 / Server 2019 is almost impossible.

However under Windows 11 / Server 2022 Windows API support is much better. With the I210-T1 adapter, the functions GetInterfaceSupportedTimestampCapabilities and CaptureInterfaceHardwareCrossTimestamp work. PTP TX and RX packets are delivered with hardware timestamps when PTP hardware timestamping is enabled in adapter properties or using PowerShell. The adapter has to be restarted after enabling PTP hardware timestamping. CaptureInterfaceHardwareCrossTimestamp implementation is wrong at least on the I210-T1. GetInterfaceActiveTimestampCapabilities does not seem to work on Intel adapters, however, you can obtain more or less the same information using GetInterfaceSupportedTimestampCapabilities.

You can test the Windows PTP functionality on Windows 11 / Server 2022 using the following:

w32tm /ptp_monitor /duration:10

I totally agree, that it would be time that Intel includes the missing functionality for the new Windows 11 / Server 2022 timestamping functions to work and corrects the bugs. I just don't agree when you say that did not do it correctly until now. They had a project probably back in 2019 to implement what was needed and supported by Windows at that time. You cannot expect them to add back in 2019 functionality that Microsoft has added later (MS articles with descriptions of the new Windows 11 / Server 2022 timestamping add-ons are dated December 2021) and was not specified yet in 2019. This has to be a new project in Intel and it's already time to start it.

In my opinion, Intel has to do the following regarding PTP:

- Correct the function CaptureInterfaceHardwareCrossTimestamp. At the moment this function returns the HardwareClockTimestamp value for the previous call of this function, which is a value from some time ago and makes this function unusable on Intel adapters at the moment. Looks like a double buffering problem.
- Make the function GetInterfaceActiveTimestampCapabilities working.
- The HardwareClockFrequencyHz reported in GetInterfaceSupportedTimestampCapabilities is off by about 0,5%-1% from the actual frequency. I don't know whether it can be reported more exactly or whether the oscillator on the adapter is so inaccurate.
- Get timestamping to work correctly at least on the adapters where it is supposed to work. I could get it working on I210-T1, but not on an I211. I don't remember whether there were no timestamps or zero timestamps delivered.
- There is no timestamping functionality in the inf file for the i350 adapters.
- Server installation section [E1539.19H1] is missing for the I211 adapter in the inf file or has no timestamping. Only workstation (Win10/11) section is present or has the timestamping for the I211.
- Extend the hardware timestamping functionality support for Windows to other products, like X710 etc.

According to the inf files, the PTP hardware timestamping seems to be configurable for the following adapters:
I210 (E1533, E1536, E1538)
I211 (E1539) Win10/11 only, no server support
E810 (F1591PM, F1592, F1592PM, F1592PM50G, F1593PM, F1593SFP25, F1593SFP28, F159BSFP28PM, F159BSFP28, F1598PM, F1599PM, F159APM, F159BPM, F1593SFP56)
I217 (E153A, E153B)
I218 (E155A, E1559, E15A0, E15A1, E15A2, E15A3)
I219 (E156F, E15B7, E1570, E15B8, E15B9, E15D7, E15E3, E15D8, E15D6, E15BD, E15BB, E15BE, E15BC, E15DF, E15E1, E0D4E, E0D4C, E0D53, E15F9, E15FA, E15FB, E15FC, E15F4, E1A1E, E1A1F, E1A1C, E1A1D, E550A, E550B, E550C, E550D, E0DC5, E0DC6, E0DC7, E0DC8, E15E0, E15E2, E0D4F, E0D4D, E0D55)

[Peterdoo]

Windows 10 and Server 2019 support hardware timestamping since 19H1. w32tm time sync which is Windows time synchronization service supports since then Windows time sync with PTP also with the Intel adapters that support hardware timestamping. Apart from the internal PTP client, the API support for timestamping in Windows 10 / Server 2019 is very scarce, so using timestamping from programs running on Windows 10 / Server 2019 is almost impossible.

However under Windows 11 / Server 2022 Windows API support is much better. With the I210-T1 adapter, the functions GetInterfaceSupportedTimestampCapabilities and CaptureInterfaceHardwareCrossTimestamp work. PTP TX and RX packets are delivered with hardware timestamps when PTP hardware timestamping is enabled in adapter properties or using PowerShell. The adapter has to be restarted after enabling PTP hardware timestamping. CaptureInterfaceHardwareCrossTimestamp implementation is wrong at least on the I210-T1. GetInterfaceActiveTimestampCapabilities does not seem to work on Intel adapters, however, you can obtain more or less the same information using GetInterfaceSupportedTimestampCapabilities.

You can test the Windows PTP functionality on Windows 11 / Server 2022 using the following:

w32tm /ptp_monitor /duration:10

I totally agree, that it would be time that Intel includes the missing functionality for the new Windows 11 / Server 2022 timestamping functions to work and corrects the bugs. I just don't agree when you say that did not do it correctly until now. They had a project probably back in 2019 to implement what was needed and supported by Windows at that time. You cannot expect them to add back in 2019 functionality that Microsoft has added later (MS articles with descriptions of the new Windows 11 / Server 2022 timestamping add-ons are dated December 2021) and was not specified yet in 2019. This has to be a new project in Intel and it's already time to start it.

In my opinion, Intel has to do the following regarding PTP:

- Correct the function CaptureInterfaceHardwareCrossTimestamp. At the moment this function returns the HardwareClockTimestamp value for the previous call of this function, which is a value from some time ago and makes this function unusable on Intel adapters at the moment. Looks like a double buffering problem.
- Make the function GetInterfaceActiveTimestampCapabilities working.
- The HardwareClockFrequencyHz reported in GetInterfaceSupportedTimestampCapabilities is off by about 0,5%-1% from the actual frequency. I don't know whether it can be reported more exactly or whether the oscillator on the adapter is so inaccurate.
- Get timestamping to work correctly at least on the adapters where it is supposed to work. I could get it working on I210-T1, but not on an I211. I don't remember whether there were no timestamps or zero timestamps delivered.
- There is no timestamping functionality in the inf file for the i350 adapters.
- Server installation section E1539.19H1 is missing for the I211 adapter in the inf file or has no timestamping. Only workstation (Win10/11) section is present or has the timestamping for the I211.
- Extend the hardware timestamping functionality support for Windows to other products, like X710 etc.

According to the inf files, the PTP hardware timestamping seems to be configurable for the following adapters:
I210 (E1533, E1536, E1538)
I211 (E1539) Win10/11 only, no server support
E810 (F1591PM, F1592, F1592PM, F1592PM50G, F1593PM, F1593SFP25, F1593SFP28, F159BSFP28PM, F159BSFP28, F1598PM, F1599PM, F159APM, F159BPM, F1593SFP56)
I217 (E153A, E153B)
I218 (E155A, E1559, E15A0, E15A1, E15A2, E15A3)
I219 (E156F, E15B7, E1570, E15B8, E15B9, E15D7, E15E3, E15D8, E15D6, E15BD, E15BB, E15BE, E15BC, E15DF, E15E1, E0D4E, E0D4C, E0D53, E15F9, E15FA, E15FB, E15FC, E15F4, E1A1E, E1A1F, E1A1C, E1A1D, E550A, E550B, E550C, E550D, E0DC5, E0DC6, E0DC7, E0DC8, E15E0, E15E2, E0D4F, E0D4D, E0D55)

[Peterdoo]

Windows 10 and Server 2019 support hardware timestamping since 19H1. w32tm time sync which is Windows time synchronization service supports since then Windows time sync with PTP also with the Intel adapters that support hardware timestamping. Apart from the internal PTP client, the API support for timestamping in Windows 10 / Server 2019 is very scarce, so using timestamping from programs running on Windows 10 / Server 2019 is almost impossible.

However under Windows 11 / Server 2022 Windows API support is much better. With the I210-T1 adapter, the functions GetInterfaceSupportedTimestampCapabilities and CaptureInterfaceHardwareCrossTimestamp work. PTP TX and RX packets are delivered with hardware timestamps when PTP hardware timestamping is enabled in adapter properties or using PowerShell. The adapter has to be restarted after enabling PTP hardware timestamping. CaptureInterfaceHardwareCrossTimestamp implementation is wrong at least on the I210-T1. GetInterfaceActiveTimestampCapabilities does not seem to work on Intel adapters, however, you can obtain more or less the same information using GetInterfaceSupportedTimestampCapabilities.

You can test the Windows PTP functionality on Windows 11 / Server 2022 using the following:

w32tm /ptp_monitor /duration:10

I totally agree, that it would be time that Intel includes the missing functionality for the new Windows 11 / Server 2022 timestamping functions to work and corrects the bugs. I just don't agree when you say that did not do it correctly until now. They had a project probably back in 2019 to implement what was needed and supported by Windows at that time. You cannot expect them to add back in 2019 functionality that Microsoft has added later (MS articles with descriptions of the new Windows 11 / Server 2022 timestamping add-ons are dated December 2021) and was not specified yet in 2019. This has to be a new project in Intel and it's already time to start it.

In my opinion, Intel has to do the following regarding PTP:

- Correct the function CaptureInterfaceHardwareCrossTimestamp. At the moment this function returns the HardwareClockTimestamp value for the previous call of this function, which is a value from some time ago and makes this function unusable on Intel adapters at the moment. Looks like a double buffering problem.
- Make the function GetInterfaceActiveTimestampCapabilities working.
- The HardwareClockFrequencyHz reported in GetInterfaceSupportedTimestampCapabilities is off by about 0,5%-1% from the actual frequency. I don't know whether it can be reported more exactly or whether the oscillator on the adapter is so inaccurate.
- Get timestamping to work correctly at least on the adapters where it is supposed to work. I could get it working on I210-T1, but not on an I211. I don't remember whether there were no timestamps or zero timestamps delivered.
- There is no timestamping functionality in the inf file for the i350 adapters.
- Server installation section [E1539.19H1] is missing for the I211 adapter in the inf file or has no timestamping. Only workstation (Win10/11) section is present or has the timestamping for the I211.
- Extend the hardware timestamping functionality support for Windows to other products, like X710 etc.

According to the inf files, the PTP hardware timestamping seems to be configurable for the following adapters:
I210 (E1533, E1536, E1538)
I211 (E1539) Win10/11 only, no server support
E810 (F1591PM, F1592, F1592PM, F1592PM50G, F1593PM, F1593SFP25, F1593SFP28, F159BSFP28PM, F159BSFP28, F1598PM, F1599PM, F159APM, F159BPM, F1593SFP56)
I217 (E153A, E153B)
I218 (E155A, E1559, E15A0, E15A1, E15A2, E15A3)
I219 (E156F, E15B7, E1570, E15B8, E15B9, E15D7, E15E3, E15D8, E15D6, E15BD, E15BB, E15BE, E15BC, E15DF, E15E1, E0D4E, E0D4C, E0D53, E15F9, E15FA, E15FB, E15FC, E15F4, E1A1E, E1A1F, E1A1C, E1A1D, E550A, E550B, E550C, E550D, E0DC5, E0DC6, E0DC7, E0DC8, E15E0, E15E2, E0D4F, E0D4D, E0D55)

[Peterdoo]

In my opinion, Intel has to do the following regarding PTP:

- Correct the function CaptureInterfaceHardwareCrossTimestamp. At the moment this function returns the HardwareClockTimestamp value for the previous call of this function, which is a value from some time ago and makes this function unusable on Intel adapters at the moment. Looks like a double buffering problem.
- Make the function GetInterfaceActiveTimestampCapabilities working.
- The HardwareClockFrequencyHz reported in GetInterfaceSupportedTimestampCapabilities is off by about 0,5%-1% from the actual frequency. I don't know whether it can be reported more exactly or whether the oscillator on the adapter is so inaccurate.
- Get timestamping to work correctly at least on the adapters where it is supposed to work. I could get it working on I210-T1, but not on an I211. I don't remember whether there were no timestamps or zero timestamps delivered.
- There is no timestamping functionality in the inf file for the i350 adapters.
- Server installation section [E1539.19H1] is missing for the I211 adapter in the inf file or has no timestamping. Only workstation (Win10/11) section is present or has the timestamping for the I211.
- Extend the hardware timestamping functionality support for Windows to other products, like X710 etc.

According to the inf files, the PTP hardware timestamping seems to be configurable for the following adapters:
I210 (E1533, E1536, E1538)
I211 (E1539) Win10/11 only, no server support
E810 (F1591PM, F1592, F1592PM, F1592PM50G, F1593PM, F1593SFP25, F1593SFP28, F159BSFP28PM, F159BSFP28, F1598PM, F1599PM, F159APM, F159BPM, F1593SFP56)
I217 (E153A, E153B)
I218 (E155A, E1559, E15A0, E15A1, E15A2, E15A3)
I219 (E156F, E15B7, E1570, E15B8, E15B9, E15D7, E15E3, E15D8, E15D6, E15BD, E15BB, E15BE, E15BC, E15DF, E15E1, E0D4E, E0D4C, E0D53, E15F9, E15FA, E15FB, E15FC, E15F4, E1A1E, E1A1F, E1A1C, E1A1D, E550A, E550B, E550C, E550D, E0DC5, E0DC6, E0DC7, E0DC8, E15E0, E15E2, E0D4F, E0D4D, E0D55)

[Peterdoo]

Windows 10 and Server 2019 support hardware timestamping since 19H1. w32tm time sync which is Windows time synchronization service supports since then Windows time sync with PTP also with the Intel adapters that support hardware timestamping. Apart from the internal PTP client, the API support for timestamping in Windows 10 / Server 2019 is very scarce, so using timestamping from programs running on Windows 10 / Server 2019 is almost impossible.

However under Windows 11 / Server 2022 Windows API support is much better. With the I210-T1 adapter, the functions GetInterfaceSupportedTimestampCapabilities and CaptureInterfaceHardwareCrossTimestamp work. PTP TX and RX packets are delivered with hardware timestamps when PTP hardware timestamping is enabled in adapter properties or using PowerShell. The adapter has to be restarted after enabling PTP hardware timestamping. CaptureInterfaceHardwareCrossTimestamp implementation is wrong at least on the I210-T1. GetInterfaceActiveTimestampCapabilities does not seem to work on Intel adapters, however, you can obtain more or less the same information using GetInterfaceSupportedTimestampCapabilities.

You can test the Windows PTP functionality on Windows 11 / Server 2022 using the following:

w32tm /ptp_monitor /duration:10

I totally agree, that it would be time that Intel includes the missing functionality for the new Windows 11 / Server 2022 timestamping functions to work and corrects the bugs. I just don't agree when you say that did not do it correctly until now. They had a project probably back in 2019 to implement what was needed and supported by Windows at that time. You cannot expect them to add back in 2019 functionality that Microsoft has added later (MS articles with descriptions of the new Windows 11 / Server 2022 timestamping add-ons are dated December 2021) and was not specified yet in 2019. This has to be a new project in Intel and it's already time to start it.

In my opinion, Intel has to do the following regarding PTP:

- Correct the function CaptureInterfaceHardwareCrossTimestamp. At the moment this function returns the HardwareClockTimestamp value for the previous call of this function, which is a value from some time ago and makes this function unusable on Intel adapters at the moment. Looks like a double buffering problem.
- Make the function GetInterfaceActiveTimestampCapabilities working.
- The HardwareClockFrequencyHz reported in GetInterfaceSupportedTimestampCapabilities is off by about 0,5%-1% from the actual frequency. I don't know whether it can be reported more exactly or whether the oscillator on the adapter is so inaccurate.
- Get timestamping to work correctly at least on the adapters where it is supposed to work. I could get it working on I210-T1, but not on an I211. I don't remember whether there were no timestamps or zero timestamps delivered.
- There is no timestamping functionality in the inf file for the i350 adapters.
- Server installation section E1539.19H1 is missing for the I211 adapter in the inf file or has no timestamping. Only workstation (Win10/11) section is present or has the timestamping for the I211.
- Extend the hardware timestamping functionality support for Windows to other products, like X710 etc.

According to the inf files, the PTP hardware timestamping seems to be configurable for the following adapters:
I210
I211 Win10/11 only, no server support
E810
I217
I218
I219

[lexa]

Great information, thank you Peter.

I'll check if I can make use of GetInterfaceSupportedTimestampCapabilities when GetInterfaceActiveTimestampCapabilities is failing.

Remains the major issue with CaptureInterfaceHardwareCrossTimestamp, but perhaps this can be worked around with just taking the QPC value and the relation between QPC and PHC. Unfortunately this means that there has to be some training (reception of enough sync messages) to be sure about the relation.

I second your list of things Intel will have to if they want to remain taken as a professional Ethernet adapter/controller company and not being put into the same locker as Realtek for example (BTW, the newest Realtek silicon is supporting hardware timestamping, but - you guessed it - not their Windows drivers).

[Caguicla_Intel]

Hello All,

Thank you for providing feedback on this thread and rest assured that we will forward this to our engineering team. 

Unfortunately, we are still waiting for their feedback regarding this matter. We will get back to you once we heard from them but no later than 3 business days. 

Thank you for your kind understanding. 

Best regards,

Crisselle C.

Intel Customer Support

[Ossama-MOUSTAFA]

Hi. 

Ok, thank you for this forwarding, and this update. Have a great day. 

Best regards. 

[lexa]

Hi Criselle et al,

another five business days have passed and there's no update.

Could you please be so kind and tell us what we can expect and when?

Thank you.

[lexa]

Hi Intel and Criselle,

another two weeks have passed and meanwhile - after all the layoffs that have happened at Intel - I'm not so sure anymore if the Ethernet support is still in place.

Could someone at Intel please comment why there is no progress?

What do we have to do to have the support we're entitled to have?

Thank you.

[lexa]

Hello all,

a new Ethernet driver pack 28.0 was released and still the PTP on Windows issues were not resolved!

Intel, where are you?

Please comment why we're stuck here and what Intel is planning to do to fix the issues.

[JNiko]

Any updates on this guys?

We have a couple I350 and cannot enable hardware timestamps, only on I210 and I217-LM is working on our side.

I think Intel is avoiding to enable this I do not why.

[Ossama-MOUSTAFA]

Hi. No, sorry, I don't have any update on this. 

Kind regards. 

[lexa]

I think Intel laid off all the employees in Ethernet support.

There's no replies anymore. I have an open support case, also there no more response.

I think finally one should avoid Intel for Ethernet NICs.

[Faez_Intel]

Hello,

Good day and I hope this message finds you well.

We sincerely apologize for the delay in response of this thread. We've bee waiting an update from the engineering team and verified the i210 and i2111 should be able to support the HW timestamp. You may use use the PROSet Adapter Configuration Utility (ACU) to set this to enabled.

https://www.intel.com/content/www/us/en/download/18293/intel-network-adapter-driver-for-windows-10.html

Kindly let us know if you have any other inquiries.

Best regards,

Faez.

Intel Customer Support

[lexa]

Hello Faez,

while it's great that at least not everybody at Intel has been laid off and that we finally have a reaction from Intel, the information you provide is outdated and not related to the OP's question.

Intel PROSet is not available for Windows 11 and neither Windows Server 2022 as it was discontinued by Intel.

The OP's question also was not related to enabling PTP hardware timestamping (this can easily be done via the standard Windows device manager properties dialog), but to the Intel drivers failing when a software program is using the GetInterfaceActiveTimestampCapabilities Win32 function: the return value is ERROR_BAD_DRIVER.

So please talk back again with the engineering team and ask them specifically regarding the Win32 function GetInterfaceActiveTimestampCapabilities and that it's failing with ERROR_BAD_DRIVER when an Intel NIC is used.

Additionally, what about i350?

Best regards

[Peterdoo]

Windows API support is not really suitable for PTP before Windows 11 / Server 2022. So, there is no real requirement for the drivers to support HW timestamping in the OS versions lower than Windows 11 / Server 2022.

Under Windows 11 / Server 2022 enabling HW timestamping can be done in the device properties on the Advanced tab. There is no need for Intel PROSet.

[Peterdoo]

Thank you for the reply. Unfortunately the link to the drivers that you have posted includes driver version 13.0.14.0 for the I210 and I211 which has been published in February 2022 and contains all the problems mentioned above:

- The function CaptureInterfaceHardwareCrossTimestamp returns the HardwareClockTimestamp value for the previous call of this function, which is a value from some time ago and makes this function unusable on Intel adapters at the moment. Looks like a double buffering problem.
- The function GetInterfaceActiveTimestampCapabilities does not work.
- The HardwareClockFrequencyHz reported in GetInterfaceSupportedTimestampCapabilities is off by about 0,5%-1% from the actual frequency. I don't know whether it can be reported more exactly or whether the oscillator on the adapter is so inaccurate.

If you say that hardware timestamping is only supported under Windows for I210 and I211 then obviously we have to live with that and use other manufacturers adapters for PTP functionality on the systems where I210 and I211 is not suitable.

However as has been reported, the hardware timestamping on I210 and I211 is not usable with the current driver. At least the three points above have to be corrected to make it usable. You have not addressed those at all in your reply.