forked from labgrid-project/labgrid
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
driver/usbloader: rename RKUSBDriver to reflect rkdeveloptool usage
To interact with a Rockchip SoC in BootROM mode over USB, Rockchip offers the rkdeveloptool, which is among others already packaged in Debian. We currently support this via the RKUSBDriver, which binds to the RKUSBLoader resource, which currently lists a single VID/PID pair. Actually making use of this is where things get confusing: Labgrid will look up the rk-usb-loader key to find rkdeveloptool and then fall back to a binary named `rk-usb-loader`. To my knowledge, no one names their rkdeveloptool that way and `rk-usb-loader` has since become the name of the Rockchip USB loader distributed by barebox. On systems, like the LXA TAC, this is doubly confusing: There's a rk-usb-loader binary, which Labgrid would use by default, but it's not compatible with rkdeveloptool, supports only the RK35xx SoCs barebox supports and is currently not supported by Labgrid at all. Given that RKUSBLoader only supports a single SoC, our documentation is wrong (it references the unrelated barebox' rk-usb-loader) and that our usage of rkdeveloptool goes beyond the BootROM's USB protocol and additionally flashes persistent media by talking to a first stage usb_loader that's uploaded first, I think the best course of action is to rename both the driver and the tool key to reflect that rkdeveloptool is actually used. Signed-off-by: Ahmad Fatoum <[email protected]>
- Loading branch information
Showing
7 changed files
with
22 additions
and
17 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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