Re: USB-serial adapter suggestions needed

On Fri, Jan 12, 2024 at 01:45:04PM -0800, Mark Millard wrote:
> 
> So each of the signals result in a full
> 
> ucom_close: tp=. . .
> . . .
> ucom_cfg_close:
> 
> sequence?
Yes, that part seemed quite consistent. Here's an example

Jan 12 10:47:43 nemesis kernel: ucom_param: sc = 0xffffa00002466088
Jan 12 10:47:43 nemesis kernel: ucom_ioctl: cmd = 0x8004667e
Jan 12 10:47:43 nemesis kernel: ucom_ioctl: cmd = 0x8004667d
Jan 12 10:47:43 nemesis kernel: ucom_get_data: cnt=0
Jan 12 10:47:44 nemesis kernel: ucom_outwakeup: sc = 0xffffa00002466088
Jan 12 10:47:44 nemesis kernel: ucom_get_data: cnt=1
Jan 12 10:47:44 nemesis kernel: ucom_get_data: cnt=0
Jan 12 10:47:44 nemesis kernel: ucom_inwakeup: tp=0xffffa00001979800
Jan 12 10:57:36 nemesis kernel: ucom_close: tp=0xffffa00001979800
Jan 12 10:57:36 nemesis kernel: ucom_shutdown:
Jan 12 10:57:36 nemesis kernel: ucom_dtr: onoff = 0
Jan 12 10:57:36 nemesis kernel: ucom_line_state: on=0x00, off=0x01
Jan 12 10:57:36 nemesis kernel: ucom_rts: onoff = 1
Jan 12 10:57:36 nemesis kernel: ucom_line_state: on=0x02, off=0x00
Jan 12 10:57:36 nemesis kernel: ucom_cfg_close:
Jan 12 10:57:44 nemesis kernel: ucom_open: tp = 0xffffa00001979800
Jan 12 10:57:44 nemesis kernel: ucom_cfg_open:
Jan 12 10:57:44 nemesis kernel: ucom_dtr: onoff = 1
Jan 12 10:57:44 nemesis kernel: ucom_line_state: on=0x01, off=0x00

The lines before ucom_close... seemed to vary slightly in order but
not content. My method was crude, to say the least, however. I
just used vi to search a version of messages with all but
lines containing ucom_ stripped out. There was nary a twitch
in the lines following ucom_shutdown, some ordering changes
in the lines above. 

Thanks for writing,

bob prohaska
 




> If yes, that answers my question. Otherwise I'd like to 
> see the variations.
> 
> ===
> Mark Millard
> marklmi at yahoo.com
> 
>