[Kernel-packages] [Bug 1938626] Re: PPS API broken

2021-08-13 Thread Jim Pennino
I have verified the kernel pps_api only looks at CD by building a patch cable to map the PPS signal into the CD pin and now all the pps_api calls work as expected. It is still my position that the kernel pps_api should look at all commonly used control lines for PPS just like the pps-tools

[Kernel-packages] [Bug 1938626] Re: PPS API broken

2021-08-10 Thread Jim Pennino
According to linux/drivers/pps/clients/Kconfig config PPS_CLIENT_LDISC tristate "PPS line discipline" depends on TTY help If you say yes here you get support for a PPS source connected with the CD (Carrier Detect) pin of your serial port. If this is

[Kernel-packages] [Bug 1938626] Re: PPS API broken

2021-08-09 Thread Jim Pennino
A possible cause for this bug has occurred to me, but I wouldn't know where in the kernel code to check for this. Note: When I talk about a control line, I am using the DTE, i.e computer, end connector reference. In years past there was no standardization for which line on a serial port carried

[Kernel-packages] [Bug 1938626] Re: PPS API broken

2021-08-06 Thread Jim Pennino
I have rebooted with the oldest installed kernel, 5.4.0-54, and it too has the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938626 Title: PPS API broken Status in linux package

Re: [Kernel-packages] [Bug 1938626] Re: PPS API broken

2021-08-04 Thread Jim Pennino
I had been running with a USB GPS for years and recently purchased a GOOD GNSS device, so I have not had anything on this machine that accesses the pps_api until a few days ago. FYI I have a Raspberry Pi with Ubuntu where the pps_api works with raspberrypi-kernel 1:1.2010727-1 if that is of any

[Kernel-packages] [Bug 1938626] Re: PPS API broken

2021-08-04 Thread Kleber Sacilotto de Souza
Hello Jim, Did it work before with your system and got broken after a kernel update? If yes, would you be able to identify the kernel version which was working before? If you didn't run this use case before, would you be able to boot with an older kernel version and check whether it works?