apps/system USB Functional Partitioning

Open
#322 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
c
Domain
operating-systems

Research direction

Start by reviewing usbmsc_configure, usbmsc_bindlun, and usbmsc_exportluns, along with their callers in apps/system/usbmsc and apps/system/composite. Compare them with the existing BOARDIOC_USBDEV_CONTROL boardctl() changes. Done means the listed helper applications no longer call these operating-system functions directly and remain usable in kernel or protected builds.

Written by the indexing model from the issue text.

Description

Area: modularity

Several of the USB device helper applications in apps/system violate OS/application partitioning and will fail on a kernel or protected build. Many of these have been fixed by adding the BOARDIOC_USBDEV_CONTROL boardctl() command. But there are still issues.

These functions still call directly into operating system functions:

  • usbmsc_configure - Called from apps/system/usbmsc and apps/system/composite
  • usbmsc_bindlun - Called from apps/system/usbmsc
  • usbmsc_exportluns - Called from apps/system/usbmsc.
Dominant language
C
Stars
465
Forks
782
Avg merge
3d 11h
Merged PRs (30d)
44

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/nuttx-apps

All issues in apache/nuttx-apps

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.