raspi: load USB classes from disk#799
Open
bsek wants to merge 2 commits into
Open
Conversation
BSP rom no longer bakes USB/hid, USB/hub, USB/bootmouse, USB/bootkeyboard or USB/massstorage. AddUSBClasses in Startup-Sequence picks them up from SYS:Classes/USB once DOS comes up. usbromstartup trimmed to just register usb2otg.device.
Member
|
This change prevents older PI's from starting boot on sdcard, but continuing from a USB device. |
USB-MSD boot needs hub.class + massstorage.class available before Startup-Sequence runs (which is where AddUSBClasses loads the disk-side classes). Reintroduce ROM-side registration and class scan for those two, plus the mass-storage boot delay. HID classes (hid, bootmouse, bootkeyboard) remain disk-loaded.
Contributor
Author
Good point — I've put hub.class and massstorage.class back into the ROM so usb-msd boot still works |
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
2 participants
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.
Device binding now happens during execution of startup-sequence.