d95d8c0fb1
A host that enumerates a device says nothing about it unless the whole of CONFIG_DEBUG_USB_INFO is on, and then it says a great deal else besides. The quietest case is the one that matters most: a device no class driver claims produces no output at all, so a user with an unsupported device sees exactly what a user with no device sees. Add CONFIG_USBHOST_ANNOUNCE, reporting each device once, in the shape a reader is likely to recognise from other systems: where it is, what it is, its vendor, product and release, and the maker, product and serial number it reports in its own string descriptors. Those cost a control transfer each, so they are read only where a report was asked for, and only once the device is addressed. The report is made after binding rather than from within it, because a composite device never reaches the class lookup: usbhost_composite() is tried first and binds it. Whether a driver claimed the device is tracked rather than read from the returned status, which the per interface loop sets to OK whatever happened. The port is given as the path from the root hub, and the path names the bus, because a device on the first port of a hub and one on the first port of a controller are otherwise reported identically. struct usbhost_roothubport_s gains that bus number for the purpose; a driver that does not set it reports zero, which is the only bus it has. Class codes are translated where a name is more use than a number, which includes the HID boot protocols, so a keyboard is reported as a keyboard. Default n, so no existing configuration changes. Assisted-by: Claude:claude-opus-5 Signed-off-by: Justin Hammond <justin@dynam.ac> |
||
|---|---|---|
| .github | ||
| arch | ||
| audio | ||
| binfmt | ||
| boards | ||
| cmake | ||
| crypto | ||
| Documentation | ||
| drivers | ||
| dummy | ||
| fs | ||
| graphics | ||
| include | ||
| libs | ||
| mm | ||
| net | ||
| openamp | ||
| pass1 | ||
| sched | ||
| syscall | ||
| tools | ||
| video | ||
| wireless | ||
| .asf.yaml | ||
| .codespell-ignore-lines | ||
| .codespellrc | ||
| .editorconfig | ||
| .gitignore | ||
| .gitmessage | ||
| .pre-commit-config.yaml | ||
| .yamllint | ||
| AUTHORS | ||
| CMakeLists.txt | ||
| CONTRIBUTING.md | ||
| INVIOLABLES.md | ||
| Kconfig | ||
| LICENSE | ||
| Makefile | ||
| NOTICE | ||
| README.md | ||
| ReleaseNotes | ||
Apache NuttX is a real-time operating system (RTOS) with an emphasis on standards compliance and small footprint. Scalable from 8-bit to 64-bit microcontroller environments, the primary governing standards in NuttX are POSIX and ANSI standards. Additional standard APIs from Unix and other common RTOSs (such as VxWorks) are adopted for functionality not available under these standards, or for functionality that is not appropriate for deeply-embedded environments (such as fork()).
For brevity, many parts of the documentation will refer to Apache NuttX as simply NuttX.
Getting Started
First time on NuttX? Read the Getting Started guide! If you don't have a board available, NuttX has its own simulator that you can run on terminal.
Documentation
You can find the current NuttX documentation on the Documentation Page.
Alternatively, you can build the documentation yourself by following the Documentation Build Instructions.
The old NuttX documentation is still available in the Apache wiki.
Supported Boards
NuttX supports a wide variety of platforms. See the full list on the Supported Platforms page.
Contributing
If you wish to contribute to the NuttX project, read the Contributing guidelines for information on Git usage, coding standard, workflow and the NuttX principles.
License
The code in this repository is under either the Apache 2 license, or a license compatible with the Apache 2 license. See the License Page for more information.