From: Johan Hovold <johan@kernel.org> To: Andy KN4UCL <kn4ucl@gmail.com> Cc: Johan Hovold <johan@kernel.org>, "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org> Subject: Re: Edgeport/4 Compatibility Re: your mail Date: Fri, 18 Sep 2020 16:36:16 +0200 Message-ID: <20200918143616.GB21896@localhost> (raw) In-Reply-To: <CA+H6KCm1YJ_-X6D61ujqWZDJzTyMBGKCR7W07QpWz9J6CSEwVA@mail.gmail.com> On Fri, Sep 18, 2020 at 06:54:17AM -0400, Andy KN4UCL wrote: > Hello Johan - resending without disclaimer :-) Thanks. Also try sending without HTML so that your messages reach the mailing lists (e.g. gmail's plaintext option). > I emailed Greg and via automated email indicated I should post my > question here. I've added linux-usb on CC as well. > I am trying to get some legacy EdgePort/4 and 8 devices to work on > Linux using Raspberry Pi OS. > > I notice in the kernel.org notes, compatibility with Edgeport seems to > be a good possibility. > > Can you advise? I get "cannot send clear loopback command" messages > in dmesg and these seem to be directly from the driver code I found > while googling. I assume these errors prevent the serial connection > from starting up. Devices seem to behave fine under Windows 10 (if > that's any kind of validation.) First, what are the VID and PIDs for these devices? Perhaps you can include the full output of "lsusb -v" for both types as well for completeness. > I do not have any problems with several Keyspan USA-49W devices which > are also referenced in the Compatibility section in the notes, so I > think my Linux machine is good. > > Apologies - I am not a Linux expert, just an end user. > > Any guidance or tips would be appreciated! > > Thanks in advance Johan
prev parent reply index Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-03 17:36 Barnett, Andy 2020-09-18 7:56 ` your mail Johan Hovold [not found] ` <CA+H6KCm1YJ_-X6D61ujqWZDJzTyMBGKCR7W07QpWz9J6CSEwVA@mail.gmail.com> 2020-09-18 14:36 ` Johan Hovold [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20200918143616.GB21896@localhost \ --to=johan@kernel.org \ --cc=kn4ucl@gmail.com \ --cc=linux-serial@vger.kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Linux-Serial Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-serial/0 linux-serial/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-serial linux-serial/ https://lore.kernel.org/linux-serial \ linux-serial@vger.kernel.org public-inbox-index linux-serial Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-serial AGPL code for this site: git clone https://public-inbox.org/public-inbox.git