Hi,
Le samedi 24 septembre 2016 à 18:01 -0700, Steve Rae a écrit :
> On Aug 25, 2016 01:30, "Paul Kocialkowski" wrote:
> > Le mercredi 24 août 2016 à 16:52 -0700, Steve Rae a écrit :
> > > So, I wanted to:
> > > (1) simplify this to not depend on any env variable, and not depend on
> > > the CONF
On Aug 25, 2016 01:30, "Paul Kocialkowski" wrote:
>
> Le mercredi 24 août 2016 à 16:52 -0700, Steve Rae a écrit :
> > So, I wanted to:
> > (1) simplify this to not depend on any env variable, and not depend on
> > the CONFIG_BOOTCOMMAND (can this be accidentally wiped out in the
> > environment?)
Le mercredi 24 août 2016 à 16:52 -0700, Steve Rae a écrit :
> So, I wanted to:
> (1) simplify this to not depend on any env variable, and not depend on
> the CONFIG_BOOTCOMMAND (can this be accidentally wiped out in the
> environment?)
I'm not sure it really simplifies much. fastboot is a boot com
Correct, with the current implementation, I think that you have the
only solution...
(1) add code during the startup sequence to test that rebooting into
fastboot is desired (as done in the misc_init_r functions that you
described)
(2) once this has been detected, then write an env variable (as don
Hi,
Le mardi 23 août 2016 à 16:38 -0700, Steve Rae a écrit :
> The "fastboot reboot-bootloader" command is defined to
> re-enter into fastboot mode after rebooting into the
> bootloader.
>
> There is current support for setting the reset flag
> via the __weak fb_set_reboot_flag() function.
>
> T
The "fastboot reboot-bootloader" command is defined to
re-enter into fastboot mode after rebooting into the
bootloader.
There is current support for setting the reset flag
via the __weak fb_set_reboot_flag() function.
This commit adds a generic handler to implement code
which could launch fastboo
6 matches
Mail list logo
