From: Eli Cohen <echoline@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] new nusb/serial driver
Date: Sat, 13 Jun 2020 07:18:12 -0700 [thread overview]
Message-ID: <CAHwi9bwPQFW4wJnrLz9kv1cVvC3m5zHrjz39W05+9Ow_9UdPmg@mail.gmail.com> (raw)
In-Reply-To: <7400801DFC95785720AF0E41835DA9C9@felloff.net>
hi cinap,
I need to work on this driver more still, and look at the openbsd
driver closer. I'm not even using the interrupt yet but it seems to
work with this device.
what I meant was, epintr is found on the first USB interface but epin
and epout are on the second USB interface, but I can't just set nifcs
= 2 because it's only one serial port. there is one serial port using
*two* USB interfaces, one for the (unused) interrupt endpoint, and the
next one for in/out
- echoline
On Sat, Jun 13, 2020 at 7:04 AM <cinap_lenrek@felloff.net> wrote:
>
> what makes you think that?
>
> the only driver using interrupt endpoints is the prolific driver, and it is
> used for getting serial line status for a port. if you have multiple ports,
> on different interfaces how are you going to know which port the status
> is for?
>
> prolific driver only supports one iface. the previous code would *NOT* do
> multiple calls to findendpoints() because nifc == 1. and it would sysfatal()
> if findendpoints() failed..
>
> so my assumption is that the interrupt endpoint is indeed per interface.
>
> does this make sense?
>
> --
> cinap
next prev parent reply other threads:[~2020-06-13 14:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 7:03 Eli Cohen
2020-06-11 7:17 ` [9front] " Alex Musolino
2020-06-11 7:19 ` Eli Cohen
2020-06-11 7:29 ` Alex Musolino
2020-06-11 7:36 ` Eli Cohen
2020-06-11 7:57 ` Eli Cohen
2020-06-11 12:15 ` cinap_lenrek
2020-06-11 14:08 ` Eli Cohen
2020-06-11 17:10 ` cinap_lenrek
2020-06-12 1:28 ` Eli Cohen
2020-06-12 18:02 ` cinap_lenrek
2020-06-12 22:15 ` Eli Cohen
2020-06-13 14:03 ` cinap_lenrek
2020-06-13 14:18 ` Eli Cohen [this message]
2020-06-13 15:37 ` cinap_lenrek
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=CAHwi9bwPQFW4wJnrLz9kv1cVvC3m5zHrjz39W05+9Ow_9UdPmg@mail.gmail.com \
--to=echoline@gmail.com \
--cc=9front@9front.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).