> >>> Simply pressing the volume up button on boot will expose the eMMC drive as a USB mass storage device, refer to https://github.com/Tow-Boot/Tow-Boot/pull/67 for details about the UX design.
> >> Unless you mean something else by "USB recovery".
> > Yes, I do, the rockchip recovery doesn't expose mass storage, that
> > must be a tow-boot thing, hence why I discounted that. The rockchip
> > recovery isn't dependent on software.
> What is "Rockchip recovery"? Do you mean this:
> https://github.com/rockchip-linux/recovery ? I think that's some sort of
> "Android recovery" thing? How is that relevant to Fedora? Why would you
> want some Androidism rather than Tow Boot's USB mass storage mode?
It runs from MASKROM so it's low level recovery, it's a means of
recovering the firmware to recover bricked devices, the OS is
> >> What will be the UI for that? It will need an on screen keyboard to be
> >> usable for mobile devices. Maybe an OSK for Plymouth could be reused?
> > Out of scope for the work we're doing for IoT/Edge, the OSK is
> > specific for Mobility so it's something the mobility project will need
> > to deal with as IoT doesn't have that requirement so it's not
> > something we've got the resources to deal with.
> So I guess this is a CLI tool that reads the password from stdin? If so
> it should be easy enough for an OSK to output to it.
arm mailing list -- firstname.lastname@example.org
To unsubscribe send an email to email@example.com
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://firstname.lastname@example.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure