Skip to content

functions: parse options with getopts

A Reform user just sent me their /boot to debug and it contained the path /boot/dtbs/--verbose/amlogic. Turns out that the user tried to get more output by running flash-kernel with --verbose and flash-kernel interprets --verbose as kvers...

Can we have a proper argument parser with proper error messages if flash-kernel is used wrongly?

Merge request reports

Loading