From nobody Fri Jan 12 22:14:43 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TBbS14hrBz56W4g for ; Fri, 12 Jan 2024 22:14:41 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TBbS11LMVz4lBK for ; Fri, 12 Jan 2024 22:14:41 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.17.1/8.15.2) with ESMTPS id 40CMEhAO017420 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 12 Jan 2024 14:14:44 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 40CMEhQN017419; Fri, 12 Jan 2024 14:14:43 -0800 (PST) (envelope-from fbsd) Date: Fri, 12 Jan 2024 14:14:43 -0800 From: bob prohaska To: Mark Millard Cc: freebsd-arm@freebsd.org Subject: Re: USB-serial adapter suggestions needed Message-ID: References: <041F74B4-3D44-4364-9EBD-9F21A4F3B313@yahoo.com> <902798B1-2B66-4ECD-BDAC-195C85066FE6@yahoo.com> <8B4C76B2-707E-4978-9CB3-5D547303A7E5@yahoo.com> <482FA770-89E8-42E8-945E-B662AD564AFE@yahoo.com> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4TBbS11LMVz4lBK X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US] 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 > >