RE: Request new serial name support for ubxtool and pygpsclient

[Kuo, Danny]

Hi Gerg and Frank,

 

Sorry the image not pass correctly, I resend the file status with text format,

 

New driver/serial name:

[root@NGSNEXHPN06 ~]# ls -l /dev/gnss*

crw-rw-rw- 1 root root 238, 0 Feb 24 07:00 /dev/gnss0

[root@NGSNEXHPN06 ~]#

[root@NGSNEXHPN06 ~]# file /dev/gnss0

/dev/gnss0: character special (238/0)

 

Original driver/serial name:

[root@NGSNEXHPN06 ~]# ls -l /dev/ttyGNSS*

crw-rw---- 1 root dialout 510, 0 Feb 24 07:21 /dev/ttyGNSS_5e00

[root@NGSNEXHPN06 ~]#

[root@NGSNEXHPN06 ~]# file /dev/ttyGNSS_5e00

/dev/ttyGNSS_5e00: character special (510/0)

 

 

BR

Sanny

From: Kuo, Danny
Sent: Friday, February 24, 2023 7:04 AM
To: Frank Nicholas <frank@nicholasfamilycentral.com>
Cc: gpsd-dev@nongnu.org
Subject: RE: Request new serial name support for ubxtool and pygpsclient

 

Hi Frank:

 

Thank for look into this issue, below compare two file difference, I add stty command output, let me know if it help.

 

New driver/serial name:

 

Original driver/serial name:

 

 

BR

Danny

 

From: Frank Nicholas <frank@nicholasfamilycentral.com>
Sent: Thursday, February 23, 2023 10:51 PM
To: Kuo, Danny <danny.kuo@intel.com>
Cc: gpsd-dev@nongnu.org
Subject: Re: Request new serial name support for ubxtool and pygpsclient

 

Hello,

 

How was the device file /dev/gnss0 created?  It looks like it does not have the correct device type, indicating it’s not a problem with the GPS apps.

 

Do a `ls -l /dev/tty*` & `ls -l /dev/gnss*`.  Compare the device types.

 

You might also do a `file /dev/tty*` & `file /dev/gnss*` to compare the device files.

 

Thanks,

Frank

 

On Feb 23, 2023, at 7:02 AM, Kuo, Danny <danny.kuo@intel.com> wrote:

 

Hi Team:

 

I am new to this community, sorry that my first email is about to request feature support to one of Intel NIC which build-in a GNSS module.

 

Intel NIC E810-XXVDA4T is for 5G Time Sync purpose, and one of the ITU-T spec is T-GM which need a precision time from satellite. This NIC build-in a u-Blox ZED-F9T controller.

 

The NIC driver originally use serial name /dev/ttyxx to identify GNSS serial interface, it is working fine with gpsd, stty, ubxtool and pygosclient.

 

After we change serial name to /dev/gnss0, the stty and ubxtool fail to open this device, and the pygpsclient fail to connect to this device.

The new serial name /dev/gnssx is going to upstream to RHEL 9.x with kernel 6.x, that is the reason Intel change driver to compliant with RHEL.

 

We think(not 100% sure) this issue is due to ubxtool and pygpsclient not support the new serial name(/dev/gnssx), we would like to know how to change gpsd/ubxtool/pygpsclient code to make it support /dev/gnssx.

Or, if the gpsd community can help to support the new serial interface /dev/gnssx that will be appreciated. 😊

 

See below error message.

<image003.png>

 

<image002.png>

 

please refer to below link for Intel NIC spec detail.

https://www.intel.com/content/www/us/en/products/sku/211608/intel-ethernet-network-adapter-e810xxvda4t/specifications.html

 

Thanks in advance for your help. 

If you need more information or a live demo, please let Intel know, we can arrange a meeting for further discussion.

 

Intel NEX NCNG

Danny Kuo