PEAK-System Forum

Hello Michael,

great, thanks. The Mainboard we are considering is not embedded but its M2 slots definitely have PCIe.

Best regards,
Thomas

Hello Michael,

ok, thanks.

So what systems the PCAN-M.2 is designed for or typically used in?

Best regards,
Thomas

Hi Michael,

ok, thanks for your response.

But it is possible to operate in an M2 M-key slot on a motherboard, which is dedicated for NVMe drives that provides PCIe, right?

Regards,
Thomas

Is it possible to operate the PCAN-M.2 in an external M2 enclosure with Thunderbolt connection? If so, is it sufficient to have NVMe compatibility or are there other specifications to be taken into account? Are there any performance degradations (latency wise) to expect?

Hi Stéphane,

ok, thanks for clarifying. In that case, I understand even less why you don't allow your users to change the behavior with the deftsmode parameter. Changing parameters with the mainline driver is not allowed anyway.

Best regards,
Thomas

Hi Stéphane,

I am aware that time synchronization is quite complex. That is one of the reasons we want to make use of hardware timestamps.

I think I still do not understand fully. Does that mean, the cooked stamps were working up to 8.10.2 as "hardware timestamps"? As I said, we are using the ...

Hi Stéphane,

I still do not understand why it is not possible to default the driver to deftsmode=3 and still make it possible to change its behavior with the parameter. Could you please elaborate on this decision?

Best regards,
Thomas

Hi Stéphane,

thanks for the suggestion. I copied over

if (pf->flags & PCANFD_HWTIMESTAMP)
{
struct skb_shared_hwtstamps *hwts = skb_hwtstamps(skb);

// pqm->hwtv.ts_mode = PCANFD_OPT_HWTIMESTAMP_RAW;

/* cook the hw timestamp according to ts_mode */
pcan_sync_timestamps(dev, pqm);

hwts ...

Hello again,

I searched the forum a bit more and just found this post, suggesting the netdev should allow to change the timestamp behavior.

Best regards,
Thomas

Hello Stéphane,

thank you very much for your quick response.

I do not understand the reason why deftsmode is ignored. Isn't the reason for the parameters to override the default behavior? For example, parameters like fdirqcl are working. Could you please consider to change this behavior? For us ...