> -Original Message-
> From: Petr Machata [mailto:pe...@mellanox.com]
> Sent: Monday, June 10, 2019 9:42 AM
> To: Keller, Jacob E
> Cc: linuxptp-devel@lists.sourceforge.net
> Subject: Re: [PATCH] sk: Recognize HWTSTAMP_FILTER_SOME
>
>
> Keller, Jacob E writes:
>
> >> index
Keller, Jacob E writes:
>> index 93ba77a..416d784 100644
>> --- a/sk.c
>> +++ b/sk.c
>> @@ -105,7 +105,8 @@ static int hwts_init(int fd, const char *device, int
>> rx_filter,
>> if (cfg.tx_type != tx_type ||
>> (cfg.rx_filter != rx_filter &&
>> cfg.rx_filter !=
> -Original Message-
> From: Petr Machata [mailto:pe...@mellanox.com]
> Sent: Monday, June 10, 2019 7:09 AM
> To: linuxptp-devel@lists.sourceforge.net
> Subject: [Linuxptp-devel] [PATCH] sk: Recognize HWTSTAMP_FILTER_SOME
>
> struct hwtstamp_config.rx_filter passed to SIOCSHWTSTAMP can be
struct hwtstamp_config.rx_filter passed to SIOCSHWTSTAMP can be updated by
the kernel with the value of HWTSTAMP_FILTER_SOME. That indicates that all
requested packets will be timestamped, and some others as well.
Update hwts_init() to recognize this as a valid response, instead of
rejecting it
struct hwtstamp_config.rx_filter passed to SIOCSHWTSTAMP can be updated by
the kernel with the value of HWTSTAMP_FILTER_SOME. That indicates that all
requested packets will be timestamped, and some others as well.
Update hwts_init() to recognize this as a valid response, instead of
rejecting it
Petr Machata writes:
> @@ -105,7 +105,8 @@ static int hwts_init(int fd, const char *device, int
> rx_filter,
> if (cfg.tx_type != tx_type ||
> (cfg.rx_filter != rx_filter &&
>cfg.rx_filter != rx_filter2 &&
> - cfg.rx_filter != HWTSTAMP_FILTER_ALL)) {
> +
It seems like there are use cases for setting the PHC from another time
source (like a GPS), for example, when the node needs to be a grandmaster.
There is a discussion on this on the user mailing list (https://is.gd/qyYHDt
).
Has it been considered adding a chrony like refclock SOCK interface (
