diff options
| author | 3gg <3gg@shellblade.net> | 2026-03-06 13:30:59 -0800 |
|---|---|---|
| committer | 3gg <3gg@shellblade.net> | 2026-03-06 13:30:59 -0800 |
| commit | 30f41c02aec763d32e62351452da9ef582bc3472 (patch) | |
| tree | 6bec3f65bfdcbf7f1a631da21a6d613bef5db2fa /contrib/SDL-3.2.8/src/hidapi/netbsd/README.md | |
| parent | 452ff21ca02e315c64ceeb3f21c1ea357aeb1bc8 (diff) | |
Move contrib libraries to contrib repo
Diffstat (limited to 'contrib/SDL-3.2.8/src/hidapi/netbsd/README.md')
| -rw-r--r-- | contrib/SDL-3.2.8/src/hidapi/netbsd/README.md | 29 |
1 files changed, 0 insertions, 29 deletions
diff --git a/contrib/SDL-3.2.8/src/hidapi/netbsd/README.md b/contrib/SDL-3.2.8/src/hidapi/netbsd/README.md deleted file mode 100644 index f1b12a0..0000000 --- a/contrib/SDL-3.2.8/src/hidapi/netbsd/README.md +++ /dev/null | |||
| @@ -1,29 +0,0 @@ | |||
| 1 | Implementation Notes | ||
| 2 | -------------------- | ||
| 3 | NetBSD maps every `uhidev` device to one or more `uhid` | ||
| 4 | devices. Each `uhid` device only supports one report ID. | ||
| 5 | The parent device `uhidev` creates one `uhid` device per | ||
| 6 | report ID found in the hardware's report descriptor. | ||
| 7 | |||
| 8 | In the event there are no report ID(s) found within the | ||
| 9 | report descriptor, only one `uhid` device with a report ID | ||
| 10 | of `0` is created. | ||
| 11 | |||
| 12 | In order to remain compatible with existing `hidapi` APIs, | ||
| 13 | all the `uhid` devices created by the parent `uhidev` device | ||
| 14 | must be opened under the same `hid_device` instance to ensure | ||
| 15 | that we can route reports to their appropriate `uhid` device. | ||
| 16 | |||
| 17 | Internally the `uhid` driver will insert the report ID as | ||
| 18 | needed so we must also omit the report ID in any situation | ||
| 19 | where the `hidapi` API expects it to be included in the | ||
| 20 | report data stream. | ||
| 21 | |||
| 22 | Given the design of `uhid`, it must be augmented with extra | ||
| 23 | platform specific APIs to ensure that the exact relationship | ||
| 24 | between `uhidev` devices and `uhid` devices can be determined. | ||
| 25 | |||
| 26 | The NetBSD implementation does this via the `drvctl` kernel | ||
| 27 | driver. At present there is no known way to do this on OpenBSD | ||
| 28 | for a `uhid` implementation to be at the same level as the | ||
| 29 | NetBSD one. | ||
