From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from duke.felloff.net ([216.126.196.34]) by ewsd; Sat Jun 13 10:03:39 EDT 2020
Message-ID: <7400801DFC95785720AF0E41835DA9C9@felloff.net>
Date: Sat, 13 Jun 2020 16:03:19 +0200
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] new nusb/serial driver
In-Reply-To: <CAHwi9bzN2O1BwjXL3i2RtrhWzyuRSLcAJ2X1dcAHwcwzb9ZLzw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: extended metadata app-based lifecycle-scale hosting-aware API-scale control 

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