lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 23 Jun 2022 13:39:35 +0000 From: "Kolacinski, Karol" <karol.kolacinski@...el.com> To: Jakub Kicinski <kuba@...nel.org> CC: "davem@...emloft.net" <davem@...emloft.net>, "pabeni@...hat.com" <pabeni@...hat.com>, "edumazet@...gle.com" <edumazet@...gle.com>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "richardcochran@...il.com" <richardcochran@...il.com>, "G, GurucharanX" <gurucharanx.g@...el.com>, "Nguyen, Anthony L" <anthony.l.nguyen@...el.com> Subject: Re: [PATCH net-next 3/3] ice: add write functionality for GNSS TTY On Mon, 23 May 2022 19:58 +0000 Jakub Kicinski wrote: > I meant discovered at the uAPI level. Imagine I plug in a shiny E810T > with a GNSS receiver into a box, the PRSNT_N bit is set and the driver > registered the ttys. How do I find the GNSS under /dev ? If the module is physically present, driver creates 2 TTYs for each supported device in /dev, ttyGNSS_<device>:<function>_0 and _1. First one (_0) is RW and the second one is RO. The protocol of write commands is dependent on the GNSS module as the driver writes raw bytes from the TTY to the GNSS i2c. I added this to Documentation/. Thanks, Karol
Powered by blists - more mailing lists