On Mon, Mar 06, 2017 at 03:52:26PM +0000, Rommel, Albrecht wrote: > There is a demand for changing PORT_DATA_SET and probably > CLOCK_DESCRIPTION while ptp4l is running.
First off, according to 1588 CLOCK_DESCRIPTION is GET only. There is no SET. Secondly, PORT_DATA_SET is a collection, and thus it also has no SET. The individual elements are set-able, but these are determined by the profile, and you don't go changing the profile suddenly. At least, I have never heard of use case for that. > The main reason is due to the circumstances involved for stopping > ptp4l, modifying the config file (possibly from remote!), restarting > ptp4l, and the likelihood of config file corruption. There is no issue changing a configuration file and restarting remotely. That is what SSH was invented for. Also, we *never* allow SET remotely, only via UDS. The PTP management mechanism has no authentication at all, and so we cannot allow it over the network. > Having a network API (TLVs) to modify attributes would be more > elegant and safe. If we want to complete the SET/GET TLVs for > pmc/ptp4l, who would you recommend to do this? It should be aligned > with the allowed GET/SET actions as defined in IEEE1588-2008, table > 40 - managementtld values. I'll consider patches that correctly implement SET actions from 1588. Thanks, Richard ------------------------------------------------------------------------------ Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition. http://sdm.link/oxford _______________________________________________ Linuxptp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
