summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2020-11-19rbutil: Convert ServerInfo to singleton.Dominik Riebeling7-31/+45
Change-Id: I29d94eb6bae084754e5e3f337c41de8354ba123c
2020-11-19rbutil: Rework server info data handling.Dominik Riebeling2-4/+0
Remove map that isn't used anymore. Change-Id: I771a98c9b64f3dac36e71041c566b89fbea51e06
2020-11-19Add libraries to native MIPS toolchain to enable bluetooth supportSolomon Peachy1-4/+73
libffi, zlib, glib, expat, and dbus Change-Id: I9453b3cabe91fd3dc992e065729d61d7e005091e
2020-11-19languages: convert recording_swcodec -> recordingSolomon Peachy47-506/+507
Change-Id: I481a53284d63457717f4a6524edc5b477f29a20a
2020-11-19Clean out some obsolete strings from the Russian translationSolomon Peachy1-299/+12
Change-Id: Ic0878ae5d8e5d12c803702f3c069a1d1a3a74ef8
2020-11-18hosted: Improve buffer underrun handling in the ALSA driverSolomon Peachy4-19/+66
* Bump internal mix buffer size by 4x, to 1K frames (matching ALSA period) * Handle an underrun that occurs when filling the audio buffer * Log underruns and make them available in the debug info Change-Id: I28d56dd35d88851fa167ad92368a5882937a758f
2020-11-18Minor additions to g#3035Moshe Piekarski1-30/+30
Change-Id: I6f518ccbca9834d738eb4a5621ddef638b335195
2020-11-18Manual: remove most HWCODEC artifactsMoshe Piekarski24-613/+451
This causes 3 changes in layout. 2 I can't track down and 1 is better this way. Change-Id: If4ad5e1d7431b4c2cbaaf9767d78139ef4e2dc44
2020-11-18configure: Add prompt for USB Serial into the advanced modeSolomon Peachy2-6/+10
And explicitly disable USB_ENABLE_SERIAL when HAVE_USBSTACK is not define Change-Id: Ieb4176b02a60eb1b9db81f0b8c69403898a76ca1
2020-11-17Update english-US languageSolomon Peachy1-16/+52
Change-Id: I0a20e76d2e5267eb15e85dac0cd1f524eafe0415
2020-11-17lang: Drop all deprecated strings, and rename LANG__NEVER to LANG_NEVERSolomon Peachy47-5248/+16
Change-Id: Ie1a1cb04ecb566b75d9884b98a8c4e37a4e8736f
2020-11-17lang: Make all swcodec &| lcd_bitmap strings default.Solomon Peachy49-35493/+21030
Change-Id: Id0a3282884c3e258c5b2f24b35aa7e618a8e8bbe
2020-11-17usb: increase the stack size.Solomon Peachy1-1/+1
It's not large enough on some targets. (this will be revisited when the USB insertion prompt stuff is moved out of the USB helper and over to the main thread) Change-Id: Iefed2cdf2fbb4ce92569fc5cacbdb479b7d24e61
2020-11-16Manual Bugfix SetWPSContextPluginWilliam Wilgus1-1/+2
Change-Id: Idf06c12ecbabbd6a1adb7ba9eaa6b183d3a0c289
2020-11-16fwpatcher: fix compile errors and warnings on modern LinuxJames Buren2-6/+6
Change-Id: I87b71654ce8669904cfb587cb0673a46455bcbd1
2020-11-16update fwpatcher and rbutil checksums for iriver h1x0/h300 V8 bootloaderJames Buren6-56/+56
Change-Id: Icf6bc96889fbe682832a99882c5d66c832ffb2f7
2020-11-16rockbox: fix iriver firmware validation for larger bootloadersJames Buren2-25/+103
It turns out the code for the firmware size validation was incorrectly using the total length of the firmware file to check if it was too big for the flash rom which caused it to incorrectly flag larger bootloaders as too big even though they would still fit. As it happens this situation can only really arise after mkboot has been run on the decoded firmware image. Because mkboot writes the actual binary size to the ESTFBINR header we will be using that to check if the firmware image is too large for the flash rom. Now because this information is embedded in the decrypted / encrypted region we have to collect it as the region is processed so the validation is also moved to after the data processing loop. Change-Id: I8bfead73812fe4e59f08fbbe8956790604dcb4e2
2020-11-16mkboot: fix the buffer size used for constructing the final firmware imageJames Buren1-1/+13
It was short by a fair number of bytes which could be reached when attempting to insert bootloaders near the maximum size of 64k. This ensures even the largest acceptable bootloader will not overflow the buffer. Change-Id: I8fbc92d4e3452192bf47104d7a32b49248eefc0e
2020-11-16Fix the fix, which managed to make things _worse_Solomon Peachy1-1/+1
Change-Id: I91b6bc71cf1d5c4cf06d839dfa783cb799756b77
2020-11-16Fix the red introduced in 9c68c69Solomon Peachy1-1/+1
Change-Id: I5f3e3ddd5bc11b8d58e5c05ec3bf7171537c016d
2020-11-16FS13257: Fix inconsistent defaults in the USB mode selectionSolomon Peachy4-4/+16
Change-Id: I44894d13f070313ad326ce68018556573e35aad9
2020-11-16fwpatcher: fix a few issues with the mksums.pl scriptJames Buren1-2/+2
First, the way it was invoking mkboot was no longer correct so it was not producing files used in the later commands. Second, support for the H300 1.31k firmware was added sometime ago but not to this script. Change-Id: I0e9c74a3b9f83ade8d01df0bebfe06f4d3b92ce4
2020-11-16iriver_flash: update valid bootloaders tableJames Buren2-6/+4
This removes all the pre-release bootloader of version 7 and replaces them with production releases of version 8. The pre-releases have their own problems and should be left behind as they were never officially released. Change-Id: If96531ba63cf4401d04133bda94735fe94ae4de1
2020-11-15rbutil: Rework server info data handling.Dominik Riebeling5-23/+21
Return status as int, not as string, and provide a separate function for converting to string. This allows to filter based on the actual status, not a (localized) status string, which is more robust. Fix a regression that made players with missing status value show up as retired. Change-Id: I15f83ae0df484199b1b3b5b95069db8b4d425987
2020-11-15rbutil: Fix style warnings.Dominik Riebeling1-4/+4
Change-Id: I1ddcff60488b2926206309c9ef62f5f9d330da33
2020-11-15rbutil: Rework server info data handling.Dominik Riebeling6-9/+14
Allow constructing release candidate URL from configuration the same way we construct the URL for releases. Note that the server path used does not exist, taken from old release candidate builds not available anymore. Change-Id: I7332f08df05ed39724b4900556aaa1f5e0ba463b
2020-11-15rbutil: Rework server info data handling.Dominik Riebeling2-9/+3
Allow extracting release candidate version even if no URL is present. Avoids a special case for version handling. Change-Id: If496d30059c3181899ab9337a35a07b39eaef52e
2020-11-15rbutil: Rework server info data handling.Dominik Riebeling4-160/+127
Don't create our own in-memory map with server data. Instead use the configuration file retrieved from the download server, and do the resolve / replacement on the fly. Simplifies things, and prepares for cleaner handling for different build types. Change-Id: Ifd027b21486e402fda3df9c2f7a30264651f733d
2020-11-15rbutil: Simplify manual download URL handling.Dominik Riebeling1-6/+1
- Don't construct the URL directly. The ServerInfo already has it, use that instead. - Don't manually construct the output filename. ZipInstaller will use the server filename automatically. Change-Id: Ib44616daf5efc95b238418b6e699ccd56c40b011
2020-11-15rbutil: Extend test for ServerInfo.Dominik Riebeling3-8/+78
- Further extend stubs, pull in less non-stubbed implementations. - Change some test URLs to make sure the code actually uses the correct ones. Change-Id: Iac1d683748b5834e61aa4974d1b893b77f90b517
2020-11-15rbutil: Extend test for ServerInfo.Dominik Riebeling3-12/+70
- Add tests for missing info values. - Extend stubs, pull in less non-stubbed implementations. Change-Id: I9a349f0eafe65811de37418c141fb581b6d9f59a
2020-11-15rbutil: Fix unit test.Dominik Riebeling1-1/+1
Change-Id: I0d1a33190d6590687d9e6eadd86a7ab8d8f877df
2020-11-15h1x0/h300: change when the hold switch and failsafe are usedJames Buren2-35/+28
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-15h1x0/h300: fix h300 bootloader hold switch checkJames Buren2-12/+21
This fixes an early boot bug on the h300 where hold_status is read before it has a chance to properly check whether the hold switch is even active. This was accomplished by porting over the method the h1x0 uses to perform the same check. Change-Id: I04679d82f65a2edcbee4be9a146437c3988040a2
2020-11-15h1x0/h300: consolidate a few code paths to logical equivalentsJames Buren2-16/+18
This saves a few bytes of precious space by consolidating paths where they can be combined with no change to the underlying algorithm. Change-Id: Ie6b7ead190a87d66fcbdcf2e351010bab751d952
2020-11-14Remove some SWCODEC artifactsMoshe Piekarski2-9/+3
Change-Id: I580522bc0ec3bc86c24400625d7d9cde2eea8fc8
2020-11-14iriver_flash: add macros to reduce the rom chip tableJames Buren1-0/+5
The table is now gated by the FLASH_SIZE macro as any given target will not have a known rom chip of a differing size than the FLASH_SIZE. This will reduce the resulting code a bit as well. Change-Id: I06a283f9f44118080a106e1bcd410e81e0a48d92
2020-11-14h1x0/h300: bring the two bootloaders more in syncJames Buren2-42/+268
The most major change here is the porting of the failsafe boot menu and eeprom settings support from the h1x0 bootloader to the h300 bootloader. This has been successfully tested already and indeed works about the same as it does on the h1x0 bootloader. The other major change is the addition of new code to both bootloaders that will retry the flash boot function after exitting disk mode. It still falls back to booting from disk if this either fails or is not configured to boot from flash. There were also various other modifications to bring the two closer in sync so there are fewer differences. Change-Id: I17a5724e03225b57e9d0071387294aa6cd025178
2020-11-14iriver_flash: do not let the backlight timeout while runningJames Buren1-0/+7
I discovered it was doing this on the H300 during longer operations and I freaked out at first. This disables this feature until the program is finished so as to not give anyone else an unnecessary fright while using it. It will also cut down on frivilous reports. Change-Id: I0db406912c7f71835576203a540aba8910afa849
2020-11-14rbutil: Rework player configuration.Dominik Riebeling14-88/+84
Rename config entries and remove now unnecessary default value handling. Change-Id: I5c60ef9769fc01f45f45290dafffb80c1962e674
2020-11-14rbutil: Rework player configuration.Dominik Riebeling14-114/+107
- Split internal configuration into player specific and common parts. Always require passing the player for player specific data instead of implicitly assuming the currently selected one; only use the currently selected one if the player name is explicitly passed as empty. - Similarly adjust handling of server info data; prepare for splitting into build type specific values so the naming becomes cleaner. Change-Id: I894e694f83bd9fe2d22ad46b3f8f7df3e2c68033
2020-11-14rbutil: Show HTTP error string on download failure.Dominik Riebeling1-2/+3
Also show the error string, which usually is more helpful than just showing the HTTP error code. Change-Id: I0652d240147c0f64a7a9ea58765af9eb197a03b1
2020-11-14h1x0/h300: clean up the bootloader source a bitJames Buren2-26/+10
First this removes most of the conditionals for the CPP as they are always true for the targets that use the bootloader source. Second this moves some global variable references around to reduce some redundancy in the h1x0 bootloader source. All of this is done to make it easier to compare the two bootloaders as they are very heavily related to each other. Change-Id: I7eb4a3106fb9fce6059797310d9e053a3d3ecf63
2020-11-14h1x0/h300: remove trailing whitespace from bootloadersJames Buren2-72/+72
Change-Id: I8f3bfbc8287c8f520894e0cd258066d4c7a02197
2020-11-14h300: enable usb charging for charge mode and disk modeJames Buren1-3/+15
This enables USB charging when the bootloader is in charge mode or disk mode. As a byproduct there is a small change in behavior where charge mode is all that is available if it is triggered by the USB cable insertion. Disk mode only becomes available if the user requests to continue the boot process by pressing the power button. It had to be done this way as there's no way to tell this early whether the user wants to simply charge or trigger disk mode as well. Change-Id: I32f29398b22a76e5e754efdc9beecae39dd122d5
2020-11-14rockbox: revise charger_inserted and power_input_present functionsJames Buren1-2/+12
This makes it so the thread cached variable is only read if building the regular firmware. For bootloaders the data is now read directly. This fixes the functions for bootloaders so they do not have to import the power management code just so these functions will work when in the bootloader. Change-Id: Ic425b02c08b48df7a11a6c19c022b0e1cb316a85
2020-11-13ibasso: Hopefully hack usb into building again.Solomon Peachy5-11/+14
Change-Id: I6f369d60319704ab4d2c18b80ba6e78902630790
2020-11-14synclist add method for setting selection colorWilliam Wilgus3-5/+79
Change-Id: I8c8761d92f4fc99f65d45098ee6e97800d3fe002
2020-11-13ibasso: Fix red introduced in 60f581eSolomon Peachy1-0/+1
Change-Id: I9095e9e9213dde252de836851b743001b9483a1b
2020-11-13usb: Add ability to prompt user about what to do upon usb insertionSolomon Peachy30-156/+224
v3: Add in config option v4: Bugfixes v5: Force a redraw upon exiting v6: keypress-in-chargeonly mode enables mass storage (and vice versa) v7: Fix bootloader builds v8: Update manual, and have bootloader respect keypresses v9: Change default to mass storage (ie no change in behavior) todo: * test-build dx50/dx90 * Switch from yes/no to proper menu? * prevent WPS progress bar from drawing over us Change-Id: I82e0ccb08497b7a5aa756ce77f1332ee963703a7 ... Change-Id: I7946cf240b18a4fa8ace5e25e1eb6e97b8b12d7c