linux-kernel - R: R: R: R: [PATCH v1] serial: 8250

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <44e270c8097c4351a92885fc21793f8d@asem.it>
Date:   Wed, 16 Dec 2020 09:44:08 +0000
From:   Flavio Suligoi <f.suligoi@...m.it>
To:     "Ji-Ze Hong (Peter Hong)" <hpeter@...il.com>
CC:     Jiri Slaby <jirislaby@...nel.org>,
        "Gustavo A . R . Silva" <gustavoars@...nel.org>,
        "linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: R: R: R: R: [PATCH v1] serial: 8250_fintek: Print Fintek chip name

Hi Peter,

> >>>
> >>> dmesg| grep ttyS
> >>
> >> But as they work the same, why does it matter?
> >
> > Yes you are right, by the user point of view, they are the same.
> >
> >>
> >> Userspace should not care here.  Isn't there some other id you can
> >> read/query for a hardware database tool to determine this?
> 
> 
> As Greg mentions, The userspace don't care what IC they are using.
> We can use Linux RS485 API to control or check the serial port.
> 
> https://www.kernel.org/doc/html/latest/driver-api/serial/serial-rs485.html

Yes, right! 
Thanks for your info!

> 
> --
> With Best Regards,
> Peter Hong

Best regards,
Flavio