summaryrefslogtreecommitdiffstats
path: root/firmware/export/config/creativezen.h
AgeCommit message (Collapse)AuthorFilesLines
2020-10-03imx233: Enable 96/192K playback for all imx233 targets that have roomSolomon Peachy1-2/+2
Change-Id: Ief00cc9243af3168f0c088520936137b64f3b581
2020-09-30audio: Add support for 192 and 176KHz playbackSolomon Peachy1-2/+2
* SAMPR_CAPS_ALL -> SAMPR_CAPS_ALL_48/96/192 * All targets claiming SAMPR_CAPS_ALL now get appropriate subset * No need to explicitly define HAVE_PLAY_FREQ * Rates that are a multiple of 44 or 48KHz can be used for playback Inspired by a patch by Roman Stolyarov, but substantially rewritten by myself. Change-Id: Iaca7363521b1cb9921e047ba1004d3cbe9c9c23e
2020-07-24[4/4] Remove HAVE_LCD_BITMAP, as it's now the only choice.Solomon Peachy1-2/+2
Note: I left behind lcd_bitmap in features.txt, because removing it would require considerable work in the manual and the translations. Change-Id: Ia8ca7761f610d9332a0d22a7d189775fb15ec88a
2020-07-24[3/4] Completely remove HWCODEC supportSolomon Peachy1-2/+2
'swcodec' is now always set (and recording_swcodec for recording-capable units) in feature.txt so the manual and language strings don't need to all be fixed up. Change-Id: Ib2c9d5d157af8d33653e2d4b4a12881b9aa6ddb0
2019-07-31Revert "cleanup: Remove HAVE_MULTIVOLUME from targets with HAVE_MULTIDRIVE"Solomon Peachy1-0/+1
This reverts commit a89bf68e889dd989e486b0a131618f69e5fc26c6. HAVE_MULTIVOLUME && HAVE_MULTIDRIVE implicitly means "allow 4 volumes per drive" whereas the normal MULTIDRIVE behavior is to only allow 1 volume per drive.
2019-07-30cleanup: Remove HAVE_MULTIVOLUME from targets with HAVE_MULTIDRIVESolomon Peachy1-1/+0
The latter always enables the former. There are no remaining HAVE_MULTIVOLUME users in-tree. Change-Id: I0f4fd03a6ffed5c0eb3fb5f916f671bd199f1c8e
2017-10-29Add boot data support to rockbox.William Wilgus1-0/+2
Bootdata is a special location in the Firmware marked by a magic header The bootloader is able to copy information to the firmware by locating this struct and passing data to the firmware when it is loaded but before it is actually executed Data is verified by a crc of the bootdata Change-Id: Ib3d78cc0c3a9d47d6fe73be4747a11b7ad6f0a9e
2015-01-08Get rid of USE_ROCKBOX_USBAmaury Pouly1-1/+0
Except for unfinished or experimental ports, it isthe case that USE_ROCKBOX_USB and HAVE_USBSTACK are both defined or both undefined. Furthermore, it is a leftover of some early developments on the USB stack and doesn't make sense anymore. Change-Id: Ic87a865b6bb4c7c9a8d45d1f0bb0f2fb536b8cad Reviewed-on: http://gerrit.rockbox.org/1091 Reviewed-by: Amaury Pouly <amaury.pouly@gmail.com>
2014-07-17zen/zenxfi/zenxfistyle/zenmozaic: implement plugin keymaps and enable pluginsAmaury Pouly1-1/+1
Plugins on the ZEN/ZEN X-Fi require to increase the plugin buffer size. Change-Id: If4651c87b402060faa24530985c6e871379c8ea1
2014-06-25zen/zenxfi: fix config file commentsAmaury Pouly1-2/+2
Change-Id: I7c9c73f749622ffc552638e84e5907a187087381
2014-06-24zen/zenxfi: switch lcd driver to 24-bit modeAmaury Pouly1-4/+2
Change-Id: I2c42f0e422130bcdaf1aaf92c7b56776752f4f64
2014-03-08zen(xfi): enable frequency scalingAmaury Pouly1-1/+1
With the lcd underflow code at work, it results in small flicker when switching frequency but it should be fine because it doesn't happen very often and I don't think there is a way to avoid it without disabling EMI frequency scaling. Change-Id: I458732d52bbf27cda2510c3836539db1fb24ea15
2014-03-03Implement lcd_get_dpi() for all bitmap targets.Thomas Martitz1-0/+2
DPI values are autogenerated from the resolution and collected display size values. These values are inserted as comments as well. Change-Id: Id03aedf9af18348f773dfce002805e480f6751e8
2014-02-10zen/bootloader: power down the LCD at the end of the bootloader if neededAmaury Pouly1-3/+3
On the ZEN, the LCD is fed continuously by the DMA and this refresh needs to be stop when the bootloader gives control to the firmware, otherwise the DMA will source data from invalid region and it might even lock-up if the new code touches the memory setup. Work around this by properly stopping the LCD driver: the bootloader assumes that if the target defines HAVE_LCD_ENABLE in bootloader build (which is unusual) then it needs to stop the LCD. Since stopping the LCD could produce funny screens, power down backlight which is expected to power down the LCD too, giving a nice black screen instead of some random pixels. Change-Id: I7ce5ba9bfd08e596907c4ff8f80feb189f0576ce
2013-10-26Forgot the config files for ZEN, ZEN Mozaic and ZEN X-FiAmaury Pouly1-0/+198
Change-Id: Id95d0078d7f4862e596d47ef1bdbfe75942c50fa
generated by cgit (git 2.34.1) at 2024-04-19 12:21:13 +0000