Skip to content

Conversation

@mmmspatz
Copy link

An endpoint address is made up of two nibbles. The upper nibble specifies
the endpoint direction, and the lower nibble is the endpoint number.

libusbpp currently treats endpoint numbers as unique, which is
problematic in the case of a bidirectional endpoint (eg addresses 0x04
and 0x84.)

Change the API to reference endpoints by address, not number.

An endpoint address is made up of two nibbles. The upper nibble specifies
the endpoint direction, and the lower nibble is the endpoint number.

libusbpp currently treats endpoint numbers as unique, which is
problematic in the case of a bidirectional endpoint (eg addresses 0x04
and 0x84.)

Change the API to reference endpoints by address, not number.
@mcuee
Copy link

mcuee commented Feb 11, 2023

In reality 0x04 and 0x84 are two different endpoint in the context of USB. The only bi-directional endpoint is the control endpoint (usually EP0).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants