Repository navigation
Conversation
aaaldo
changed the title
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This requests PID 0x1209:0xBC0C for Brick Controller, an open-source NextUI pak
(GPL-3.0-only) that turns a TrimUI Brick or Brick Pro into a Bluetooth and wired
USB HID gamepad.
Source: https://github.com/aaaldo/brick-controller
License: GPL-3.0-only (LICENSE at repository root)
USB interface: a generic PC HID gamepad exposed through the bottom USB-C device
port using FunctionFS; descriptors and report handling are in the public source.
The project is software-only: it does not ship a custom PCB. The USB identity is
part of the released pak and must be stable for every user, so host driver
caching, support and the "no host driver" promise behave consistently. Asking
each end user to request a PID would be impractical and would create collisions.
One PID is requested; the Bluetooth profiles use emulated console identities and
are not covered by this request.
Development builds currently use the official pid.codes test PID 0x1209:0x0002.
The assigned PID 0xBC0C will replace it before the first release archive.