James Buren 1bc68d5ad7 h1x0/h300: change when the hold switch and failsafe are used ... After reviewing the code awhile I realized that the failsafe and hold switch have no impact on the boot process when the usb or charger is connected. That makes no real sense to me. If these are connected then neither will be used at all. The boot process will never revisit it either once those other modes end and resume the boot process. It will just continue to try to boot from disk as if these emergency settings never existed. I have decided it makes more sense for them to be evaluated once the higher priority charge and disk mode have finished their roles. Given how the code was originally written it seems to be they were not intended to run prior to these at the very least since the logical conditions preclude that possibility as they include the inverse of the conditions that trigger the charge and disk modes. Change-Id: I0531c97474572c573178f480c239c3c1659f9653		2020-11-15 11:01:53 +00:00
..
bootloader.make
common.c
common.h
creativezvm.c
fat32format.c
format.c
format.h
gigabeat-s.c
gigabeat.c
iaudio_coldfire.c
imx233.c
ipod.c
ipod6g.c
ipodnano2g.c
iriver_h1x0.c	h1x0/h300: change when the hold switch and failsafe are used	2020-11-15 11:01:53 +00:00
iriver_h300.c	h1x0/h300: change when the hold switch and failsafe are used	2020-11-15 11:01:53 +00:00
lyre_proto1.c
main-e200r-installer.c
main-pp.c
main-ppsansawipe.c
Makefile
meizu_m3.c
meizu_m6sl.c
meizu_m6sp.c
mini2440.c
mpio_hd200_hd300.c
mrobe500.c
nwz_linux.c
ondavx747.c
rk27xx.c
rocker_linux.c
samsung_yps3.c
sansa_as3525.c
sansaconnect.c
sansaview.c
show_logo.c
snprintf.c
SOURCES
telechips.c
tpj1022.c
xduoox3.c