mirror of
https://github.com/Rockbox/rockbox.git
synced 2026-07-10 13:29:52 -04:00
383e227671
Enable HAVE_LCD_FLIP for the Clip Zip and implement lcd_set_flip() in the LCD driver, making the Display -> Flip Display setting work. This lets the player be used upside down, e.g. clipped to clothing with the control buttons pointing up and screen on the bottom. Defining HAVE_LCD_FLIP also activates the existing button remap in button_flip() (firmware/drivers/button.c) for this target: while the display is flipped, LEFT/RIGHT, UP/DOWN and the volume keys are all swapped to match the new orientation, so the whole device is usable upside down, not just readable. The flip is done in hardware by reversing the controller's GRAM write direction and mirroring the write window in lcd_setup_rect, so partial updates keep working and there is no per-frame cost. Both panel variants are handled: the type 0 WiseChip/SEPS114A via MEMORY_WRITE/READ (1Dh, 0x02), and the type 1 Visionox/LD7134 via the Graphic RAM Writing Direction register (05h, 0x03). The direction register is written in lcd_enable(), so it is set while the panel is powered and is re-applied after display standby; lcd_set_flip() cycles the panel off and on so a change to the setting takes effect immediately. For the simulator, which has no real LCD controller, lcd_set_flip() is implemented in the SDL LCD driver (lcd-bitmap.c) as a software mirror of the framebuffer, so the flip is visible in theme previews; the generic uisimulator stub is guarded out when HAVE_LCD_FLIP is defined. Tested on real type 1 / LD7134 hardware in both orientations: display content, button remapping and album art are all correct, and test_fps shows partial updates run at full speed when flipped (1/4 frame 325 fps, matching the non-flipped rate). The type 0 / SEPS114A path uses the same approach; the 0x02 direction value was confirmed to flip a type 0 panel by William Wilgus during review. Change-Id: I99ef13949102b344826e72d1d90c71e2271448a6 |
||
|---|---|---|
| android | ||
| apps | ||
| backdrops | ||
| bootloader | ||
| docs | ||
| firmware | ||
| fonts | ||
| icons | ||
| lib | ||
| manual | ||
| packaging | ||
| tools | ||
| uisimulator | ||
| utils | ||
| wps | ||
| .gitattributes | ||
| .gitignore | ||
| .gitreview | ||
__________ __ ___.
Open \______ \ ____ ____ | | _\_ |__ _______ ___
Source | _// _ \_/ ___\| |/ /| __ \ / _ \ \/ /
Jukebox | | ( <_> ) \___| < | \_\ ( <_> > < <
Firmware |____|_ /\____/ \___ >__|_ \|___ /\____/__/\_ \
\/ \/ \/ \/ \/
Build Your Own Rockbox
1. Clone 'rockbox' from git (or extract a downloaded archive).
$ git clone git://git.rockbox.org/rockbox
or
$ tar xJf rockbox.tar.xz
2. Create a build directory, preferably in the same directory as the firmware/
and apps/ directories. This is where all generated files will be written.
$ cd rockbox
$ mkdir build
$ cd build
3. Make sure you have mips/m68k/arm-elf-gcc and siblings in the PATH. Make sure
that you have 'perl' in your PATH too. Your gcc cross compiler needs to be
a particular version depending on what player you are compiling for. These
can be generated using the rockboxdev.sh script in the /tools/ folder of the
source.
$ which arm-elf-eabi-gcc
$ which perl
4. In your build directory, run the 'tools/configure' script and enter what
target you want to build for and if you want a debug version or not (and a
few more questions). It'll prompt you. The debug version is for making a
gdb version out of it. It is only useful if you run gdb towards your target
Archos.
$ ../tools/configure
5. *ploink*. Now you have got a Makefile generated for you.
6. Run 'make' and soon the necessary pieces from the firmware and the apps
directories have been compiled, linked and scrambled for you.
$ make
$ make zip
7. unzip the rockbox.zip on your music player, reboot it and
*smile*.
If you want to build for more than one target, just create several build
directories and create a setup for each target:
$ mkdir build-fuzeplus
$ cd build-fuzeplus
$ ../tools/configure
$ mkdir build-xduoox3
$ cd build-xduoox3
$ ../tools/configure
Questions anyone? Ask on the mailing list or on IRC. We'll be happy to help you!