Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support firmware loading #17

Open
lu-zero opened this issue Nov 20, 2021 · 0 comments
Open

Support firmware loading #17

lu-zero opened this issue Nov 20, 2021 · 0 comments
Labels
mdev-parity Feature present in busybox mdev

Comments

@lu-zero
Copy link
Collaborator

lu-zero commented Nov 20, 2021

  • look for FIRMWARE entries in the UEvent
  • On Add try to load the firmware according to linux/Documentation/firmware_class/README

mdev summarizes it this way:

/*
 * Firmware loading works like this:
 * - kernel sets FIRMWARE env var
 * - userspace checks /lib/firmware/$FIRMWARE
 * - userspace waits for /sys/$DEVPATH/loading to appear
 * - userspace writes "1" to /sys/$DEVPATH/loading
 * - userspace copies /lib/firmware/$FIRMWARE into /sys/$DEVPATH/data
 * - userspace writes "0" (worked) or "-1" (failed) to /sys/$DEVPATH/loading
 * - kernel loads firmware into device
 */
@lu-zero lu-zero added the mdev-parity Feature present in busybox mdev label Nov 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
mdev-parity Feature present in busybox mdev
Projects
None yet
Development

No branches or pull requests

1 participant